From 9a9106675f154e4d9ae22bc4e3cf9368dc997c9d Mon Sep 17 00:00:00 2001 From: Udo Erdelhoff Date: Tue, 22 May 2001 17:13:11 +0000 Subject: [PATCH] Use to mark up device nodes as well. While I'm here, pour some s on all those cuaaX and ttydX --- en_US.ISO8859-1/books/faq/book.sgml | 92 ++++++++++++++-------------- en_US.ISO_8859-1/books/faq/book.sgml | 92 ++++++++++++++-------------- 2 files changed, 92 insertions(+), 92 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 7575f27e06..cf571b981c 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.199 2001/05/19 15:05:15 dannyboy Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.200 2001/05/20 23:04:46 ue Exp $ 1995 @@ -2655,7 +2655,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on vp0 drivers (the GENERIC kernel contains everything except vp0). With all these drivers present, the Parallel Port drive should be - available as /dev/da0s4. Disks can be + available as /dev/da0s4. Disks can be mounted using mount /dev/da0s4 /mnt OR (for dos disks) mount_msdos /dev/da0s4 /mnt as appropriate. @@ -2763,10 +2763,10 @@ usbd_flags="" After the system is rebooted, the AT keyboard becomes - /dev/kbd0 and the USB keyboard becomes - /dev/kbd1, if both are connected to the + /dev/kbd0 and the USB keyboard becomes + /dev/kbd1, if both are connected to the system. If there is the USB keyboard only, it will be - /dev/ukbd0. + /dev/ukbd0. If you want to use the USB keyboard in the console, you have to explicitly tell the console driver to use the existence @@ -2776,7 +2776,7 @@ usbd_flags="" &prompt.root; kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null Note that if the USB keyboard is the only keyboard, it is - accessed as /dev/kbd0, thus, the command + accessed as /dev/kbd0, thus, the command should look like: &prompt.root; kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null @@ -3690,12 +3690,12 @@ quit Ridge (long filename) extensions as well. As an example, if you want to mount the CDROM device, - /dev/cd0c, under /mnt, + /dev/cd0c, under /mnt, you would execute: &prompt.root; mount -t cd9660 /dev/cd0c /mnt - Note that your device name (/dev/cd0c + Note that your device name (/dev/cd0c in this example) could be different, depending on the CDROM interface. Note that the option just causes the mount_cd9660 command to be @@ -5074,7 +5074,7 @@ lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -> /dev/null crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx You just need socksys to go to - /dev/null (see &man.null.4;) + /dev/null (see &man.null.4;) to fake the open & close. The code in -CURRENT will handle the rest. This is much cleaner than the way it was done before. If you want the spx driver for a local @@ -5776,7 +5776,7 @@ C:\="DOS" label=FreeBSD (the above assumes that your FreeBSD slice is known to Linux - as /dev/hda2; tailor to suit your setup). + as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. @@ -6923,8 +6923,8 @@ define(`confDELIVERY_MODE',`deferred')dnl write to kernel memory via - /dev/mem and - /dev/kmem, + /dev/mem and + /dev/kmem, @@ -7040,14 +7040,14 @@ define(`confDELIVERY_MODE',`deferred')dnl All users can now mount the floppy - /dev/fd0 onto a directory that they + /dev/fd0 onto a directory that they own: &prompt.user; mkdir ~/my-mount-point &prompt.user; mount -t msdos /dev/fd0 ~/my-mount-point Users in group operator can now - mount the cdrom /dev/cd0c onto a + mount the cdrom /dev/cd0c onto a directory that they own: &prompt.user; mkdir ~/my-mount-point @@ -7055,7 +7055,7 @@ define(`confDELIVERY_MODE',`deferred')dnl Unmounting the device is simple: - &prompt.user; umount ~/my-mount-point + &prompt.user; umount ~/my-mount-point Enabling vfs.usermount, however, has negative security implications. A better way to access MSDOS @@ -7128,7 +7128,7 @@ define(`confDELIVERY_MODE',`deferred')dnl For example, if you are going to move root to - /dev/ad1s1a, with + /dev/ad1s1a, with /mnt as the temporary mount point, it's: @@ -7353,7 +7353,7 @@ define(`confDELIVERY_MODE',`deferred')dnl you can configure FreeBSD to support a mouse pointer on each virtual screen. In order to avoid conflicting with X, syscons supports a virtual device called - /dev/sysmouse. All mouse events received + /dev/sysmouse. All mouse events received from the real mouse device are written to the sysmouse device via moused. If you wish to use your mouse on one or more virtual consoles, and use X, see @@ -7372,10 +7372,10 @@ Device "/dev/sysmouse" earlier versions, the Protocol should be MouseSystems. - Some people prefer to use /dev/mouse - under X. To make this work, /dev/mouse + Some people prefer to use /dev/mouse + under X. To make this work, /dev/mouse should be linked to - /dev/sysmouse (see &man.sysmouse.4;): + /dev/sysmouse (see &man.sysmouse.4;): &prompt.root; cd /dev &prompt.root; rm -f mouse @@ -7814,7 +7814,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure :0 local /usr/X11R6/bin/X vt4 The above example will direct the X server to run in - /dev/ttyv3. Note the number is offset by + /dev/ttyv3. Note the number is offset by one. The X server counts the vty from one, whereas the FreeBSD kernel numbers the vty from zero. @@ -7830,7 +7830,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure If you start X with startx, the permissions on - /dev/console will + /dev/console will not get changed, resulting in things like xterm -C and @@ -7850,7 +7850,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure is in /etc/fbtab (see &man.fbtab.5;) and it will ensure that whomever logs in on - /dev/ttyv0 will own the console. + /dev/ttyv0 will own the console. @@ -8352,7 +8352,7 @@ Key F15 A A Menu Workplace Nop - I can't create a /dev/ed0 + I can't create a /dev/ed0 device! @@ -10123,12 +10123,12 @@ sio1: type 16550A I just upgraded to 2.0.5 and my - tty0X are missing! + tty0X are missing! Don't worry, they have been merged with the - ttydX devices. You'll have to change + ttydX devices. You'll have to change any old configuration files you have, though. @@ -10141,21 +10141,21 @@ sio1: type 16550A The third serial port, sio2 - (see &man.sio.4;, known as COM3 in DOS), is on /dev/cuaa2 - for dial-out devices, and on /dev/ttyd2 + (see &man.sio.4;, known as COM3 in DOS), is on /dev/cuaa2 + for dial-out devices, and on /dev/ttyd2 for dial-in devices. What's the difference between these two classes of devices? - You use ttydX for dial-ins. When - opening /dev/ttydX in blocking mode, a + You use ttydX for dial-ins. When + opening /dev/ttydX in blocking mode, a process will wait for the corresponding - cuaaX device to become inactive, and then + cuaaX device to become inactive, and then wait for the carrier detect line to go active. When you open - the cuaaX device, it makes sure the serial - port isn't already in use by the ttydX + the cuaaX device, it makes sure the serial + port isn't already in use by the ttydX device. If the port's available, it steals it - from the ttydX device. Also, the - cuaXX device doesn't care about carrier + from the ttydX device. Also, the + cuaaX device doesn't care about carrier detect. With this scheme and an auto-answer modem, you can have remote users log in and you can still dialout with the same modem and the system will take care of all the @@ -10216,8 +10216,8 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - The ttydX (or - cuaaX) device is the regular device + The ttydX (or + cuaaX) device is the regular device you'll want to open for your applications. When a process opens the device, it'll have a default set of terminal I/O settings. You can see these settings with the command @@ -10244,11 +10244,11 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrYou can also prevent certain settings from being changed by an application by making adjustments to the lock state device. For example, to lock the - speed of ttyd5 to 57600 bps, do + speed of ttyd5 to 57600 bps, do &prompt.root; stty -f /dev/ttyld5 57600 - Now, an application that opens ttyd5 + Now, an application that opens ttyd5 and tries to change the speed of the port will be stuck with 57600 bps. @@ -10296,7 +10296,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrttyd1 "/usr/libexec/getty std.57600" dialup on insecure This line indicates that the second serial port - (/dev/ttyd1) has a modem connected + (/dev/ttyd1) has a modem connected running at 57600 bps and no parity (std.57600, which comes from the file /etc/gettytab, see &man.gettytab.5;). @@ -10304,7 +10304,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointron and is insecure---meaning root logins on the port aren't allowed. For dialin ports like this one, use the - ttydX entry. + ttydX entry. It's common practice to use dialup as the terminal type. Many users set up in their .profile or @@ -10355,7 +10355,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrttyd4 "/usr/libexec/getty std.38400" wyse50 on secure This example shows that the port on - /dev/ttyd4 has a wyse50 terminal + /dev/ttyd4 has a wyse50 terminal connected at 38400 bps with no parity (std.38400 from /etc/gettytab, see &man.gettytab.5;) and root logins are @@ -10433,17 +10433,17 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr Make what's called a direct entry in your /etc/remote file (see &man.remote.5;). For example, if your modem's hooked - up to the first serial port, /dev/cuaa0, + up to the first serial port, /dev/cuaa0, then put in the following line: cuaa0:dv=/dev/cuaa0:br#19200:pa=none Use the highest bps rate your modem supports in the br capability. Then, type - tip cuaa0 (see &man.tip.1;) + tip cuaa0 (see &man.tip.1;) and you'll be connected to your modem. - If there is no /dev/cuaa0 on your + If there is no /dev/cuaa0 on your system, do this: &prompt.root; cd /dev @@ -10454,7 +10454,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr&prompt.root; cu -lline -sspeed with line being the serial port (e.g. - /dev/cuaa0) and speed being the speed + /dev/cuaa0) and speed being the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit. diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 7575f27e06..cf571b981c 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -14,7 +14,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.199 2001/05/19 15:05:15 dannyboy Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.200 2001/05/20 23:04:46 ue Exp $ 1995 @@ -2655,7 +2655,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on vp0 drivers (the GENERIC kernel contains everything except vp0). With all these drivers present, the Parallel Port drive should be - available as /dev/da0s4. Disks can be + available as /dev/da0s4. Disks can be mounted using mount /dev/da0s4 /mnt OR (for dos disks) mount_msdos /dev/da0s4 /mnt as appropriate. @@ -2763,10 +2763,10 @@ usbd_flags="" After the system is rebooted, the AT keyboard becomes - /dev/kbd0 and the USB keyboard becomes - /dev/kbd1, if both are connected to the + /dev/kbd0 and the USB keyboard becomes + /dev/kbd1, if both are connected to the system. If there is the USB keyboard only, it will be - /dev/ukbd0. + /dev/ukbd0. If you want to use the USB keyboard in the console, you have to explicitly tell the console driver to use the existence @@ -2776,7 +2776,7 @@ usbd_flags="" &prompt.root; kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null Note that if the USB keyboard is the only keyboard, it is - accessed as /dev/kbd0, thus, the command + accessed as /dev/kbd0, thus, the command should look like: &prompt.root; kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null @@ -3690,12 +3690,12 @@ quit Ridge (long filename) extensions as well. As an example, if you want to mount the CDROM device, - /dev/cd0c, under /mnt, + /dev/cd0c, under /mnt, you would execute: &prompt.root; mount -t cd9660 /dev/cd0c /mnt - Note that your device name (/dev/cd0c + Note that your device name (/dev/cd0c in this example) could be different, depending on the CDROM interface. Note that the option just causes the mount_cd9660 command to be @@ -5074,7 +5074,7 @@ lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -> /dev/null crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx You just need socksys to go to - /dev/null (see &man.null.4;) + /dev/null (see &man.null.4;) to fake the open & close. The code in -CURRENT will handle the rest. This is much cleaner than the way it was done before. If you want the spx driver for a local @@ -5776,7 +5776,7 @@ C:\="DOS" label=FreeBSD (the above assumes that your FreeBSD slice is known to Linux - as /dev/hda2; tailor to suit your setup). + as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. @@ -6923,8 +6923,8 @@ define(`confDELIVERY_MODE',`deferred')dnl write to kernel memory via - /dev/mem and - /dev/kmem, + /dev/mem and + /dev/kmem, @@ -7040,14 +7040,14 @@ define(`confDELIVERY_MODE',`deferred')dnl All users can now mount the floppy - /dev/fd0 onto a directory that they + /dev/fd0 onto a directory that they own: &prompt.user; mkdir ~/my-mount-point &prompt.user; mount -t msdos /dev/fd0 ~/my-mount-point Users in group operator can now - mount the cdrom /dev/cd0c onto a + mount the cdrom /dev/cd0c onto a directory that they own: &prompt.user; mkdir ~/my-mount-point @@ -7055,7 +7055,7 @@ define(`confDELIVERY_MODE',`deferred')dnl Unmounting the device is simple: - &prompt.user; umount ~/my-mount-point + &prompt.user; umount ~/my-mount-point Enabling vfs.usermount, however, has negative security implications. A better way to access MSDOS @@ -7128,7 +7128,7 @@ define(`confDELIVERY_MODE',`deferred')dnl For example, if you are going to move root to - /dev/ad1s1a, with + /dev/ad1s1a, with /mnt as the temporary mount point, it's: @@ -7353,7 +7353,7 @@ define(`confDELIVERY_MODE',`deferred')dnl you can configure FreeBSD to support a mouse pointer on each virtual screen. In order to avoid conflicting with X, syscons supports a virtual device called - /dev/sysmouse. All mouse events received + /dev/sysmouse. All mouse events received from the real mouse device are written to the sysmouse device via moused. If you wish to use your mouse on one or more virtual consoles, and use X, see @@ -7372,10 +7372,10 @@ Device "/dev/sysmouse" earlier versions, the Protocol should be MouseSystems. - Some people prefer to use /dev/mouse - under X. To make this work, /dev/mouse + Some people prefer to use /dev/mouse + under X. To make this work, /dev/mouse should be linked to - /dev/sysmouse (see &man.sysmouse.4;): + /dev/sysmouse (see &man.sysmouse.4;): &prompt.root; cd /dev &prompt.root; rm -f mouse @@ -7814,7 +7814,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure :0 local /usr/X11R6/bin/X vt4 The above example will direct the X server to run in - /dev/ttyv3. Note the number is offset by + /dev/ttyv3. Note the number is offset by one. The X server counts the vty from one, whereas the FreeBSD kernel numbers the vty from zero. @@ -7830,7 +7830,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure If you start X with startx, the permissions on - /dev/console will + /dev/console will not get changed, resulting in things like xterm -C and @@ -7850,7 +7850,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure is in /etc/fbtab (see &man.fbtab.5;) and it will ensure that whomever logs in on - /dev/ttyv0 will own the console. + /dev/ttyv0 will own the console. @@ -8352,7 +8352,7 @@ Key F15 A A Menu Workplace Nop - I can't create a /dev/ed0 + I can't create a /dev/ed0 device! @@ -10123,12 +10123,12 @@ sio1: type 16550A I just upgraded to 2.0.5 and my - tty0X are missing! + tty0X are missing! Don't worry, they have been merged with the - ttydX devices. You'll have to change + ttydX devices. You'll have to change any old configuration files you have, though. @@ -10141,21 +10141,21 @@ sio1: type 16550A The third serial port, sio2 - (see &man.sio.4;, known as COM3 in DOS), is on /dev/cuaa2 - for dial-out devices, and on /dev/ttyd2 + (see &man.sio.4;, known as COM3 in DOS), is on /dev/cuaa2 + for dial-out devices, and on /dev/ttyd2 for dial-in devices. What's the difference between these two classes of devices? - You use ttydX for dial-ins. When - opening /dev/ttydX in blocking mode, a + You use ttydX for dial-ins. When + opening /dev/ttydX in blocking mode, a process will wait for the corresponding - cuaaX device to become inactive, and then + cuaaX device to become inactive, and then wait for the carrier detect line to go active. When you open - the cuaaX device, it makes sure the serial - port isn't already in use by the ttydX + the cuaaX device, it makes sure the serial + port isn't already in use by the ttydX device. If the port's available, it steals it - from the ttydX device. Also, the - cuaXX device doesn't care about carrier + from the ttydX device. Also, the + cuaaX device doesn't care about carrier detect. With this scheme and an auto-answer modem, you can have remote users log in and you can still dialout with the same modem and the system will take care of all the @@ -10216,8 +10216,8 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr - The ttydX (or - cuaaX) device is the regular device + The ttydX (or + cuaaX) device is the regular device you'll want to open for your applications. When a process opens the device, it'll have a default set of terminal I/O settings. You can see these settings with the command @@ -10244,11 +10244,11 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrYou can also prevent certain settings from being changed by an application by making adjustments to the lock state device. For example, to lock the - speed of ttyd5 to 57600 bps, do + speed of ttyd5 to 57600 bps, do &prompt.root; stty -f /dev/ttyld5 57600 - Now, an application that opens ttyd5 + Now, an application that opens ttyd5 and tries to change the speed of the port will be stuck with 57600 bps. @@ -10296,7 +10296,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrttyd1 "/usr/libexec/getty std.57600" dialup on insecure This line indicates that the second serial port - (/dev/ttyd1) has a modem connected + (/dev/ttyd1) has a modem connected running at 57600 bps and no parity (std.57600, which comes from the file /etc/gettytab, see &man.gettytab.5;). @@ -10304,7 +10304,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointron and is insecure---meaning root logins on the port aren't allowed. For dialin ports like this one, use the - ttydX entry. + ttydX entry. It's common practice to use dialup as the terminal type. Many users set up in their .profile or @@ -10355,7 +10355,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointrttyd4 "/usr/libexec/getty std.38400" wyse50 on secure This example shows that the port on - /dev/ttyd4 has a wyse50 terminal + /dev/ttyd4 has a wyse50 terminal connected at 38400 bps with no parity (std.38400 from /etc/gettytab, see &man.gettytab.5;) and root logins are @@ -10433,17 +10433,17 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr Make what's called a direct entry in your /etc/remote file (see &man.remote.5;). For example, if your modem's hooked - up to the first serial port, /dev/cuaa0, + up to the first serial port, /dev/cuaa0, then put in the following line: cuaa0:dv=/dev/cuaa0:br#19200:pa=none Use the highest bps rate your modem supports in the br capability. Then, type - tip cuaa0 (see &man.tip.1;) + tip cuaa0 (see &man.tip.1;) and you'll be connected to your modem. - If there is no /dev/cuaa0 on your + If there is no /dev/cuaa0 on your system, do this: &prompt.root; cd /dev @@ -10454,7 +10454,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr&prompt.root; cu -lline -sspeed with line being the serial port (e.g. - /dev/cuaa0) and speed being the speed + /dev/cuaa0) and speed being the speed (e.g.57600). When you are done entering the AT commands hit ~. to exit.