On Wed, 16 Feb 2000, Tigran Aivazian wrote:
>
> Of Linus' /proc/driver vs /dev argument I understood b) but not a) or
> c). Namely,
>
> a) there is still userspace setup of using ioct on a proc file
I'm not talking about the ioctl() when I say "setup".
I'm talking about the "mknod".
> c) whether kernel has update support or not is determined by whether
> the minor=184 is accessible (perhaps by loading a driver) or not.
> /proc does not make things much easier.
Sure it does. It makes it an issue of being able to use standard tools
like "ls" or do things like
if [ -f /proc/drivers/microcode ]; then
...
in startup scripts.
I absolutely _detest_ people who think it's ok to have specialized
applications for things like this. That's another reason I hate sysctl: I
think it's against the whole philosophy of UNIX. Remember, the UNIX way is
"everything is a process or a file, and you can string many small things
together to create a bigger thing".
You _should_ be able to do something like this
if [ -f /proc/drivers/microcode ]; then
dd if=microcodefile of=/proc/drivers/microcode bs=500 count=1
fi
and having to have special tools is not a good feature.
Linus
-
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/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:16 EST