You didn't really create /dev/hda by typing "mknod /dev/hda b 3 0" on the command line, did you? I know for sure I never did, but the file is still there, which makes me assume "mknod" is NOT the "best" or "recommended" way of creating the default devices for a hardware/driver combination, hence my question.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 10 January 2003 11:07 am, Toralf Lund wrote: > I have a driver for an optional hardware component (a frame grabber) > that I want the system to set up automatically upon reboot after the > hardware has been installed. I've managed to modify > /usr/share/hwdata/pci.ids and /usr/share/hwdata/pcitable in such a > manner that "kudzu" will correctly update /etc/modules.conf (after the > usual user confirmation.) However, I also need to create special device > files for the unit. What's the best/recommended way of doing that?mknod 'man mknod' for details, but basic usage is: mknod NAME TYPE MAJOR MINOR As an example, the device file for /dev/hda: mknod /dev/hda b 3 0 /dev/hda is a block device (b) major 3 minor 0 $ ll /dev/hda brw-rw---- 1 root disk 3, 0 Aug 30 19:31 /dev/hda
Actually, I know where this particular device (/dev/hda) came from; it's installed via the "dev" software package (RPM), but I'm not sure if RPM file installation is a good way of creating the files I want. Also, it seems to me that there must be some boot time magic or something involved since other /dev files are specific to each system and/or not owned by any package.
- Toralf
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
