The tools for raidN (mdadm and friends) don't seem to compile with klibc. Has anyone tackled that, lvm or evms yet in a klibc-based initramfs, or do you usually include uclibc or something when it comes time to get fancy (also, looking ahead to crypto-root and such) Tks, Jeff Bailey
Jeff Bailey wrote:> The tools for raidN (mdadm and friends) don't seem to compile with > klibc. Has anyone tackled that, lvm or evms yet in a klibc-based > initramfs, or do you usually include uclibc or something when it comes > time to get fancy (also, looking ahead to crypto-root and such)Haven't looked at those particular ones myself. Don't think any of them should be inherently hard, though. -hpa
Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://www.vas.nu/pipermail/klibc/attachments/20050805/85a17f30/attachment.bin
Martin Schlemmer wrote:> > I ported dmraid, and also an older version of device-mapper. The dmraid > was accepted upstream, but I have heard no word from the device-mapper > list. I have plans for doing lvm/evms and mdadm, but as of yet have not > gotten around to it. > > I also have klibc.m4 attached with I used with both dmraid and > device-mapper (and also install with our klibc package for Gentoo). I > would appreciate comments, and if Peter might accept in for inclusion in > a contrib/m4 directory for klibc? >Presumably contrib/autoconf or just plain autoconf might make more sense. Agreed this would be good to include. -hpa