Skip to contentSkip to conversation

struct char_device

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

lore
Share & tools
lore
#0 lore raw
Quoted 1 line

Andries, initrd code is _sick_.

Oh, but the fact that there exists a bad implementation does not mean the idea is wrong. It is really easy to make an elegant implementation.

Andries

#1 lore raw
Quoted 5 lines · On Wed, 23 May 2001 [email protected] wrote:
Quoted 1 line

Andries, initrd code is _sick_.

Oh, but the fact that there exists a bad implementation does not mean the idea is wrong. It is really easy to make an elegant implementation.

Andries, I've been doing cleanups of that logics (see namespaces-patch - they've got merged into it) and I have to say that you are sadly mistaken.

It's not just an implementation that is ugly, it's behaviour currently implemented (and relied upon by existing boot setups) that is extremely ill-defined and crufty. I would rather get rid of the abortion, but that is impossible without breaking tons of existing setups.

And that _is_ an area where "we can do something vaguely similar to current behaviour that wouldn't take pages to describe" does not work. You don't fsck with others' boot sequences, unless you want a free tar-and-feather ride. I don't want it.

Besides, just on general principles, we'd better have clean interface for changing partitioning on the kernel side and rip that crap out of $BIGNUM fdisk implmentations. It can be made modular, so problem of teaching it new types of partitions is not hard.