I'll worry about that when there's an error message available that makes
sense to, is ANY use to, a first-time installer in English.
>
> > I don't think you're opposed to the code,
> > though. Surely not. I think you're opposed to the choice.
>
> but I am opposed to the code. I'm opposed to doing anything in the
> kernel that can be done equally well in userspace. I think Linux is too
> big, and I welcome anything which makes it smaller, cleaner or more
> straightforward.
Good rule. You have the makings of a pretty fair Forth programmer.
Absolutism is bad, however. A bootloader is not user-space. User-space
doesn't exist at boot-time. If you're not opposed to the choice, then
making the choice dependant on a bootloader loses, regardless of what you
consider "the kernel". Given that the choice is good, this is the simplest
approach, and the cost within THE kernel is trivial.
This isn't sched.c we're talking about. This is the point at which the
kernel spawns user-space. We should be joyous! Enthused! Positive! Sloppy!
Or at least not absolutist. Look at the unholy mess the SysV init binary
is. Expedience rules at boot time.
No, you're right. Let's stick it in the bootloader. Along with a Forth
compiler, realtime scheduling, Plan9 device-space under #, Open Firmware
driver translation, X....
Rick Hohensee
(note to the reader, I know Wilcox from elsewhere and we have already
established that he is a cat and I am a dog. i.e. I'm not quite this
snide ALL the time. I love the dude. Really.)
>
> [snip]
> --
> Matthew Wilcox <willy@bofh.ai>
> "Windows and MacOS are products, contrived by engineers in the service of
> specific companies. Unix, by contrast, is not so much a product as it is a
> painstakingly compiled oral history of the hacker subculture." - N Stephenson
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/