device arguments from lookup, partion code inuserspace
Quoted 2 lines
initrd is an unnecessary pain in the ass for most people. It had better not become mandatory.
You would not notice the difference, only your kernel would be a bit smaller and the RRPART ioctl disappears.
[Besides: we have lived with DOS-type partition tables for ten years, but they will not last another ten years. Very soon disk partitions will look very different. It will be good to move knowledge about these things out of the kernel before this happens.]
Andries
Quoted 5 lines · On Sat, May 19, 2001 at 08:05:02PM +0200, [email protected] wrote:
Quoted 2 lines
initrd is an unnecessary pain in the ass for most people. It had better not become mandatory.
You would not notice the difference, only your kernel would be a bit smaller and the RRPART ioctl disappears.
Would I not notice the difference as a user, as a sysadmin, as a kernel builder, as a kernel hacker, or all of the above?
Quoted 9 lines · Aaron Lehmann
Quoted 5 lines · On Sat, May 19, 2001 at 08:05:02PM +0200, [email protected] wrote:
Quoted 2 lines
initrd is an unnecessary pain in the ass for most people. It had better not become mandatory.
You would not notice the difference, only your kernel would be a bit smaller and the RRPART ioctl disappears.
Would I not notice the difference as a user, as a sysadmin, as a kernel builder, as a kernel hacker, or all of the above?
If I understand the status of stuff correctly, I think this would make it a lot more painful to admin if it became a requirement to use initrd on everything just to be able to boot. If you've ever seen the way some of the bootloaders for alterate platforms (like ppc and 68k) handle booting, you'd see what a pain it can be to have anything more than a simple string of options getting passed to the kernel. It's particularly bad on some of the embedded ppc platforms. I suspect that if this happened, it would never be allowed into many people's trees, because it would be worth their effort to maintain different code so they don't have to squeeze an initrd on flash along with their kernel and root filesystem. If I'm missing the boat here, please tell me, but it sure seems like a bad idea to me.
Brad Boyer
Quoted 4 lines · Brad Boyer
If I understand the status of stuff correctly, I think this would make it a lot more painful to admin if it became a requirement to use initrd on everything just to be able to boot.
Don't get too hung up on initrd. Symbolic links really _are_ workable ways to basically cache the information across boots, and the real problems are elsewhere.
Linus