Re: [leaf-devel] Bering uClibc with Kernel 2.6

2008-03-11 Thread Eric Spakman
Hi David, > (2) with a 2.6 you can embed your whole file system into the > kernel and boot and go just from the kernel -- no file system at all -- > that way you don't have to pivot-root from the initrd -- just stay there. > > > I'm sort of fishing for stories about why that might be a bad idea, >

Re: [leaf-devel] Bering uClibc with Kernel 2.6

2008-03-11 Thread Martin Hejl
Hi David, > I'm sort of fishing for stories about why that might be a bad idea, beyond > that 1: it varies from standard practice and 2: the initramfs is not backed > by swap, as normal shmfs is Well, one downside of this approach is that you cannot control the size of the root-fs by a variable in

Re: [leaf-devel] Bering uClibc with Kernel 2.6

2008-03-11 Thread Eric Spakman
Hi David, > (2) with a 2.6 you can embed your whole file system into the > kernel and boot and go just from the kernel -- no file system at all -- > that way you don't have to pivot-root from the initrd -- just stay there. > That's not correct. Indeed you can make a choice to include the initramfs

Re: [leaf-devel] Bering uClibc with Kernel 2.6

2008-03-11 Thread David Nicol
On Mon, Mar 10, 2008 at 4:58 PM, Martin Hejl <[EMAIL PROTECTED]> wrote: > oops - sorry > > > Hi Nicol, > make that "Hi David" I wasn't trying to make any point; just sharing my experiences that (1) tinygentoo image was easy to work with for creating uclibc-linked this and that (2) with a 2.6 you