>> Indeed, many Cyrix users use the K.Gadeyne's set6x86 program with
>> a simple rc script in order to enable several 6x86 features at bootup.
>> So why not just merging these initializations in the kernel ?
>
> Ah... sorry, but no. What would happen if someone would use some of
> those performace-enhancing options in the intitialization of the kernel?
> Either:
> a) They would work great and the kernel would be super fast
great
> b) They wouldn't work at all and would completely mess things up
> (lock the machine, interfere with HD operation, I can't recall
as with anything: PCI bridge optimization, 486+ features...
> Besides, what if someone wanted to CHANGE those options?
> They would have to re-compile their kernel every time.
> It's so much more convenient to have the initializations
> in a user-space program.
I find that opinion shocking. It is easy to have multiple
kernels with LILO and loadlin. It is easy to make a simple boot
floppy with the new kernel. Screwed up kernels are no problem.
It is difficult to create a complete rescue disk with all the
tools needed to rescue a system with a screwed up /etc or /lib.
I have a rather lengthy procedure involving a tar file, ramdisk,
ext2 tools, dd, rdev... Maybe an msdos disk with syslinux would
do if /bin/ed is your editor of choice.
This isn't kernel bloat, since it could be freed at boot along
with all the other one-time initialization code.
I'm not even a Cyrix user.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu