···181181--------------------182182183183A driver has been added to allow updating of Intel IA32 microcode,184184-accessible as both a devfs regular file and as a normal (misc)185185-character device. If you are not using devfs you may need to:184184+accessible as a normal (misc) character device. If you are not using185185+udev you may need to:186186187187mkdir /dev/cpu188188mknod /dev/cpu/microcode c 10 184···201201udev202202----203203udev is a userspace application for populating /dev dynamically with204204-only entries for devices actually present. udev replaces devfs.204204+only entries for devices actually present. udev replaces the basic205205+functionality of devfs, while allowing persistant device naming for206206+devices.205207206208FUSE207209----···233231enable it to operate over diverse media layers. If you use PPP,234232upgrade pppd to at least 2.4.0.235233236236-If you are not using devfs, you must have the device file /dev/ppp234234+If you are not using udev, you must have the device file /dev/ppp237235which can be made by:238236239237mknod /dev/ppp c 108 0240238241239as root.242242-243243-If you use devfsd and build ppp support as modules, you will need244244-the following in your /etc/devfsd.conf file:245245-246246-LOOKUP PPP MODLOAD247240248241Isdn4k-utils249242------------
···7878terms are in use in the Mylex documentation; I have chosen to standardize on7979the more generic "Logical Drive" and "Drive Group".80808181-DAC960 RAID disk devices are named in the style of the Device File System8282-(DEVFS). The device corresponding to Logical Drive D on Controller C is8383-referred to as /dev/rd/cCdD, and the partitions are called /dev/rd/cCdDp18181+DAC960 RAID disk devices are named in the style of the obsolete Device File8282+System (DEVFS). The device corresponding to Logical Drive D on Controller C8383+is referred to as /dev/rd/cCdD, and the partitions are called /dev/rd/cCdDp18484through /dev/rd/cCdDp7. For example, partition 3 of Logical Drive 5 on8585Controller 2 is referred to as /dev/rd/c2d5p3. Note that unlike with SCSI8686disks the device names will not change in the event of a disk drive failure.
+8-16
Documentation/initrd.txt
···6767 as the last process has closed it, all data is freed and /dev/initrd6868 can't be opened anymore.69697070- root=/dev/ram0 (without devfs)7171- root=/dev/rd/0 (with devfs)7070+ root=/dev/ram072717372 initrd is mounted as root, and the normal boot procedure is followed,7473 with the RAM disk still mounted as root.···8990procedure should create the /initrd directory.90919192If initrd will not be mounted in some cases, its content is still9292-accessible if the following device has been created (note that this9393-does not work if using devfs):9393+accessible if the following device has been created:94949595# mknod /dev/initrd b 1 250 9696# chmod 400 /dev/initrd···117119 (if space is critical, you may want to use the Minix FS instead of Ext2)118120 3) mount the file system, e.g.119121 # mount -t ext2 -o loop initrd /mnt120120- 4) create the console device (not necessary if using devfs, but it can't121121- hurt to do it anyway):122122+ 4) create the console device:122123 # mkdir /mnt/dev123124 # mknod /mnt/dev/console c 5 1124125 5) copy all the files that are needed to properly use the initrd···149152150153 root=/dev/ram0 init=/linuxrc rw151154152152-if not using devfs, or153153-154154- root=/dev/rd/0 init=/linuxrc rw155155-156156-if using devfs. (rw is only necessary if writing to the initrd file157157-system.)155155+(rw is only necessary if writing to the initrd file system.)158156159157With LOADLIN, you simply execute160158···209217# exec chroot . what-follows <dev/console >dev/console 2>&1210218211219Where what-follows is a program under the new root, e.g. /sbin/init212212-If the new root file system will be used with devfs and has no valid213213-/dev directory, devfs must be mounted before invoking chroot in order to214214-provide /dev/console.220220+If the new root file system will be used with udev and has no valid221221+/dev directory, udev must be initialized before invoking chroot in order222222+to provide /dev/console.215223216224Note: implementation details of pivot_root may change with time. In order217225to ensure compatibility, the following points should be observed:···228236disk can be freed:229237230238# umount /initrd231231-# blockdev --flushbufs /dev/ram0 # /dev/rd/0 if using devfs239239+# blockdev --flushbufs /dev/ram0232240233241It is also possible to use initrd with an NFS-mounted root, see the234242pivot_root(8) man page for details.
···3535 APM Advanced Power Management support is enabled.3636 AX25 Appropriate AX.25 support is enabled.3737 CD Appropriate CD support is enabled.3838- DEVFS devfs support is enabled.3938 DRM Direct Rendering Management support is enabled.4039 EDD BIOS Enhanced Disk Drive Services (EDD) is enabled4140 EFI EFI Partitioning (GPT) is enabled···438439 decnet= [HW,NET]439440 Format: <area>[,<node>]440441 See also Documentation/networking/decnet.txt.441441-442442- devfs= [DEVFS]443443- See Documentation/filesystems/devfs/boot-options.444442445443 dhash_entries= [KNL]446444 Set number of hash buckets for dentry cache.
-1
drivers/block/viodasd.c
···5959 * numbers 0-255 we get a maximum of 32 disks.6060 */6161#define VIOD_GENHD_NAME "iseries/vd"6262-#define VIOD_GENHD_DEVFS_NAME "iseries/disc"63626463#define VIOD_VERS "1.64"6564