Andries Brouwer writes:
> Andrew Morton writes:
>
> > > (2) what about bootstrapping? how do you find the root device?
> > > Do you do "root=/dev/hda/offset=63,limit=1235823"? Bit nasty.
> >
> > Ben's patch makes initrd mandatory.
>
> Can this be fixed? I've *never* had to futz with initrd.
> Probably most systems are the same. It seems a step
> backward to make it necessary.
>
> I don't think so. It is necessary, and it is good.
It most certainly is not. This attitude of pushing more and more stuff
out of the kernel and into initrd is really annoying. Initrd is messy,
nasty and opaque. It makes the boot process more complex. There is no
way in hell I want to be forced to use it.
Removing N lines from the kernel at the cost of adding N+k lines to
user-space is a *loss*, not a gain. I want my *system* to be simple
and transparent.
> But it is easy to make the transition painless.
No, initrd is fundamentally painful. Let go of this ideology of
removing code from the kernel at all costs. A super-slim kernel which
requires a more complex to administer user-space is too high a cost.
The benefits of removing partition support from the kernel are
basically zero.
Regards,
Richard....
Permanent: [EMAIL PROTECTED]
Current: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
