On 7/3/07, Simon Geard <[EMAIL PROTECTED]> wrote: > On Mon, 2007-07-02 at 06:30 -0700, Dan Nicholson wrote: > > 're in luck. Bryan has been putting together a mkinitramfs script > > for LFS that I think will try to land post-6.3 (whenever that > > happens). Follow this thread: > > > > http://linuxfromscratch.org/pipermail/lfs-dev/2007-June/059512.html > > > > Yes, that looks interesting. Is the stuff in that lfs-initramfs SVN > repository usable yet, do you know?
I think Bryan's using it. I haven't tested it yet. I would certainly give it a go, though. That would also be nice for testing purposes. > Also, do I correctly understand that in future, an initramfs will be a > standard in the book, a core part to making an LFS system bootable? I don't know what's gonna happen there as I didn't really follow the LKML discussion about why it was so critical to have it. But it should be easy enough to have an initramfs or not depending on what modules are built into your kernel and if you have an lvm/raid enabled rootfs. > > On my system, I use klibc, but if you don't care about size too much, > > just use glibc. It's easier to get started. My current initramfs is > > ~1MB. I wouldn't care if that grew to accommodate glibc. > > So, what does the archive consist of? Is it just the binaries provided > by klibc, plus udev binaries built using klcc? Anything else? I also build modprobe against klcc, but right now don't support lvm or dmraid. This is what I do: http://gitweb.dwcab.com/?p=gado.git;a=blob;f=spec/initramfs-tools.spec;hb=HEAD For full support, you'd also need device-mapper, dmraid and lvm2 built against klcc. > So what, fstab contains /dev/disk/by-label/BootDisk for the root entry? > Yeah, that's another way, I suppose. Normal fstab entries, but it gets parsed and any LABEL= or UUID= entries get temporary udev rules that use vol_id to test the LABEL and creates the /dev/root symlink. I didn't write that part. I don't know how Bryan's handling this offhand. > I'm not so concerned about that part now though - I've found enough > examples of how that's done. My main issue now is simply over what kind > of binaries I need in the initramfs archive. The two links you've > provided will hopefully answer that question. The main things are udev, modprobe, mount, sh and run-init, I think. Then other things as needed by the script. I suppose that's the other nice thing about using klibc: initramfs is it's main use case, so most of the stuff you need is there. But Bryan has figured most of this out using glibc, so that should give an alternative. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
