-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Alexander E. Patrakov wrote: > I wrote: >> Bryan Kadzban wrote: >> >>> Anything else that it should support? >> >> 1) Some users may want to use EVMS instead of LVM2. The packages >> conflict, but on-disk formats are the same. Unfortunately, I am not >> an EVMS specialist (and it is not on the CD), so no immediate help >> is available.
Well, my impression of EVMS is that it's just a different toolkit on top of the LVM2 kernel driver (or at least, that's all it is *now*; it used to be a different driver too). I'd be inclined to punt it, at least for now. (The problem with that is, I bet the metadata is different, so it's not like we can say "oh just use the LVM2 stuff". That'd be a problem.) >> 2) Software RAID (with the help of mdadm), even if the disk driver >> is a module (so that in-kernel autoassembly doesn't work). LVM2 on >> RAID. OK, I almost have LVM2-on-mdadm-RAID working. I just used different partitions on a single qemu disk for testing -- even though that's specifically not recommended (because if a disk dies, you lose at least 2 partitions), that doesn't apply in qemu, and I was just testing anyway. I created 5 partitions (2 for a RAID1 for /boot, and 3 for a RAID5 to hold an LVM PV that would hold / and swap). I named the arrays "boot" and "main", so I got /dev/md/boot and /dev/md/main devices. (Along with /dev/md_boot and /dev/md_main, but I didn't use those.) The initramfs works fine (as long as I use v1.0 metadata, at the end of the disk) -- it assembles the RAID1 (although it isn't needed) and RAID5 just fine, and with a few tweaks to /etc/lvm/lvm.conf (filtering out the non-RAID devices), vgchange -ay finds everything on the RAID devices as well. The one sticking point is the same sticking point I had with dmraid -- how do you get the /dev/md/* named device nodes to be recreated once the initramfs is finished, from the system bootscripts? Device-mapper has "dmsetup mknodes", and LVM2 has "vgmknodes", but I can't find anything similar in mdadm. The filter that I have makes the LVM scan work fine (since the system does create /dev/md126 and /dev/md127 devices), but I'd rather have it create the names, if possible. I suppose the boot script could manually create them, using mdadm - --detail and some shell magic to generate the name. If there's no pre-built way to do it, I'll start hacking on that. >> 3) NFS root (including v4, which is not on the CD). I have no idea what'd even be required there, but I'll start doing some reading after I get the md and crypto stuff working. > 4) Encrypted root (with dm-crypt, cryptoloop, or loop-aes). Note that > this requires "loadkeys" and keymaps in the initramfs. Also, I have > never tried this, but the 6.2-5 CD (not 6.3-X!) includes support for > loop-aes. loadkeys/keymaps -- I assume that's just while typing in the passphrase, right? I'll see what I can find on this after md is fixed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGmmj3S5vET1Wea5wRAx5rAJ0ZUELhO/6XgnV3oPLJrLl7EpAMRgCgkmJ6 EF5cj7Qj81QuD7WPKY5+N3U= =ACO2 -----END PGP SIGNATURE----- -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
