device arguments from lookup, partion code inuserspace
Quoted 4 lines · Andrew Morton
Quoted 2 lines
(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.
But it is easy to make the transition painless. Instead of the current choice between INITRD (yes/no) we have INITRD (default built-in / external).
The built-in version can then slowly become smaller and die.
Andries
Quoted 6 lines · On Sat, May 19, 2001 at 01:30:14PM +0200, [email protected] wrote:
I don't think so. It is necessary, and it is good.
But it is easy to make the transition painless. Instead of the current choice between INITRD (yes/no) we have INITRD (default built-in / external).
The built-in version can then slowly become smaller and die.
initrd is an unnecessary pain in the ass for most people. It had better not become mandatory.
Quoted 5 lines · Andries Brouwer
Quoted 3 lines · Andrew Morton
Quoted 2 lines
(2) what about bootstrapping? how do you find the root device? Do you do "root=/dev/hda/offset=63,limit=1235823"? Bit nasty.
Quoted 7 lines
Quoted 1 line
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.
Quoted 1 line
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]