Re: Adding device file to /dev
Arthur Korn <firstname.lastname@example.org> wrote:
> > > On Sun, Jun 03, 2001 at 02:37:19PM +0200, Russell Coker wrote:
> > > > Also make the package check for the presence of the character device
> > > > /dev/.devfsd first, if that device exists then your script must not
> > > > attempt to create the device node and it should be left for the kernel to
> > > > do it! If you create a node under /dev when devfs is running it may
> > > > result in an attempt to load the module, also the node will disappear on
> > > > reboot!
> MAKEDEV does check for /dev/.devfsd, so as long as people use
> MAKEDEV they don't have to bother.
> I would propose to use MAKEDEV in all cases (and nothing else)
> and thus depend on it. (ie packages (except devfsd and such)
> must not create device nodes directly but use MAKEDEV.
That means that developers are always having to pester the MAKEDEV maintainer
to update the details for the devices that their packages handle. Do we risk
this becoming a bottleneck? I suppose that Linus is trying to avoid to many
new devices being created, and it is probably good to have the list of devices
maintained by a central authority, so that they do not get out of hand and
conflict with each other.
Don't worry -- shop.