> [ Stupidity snipped ]
To be accurate, comments you can't answer without appearing stupider
than you already do were snipped.
>> Everything you list as examples of "useless bloat" are things
>> that only the kernel can do properly in a multiuser system.
> #1 Serial console? edit /etc/inittab and put a getty on /dev/ttyS0
Doesn't work...programjs like getty don't run until AFTER the kernel
finishes its initialisation...
> #2 /dev/nvram? userlandable
Agreed...but I said as much previously...
> #3 intird? FS on the HD, or floppy. A custom 'init' will let you
> compress it.
Doesn't work...too much overhead involved...
> #4 romfs? Minix is already there. Use read only mode.
No idea - I've never tried it...but then, you clearly haven't tried
any of your suggestions either...
> NONE of these NEED to be in the kernel. They are in there because
> they work BETTER, and offer greater flexablity.
(1) and (3) NEED to be in the kernel to work at all...
>> The point is that if you want to spew a lot of repeated data into
>> a disk file, writing a small user-space utility to do it will
>> actually be _faster_ (because it doesn't have to read() a block
>> for every write() it does) and quite likely smaller than the
>> amount of extra kernel code needed to implement a pseudodevice.
> THE POINT IS IT IS MUCH MORE FLEXABLE THEN THAT. Get it through
> your skull.
Show me some use for the facilities you suggest that can't be achieved
better by a purely userland program then?
OTOH don't strain that single gray cell of yours too hard - you've
been challenged to do this at least six times so far by various
people, and haven't managed it yet, so I for one seriously doubt you
will achieve it...
Best wishes from Riley.
-
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/