-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 13 January 2003 07:39 am, Toralf Lund wrote:
> > 'man mknod' for details, but basic usage is: > > mknod NAME TYPE MAJOR MINOR > > I had a feeling someone would misunderstand my request... > > I *know* how a device file may be created, that was not the question. > What I asked for was the "right" or "best" way to create the standard > devices for a hardware driver driver. I'm assuming 'mknod' on the > command driver is not it, since I didn't do that for the SCSI modules, > or audio, or Normally, for add on drivers, the files are created by the driver's install script, be that part of a tar archive or a rpm post install script. You didn't have to create the /dev entries for SCSI or sound, etc. because they already exist as part of the 'dev' package. rpm -ql dev See also 'man MAKEDEV' Even if you didn't, someone used mknod or something similar to create all the files in /dev. > that was not the question. How can the device creation process be > automated? And to a certain extent also: Where do the device files from > other standard or optional hardware/drivers come from? "Standard" dev entries are created by the 'dev' package as part of the distribution. If you want to create a /dev entry for a non standard device, it needs to be created manually as part of the drivers installation. I'm not aware of any way to automatically create a needed /dev entry for a specific module. Am I still misunderstanding the question? - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Ir06n/07WoAb/SsRAhscAJ4xvpJXXwcKjqFEFUDMe0QsFtlQWACgpoVc BCakk8iG3VF+aKLrUGexkww= =8Asp -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
