Skip to contentSkip to conversation

struct char_device

PATCH [email protected] 3 participants 3 messages May 23, 2001

lore
Share & tools
lore
#0 lore raw

From [email protected] Wed May 23 14:16:46 2001

> It is entirely possible to remove all partition table handling code > from the kernel. User space can figure out where the partitions > are supposed to be and tell the kernel.
> For the initial boot this user space can be in an initrd, > or it could just be a boot parameter: rootdev=/dev/hda, > rootpartition:offset=N,length=L, rootfstype=ext3.

Not if you want compatibility.

I don't think compatibility is a problem.
It would go like this: at configure time you get the choice of the default initrd or a custom initrd. If you choose the custom one you construct it yourself. If you choose the default one, then you get something that comes together with the kernel image, just like the piggyback stuff today. This default initrd does the partition parsing that up to now the kernel did. That way nobody need to notice a difference, except for those who use initrd already now. They can solve their problems.

Andries

#1 lore raw
Quoted 5 lines

the piggyback stuff today. This default initrd does the partition parsing that up to now the kernel did. That way nobody need to notice a difference, except for those who use initrd already now. They can solve their problems.

as a longer term path that seems reasonable. If we want large numbers of less than guru level developers to play with 2.5 kernels for fun then its likely to be a barrier unless its progressed stage by stage

#2 lore raw
In reply to [email protected]
Quoted 10 lines · [email protected] wrote:

From [email protected] Wed May 23 14:16:46 2001

> It is entirely possible to remove all partition table handling code > from the kernel. User space can figure out where the partitions > are supposed to be and tell the kernel.
> For the initial boot this user space can be in an initrd, > or it could just be a boot parameter: rootdev=/dev/hda, > rootpartition:offset=N,length=L, rootfstype=ext3.

Quoted 5 lines

Not if you want compatibility.

I don't think compatibility is a problem.
It would go like this: at configure time you get the choice of the default initrd or a custom initrd.

But I don't want an initrd. I want to get the root fs directly from disk the way I always have. Initrd may be useful for install floppies and such, not something I want for an ordinary installed system.

The kernel parameter way is better, just add to lilo.conf and it works. Forcing an initrd is also incompatibility, because I don't use one now.

Helge Hafting