# When building a target filesystem, it is desirable to not have to # become root and then run 'mknod' a thousand times. Using a device # table you can create device nodes and directories "on the fly". # # This is a sample device table file for use with genext2fs. You can # do all sorts of interesting things with a device table file. For # example, if you want to adjust the permissions on a particular file # you can just add an entry like: # /sbin/foobar f 2755 0 0 - - - - - # and (assuming the file /sbin/foobar exists) it will be made setuid # root (regardless of what its permissions are on the host filesystem. # Furthermore, you can use a single table entry to create a many device # minors. For example, if I wanted to create /dev/hda and /dev/hda[0-15] # I could just use the following two table entries: # /dev/hda b 640 0 0 3 0 0 0 - # /dev/hda b 640 0 0 3 1 1 1 15 # # Device table entries take the form of: # # where name is the file name, type can be one of: # f A regular file # d Directory # c Character special device file # b Block special device file # p Fifo (named pipe) # uid is the user id for the target file, gid is the group id for the # target file. The rest of the entries (major, minor, etc) apply only # to device special files. # Have fun # -Erik Andersen # # /dev d 755 0 0 - - - - - /dev/mem c 640 0 0 1 1 0 0 - /dev/kmem c 640 0 0 1 2 0 0 - /dev/null c 640 0 0 1 3 0 0 - /dev/zero c 640 0 0 1 5 0 0 - /dev/random c 640 0 0 1 8 0 0 - /dev/urandom c 640 0 0 1 9 0 0 - /dev/ptyp c 640 0 0 2 0 0 1 16 /dev/tty c 666 0 0 5 0 0 0 - /dev/tty c 666 0 0 4 0 0 1 4 /dev/ttyp c 640 0 0 3 0 0 1 16 /dev/console c 640 0 0 5 1 0 0 - /dev/cua c 660 0 0 5 64 0 1 2 /dev/ram b 640 0 0 1 1 0 0 - /dev/ram b 640 0 0 1 0 0 1 2 /dev/loop b 640 0 0 7 0 0 1 2 /dev/ttyS c 640 0 0 4 64 0 1 2 /dev/ppp c 640 0 0 108 0 0 0 - /dev/rom b 640 0 0 31 0 0 1 10 /dev/mtd c 640 0 0 90 0 0 2 6 /dev/mtdr c 640 0 0 90 1 0 2 6 /dev/mtdblock b 640 0 0 31 0 0 1 6