Tom Peters wrote:
>
[snip]
>
> Right: the issue is, that there has been no requirements neither in L1 nor
> in L2, to understand how the traditional /dev/ or the new Linux 2.4 devfs
> works and how to use mknod or MAKEDEV. I think it is an omission.
am omission: I would say MAKEDEV for L1, mknod for L2.
>
> Now how much of all this is appropriate for a L1 sysadmin? Surely
> knowledge of the device files and their use is required. Understanding
> about the major|minor number system? When and how to use mknod ? (I
> believe I managed to get away with MAKEDEV only thusfar). How frequently
> do sysadmins actually have to use mknod in practice?
>
Infrequently. But that doesn't make it less valuable. Often, when a
new piece of hardware is added to the kernel it requires a new device.
I remember when the frame buffers devices were added. I wrote a script
to create 8 and even posted it on a couple of mailing lists. I've
talked others through making device nodes for new hardware (digital
cameras, etc.). These are added to MAKEDEV, but only after they've been
around for a while.
Ciao,
David A. Bandel
--
Focus on the dream, not the competition.
-- Nemesis Racing Team motto
--
This message was sent from the lpi-examdev mailing list.
Send `unsubscribe lpi-examdev' in the subject to [EMAIL PROTECTED]
to leave the list.
