Messages in this thread |  | | Date | Thu, 24 May 2001 11:35:39 +0100 | From | "Stephen C. Tweedie" <> | Subject | Re: [PATCH] struct char_device |
| |
Hi,
On Wed, May 23, 2001 at 01:54:15PM -0400, Alexander Viro wrote: > On Wed, 23 May 2001 Andries.Brouwer@cwi.nl wrote: > > > > But I don't want an initrd. > > Don't be afraid of words. You wouldnt notice - it would do its > > job and disappear just like piggyback today. > > Andries, initrd code is _sick_. Our boot sequence is not a wonder of > elegance, but that crap is the worst part. I certainly can understand > people not wanting to use that on aesthetical reasons alone.
It's the principle of a kernel-linked boot image, not initrd, which is important. Unpacking a cramfs image from an __init section is much cleaner than initrd and has almost the same effect: the boot filesystem just ends up readonly that way. Either way we can hook in that default user-space code at boot time transparently.
--Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |