struct char_device
Quoted 1 line
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.
Quoted 4 lines · On Wed, 23 May 2001 [email protected] wrote:
Quoted 1 line
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.
Hi,
Quoted 9 lines · Alexander Viro
Quoted 3 lines · On Wed, 23 May 2001 [email protected] wrote:
Quoted 1 line
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