Jeff Garzik <jgarzik@pobox.com> wrote:
Too big to post,
http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.5-rc1-klibc1.patch.bz2 or bk://kernel.bkbits.net/jgarzik/klibc-2.5
IIRC, this is: my update of Bryan O'Sullivan's update of Greg KH's update of my merge of hpa's and viro's hacking :)
WRT overall klibc merge: when it can do md RAID autorun, it's mergeable. And didn't somebody write a tiny mdctl program...
It's so long since klibc was discussed (ie: more than five minutes ago) that I forget the reasons why it should be delivered via the kernel tree.
Remind me please?
Several reasons. The big one in my mind is, it will be delivering pieces without which the kernel will not boot, so you really really want to keep that software in sync with the latest kernel... at least until all the details are worked out. Otherwise version skew will as we remove code from the kernel and move it to userspace will be painful -- users would be rebuilding their external klibc trees just about every day, as code was moved from kernel to early-userspace.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
