diff options
| author | Nik Clayton <nik@FreeBSD.org> | 1998-10-21 22:05:23 +0000 |
|---|---|---|
| committer | Nik Clayton <nik@FreeBSD.org> | 1998-10-21 22:05:23 +0000 |
| commit | 3ea0381580b4f3343e4f3be64ea2027b364d7c9f (patch) | |
| tree | 53cdadccec62af73abc778e994ee52b7758eadf8 | |
| parent | eb020dff6d6ed8600c080e3b01cb4987119c3c7d (diff) | |
Notes
| -rw-r--r-- | en/handbook/README | 2 | ||||
| -rw-r--r-- | en/handbook/handbook.sgml | 613 | ||||
| -rw-r--r-- | en_US.ISO8859-1/books/handbook/book.sgml | 613 | ||||
| -rw-r--r-- | en_US.ISO_8859-1/books/handbook/book.sgml | 613 |
4 files changed, 941 insertions, 900 deletions
diff --git a/en/handbook/README b/en/handbook/README index ce5d93b7b8..0bea96c5af 100644 --- a/en/handbook/README +++ b/en/handbook/README @@ -458,3 +458,5 @@ for example, 39. . . . to line 15126 . . . + 40. . . . to line 20370 . . . + diff --git a/en/handbook/handbook.sgml b/en/handbook/handbook.sgml index ddc351fe26..60a35a95d9 100644 --- a/en/handbook/handbook.sgml +++ b/en/handbook/handbook.sgml @@ -15316,7 +15316,7 @@ disk wd3 at wdc1 drive 1 jargon in use to abbreviate the different bus types. A small list:</para> - <para> + <itemizedlist> <listitem> @@ -15340,7 +15340,7 @@ disk wd3 at wdc1 drive 1 </listitem> </itemizedlist> - </para> + <para>With a minor amount of imagination one can usually imagine what is meant.</para> @@ -15604,8 +15604,7 @@ disk wd3 at wdc1 drive 1 the highest SCSI ID will win. This also means that the SCSI host adapter usually uses target ID 7. Note however that the lower 8 IDs have higher priorities than the higher 8 IDs on a - wide-SCSI bus. Thus, the order of target IDs is: <emphasis - remap=tt>[7 6 .. 1 0 15 14 .. 9 8]</emphasis> on a wide-SCSI + wide-SCSI bus. Thus, the order of target IDs is: [7 6 .. 1 0 15 14 .. 9 8] on a wide-SCSI system. (If you you are wondering why the lower 8 have higher priority, read the previous paragraph for a hint.)</para> @@ -15643,7 +15642,7 @@ disk wd3 at wdc1 drive 1 ultimately the reliability of it all are tightly related to linear bus rule.</para> - <para><emphasis remap=bf>Stick to the linear bus + <para><emphasis>Stick to the linear bus rule!</emphasis></para> </sect4> @@ -15708,9 +15707,8 @@ disk wd3 at wdc1 drive 1 of a jumper or software setup selection, to switch the translation the SCSI BIOS uses.</para> - <para>It is very important that <emphasis - remap=bf>all</emphasis> operating systems on the disk use - the <emphasis remap=bf>same translation</emphasis> to get the + <para>It is very important that <emphasis>all</emphasis> operating systems on the disk use + the <emphasis>same translation</emphasis> to get the right idea about where to find the relevant partitions. So, when installing FreeBSD you must answer any questions about heads/cylinders etc using the translated values your host @@ -15721,7 +15719,7 @@ disk wd3 at wdc1 drive 1 others partitions. Using fdisk you should be able to see all partitions.</para> - <para>You might have heard some talk of 'lying' devices? Older + <para>You might have heard some talk of <quote>lying</quote> devices? Older FreeBSD kernels used to report the geometry of SCSI disks when booting. An example from one of my systems:</para> @@ -15730,12 +15728,12 @@ disk wd3 at wdc1 drive 1 sd0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512</screen> </informalexample> - <para>Newer kernels usually do not report this information. e.g. + <para>Newer kernels usually do not report this information. e.g.</para> <informalexample> <screen>(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen> - </informalexample></para> + </informalexample> <para>Why has this changed?</para> @@ -15812,7 +15810,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen> </note> <para>An example loosely based on the FreeBSD 2.2.5-Release - kernel config file LINT with some added comments (between + kernel config file <filename>LINT</filename> with some added comments (between []):</para> <programlisting> @@ -15861,9 +15859,9 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <emphasis>only</emphasis> attach them when they match the target ID and LUN specified on the corresponding bus.</para> - <para>Wired down devices get 'first shot' at the unit numbers so - the first non 'wired down' device, is allocated the unit - number one greater than the highest 'wired down' unit number + <para>Wired down devices get <quote>first shot</quote> at the unit numbers so + the first non <quote>wired down</quote> device, is allocated the unit + number one greater than the highest <quote>wired down</quote> unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 is wired down to unit number 1.</para> @@ -15880,7 +15878,7 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <para>Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first - example is that devices are not 'wired down'. 'Wired down' + example is that devices are not <quote>wired down</quote>. <quote>Wired down</quote> means that you specify which SCSI target belongs to which device.</para> @@ -15921,13 +15919,13 @@ device cd0 #Only need one of these, the code dynamically grows devices of a specific type (e.g. sd disks) are found than are configured in the booting kernel, the system will simply allocate more devices, incrementing the unit number starting - at the last number 'wired down'. If there are no 'wired down' + at the last number <quote>wired down</quote>. If there are no <quote>wired down</quote> devices then counting starts at unit 0.</para> - <para>Use <emphasis remap=tt>man 4 scsi</emphasis> to check for + <para>Use <command>man 4 scsi</command> to check for the latest info on the SCSI subsystem. For more detailed info - on host adapter drivers use eg <emphasis remap=tt>man 4 - ahc</emphasis> for info on the Adaptec 294x driver.</para> + on host adapter drivers use eg <command>man 4 + ahc</command> for info on the Adaptec 294x driver.</para> </sect4> @@ -15969,7 +15967,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device correctly is no easy task. Some vendors do a better job then others.</para> - <para>This is exactly where the 'rogue' devices come into view. + <para>This is exactly where the <quote>rogue</quote> devices come into view. Rogues are devices that are recognized by the FreeBSD kernel as behaving slightly (...) non-standard. Rogue devices are reported by the kernel when booting. An example for two of my @@ -16000,7 +15998,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> this is done.</para> <para>This scheme works fine, but keep in mind that it of course - only works for devices that are KNOWN to be weird. If you are + only works for devices that are known to be weird. If you are the first to connect your bogus Mumbletech SCSI CD-ROM you might be the one that has to define which workaround is needed.</para> @@ -16027,14 +16025,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> around this problem you must add an appropriate entry in /sys/scsi/scsiconf.c and rebuild your kernel.</para> - <para>Look for a struct that is initialized like below: + <para>Look for a struct that is initialized like below:</para> <programlisting> { T_DIRECT, T_FIXED, "MAXTOR", "XT-4170S", "B5A", "mx1", SC_ONE_LU } - </programlisting></para> + </programlisting> <para>For you Mumbletech BRIDGE2000 that has more than one LUN, acts as a SCSI disk and has firmware revision 123 you would @@ -16067,13 +16065,13 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> TCQ function is indispensable to take advantage of the device's inherent parallelism.</para> - <para>Each I/O request is uniquely identified by a 'tag' (hence + <para>Each I/O request is uniquely identified by a <quote>tag</quote> (hence the name tagged command queuing) and this tag is used by FreeBSD to see which I/O in the device drivers queue is reported as complete by the device.</para> <para>It should be noted however that TCQ requires device driver - support and that some devices implemented it 'not quite right' + support and that some devices implemented it <quote>not quite right</quote> in their firmware. This problem bit me once, and it leads to highly mysterious problems. In such cases, try to disable TCQ.</para> @@ -16126,7 +16124,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed most common SCSI problems and their solutions. It is by no means complete.</para> - <para> + <itemizedlist> <listitem> @@ -16170,22 +16168,22 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <listitem> <para>If you can compile a kernel, make one with the - SCSIDEBUG option, and try accessing the device with + <literal>SCSIDEBUG</literal> option, and try accessing the device with debugging turned on for that device. If your device does not even probe at startup, you may have to define the address of the device that is failing, and the desired debug level in <filename>/sys/scsi/scsidebug.h</filename>. If it probes but just does not work, you can use the <citerefentry><refentrytitle>scsi</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to dynamically set a - debug level to it in a running kernel (if SCSIDEBUG is - defined). This will give you COPIOUS debugging output with - which to confuse the gurus. see <emphasis remap=tt>man 4 - scsi</emphasis> for more exact information. Also look at - <emphasis remap=tt>man 8 scsi</emphasis>.</para> + debug level to it in a running kernel (if <literal>SCSIDEBUG</literal> is + defined). This will give you <emphasis>copious</emphasis> debugging output with + which to confuse the gurus. see <command>man 4 + scsi</command> for more exact information. Also look at + <command>man 8 scsi</command>.</para> </listitem> </itemizedlist> - </para> + </sect3> @@ -16197,18 +16195,37 @@ options "TUNE_1542" #dynamic tune of bus DMA speed want to have the official standard at hand:</para> <para>Approved American National Standards can be purchased from - ANSI at 11 West 42nd Street, 13th Floor, New York, NY 10036, - Sales Dept: (212) 642-4900. You can also buy many ANSI + ANSI at + + <address> + <otheraddr>13th Floor</otheraddr> + <street>11 West 42nd Street</street> + <city>New York</city> + <state>NY</state> <postcode>10036</postcode> + Sales Dept: <phone>(212) 642-4900</phone> + </address> + </para> + + <para>You can also buy many ANSI standards and most committee draft documents from Global - Engineering Documents, 15 Inverness Way East, Englewood, CO - 80112-5704, Phone: (800) 854-7179, Outside USA and Canada: (303) - 792-2181, FAX: (303) 792- 2192.</para> + Engineering Documents, + + <address> + <street>15 Inverness Way East</street> + <city>Englewood</city> + <state>CO</state>, <postcode>80112-5704</postcode> + Phone: <phone>(800) 854-7179</phone> + Outside USA and Canada: <phone>(303) 792-2181</phone> + Fax: <fax>(303) 792- 2192</fax> + </address> + </para> <para>Many X3T10 draft documents are available electronically on - the SCSI BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous + the SCSI BBS (719-574-0424) and on the <hostid role="fqdn">ncrinfo.ncr.com</hostid> anonymous ftp site.</para> - <para>Latest X3T10 committee documents are: + <para>Latest X3T10 committee documents are:</para> + <itemizedlist> <listitem> @@ -16236,8 +16253,11 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Interface Module (CAM) [X3T10/792D Rev 11]</para> </listitem> - </itemizedlist> Other publications that might provide you with - additional information are: + </itemizedlist> + + <para>Other publications that might provide you with + additional information are:</para> + <itemizedlist> <listitem> @@ -16281,7 +16301,6 @@ options "TUNE_1542" #dynamic tune of bus DMA speed </listitem> </itemizedlist> - </para> <para>On Usenet the newsgroups <ulink URL="news:comp.periphs.scsi">comp.periphs.scsi</ulink> and @@ -16477,10 +16496,9 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <title> General tape access commands</title> <para><citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> provides generic access to the tape - drives. Some of the more common commands are <emphasis - remap=tt>rewind</emphasis>, <emphasis - remap=tt>erase</emphasis>, and <emphasis - remap=tt>status</emphasis>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> + drives. Some of the more common commands are + <command>rewind</command>, <command>erase</command>, and + <command>status</command>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page for a detailed description.</para> </sect3> @@ -16717,7 +16735,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>This drive was repackaged by Sun Microsystems as model 411.</para> - <para>Reported by: Bob Bishop rb@gid.co.uk</para> + <para>Reported by: Bob Bishop <email>rb@gid.co.uk</email></para> </sect4> @@ -16738,7 +16756,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> - <para>Reported by: Philippe Regnauld regnauld@hsc.fr</para> + <para>Reported by: Philippe Regnauld <email>regnauld@hsc.fr</email></para> </sect4> @@ -16778,10 +16796,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> <para>Reported by: Pedro A M Vazquez - vazquez@IQM.Unicamp.BR</para> + <email>vazquez@IQM.Unicamp.BR</email></para> <para>Mike Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -16826,7 +16844,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive uses QIC-80 tape cartridges.</para> - <para>Reported by: Mark Hannon mark@seeware.DIALix.oz.au</para> + <para>Reported by: Mark Hannon <email>mark@seeware.DIALix.oz.au</email></para> </sect4> @@ -16846,7 +16864,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive uses QIC-3080 tape cartridges.</para> - <para>Reported by: Thomas S. Traylor tst@titan.cs.mci.com</para> + <para>Reported by: Thomas S. Traylor <email>tst@titan.cs.mci.com</email></para> </sect4> @@ -16924,7 +16942,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Right now, this drive cannot really be recommended for FreeBSD.</para> - <para>Reported by: Bob Beaulieu ez@eztravel.com</para> + <para>Reported by: Bob Beaulieu <email>ez@eztravel.com</email></para> </sect4> @@ -16953,7 +16971,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> <para>Reported by: Mike Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -16971,7 +16989,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Data transfer rate is 300kB/s.</para> - <para>Reported by: Greg Lehey grog@lemis.de</para> + <para>Reported by: Greg Lehey <email>grog@lemis.de</email></para> </sect4> @@ -16993,7 +17011,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Data transfer rate is 300kB/s.</para> - <para>Reported by: Glen Foster gfoster@gfoster.com</para> + <para>Reported by: Glen Foster <email>gfoster@gfoster.com</email></para> </sect4> @@ -17019,7 +17037,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive has a block of 8 dip switches. The proper settings for FreeBSD are: 1 ON; 2 ON; 3 OFF; 4 ON; 5 ON; 6 ON; - 7 ON; 8 ON. + 7 ON; 8 ON.</para> <informaltable frame="none"> <tgroup cols="3"> @@ -17061,7 +17079,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed </row> </tbody> </tgroup> - </informaltable></para> + </informaltable> <para>Switch 3 controls MRS (Media Recognition System). MRS tapes have stripes on the transparent leader. These identify @@ -17113,7 +17131,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed nearing the end of its useful life, steady indicates an hard fault. (factory service required?)</para> - <para>Reported by Gary Crutcher gcrutchr@nightflight.com</para> + <para>Reported by Gary Crutcher <email>gcrutchr@nightflight.com</email></para> </sect4> @@ -17206,7 +17224,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Data transfer rate is 160kB/s.</para> <para>Reported by: mark thompson - mark.a.thompson@pobox.com</para> + <email>mark.a.thompson@pobox.com</email></para> </sect4> @@ -17236,7 +17254,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" returned 5 of these drives. None lasted more than 9 months.</para> - <para>Reported by: David Dawes dawes@rf900.physics.usyd.edu.au + <para>Reported by: David Dawes <email>dawes@rf900.physics.usyd.edu.au</email> (9 09)</para> </sect4> @@ -17340,7 +17358,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" firmware EPROM of these units will solve the problem.</para> <para>Reported by: Michael Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -17418,8 +17436,8 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Other firmware revisions that are known to work are: M75D</para> - <para>Reported by: Marc van Kempen marc@bowtie.nl <literal>REV73R1</literal> - Andrew Gordon Andrew.Gordon@net-tel.co.uk <literal>M75D</literal></para> + <para>Reported by: Marc van Kempen <email>marc@bowtie.nl</email> <literal>REV73R1</literal> + Andrew Gordon <email>Andrew.Gordon@net-tel.co.uk</email> <literal>M75D</literal></para> </sect4> @@ -17438,7 +17456,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Data transfer rate is 150kB/s.</para> - <para>Reported by: Tony Kimball alk@Think.COM</para> + <para>Reported by: Tony Kimball <email>alk@Think.COM</email></para> </sect4> </sect3> @@ -17658,11 +17676,12 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>The first time that you try to read or write a new, completely blank tape, the operation will fail. The console - messages should be similar to: + messages should be similar to:</para> + <informalexample> <screen>st0(ncr1:4:0): NOT READY asc:4,1 st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> - </informalexample></para> + </informalexample> <para>The tape does not contain an Identifier Block (block number 0). All QIC tape drives since the adoption of QIC-525 standard @@ -17676,10 +17695,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <para>Re-insert the tape and <citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> data to the tape.</para> - <para><citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> will report <emphasis - remap=tt>DUMP: End of tape detected</emphasis> and the console - will show: <emphasis remap=tt>HARDWARE FAILURE info:280 - asc:80,96</emphasis></para> + <para><citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> will report <errorname>DUMP: End of tape detected</errorname> and the console + will show: <errorname>HARDWARE FAILURE info:280 + asc:80,96</errorname></para> <para>rewind the tape using: <command>mt rewind</command></para> @@ -17724,7 +17742,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> rely upon <citerefentry><refentrytitle>rcmd</refentrytitle><manvolnum>3</manvolnum></citerefentry> and <citerefentry><refentrytitle>ruserok</refentrytitle><manvolnum>3</manvolnum></citerefentry> to access the remote tape drive. Therefore, the user performing the backup must have - <emphasis remap=tt>rhosts</emphasis> access to the remote + <filename>rhosts</filename> access to the remote computer. The arguments to <citerefentry><refentrytitle>rdump</refentrytitle><manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rrestore</refentrytitle><manvolnum>8</manvolnum></citerefentry> must suitable to use on the remote computer. (e.g. When <command>rdump</command>'ing from a FreeBSD computer to an @@ -17733,8 +17751,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <informalexample> <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</userinput></screen> </informalexample>) Beware: - there are security implications to allowing <emphasis - remap=tt>rhosts</emphasis> commands. Evaluate your + there are security implications to allowing <filename>rhosts</filename> commands. Evaluate your situation carefully.</para> </sect4> @@ -17881,14 +17898,18 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <para>There are only four steps that you need to perform in preparation for any disaster that may occur.</para> - - <para>First, print the disklabel from each of your disks - (<command>e.g. disklabel sd0 | lpr</command>), your + + <procedure> + <step> + <para>Print the disklabel from each of your disks + (e.g., <command>disklabel sd0 | lpr</command>), your filesystem table (<filename>/etc/fstab</filename>) and all boot messages, two copies of each.</para> - - <para>Second, determine the boot and fixit floppies (boot.flp - and fixit.flp) have all your devices. The easiest way to + </step> + + <step> + <para>Determine the boot and fixit floppies (<filename>boot.flp</filename> + and <filename>fixit.flp</filename>) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot messages. If all your devices are listed and functional, skip on to step three.</para> @@ -17901,12 +17922,16 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> whichever backup program you use. These programs must be statically linked. If you use <citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry>, the floppy must contain <citerefentry><refentrytitle>restore</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para> - - <para>Third, create backup tapes regularly. Any changes that you + </step> + + <step> + <para>Create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. Write-protect the backup tapes.</para> - - <para>Fourth, test the floppies (either boot.flp and fixit.flp + </step> + + <step> + <para>Test the floppies (either <filename>boot.flp</filename> and <filename>fixit.flp</filename> or the two custom bootable floppies you made in step two.) and backup tapes. Make notes of the procedure. Store these notes with the bootable floppy, the printouts and the backup @@ -18078,7 +18103,8 @@ chmod 644 /mnt/etc/passwd # /sbin/umount /mnt </programlisting></para> - + </step> + </procedure> </sect4> <sect4> @@ -18093,13 +18119,13 @@ chmod 644 /mnt/etc/passwd <para>If your hardware is okay, check your floppies. If you are using a custom boot floppy, boot single-user (type <option>-s</option> at the - "boot:" prompt). Skip the following paragraph.</para> + <prompt>boot:</prompt> prompt). Skip the following paragraph.</para> <para>If you are using the boot.flp and fixit.flp floppies, keep reading. Insert the boot.flp floppy in the first floppy drive and boot the computer. The original install menu will be displayed on the screen. Select the "Fixit--Repair mode with - CDROM or floppy." option. Insert the fixit.flp when prompted. + CDROM or floppy." option. Insert the <filename>fixit.flp</filename> when prompted. <command>restore</command> and the other programs that you need are located in <filename>/mnt2/stand</filename>.</para> @@ -18168,10 +18194,10 @@ chmod 644 /mnt/etc/passwd id="russian-console"> <title>Console Setup</title> - <para> - <orderedlist> + + <procedure> - <listitem> + <step> <para>Add following line to your kernel configuration file: <programlisting> @@ -18179,9 +18205,9 @@ options "SC_MOUSE_CHAR=0x03" </programlisting> to move character codes used for mouse cursor off KOI8-R pseudographics range.</para> - </listitem> + </step> - <listitem> + <step> <para>Russian console entry in <filename>/etc/rc.conf</filename> should looks like @@ -18202,19 +18228,18 @@ font8x8=cp866-8x8 <para>This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve - pseudographics, <emphasis remap=it>Gray Delete</emphasis> + pseudographics, <literal>Gray Delete</literal> key remapped to match Russian <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry for FreeBSD console.</para> - <para>RUS/LAT switch will be <emphasis - remap=bf>CapsLock</emphasis>. Old CapsLock function still - available via <emphasis remap=bf>Shift+CapsLock</emphasis>. + <para>RUS/LAT switch will be <literal>CapsLock</literal>. Old CapsLock function still + available via <literal>Shift+CapsLock</literal>. CapsLock LED will indicate RUS mode, not CapsLock mode.</para> - </listitem> + </step> - <listitem> - <para>For each <emphasis remap=tt>ttyv?</emphasis> entry in + <step> + <para>For each <literal>ttyv?</literal> entry in <filename>/etc/ttys</filename> change terminal type from <literal>cons25</literal> to <literal>cons25r</literal>, i.e. each entry should looks like @@ -18222,10 +18247,10 @@ font8x8=cp866-8x8 <programlisting> ttyv0 "/usr/libexec/getty Pc" cons25r on secure </programlisting></para> - </listitem> + </step> - </orderedlist> - </para> + </procedure> + </sect2> @@ -18234,7 +18259,8 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure <title>Locale Setup</title> <para><anchor id="russian-env"> There is two environment variables - for locale setup: + for locale setup:</para> + <itemizedlist> <listitem> @@ -18248,10 +18274,9 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure </listitem> </itemizedlist> - </para> - + <para>The best way is using <filename>/etc/login.conf</filename> - <emphasis remap=tt>russian</emphasis> user's login class in + <literal>russian</literal> user's login class in <citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry login class position. See <citerefentry><refentrytitle>login.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details.</para> @@ -18262,15 +18287,15 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure <title>Login Class Method</title> <para>First of all check your <filename>/etc/login.conf</filename> - have <emphasis remap=tt>russian</emphasis> login class, this - entry may looks like: + have <literal>russian</literal> login class, this + entry may looks like:</para> <programlisting> russian:Russian Users Accounts:\ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R:\ :tc=default: - </programlisting></para> + </programlisting> <sect4> @@ -18278,11 +18303,11 @@ russian:Russian Users Accounts:\ <para>If you use <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users, <filename>/etc/master.passwd</filename> entry should - looks like: + looks like:</para> <programlisting> user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh - </programlisting></para> + </programlisting> </sect4> @@ -18300,19 +18325,17 @@ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh defaultclass = russian </programlisting> in <filename>/etc/adduser.conf</filename> (you must enter - <emphasis remap=tt>default</emphasis> class for all - non-Russian users in this case);<!-- <br> --><!-- <br> - --></para> + <literal>default</literal> class for all + non-Russian users in this case);</para> </listitem> <listitem> - <para>Alternative variant will be answering <emphasis - remap=tt>russian</emphasis> each time when you see + <para>Alternative variant will be answering <literal>russian</literal> each time when you see <informalexample> <screen><prompt>Enter login class:</prompt> default []:</screen> </informalexample> prompt from - <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;<!-- <br> --><!-- <br> --></para> + <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para> </listitem> <listitem> @@ -18333,11 +18356,11 @@ defaultclass = russian <title>How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title> <para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users, - call it in this form: + call it in this form:</para> <informalexample> <screen>&prompt.root; <userinput>pw useradd user_name -L russian</userinput></screen> - </informalexample></para> + </informalexample> </sect4> </sect3> @@ -18349,29 +18372,30 @@ defaultclass = russian <xref linkend="russian-class" remap="login class method"> for some reasons, just set this <xref linkend="russian-env" remap="two environment variables"> - in the following shell startup files: + in the following shell startup files:</para> + <itemizedlist> <listitem> - <para><filename>/etc/profile</filename>: + <para><filename>/etc/profile</filename>:</para> <programlisting> LANG=ru_RU.KOI8-R; export LANG MM_CHARSET=KOI8-R; export MM_CHARSET - </programlisting></para> + </programlisting> </listitem> <listitem> - <para><filename>/etc/csh.login</filename>: + <para><filename>/etc/csh.login</filename>:</para> <programlisting> setenv LANG ru_RU.KOI8-R setenv MM_CHARSET KOI8-R - </programlisting></para> + </programlisting> </listitem> </itemizedlist> - </para> + <para>Alternatively you can add this instructions to <itemizedlist> @@ -18405,13 +18429,15 @@ setenv MM_CHARSET KOI8-R -> CP866 conversion. Such filter installed by default as <filename>/usr/libexec/lpr/ru/koi2alt</filename>. So, Russian printer <filename>/etc/printcap</filename> entry should looks - like: + like:</para> <programlisting> lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: - </programlisting> see <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para> + </programlisting> + + <para>See <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para> </sect2> @@ -18420,11 +18446,13 @@ lp|Russian local line printer:\ <title>MSDOS FS and Russian file names</title> <para>Look at following example <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry to enable support for Russian - file names in MSDOS FS: + file names in MSDOS FS:</para> <programlisting> /dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0 - </programlisting> see + </programlisting> + + <para>See <citerefentry><refentrytitle>mount_msdos</refentrytitle><manvolnum>8</manvolnum></citerefentry>for detailed description of <option>-W</option> and <option>-L</option> options.</para> @@ -18434,10 +18462,11 @@ lp|Russian local line printer:\ id="russian-xwindow"> <title>X Window Setup</title> - <para>Step by step instructions: - <orderedlist> + <para>Step by step instructions:</para> + + <procedure> - <listitem> + <step> <para>Do <xref linkend="russian-locale" remap="non-X locale setup"> first as described.</para> @@ -18453,9 +18482,9 @@ lp|Russian local line printer:\ (check XFree86 version number not less than 3.3 first).</para> </note> - </listitem> + </step> - <listitem> + <step> <para>Go to <filename>/usr/ports/russian/X.language</filename> directory and say @@ -18468,19 +18497,19 @@ lp|Russian local line printer:\ <para>Check find <literal>"Files"</literal> section in your <filename>/etc/XF86Config</filename>, following lines must be before any other <literal>FontPath</literal> - entries: + entries:</para> <programlisting> FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/misc" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi" - </programlisting></para> + </programlisting> <para>If you use high resolution video mode, swap 75 dpi and 100 dpi lines.</para> - </listitem> + </step> - <listitem> + <step> <para>To activate Russian keyboard add <programlisting> @@ -18505,12 +18534,10 @@ XkbKeymap "xfree86(ru)" call <emphasis remap=bf>XtSetLanguageProc</emphasis> (NULL, NULL, NULL); function early in the program.</para> </note> - </listitem> + </step> - </orderedlist> + </procedure> - </para> - </sect2> </sect1> @@ -18521,8 +18548,6 @@ XkbKeymap "xfree86(ru)" <para>Slaven Rezic <emphasis remap=tt><ulink URL="mailto:eserte@cs.tu-berlin.de"><eserte@cs.tu-berlin.de></ulink></emphasis> wrote a tutorial how to use umlauts on a FreeBSD machine. The tutorial is written in German and available at <ulink URL="http://www.de.freebsd.org/de/umlaute/">http://www.de.freebsd.org/de/umlaute/</ulink>.</para> - <para></para> - </sect1> </chapter> </part> @@ -18545,26 +18570,26 @@ XkbKeymap "xfree86(ru)" serial ports. If you do not find what you want here, check into the Terminal and Dialup sections of the handbook.</para> - <para>The <filename>ttydX</filename> (or <filename>cuaaX</filename>) + <para>The <filename>ttyd<replaceable>X</replaceable></filename> (or <filename>cuaa<replaceable>X</replaceable></filename>) device is the regular device you will want to open for your applications. When a process opens the device, it will have a default set of terminal I/O settings. You can see these settings - with the command + with the command</para> <informalexample> <screen>&prompt.root; <userinput>stty -a -f /dev/ttyd1</userinput></screen> - </informalexample></para> + </informalexample> <para>When you change the settings to this device, the settings are in effect until the device is closed. When it is reopened, it goes back to the default set. To make changes to the default set, you can open and adjust the settings of the <quote>initial state</quote> device. For example, to turn on <acronym>CLOCAL</acronym> mode, 8 bits, and - <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do: + <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do:</para> <informalexample> <screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen> - </informalexample></para> + </informalexample> <para>A good place to do this is in <filename>/etc/rc.serial</filename>. Now, an application will have @@ -18574,11 +18599,11 @@ XkbKeymap "xfree86(ru)" <para>You can also prevent certain settings from being changed by an application by making adjustments to the <quote>lock state</quote> device. For example, to lock the speed of <filename>ttyd5</filename> to 57600 - bps, do + bps, do</para> <informalexample> <screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen> - </informalexample></para> + </informalexample> <para>Now, an application that opens <filename>ttyd5</filename> and tries to change the speed of the port will be stuck with 57600 @@ -18630,7 +18655,7 @@ XkbKeymap "xfree86(ru)" <para>For FreeBSD, there are three kinds of terminals:</para> - <para> + <itemizedlist> <listitem> @@ -18647,7 +18672,7 @@ XkbKeymap "xfree86(ru)" </listitem> </itemizedlist> - </para> + <para>The remaining subsections describe each kind.</para> @@ -18774,7 +18799,7 @@ XkbKeymap "xfree86(ru)" <para>If you like making your own cables, here is a table showing a recommended way to construct a null-modem cable for use with terminals. This table shows the RS-232C signal names - and the pin numbers on a DB-25 connector. + and the pin numbers on a DB-25 connector.</para> <informaltable frame="none"> <tgroup cols="5"> @@ -18857,7 +18882,7 @@ XkbKeymap "xfree86(ru)" </row> </tbody> </tgroup> - </informaltable></para> + </informaltable> </sect4> @@ -18910,7 +18935,8 @@ XkbKeymap "xfree86(ru)" <para>In FreeBSD, you access each serial port through an entry in the <filename>/dev</filename> directory. There are two - different kinds of entries: + different kinds of entries:</para> + <itemizedlist> <listitem> @@ -18924,14 +18950,13 @@ XkbKeymap "xfree86(ru)" </listitem> </itemizedlist> - </para> <para>See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for more information.</para> <para>If you have connected a terminal to the first serial port - (COM1 in DOS parlance), then you want to use + (<devicename>COM1</devicename> in DOS parlance), then you want to use <filename>/dev/ttyd0</filename> to refer to the terminal. If - it is on the second serial port (also known as COM2), it is + it is on the second serial port (also known as <devicename>COM2</devicename>), it is <filename>/dev/ttyd1</filename>, and so forth.</para> <para>Note that you may have to configure your kernel to support @@ -19039,12 +19064,12 @@ XkbKeymap "xfree86(ru)" port, <filename>ttyd1</filename>, which is already in the file. We need to add an entry for the 286 PC connected to the sixth serial port. Here is an excerpt of the - <filename>/etc/ttys</filename> file after we add the new entry: + <filename>/etc/ttys</filename> file after we add the new entry:</para> <programlisting> ttyd1 "/usr/libexec/getty std.9600" unknown off secure ttyd5 - </programlisting></para> + </programlisting> </sect3> @@ -19056,12 +19081,12 @@ ttyd5 <para>Next, we need to specify what program will be run to handle the logins on a terminal. For FreeBSD, the standard program to do that is <filename>/usr/libexec/getty</filename>. It is what - provides the <emphasis remap=tt>login:</emphasis> prompt.</para> + provides the <prompt>login:</prompt> prompt.</para> <para>The program <command>getty</command> takes one (optional) parameter on its command line, the - <emphasis><emphasis remap=tt>getty</emphasis> type</emphasis>. - A <emphasis remap=tt>getty</emphasis> type tells about + <replaceable>getty</replaceable> type. + A <replaceable>getty</replaceable> type tells about characteristics on the terminal line, like bps rate and parity. The <command>getty</command> program reads these characteristics from the file @@ -19074,19 +19099,21 @@ ttyd5 115200. Of course, you can add your own entries to this file. The manual page <citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> provides more information.</para> - <para>When setting the <emphasis remap=tt>getty</emphasis> type in + <para>When setting the <replaceable>getty</replaceable> type in the <filename>/etc/ttys</filename> file, make sure that the communications settings on the terminal match.</para> <para>For our example, the Wyse-50 uses no parity and connects at 38400 bps. The 286 PC uses no parity and connects at 19200 bps. Here is the <filename>/etc/ttys</filename> file so far (showing - just the two terminals in which we are interested): + just the two terminals in which we are interested):</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" unknown off secure ttyd5 "/usr/libexec/getty std.19200" - </programlisting> Note that the second field---where we specify + </programlisting> + + <para>Note that the second field---where we specify what program to run---appears in quotes. This is important, otherwise the type argument to <command>getty</command> might be interpreted as the next field.</para> @@ -19105,8 +19132,7 @@ ttyd5 "/usr/libexec/getty std.19200" For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field.</para> - <para>Users will usually use the <emphasis - remap=tt>tset</emphasis> program in their + <para>Users will usually use the <command>tset</command> program in their <filename>.login</filename> or <filename>.profile</filename> files to check the terminal type and prompt for one if necessary. By setting a terminal type in the @@ -19122,12 +19148,12 @@ ttyd5 "/usr/libexec/getty std.19200" (although it can emulate others, we will leave it in Wyse-50 mode). The 286 PC is running Procomm which will be set to emulate a VT-100. Here are the pertinent yet unfinished entries - from the <filename>/etc/ttys</filename> file: + from the <filename>/etc/ttys</filename> file:</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 off secure ttyd5 "/usr/libexec/getty std.19200" vt100 - </programlisting></para> + </programlisting> </sect3> @@ -19137,19 +19163,19 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 <para>The next field in <filename>/etc/ttys</filename>, the fourth field, tells whether to enable the port. Putting <literal>on</literal> here will have the <command>init</command> process start the program in the - second field, <emphasis remap=tt>getty</emphasis>, which will + second field, <command>getty</command>, which will prompt for a login. If you put <literal>off</literal> in the fourth field, there will be no <command>getty</command>, and hence no logins on the port.</para> <para>So, naturally, you want an <literal>on</literal> in this field. Here again is the <filename>/etc/ttys</filename> - file. We have turned each port <literal>on</literal>. + file. We have turned each port <literal>on</literal>.</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 on secure ttyd5 "/usr/libexec/getty std.19200" vt100 on - </programlisting></para> + </programlisting> </sect3> @@ -19178,10 +19204,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on command.</para> <para>Because of this, you will have two records to help track - down possible compromises of root privileges: both the login and - the <emphasis remap=tt>su</emphasis> command make records in the - system log (and logins are also recorded in the <emphasis - remap=tt>wtmp</emphasis> file).</para> + down possible compromises of root privileges: both the <command>login</command> and + the <command>su</command> command make records in the + system log (and logins are also recorded in the <filename>wtmp</filename> file).</para> <para>By marking a port as secure, the terminal will allow root in. People who know the root password will just login as root. @@ -19197,12 +19222,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on <para>Here finally are the completed entries in the <filename>/etc/ttys</filename> file, with comments added to - describe where the terminals are: + describe where the terminals are:</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 on insecure # Kitchen ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - </programlisting></para> + </programlisting> </sect3> @@ -19221,7 +19246,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom signal.</para> <para>So, after you have saved your changes to - <filename>/etc/ttys</filename>, send SIGHUP to <command>init</command> by typing: + <filename>/etc/ttys</filename>, send <literal>SIGHUP</literal> to <command>init</command> by typing: <informalexample> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> </informalexample> (The <command>init</command> @@ -19242,7 +19267,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom could still go wrong while setting up a terminal. Here is a list of symptoms and some suggested fixes.</para> - <para> + <variablelist> <varlistentry><term>No login prompt appears</term> <listitem> @@ -19263,10 +19288,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>Make sure that a <command>getty</command> process is running and serving the terminal. Type + <informalexample> <screen>&prompt.root; <userinput>ps -axww|grep getty</userinput></screen> </informalexample> to get a list of running <command>getty</command> processes. You should see an entry for the terminal. For example, the display + <informalexample> <screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1</screen> </informalexample> shows that a <command>getty</command> is running on the second @@ -19287,7 +19314,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <listitem> <para>Make sure the terminal and FreeBSD agree on the bps rate and parity settings. Check the getty processes to - make sure the correct <emphasis remap=tt>getty</emphasis> + make sure the correct <replaceable>getty</replaceable> type is in use. If not, edit <filename>/etc/ttys</filename> and run <command>kill -HUP 1</command>.</para> @@ -19304,7 +19331,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -19343,8 +19370,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>First, it is assumed that you are using FreeBSD version 1.1 or higher (including versions 2.x). FreeBSD version 1.0 included two different serial drivers, which complicates the - situation. Also, the serial device driver (<emphasis - remap=tt>sio</emphasis>) has improved in every release of + situation. Also, the serial device driver (<devicename>sio</devicename>) has improved in every release of FreeBSD, so more recent versions of FreeBSD are assumed to have better and more efficient drivers than earlier versions.</para> @@ -19355,7 +19381,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>A quick rundown of terminology:</para> - <para> + <variablelist> <varlistentry><term>bps</term> <listitem> @@ -19387,7 +19413,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </varlistentry> </variablelist> - </para> + <para>If you need more information about these terms and data communications in general, the author remembers reading that @@ -19395,10 +19421,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom a good reference.</para> <para>When talking about communications data rates, the author - does not use the term <emphasis remap=bf>baud</emphasis>. Baud + does not use the term <quote>baud</quote>. Baud refers to the number of electrical state transitions that may be - made in a period of time, while <emphasis - remap=bf>bps</emphasis> (bits per second) is the <quote>correct</quote> + made in a period of time, while <quote>bps</quote> (bits per second) is the <quote>correct</quote> term to use (at least it does not seem to bother the curmudgeons quite a much).</para> @@ -19428,7 +19453,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>A background knowledge of these items is assumed</para> - <para> + <itemizedlist> <listitem> @@ -19449,7 +19474,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </itemizedlist> - </para> + <para>The first, connecting your modem, is usually simple - most straight-through serial cables work without any problems. You @@ -19457,7 +19482,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom male or female) on each end, and the cable must be a DCE-to-DTE cable with these signals wired:</para> - <para> + <itemizedlist> <listitem> @@ -19493,7 +19518,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </itemizedlist> - </para> + <para>FreeBSD needs the <abbrev>RTS</abbrev> and <abbrev>CTS</abbrev> signals for flow-control at speeds above @@ -19552,15 +19577,16 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom example). The command <command>ps ax</command> might show this:</para> - <para> + <informalexample> <screen> 4850 ?? I 0:00.09 /usr/libexec/getty V19200 ttyd0</screen> - </informalexample></para> + </informalexample> <para>When a user dials the modem's line and the modems connect, the <abbrev>CD</abbrev> line is asserted by the modem. The kernel - notices that carrier has been detected and completes <command>getty</command>'s open of the port. <command>getty</command> sends a <emphasis - remap=tt>login:</emphasis> prompt at the specified initial line + notices that carrier has been detected and completes + <command>getty</command>'s open of the + port. <command>getty</command> sends a <prompt>login:</prompt> prompt at the specified initial line speed. <command>getty</command> watches to see if legitimate characters are received, and, in a typical configuration, if it finds junk (probably due to the modem's @@ -19568,7 +19594,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom it receives reasonable characters.</para> <para>We hope <command>getty</command> finds the correct - speed and the user sees a <emphasis remap=tt>login:</emphasis> + speed and the user sees a <prompt>login:</prompt> prompt. After the user enters his/her login name, <command>getty</command> executes <filename>/usr/bin/login</filename>, which completes the login by asking for the user's password and then starting the user's @@ -19583,9 +19609,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>FreeBSD kernels typically come prepared to search for four serial ports, known in the PC-DOS world as - <filename>COM1:</filename>, <filename>COM2:</filename>, - <filename>COM3:</filename>, and <filename - remap="tt">COM4:</filename>. FreeBSD can presently also handle + <devicename>COM1:</devicename>, <devicename>COM2:</devicename>, + <devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle <quote>dumb</quote> multiport serial interface cards, such as the Boca Board 1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information if you have a multiport serial card). The default kernel only @@ -19593,20 +19618,20 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>To see if your kernel recognizes any of your serial ports, watch for messages while the kernel is booting, or use the - <emphasis remap="tt">/sbin/dmesg</emphasis> command to replay the + <command>/sbin/dmesg</command> command to replay the kernel's boot messages. In particular, look for messages that start with the characters <literal>sio</literal>. Hint: to view just the messages that have the word <literal>sio</literal>, use the command:</para> - <para> + <informalexample> <screen>&prompt.root; <userinput>/sbin/dmesg | grep 'sio'</userinput></screen> - </informalexample></para> + </informalexample> <para>For example, on a system with four serial ports, these are the serial-port specific kernel boot messages:</para> - <para> + <informalexample> <screen>sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -19616,7 +19641,7 @@ sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A</screen> - </informalexample></para> + </informalexample> <para>If your kernel does not recognize all of your serial ports, you will probably need to configure a custom FreeBSD kernel for @@ -19630,7 +19655,7 @@ sio3: type 16550A</screen> <filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> for example being <filename>i386</filename>] for more information on configuring and building kernels. You may have to unpack the kernel source distribution if have not installed the system sources already (<filename>srcdist/srcsys.??</filename> in FreeBSD 1.1, <filename>srcdist/sys.??</filename> in FreeBSD 1.1.5.1, or the entire source distribution in FreeBSD 2.0) to be able to configure and build kernels.</para> <para>Create a kernel configuration file for your system (if you - have not already) by <emphasis remap=tt>cd</emphasis>ing to + have not already) by <command>cd</command>ing to <filename>/sys/i386/conf</filename>. Then, if you are creating a new custom configuration file, copy the file <filename>GENERICAH</filename> (or <filename>GENERICBT</filename>, @@ -19662,8 +19687,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <symbol>IO_COM4</symbol> is <literal>0x2e8</literal>, which are fairly common port addresses for their respective serial ports; interrupts 4, 3, 5, and 9 are fairly common interrupt request - lines. Also note that regular serial ports <emphasis - remap=bf>cannot</emphasis> share interrupts on ISA-bus PCs + lines. Also note that regular serial ports <emphasis>cannot</emphasis> share interrupts on ISA-bus PCs (multiport boards have on-board electronics that allow all the 16550A's on the board to share one or two interrupt request lines).</para> @@ -19683,18 +19707,17 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <para>Most devices in the kernel are accessed through <quote>device special files</quote>, which are located in the - <filename>/dev</filename> directory. The <emphasis - remap=tt>sio</emphasis> devices are accessed through the - <filename>/dev/ttyd?</filename> (dial-in) and - <filename>/dev/cua0?</filename> (call-out) devices. On FreeBSD + <filename>/dev</filename> directory. The <devicename>sio</devicename> devices are accessed through the + <filename>/dev/ttyd<replaceable>?</replaceable></filename> (dial-in) and + <filename>/dev/cua0<replaceable>?</replaceable></filename> (call-out) devices. On FreeBSD version 1.1.5 and higher, there are also initialization devices - (<filename>/dev/ttyid?</filename> and - <filename>/dev/cuai0?</filename>) and locking devices - (<filename>/dev/ttyld?</filename> and - <filename>/dev/cual0?</filename>). The initialization devices are + (<filename>/dev/ttyid<replaceable>?</replaceable></filename> and + <filename>/dev/cuai0<replaceable>?</replaceable></filename>) and locking devices + (<filename>/dev/ttyld<replaceable>?</replaceable></filename> and + <filename>/dev/cual0<replaceable>?</replaceable></filename>). The initialization devices are used to initialize communications port parameters each time a port - is opened, such as <emphasis remap=tt>crtscts</emphasis> for - modems which use <filename>CTS/RTS</filename> signaling for flow + is opened, such as <literal remap="tt">crtscts</literal> for + modems which use <literal>CTS/RTS</literal> signaling for flow control. The locking devices are used to lock flags on ports to prevent users or programs changing certain parameters; see the manual pages <citerefentry><refentrytitle>termios</refentrytitle><manvolnum>4</manvolnum></citerefentry>, <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry>, and <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for @@ -19705,23 +19728,23 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <sect3> <title>Making Device Special Files</title> - <para>A shell script called <filename>MAKEDEV</filename> in the + <para>A shell script called <command>MAKEDEV</command> in the <filename>/dev</filename> directory manages the device special files. (The manual page for <citerefentry><refentrytitle>MAKEDEV</refentrytitle><manvolnum>8</manvolnum></citerefentry> on FreeBSD 1.1.5 is fairly bogus in its discussion of <acronym>COM</acronym> ports, so ignore it.) To use - <filename>MAKEDEV</filename> to make dialup device special files - for <filename>COM1:</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue + <command>MAKEDEV</command> to make dialup device special files + for <devicename>COM1:</devicename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue the command <command>MAKEDEV ttyd0</command>. Likewise, to make dialup device special files for - <filename>COM2:</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> + <devicename>COM2:</devicename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> - <para><filename>MAKEDEV</filename> not only creates the - <filename>/dev/ttyd?</filename> device special files, but also - creates the <filename>/dev/cua0?</filename> (and all of the + <para><command>MAKEDEV</command> not only creates the + <filename>/dev/ttyd<replaceable>?</replaceable></filename> device special files, but also + creates the <filename>/dev/cua0<replaceable>?</replaceable></filename> (and all of the initializing and locking special files under FreeBSD 1.1.5 and up) and removes the hardwired terminal special file - <filename>/dev/tty0?</filename>, if it exists.</para> + <filename>/dev/tty0<replaceable>?</replaceable></filename>, if it exists.</para> <para>After making new device special files, be sure to check the permissions on the files (especially the @@ -19738,9 +19761,8 @@ crw-rw---- 1 uucp dialer 28, 161 Feb 15 14:38 /dev/cuai01 crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> </informalexample> - <para>These permissions allow the user <emphasis - remap=tt>uucp</emphasis> and users in the group <emphasis - remap=tt>dialer</emphasis> to use the call-out devices.</para> + <para>These permissions allow the user <username>uucp</username> + and users in the group <username>dialer</username> to use the call-out devices.</para> </sect3> </sect2> @@ -19754,9 +19776,8 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> <filename>/etc/gettytab</filename>, contains configuration information for the <filename>/usr/libexec/getty</filename> daemon. Second, <filename>/etc/ttys</filename> holds information - that tells <filename>/sbin/init</filename> what <emphasis - remap=tt>tty</emphasis> devices should have <emphasis - remap=tt>getty</emphasis> processes running on them. Lastly, + that tells <filename>/sbin/init</filename> what + <filename>tty</filename> devices should have <command>getty</command> processes running on them. Lastly, you can place port initialization commands in the <filename>/etc/rc.serial</filename> script if you have FreeBSD 1.1.5.1 or higher; otherwise, you can initialize ports in the @@ -19778,14 +19799,14 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> the modem run its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the modem's RS-232 interface run at 2400 bps. Because <command>getty</command> does not understand - any particular modem's connection speed reporting, <command>getty</command> gives a <emphasis - remap=tt>login:</emphasis> message at an initial speed and + any particular modem's connection speed reporting, + <command>getty</command> gives a <prompt>login:</prompt> message at an initial speed and watches the characters that come back in response. If the user sees junk, it is assumed that they know they should press the - <emphasis remap=tt><Enter></emphasis> key until they see a + <literal><Enter></literal> key until they see a recognizable prompt. If the data rates do not match, <command>getty</command> sees anything the user types as - <quote>junk</quote>, tries going to the next speed and gives the <emphasis - remap=tt>login:</emphasis> prompt again. This procedure can + <quote>junk</quote>, tries going to the next speed and gives the + <prompt>login:</prompt> prompt again. This procedure can continue ad nauseum, but normally only takes a keystroke or two before the user sees a good prompt. Obviously, this login sequence does not look as clean as the former <quote>locked-speed</quote> method, but @@ -19861,8 +19882,8 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ </programlisting> <para>On FreeBSD 1.1.5 and later, this will result in 8-bit, no - parity connections. Under FreeBSD 1.1, add <literal>:np:</literal> parameters to the <emphasis - remap=tt>std.<replaceable>xxx</replaceable></emphasis> + parity connections. Under FreeBSD 1.1, add + <literal>:np:</literal> parameters to the <literal>std.<replaceable>xxx</replaceable></literal> entries at the top of the file for 8 bits, no parity; otherwise, the default is 7 bits, even parity.</para> @@ -19870,10 +19891,10 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ Kbps (for a V.32bis connection), then cycles through 9600 bps (for V.32), 2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate cycling is implemented with the - <literal>nx=</literal> (<emphasis remap=bf>next - table</emphasis>) capability. Each of the lines uses a - <literal>tc=</literal> (<emphasis remap=bf>table - continuation</emphasis>) entry to pick up the rest of the + <literal>nx=</literal> (<quote>next + table</quote>) capability. Each of the lines uses a + <literal>tc=</literal> (<quote>table + continuation</quote>) entry to pick up the rest of the <quote>standard</quote> settings for a particular data rate.</para> <para>If you have a 28.8 Kbps modem and/or you want to take @@ -19910,12 +19931,11 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ id="dialup-ttys"> <title><filename>/etc/ttys</filename></title> - <para><filename>/etc/ttys</filename> is the list of <emphasis - remap=tt>ttys</emphasis> for <command>init</command> to monitor. + <para><filename>/etc/ttys</filename> is the list of <filename>ttys</filename> for <command>init</command> to monitor. <filename>/etc/ttys</filename> also provides security information to <command>login</command> (user - <emphasis remap=tt>root</emphasis> may only login on ttys marked - <emphasis remap=tt>secure</emphasis>). See the manual page for + <username>root</username> may only login on ttys marked + <literal>secure</literal>). See the manual page for <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more information.</para> @@ -19933,14 +19953,14 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <para>The first item in the above line is the device special file for this entry - <literal>ttyd0</literal> means <filename>/dev/ttyd0</filename> is the file that this <command>getty</command> will be watching. The second item, - <filename>"/usr/libexec/getty - <replaceable>xxx</replaceable>"</filename> - (<emphasis>xxx</emphasis> will be replaced by the initial - <emphasis remap=tt>gettytab</emphasis> capability) is the + <literal>"/usr/libexec/getty + <replaceable>xxx</replaceable>"</literal> + (<replaceable>xxx</replaceable> will be replaced by the initial + <filename>gettytab</filename> capability) is the process <command>init</command> will run on the device. The third item, <literal>dialup</literal>, - is the default terminal type. The fourth parameter, <literal>on</literal>, indicates to <emphasis - remap=tt>init</emphasis> that the line is operational. There + is the default terminal type. The fourth parameter, + <literal>on</literal>, indicates to <command>init</command> that the line is operational. There can be a fifth parameter, <literal>secure</literal>, but it should only be used for terminals which are physically secure (such as the system console).</para> @@ -19957,13 +19977,13 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <para>After you have made changes to <filename>/etc/ttys</filename>, you may send the <command>init</command> process a <acronym>HUP</acronym> - signal to re-read the file. You can use the command</para> + signal to re-read the file. You can use the command <informalexample> <screen>&prompt.root; <userinput>kill -1 1</userinput></screen> </informalexample> - <para>to send the signal. If this is your first time setting up + to send the signal. If this is your first time setting up the system, though, you may want to wait until your modem(s) are properly configured and connected before signaling <command>init</command>.</para> @@ -19971,19 +19991,16 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <sect4> <title>Locked-Speed Config</title> - <para>For a locked-speed configuration, your <emphasis - remap=tt>ttys</emphasis> entry needs to have a fixed-speed - entry provided to <emphasis remap=tt>getty</emphasis>. For a - modem whose port speed is locked at 19.2 Kbps, the <emphasis - remap=tt>ttys</emphasis> entry might look like this:</para> + <para>For a locked-speed configuration, your <filename>ttys</filename> entry needs to have a fixed-speed + entry provided to <command>getty</command>. For a + modem whose port speed is locked at 19.2 Kbps, the <filename>ttys</filename> entry might look like this:</para> <programlisting> ttyd0 "/usr/libexec/getty std.19200" dialup on </programlisting> <para>If your modem is locked at a different data rate, - substitute the appropriate name for the <emphasis - remap=tt>std.<replaceable>speed</replaceable></emphasis> + substitute the appropriate name for the <literal>std.<replaceable>speed</replaceable></literal> entry for <literal>std.19200</literal> from <filename>/etc/gettytab</filename> for your modem's data rate.</para> @@ -19993,14 +20010,13 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on <sect4> <title>Matching-Speed Config</title> - <para>In a matching-speed configuration, your <emphasis - remap=tt>ttys</emphasis> entry needs to reference the + <para>In a matching-speed configuration, your <filename>ttys</filename> entry needs to reference the appropriate beginning <quote>auto-baud</quote> (sic) entry in <filename>/etc/gettytab</filename>. For example, if you added the above suggested entry for a matching-speed modem that - starts at 19.2 Kbps (the <emphasis - remap=tt>gettytab</emphasis> entry containing the <literal>V19200</literal> starting point), your <emphasis - remap=tt>ttys</emphasis> entry might look like this:</para> + starts at 19.2 Kbps (the <filename>gettytab</filename> entry + containing the <literal>V19200</literal> starting point), your + <filename>ttys</filename> entry might look like this:</para> <programlisting> ttyd0 "/usr/libexec/getty V19200" dialup on @@ -20032,14 +20048,13 @@ stty -f /dev/ttyid1 crtscts stty -f /dev/cuai01 crtscts </programlisting> - <para>which sets the <emphasis remap=tt>termios</emphasis> flag - <emphasis remap=tt>crtscts</emphasis> on serial port #1's - (<emphasis remap=tt>COM2:</emphasis>) dialin and dialout + <para>This sets the <literal>termios</literal> flag + <literal>crtscts</literal> on serial port #1's + (<devicename>COM2:</devicename>) dialin and dialout initialization devices.</para> <para>On an old FreeBSD 1.1 system, these entries were added to - <filename>/etc/rc.local</filename> to set the <emphasis - remap=tt>crtscts</emphasis> flag on the devices:</para> + <filename>/etc/rc.local</filename> to set the <literal>crtscts</literal> flag on the devices:</para> <programlisting> # Set serial ports to use RTS/CTS flow control @@ -20067,7 +20082,7 @@ stty -f /dev/ttyd3 crtscts same communications speed as the initial speed <command>getty</command> will use and configure the modem's non-volatile RAM to match these requirements:</para> - <para> + <itemizedlist> <listitem> @@ -20100,7 +20115,7 @@ stty -f /dev/ttyd3 crtscts </listitem> </itemizedlist> - </para> + <para>Please read the documentation for your modem to find out what commands and/or DIP switch settings you need to give it.</para> @@ -20123,7 +20138,7 @@ AT&C1&D2&H1&I0&R2&W switches that need to be set; for other modems, perhaps you can use these settings as an example:</para> - <para> + <itemizedlist> <listitem> @@ -20160,11 +20175,11 @@ AT&C1&D2&H1&I0&R2&W </listitem> </itemizedlist> - </para> + <para>Result codes should be disabled/suppressed for dialup modems - to avoid problems that can occur if <command>getty</command> mistakenly gives a <emphasis - remap=tt>login:</emphasis> prompt to a modem that is in command + to avoid problems that can occur if <command>getty</command> + mistakenly gives a <prompt>login:</prompt> prompt to a modem that is in command mode and the modem echoes the command or returns a result code. I have heard this sequence can result in a extended, silly conversation between <command>getty</command> and the @@ -20210,11 +20225,11 @@ AT&B2&W <para>Most high-speed modems provide commands to view the modem's current operating parameters in a somewhat human-readable fashion. On the USR Sportster 14,400 external modems, the - command <emphasis remap=tt>ATI5</emphasis> displays the settings + command <command>ATI5</command> displays the settings that are stored in the non-volatile RAM. To see the true operating parameters of the modem (as influenced by the USR's DIP switch settings), use the commands <command>ATZ</command> - and then <emphasis remap=tt>ATI4</emphasis>.</para> + and then <command>ATI4</command>.</para> <para>If you have a different brand of modem, check your modem's manual to see how to double-check your modem's configuration @@ -20236,7 +20251,7 @@ AT&B2&W <para>Hook up your modem to your FreeBSD system, boot the system, and, if your modem has status indication lights, watch to see whether the modem's <abbrev>DTR</abbrev> indicator lights when - the <emphasis remap=tt>login:</emphasis> prompt appears on the + the <prompt>login:</prompt> prompt appears on the system's console - if it lights up, that should mean that FreeBSD has started a <command>getty</command> process on the appropriate communications port and is waiting @@ -20253,13 +20268,13 @@ AT&B2&W 115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen> </informalexample> - <para>If you see something different, like this:</para> + <para>If you see something different, like this: <informalexample> <screen> 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyd0</screen> </informalexample> - <para>and the modem has not accepted a call yet, this means that + and the modem has not accepted a call yet, this means that <command>getty</command> has completed its open on the communications port. This could indicate a problem with the cabling or a mis-configured modem, because <command>getty</command> should not be able to open the @@ -20267,7 +20282,7 @@ AT&B2&W has been asserted by the modem.</para> <para>If you do not see any <command>getty</command> - processes waiting to open the desired <filename>ttyd?</filename> + processes waiting to open the desired <filename>ttyd<replaceable>?</replaceable></filename> port, double-check your entries in <filename>/etc/ttys</filename> to see if there are any mistakes there. Also, check the log file @@ -20288,21 +20303,19 @@ AT&B2&W <para>Try dialing into the system; be sure to use 8 bits, no parity, 1 stop bit on the remote system. If you do not get a - prompt right away, or get garbage, try pressing <emphasis - remap=tt><Enter></emphasis> about once per second. If - you still do not see a <emphasis remap=tt>login:</emphasis> + prompt right away, or get garbage, try pressing <literal><Enter></literal> about once per second. If + you still do not see a <prompt>login:</prompt> prompt after a while, try sending a <command>BREAK</command>. If you are using a high-speed modem to do the dialing, try dialing again after locking the dialing modem's interface speed - (via <emphasis remap=tt>AT&B1</emphasis> on a USR Sportster, + (via <command>AT&B1</command> on a USR Sportster, for example).</para> - <para>If you still cannot get a <emphasis - remap=tt>login:</emphasis> prompt, check + <para>If you still cannot get a <prompt>login:</prompt> prompt, check <filename>/etc/gettytab</filename> again and double-check that</para> - <para> + <itemizedlist> <listitem> @@ -20322,7 +20335,7 @@ AT&B2&W </listitem> </itemizedlist> - </para> + <para>If you dial but the modem on the FreeBSD system will not answer, make sure that the modem is configured to answer the @@ -20345,7 +20358,7 @@ AT&B2&W <para>Thanks to these people for comments and advice:</para> - <para> + <variablelist> <varlistentry><term>&a.kelly;</term> <listitem> @@ -20353,7 +20366,7 @@ AT&B2&W </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -28080,7 +28093,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # Date created: 5 December 1994 # Whom: asami # -# $Id: handbook.sgml,v 1.39 1998-10-21 22:02:39 nik Exp $ +# $Id: handbook.sgml,v 1.40 1998-10-21 22:05:23 nik Exp $ # DISTNAME= oneko-1.1b diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index c62020ea09..4b74e46c0e 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -15316,7 +15316,7 @@ disk wd3 at wdc1 drive 1 jargon in use to abbreviate the different bus types. A small list:</para> - <para> + <itemizedlist> <listitem> @@ -15340,7 +15340,7 @@ disk wd3 at wdc1 drive 1 </listitem> </itemizedlist> - </para> + <para>With a minor amount of imagination one can usually imagine what is meant.</para> @@ -15604,8 +15604,7 @@ disk wd3 at wdc1 drive 1 the highest SCSI ID will win. This also means that the SCSI host adapter usually uses target ID 7. Note however that the lower 8 IDs have higher priorities than the higher 8 IDs on a - wide-SCSI bus. Thus, the order of target IDs is: <emphasis - remap=tt>[7 6 .. 1 0 15 14 .. 9 8]</emphasis> on a wide-SCSI + wide-SCSI bus. Thus, the order of target IDs is: [7 6 .. 1 0 15 14 .. 9 8] on a wide-SCSI system. (If you you are wondering why the lower 8 have higher priority, read the previous paragraph for a hint.)</para> @@ -15643,7 +15642,7 @@ disk wd3 at wdc1 drive 1 ultimately the reliability of it all are tightly related to linear bus rule.</para> - <para><emphasis remap=bf>Stick to the linear bus + <para><emphasis>Stick to the linear bus rule!</emphasis></para> </sect4> @@ -15708,9 +15707,8 @@ disk wd3 at wdc1 drive 1 of a jumper or software setup selection, to switch the translation the SCSI BIOS uses.</para> - <para>It is very important that <emphasis - remap=bf>all</emphasis> operating systems on the disk use - the <emphasis remap=bf>same translation</emphasis> to get the + <para>It is very important that <emphasis>all</emphasis> operating systems on the disk use + the <emphasis>same translation</emphasis> to get the right idea about where to find the relevant partitions. So, when installing FreeBSD you must answer any questions about heads/cylinders etc using the translated values your host @@ -15721,7 +15719,7 @@ disk wd3 at wdc1 drive 1 others partitions. Using fdisk you should be able to see all partitions.</para> - <para>You might have heard some talk of 'lying' devices? Older + <para>You might have heard some talk of <quote>lying</quote> devices? Older FreeBSD kernels used to report the geometry of SCSI disks when booting. An example from one of my systems:</para> @@ -15730,12 +15728,12 @@ disk wd3 at wdc1 drive 1 sd0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512</screen> </informalexample> - <para>Newer kernels usually do not report this information. e.g. + <para>Newer kernels usually do not report this information. e.g.</para> <informalexample> <screen>(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen> - </informalexample></para> + </informalexample> <para>Why has this changed?</para> @@ -15812,7 +15810,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen> </note> <para>An example loosely based on the FreeBSD 2.2.5-Release - kernel config file LINT with some added comments (between + kernel config file <filename>LINT</filename> with some added comments (between []):</para> <programlisting> @@ -15861,9 +15859,9 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <emphasis>only</emphasis> attach them when they match the target ID and LUN specified on the corresponding bus.</para> - <para>Wired down devices get 'first shot' at the unit numbers so - the first non 'wired down' device, is allocated the unit - number one greater than the highest 'wired down' unit number + <para>Wired down devices get <quote>first shot</quote> at the unit numbers so + the first non <quote>wired down</quote> device, is allocated the unit + number one greater than the highest <quote>wired down</quote> unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 is wired down to unit number 1.</para> @@ -15880,7 +15878,7 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <para>Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first - example is that devices are not 'wired down'. 'Wired down' + example is that devices are not <quote>wired down</quote>. <quote>Wired down</quote> means that you specify which SCSI target belongs to which device.</para> @@ -15921,13 +15919,13 @@ device cd0 #Only need one of these, the code dynamically grows devices of a specific type (e.g. sd disks) are found than are configured in the booting kernel, the system will simply allocate more devices, incrementing the unit number starting - at the last number 'wired down'. If there are no 'wired down' + at the last number <quote>wired down</quote>. If there are no <quote>wired down</quote> devices then counting starts at unit 0.</para> - <para>Use <emphasis remap=tt>man 4 scsi</emphasis> to check for + <para>Use <command>man 4 scsi</command> to check for the latest info on the SCSI subsystem. For more detailed info - on host adapter drivers use eg <emphasis remap=tt>man 4 - ahc</emphasis> for info on the Adaptec 294x driver.</para> + on host adapter drivers use eg <command>man 4 + ahc</command> for info on the Adaptec 294x driver.</para> </sect4> @@ -15969,7 +15967,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device correctly is no easy task. Some vendors do a better job then others.</para> - <para>This is exactly where the 'rogue' devices come into view. + <para>This is exactly where the <quote>rogue</quote> devices come into view. Rogues are devices that are recognized by the FreeBSD kernel as behaving slightly (...) non-standard. Rogue devices are reported by the kernel when booting. An example for two of my @@ -16000,7 +15998,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> this is done.</para> <para>This scheme works fine, but keep in mind that it of course - only works for devices that are KNOWN to be weird. If you are + only works for devices that are known to be weird. If you are the first to connect your bogus Mumbletech SCSI CD-ROM you might be the one that has to define which workaround is needed.</para> @@ -16027,14 +16025,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> around this problem you must add an appropriate entry in /sys/scsi/scsiconf.c and rebuild your kernel.</para> - <para>Look for a struct that is initialized like below: + <para>Look for a struct that is initialized like below:</para> <programlisting> { T_DIRECT, T_FIXED, "MAXTOR", "XT-4170S", "B5A", "mx1", SC_ONE_LU } - </programlisting></para> + </programlisting> <para>For you Mumbletech BRIDGE2000 that has more than one LUN, acts as a SCSI disk and has firmware revision 123 you would @@ -16067,13 +16065,13 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> TCQ function is indispensable to take advantage of the device's inherent parallelism.</para> - <para>Each I/O request is uniquely identified by a 'tag' (hence + <para>Each I/O request is uniquely identified by a <quote>tag</quote> (hence the name tagged command queuing) and this tag is used by FreeBSD to see which I/O in the device drivers queue is reported as complete by the device.</para> <para>It should be noted however that TCQ requires device driver - support and that some devices implemented it 'not quite right' + support and that some devices implemented it <quote>not quite right</quote> in their firmware. This problem bit me once, and it leads to highly mysterious problems. In such cases, try to disable TCQ.</para> @@ -16126,7 +16124,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed most common SCSI problems and their solutions. It is by no means complete.</para> - <para> + <itemizedlist> <listitem> @@ -16170,22 +16168,22 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <listitem> <para>If you can compile a kernel, make one with the - SCSIDEBUG option, and try accessing the device with + <literal>SCSIDEBUG</literal> option, and try accessing the device with debugging turned on for that device. If your device does not even probe at startup, you may have to define the address of the device that is failing, and the desired debug level in <filename>/sys/scsi/scsidebug.h</filename>. If it probes but just does not work, you can use the <citerefentry><refentrytitle>scsi</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to dynamically set a - debug level to it in a running kernel (if SCSIDEBUG is - defined). This will give you COPIOUS debugging output with - which to confuse the gurus. see <emphasis remap=tt>man 4 - scsi</emphasis> for more exact information. Also look at - <emphasis remap=tt>man 8 scsi</emphasis>.</para> + debug level to it in a running kernel (if <literal>SCSIDEBUG</literal> is + defined). This will give you <emphasis>copious</emphasis> debugging output with + which to confuse the gurus. see <command>man 4 + scsi</command> for more exact information. Also look at + <command>man 8 scsi</command>.</para> </listitem> </itemizedlist> - </para> + </sect3> @@ -16197,18 +16195,37 @@ options "TUNE_1542" #dynamic tune of bus DMA speed want to have the official standard at hand:</para> <para>Approved American National Standards can be purchased from - ANSI at 11 West 42nd Street, 13th Floor, New York, NY 10036, - Sales Dept: (212) 642-4900. You can also buy many ANSI + ANSI at + + <address> + <otheraddr>13th Floor</otheraddr> + <street>11 West 42nd Street</street> + <city>New York</city> + <state>NY</state> <postcode>10036</postcode> + Sales Dept: <phone>(212) 642-4900</phone> + </address> + </para> + + <para>You can also buy many ANSI standards and most committee draft documents from Global - Engineering Documents, 15 Inverness Way East, Englewood, CO - 80112-5704, Phone: (800) 854-7179, Outside USA and Canada: (303) - 792-2181, FAX: (303) 792- 2192.</para> + Engineering Documents, + + <address> + <street>15 Inverness Way East</street> + <city>Englewood</city> + <state>CO</state>, <postcode>80112-5704</postcode> + Phone: <phone>(800) 854-7179</phone> + Outside USA and Canada: <phone>(303) 792-2181</phone> + Fax: <fax>(303) 792- 2192</fax> + </address> + </para> <para>Many X3T10 draft documents are available electronically on - the SCSI BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous + the SCSI BBS (719-574-0424) and on the <hostid role="fqdn">ncrinfo.ncr.com</hostid> anonymous ftp site.</para> - <para>Latest X3T10 committee documents are: + <para>Latest X3T10 committee documents are:</para> + <itemizedlist> <listitem> @@ -16236,8 +16253,11 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Interface Module (CAM) [X3T10/792D Rev 11]</para> </listitem> - </itemizedlist> Other publications that might provide you with - additional information are: + </itemizedlist> + + <para>Other publications that might provide you with + additional information are:</para> + <itemizedlist> <listitem> @@ -16281,7 +16301,6 @@ options "TUNE_1542" #dynamic tune of bus DMA speed </listitem> </itemizedlist> - </para> <para>On Usenet the newsgroups <ulink URL="news:comp.periphs.scsi">comp.periphs.scsi</ulink> and @@ -16477,10 +16496,9 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <title> General tape access commands</title> <para><citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> provides generic access to the tape - drives. Some of the more common commands are <emphasis - remap=tt>rewind</emphasis>, <emphasis - remap=tt>erase</emphasis>, and <emphasis - remap=tt>status</emphasis>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> + drives. Some of the more common commands are + <command>rewind</command>, <command>erase</command>, and + <command>status</command>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page for a detailed description.</para> </sect3> @@ -16717,7 +16735,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>This drive was repackaged by Sun Microsystems as model 411.</para> - <para>Reported by: Bob Bishop rb@gid.co.uk</para> + <para>Reported by: Bob Bishop <email>rb@gid.co.uk</email></para> </sect4> @@ -16738,7 +16756,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> - <para>Reported by: Philippe Regnauld regnauld@hsc.fr</para> + <para>Reported by: Philippe Regnauld <email>regnauld@hsc.fr</email></para> </sect4> @@ -16778,10 +16796,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> <para>Reported by: Pedro A M Vazquez - vazquez@IQM.Unicamp.BR</para> + <email>vazquez@IQM.Unicamp.BR</email></para> <para>Mike Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -16826,7 +16844,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive uses QIC-80 tape cartridges.</para> - <para>Reported by: Mark Hannon mark@seeware.DIALix.oz.au</para> + <para>Reported by: Mark Hannon <email>mark@seeware.DIALix.oz.au</email></para> </sect4> @@ -16846,7 +16864,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive uses QIC-3080 tape cartridges.</para> - <para>Reported by: Thomas S. Traylor tst@titan.cs.mci.com</para> + <para>Reported by: Thomas S. Traylor <email>tst@titan.cs.mci.com</email></para> </sect4> @@ -16924,7 +16942,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Right now, this drive cannot really be recommended for FreeBSD.</para> - <para>Reported by: Bob Beaulieu ez@eztravel.com</para> + <para>Reported by: Bob Beaulieu <email>ez@eztravel.com</email></para> </sect4> @@ -16953,7 +16971,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> <para>Reported by: Mike Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -16971,7 +16989,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Data transfer rate is 300kB/s.</para> - <para>Reported by: Greg Lehey grog@lemis.de</para> + <para>Reported by: Greg Lehey <email>grog@lemis.de</email></para> </sect4> @@ -16993,7 +17011,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Data transfer rate is 300kB/s.</para> - <para>Reported by: Glen Foster gfoster@gfoster.com</para> + <para>Reported by: Glen Foster <email>gfoster@gfoster.com</email></para> </sect4> @@ -17019,7 +17037,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive has a block of 8 dip switches. The proper settings for FreeBSD are: 1 ON; 2 ON; 3 OFF; 4 ON; 5 ON; 6 ON; - 7 ON; 8 ON. + 7 ON; 8 ON.</para> <informaltable frame="none"> <tgroup cols="3"> @@ -17061,7 +17079,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed </row> </tbody> </tgroup> - </informaltable></para> + </informaltable> <para>Switch 3 controls MRS (Media Recognition System). MRS tapes have stripes on the transparent leader. These identify @@ -17113,7 +17131,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed nearing the end of its useful life, steady indicates an hard fault. (factory service required?)</para> - <para>Reported by Gary Crutcher gcrutchr@nightflight.com</para> + <para>Reported by Gary Crutcher <email>gcrutchr@nightflight.com</email></para> </sect4> @@ -17206,7 +17224,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Data transfer rate is 160kB/s.</para> <para>Reported by: mark thompson - mark.a.thompson@pobox.com</para> + <email>mark.a.thompson@pobox.com</email></para> </sect4> @@ -17236,7 +17254,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" returned 5 of these drives. None lasted more than 9 months.</para> - <para>Reported by: David Dawes dawes@rf900.physics.usyd.edu.au + <para>Reported by: David Dawes <email>dawes@rf900.physics.usyd.edu.au</email> (9 09)</para> </sect4> @@ -17340,7 +17358,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" firmware EPROM of these units will solve the problem.</para> <para>Reported by: Michael Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -17418,8 +17436,8 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Other firmware revisions that are known to work are: M75D</para> - <para>Reported by: Marc van Kempen marc@bowtie.nl <literal>REV73R1</literal> - Andrew Gordon Andrew.Gordon@net-tel.co.uk <literal>M75D</literal></para> + <para>Reported by: Marc van Kempen <email>marc@bowtie.nl</email> <literal>REV73R1</literal> + Andrew Gordon <email>Andrew.Gordon@net-tel.co.uk</email> <literal>M75D</literal></para> </sect4> @@ -17438,7 +17456,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Data transfer rate is 150kB/s.</para> - <para>Reported by: Tony Kimball alk@Think.COM</para> + <para>Reported by: Tony Kimball <email>alk@Think.COM</email></para> </sect4> </sect3> @@ -17658,11 +17676,12 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>The first time that you try to read or write a new, completely blank tape, the operation will fail. The console - messages should be similar to: + messages should be similar to:</para> + <informalexample> <screen>st0(ncr1:4:0): NOT READY asc:4,1 st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> - </informalexample></para> + </informalexample> <para>The tape does not contain an Identifier Block (block number 0). All QIC tape drives since the adoption of QIC-525 standard @@ -17676,10 +17695,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <para>Re-insert the tape and <citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> data to the tape.</para> - <para><citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> will report <emphasis - remap=tt>DUMP: End of tape detected</emphasis> and the console - will show: <emphasis remap=tt>HARDWARE FAILURE info:280 - asc:80,96</emphasis></para> + <para><citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> will report <errorname>DUMP: End of tape detected</errorname> and the console + will show: <errorname>HARDWARE FAILURE info:280 + asc:80,96</errorname></para> <para>rewind the tape using: <command>mt rewind</command></para> @@ -17724,7 +17742,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> rely upon <citerefentry><refentrytitle>rcmd</refentrytitle><manvolnum>3</manvolnum></citerefentry> and <citerefentry><refentrytitle>ruserok</refentrytitle><manvolnum>3</manvolnum></citerefentry> to access the remote tape drive. Therefore, the user performing the backup must have - <emphasis remap=tt>rhosts</emphasis> access to the remote + <filename>rhosts</filename> access to the remote computer. The arguments to <citerefentry><refentrytitle>rdump</refentrytitle><manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rrestore</refentrytitle><manvolnum>8</manvolnum></citerefentry> must suitable to use on the remote computer. (e.g. When <command>rdump</command>'ing from a FreeBSD computer to an @@ -17733,8 +17751,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <informalexample> <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</userinput></screen> </informalexample>) Beware: - there are security implications to allowing <emphasis - remap=tt>rhosts</emphasis> commands. Evaluate your + there are security implications to allowing <filename>rhosts</filename> commands. Evaluate your situation carefully.</para> </sect4> @@ -17881,14 +17898,18 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <para>There are only four steps that you need to perform in preparation for any disaster that may occur.</para> - - <para>First, print the disklabel from each of your disks - (<command>e.g. disklabel sd0 | lpr</command>), your + + <procedure> + <step> + <para>Print the disklabel from each of your disks + (e.g., <command>disklabel sd0 | lpr</command>), your filesystem table (<filename>/etc/fstab</filename>) and all boot messages, two copies of each.</para> - - <para>Second, determine the boot and fixit floppies (boot.flp - and fixit.flp) have all your devices. The easiest way to + </step> + + <step> + <para>Determine the boot and fixit floppies (<filename>boot.flp</filename> + and <filename>fixit.flp</filename>) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot messages. If all your devices are listed and functional, skip on to step three.</para> @@ -17901,12 +17922,16 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> whichever backup program you use. These programs must be statically linked. If you use <citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry>, the floppy must contain <citerefentry><refentrytitle>restore</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para> - - <para>Third, create backup tapes regularly. Any changes that you + </step> + + <step> + <para>Create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. Write-protect the backup tapes.</para> - - <para>Fourth, test the floppies (either boot.flp and fixit.flp + </step> + + <step> + <para>Test the floppies (either <filename>boot.flp</filename> and <filename>fixit.flp</filename> or the two custom bootable floppies you made in step two.) and backup tapes. Make notes of the procedure. Store these notes with the bootable floppy, the printouts and the backup @@ -18078,7 +18103,8 @@ chmod 644 /mnt/etc/passwd # /sbin/umount /mnt </programlisting></para> - + </step> + </procedure> </sect4> <sect4> @@ -18093,13 +18119,13 @@ chmod 644 /mnt/etc/passwd <para>If your hardware is okay, check your floppies. If you are using a custom boot floppy, boot single-user (type <option>-s</option> at the - "boot:" prompt). Skip the following paragraph.</para> + <prompt>boot:</prompt> prompt). Skip the following paragraph.</para> <para>If you are using the boot.flp and fixit.flp floppies, keep reading. Insert the boot.flp floppy in the first floppy drive and boot the computer. The original install menu will be displayed on the screen. Select the "Fixit--Repair mode with - CDROM or floppy." option. Insert the fixit.flp when prompted. + CDROM or floppy." option. Insert the <filename>fixit.flp</filename> when prompted. <command>restore</command> and the other programs that you need are located in <filename>/mnt2/stand</filename>.</para> @@ -18168,10 +18194,10 @@ chmod 644 /mnt/etc/passwd id="russian-console"> <title>Console Setup</title> - <para> - <orderedlist> + + <procedure> - <listitem> + <step> <para>Add following line to your kernel configuration file: <programlisting> @@ -18179,9 +18205,9 @@ options "SC_MOUSE_CHAR=0x03" </programlisting> to move character codes used for mouse cursor off KOI8-R pseudographics range.</para> - </listitem> + </step> - <listitem> + <step> <para>Russian console entry in <filename>/etc/rc.conf</filename> should looks like @@ -18202,19 +18228,18 @@ font8x8=cp866-8x8 <para>This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve - pseudographics, <emphasis remap=it>Gray Delete</emphasis> + pseudographics, <literal>Gray Delete</literal> key remapped to match Russian <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry for FreeBSD console.</para> - <para>RUS/LAT switch will be <emphasis - remap=bf>CapsLock</emphasis>. Old CapsLock function still - available via <emphasis remap=bf>Shift+CapsLock</emphasis>. + <para>RUS/LAT switch will be <literal>CapsLock</literal>. Old CapsLock function still + available via <literal>Shift+CapsLock</literal>. CapsLock LED will indicate RUS mode, not CapsLock mode.</para> - </listitem> + </step> - <listitem> - <para>For each <emphasis remap=tt>ttyv?</emphasis> entry in + <step> + <para>For each <literal>ttyv?</literal> entry in <filename>/etc/ttys</filename> change terminal type from <literal>cons25</literal> to <literal>cons25r</literal>, i.e. each entry should looks like @@ -18222,10 +18247,10 @@ font8x8=cp866-8x8 <programlisting> ttyv0 "/usr/libexec/getty Pc" cons25r on secure </programlisting></para> - </listitem> + </step> - </orderedlist> - </para> + </procedure> + </sect2> @@ -18234,7 +18259,8 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure <title>Locale Setup</title> <para><anchor id="russian-env"> There is two environment variables - for locale setup: + for locale setup:</para> + <itemizedlist> <listitem> @@ -18248,10 +18274,9 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure </listitem> </itemizedlist> - </para> - + <para>The best way is using <filename>/etc/login.conf</filename> - <emphasis remap=tt>russian</emphasis> user's login class in + <literal>russian</literal> user's login class in <citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry login class position. See <citerefentry><refentrytitle>login.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details.</para> @@ -18262,15 +18287,15 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure <title>Login Class Method</title> <para>First of all check your <filename>/etc/login.conf</filename> - have <emphasis remap=tt>russian</emphasis> login class, this - entry may looks like: + have <literal>russian</literal> login class, this + entry may looks like:</para> <programlisting> russian:Russian Users Accounts:\ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R:\ :tc=default: - </programlisting></para> + </programlisting> <sect4> @@ -18278,11 +18303,11 @@ russian:Russian Users Accounts:\ <para>If you use <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users, <filename>/etc/master.passwd</filename> entry should - looks like: + looks like:</para> <programlisting> user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh - </programlisting></para> + </programlisting> </sect4> @@ -18300,19 +18325,17 @@ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh defaultclass = russian </programlisting> in <filename>/etc/adduser.conf</filename> (you must enter - <emphasis remap=tt>default</emphasis> class for all - non-Russian users in this case);<!-- <br> --><!-- <br> - --></para> + <literal>default</literal> class for all + non-Russian users in this case);</para> </listitem> <listitem> - <para>Alternative variant will be answering <emphasis - remap=tt>russian</emphasis> each time when you see + <para>Alternative variant will be answering <literal>russian</literal> each time when you see <informalexample> <screen><prompt>Enter login class:</prompt> default []:</screen> </informalexample> prompt from - <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;<!-- <br> --><!-- <br> --></para> + <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para> </listitem> <listitem> @@ -18333,11 +18356,11 @@ defaultclass = russian <title>How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title> <para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users, - call it in this form: + call it in this form:</para> <informalexample> <screen>&prompt.root; <userinput>pw useradd user_name -L russian</userinput></screen> - </informalexample></para> + </informalexample> </sect4> </sect3> @@ -18349,29 +18372,30 @@ defaultclass = russian <xref linkend="russian-class" remap="login class method"> for some reasons, just set this <xref linkend="russian-env" remap="two environment variables"> - in the following shell startup files: + in the following shell startup files:</para> + <itemizedlist> <listitem> - <para><filename>/etc/profile</filename>: + <para><filename>/etc/profile</filename>:</para> <programlisting> LANG=ru_RU.KOI8-R; export LANG MM_CHARSET=KOI8-R; export MM_CHARSET - </programlisting></para> + </programlisting> </listitem> <listitem> - <para><filename>/etc/csh.login</filename>: + <para><filename>/etc/csh.login</filename>:</para> <programlisting> setenv LANG ru_RU.KOI8-R setenv MM_CHARSET KOI8-R - </programlisting></para> + </programlisting> </listitem> </itemizedlist> - </para> + <para>Alternatively you can add this instructions to <itemizedlist> @@ -18405,13 +18429,15 @@ setenv MM_CHARSET KOI8-R -> CP866 conversion. Such filter installed by default as <filename>/usr/libexec/lpr/ru/koi2alt</filename>. So, Russian printer <filename>/etc/printcap</filename> entry should looks - like: + like:</para> <programlisting> lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: - </programlisting> see <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para> + </programlisting> + + <para>See <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para> </sect2> @@ -18420,11 +18446,13 @@ lp|Russian local line printer:\ <title>MSDOS FS and Russian file names</title> <para>Look at following example <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry to enable support for Russian - file names in MSDOS FS: + file names in MSDOS FS:</para> <programlisting> /dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0 - </programlisting> see + </programlisting> + + <para>See <citerefentry><refentrytitle>mount_msdos</refentrytitle><manvolnum>8</manvolnum></citerefentry>for detailed description of <option>-W</option> and <option>-L</option> options.</para> @@ -18434,10 +18462,11 @@ lp|Russian local line printer:\ id="russian-xwindow"> <title>X Window Setup</title> - <para>Step by step instructions: - <orderedlist> + <para>Step by step instructions:</para> + + <procedure> - <listitem> + <step> <para>Do <xref linkend="russian-locale" remap="non-X locale setup"> first as described.</para> @@ -18453,9 +18482,9 @@ lp|Russian local line printer:\ (check XFree86 version number not less than 3.3 first).</para> </note> - </listitem> + </step> - <listitem> + <step> <para>Go to <filename>/usr/ports/russian/X.language</filename> directory and say @@ -18468,19 +18497,19 @@ lp|Russian local line printer:\ <para>Check find <literal>"Files"</literal> section in your <filename>/etc/XF86Config</filename>, following lines must be before any other <literal>FontPath</literal> - entries: + entries:</para> <programlisting> FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/misc" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi" - </programlisting></para> + </programlisting> <para>If you use high resolution video mode, swap 75 dpi and 100 dpi lines.</para> - </listitem> + </step> - <listitem> + <step> <para>To activate Russian keyboard add <programlisting> @@ -18505,12 +18534,10 @@ XkbKeymap "xfree86(ru)" call <emphasis remap=bf>XtSetLanguageProc</emphasis> (NULL, NULL, NULL); function early in the program.</para> </note> - </listitem> + </step> - </orderedlist> + </procedure> - </para> - </sect2> </sect1> @@ -18521,8 +18548,6 @@ XkbKeymap "xfree86(ru)" <para>Slaven Rezic <emphasis remap=tt><ulink URL="mailto:eserte@cs.tu-berlin.de"><eserte@cs.tu-berlin.de></ulink></emphasis> wrote a tutorial how to use umlauts on a FreeBSD machine. The tutorial is written in German and available at <ulink URL="http://www.de.freebsd.org/de/umlaute/">http://www.de.freebsd.org/de/umlaute/</ulink>.</para> - <para></para> - </sect1> </chapter> </part> @@ -18545,26 +18570,26 @@ XkbKeymap "xfree86(ru)" serial ports. If you do not find what you want here, check into the Terminal and Dialup sections of the handbook.</para> - <para>The <filename>ttydX</filename> (or <filename>cuaaX</filename>) + <para>The <filename>ttyd<replaceable>X</replaceable></filename> (or <filename>cuaa<replaceable>X</replaceable></filename>) device is the regular device you will want to open for your applications. When a process opens the device, it will have a default set of terminal I/O settings. You can see these settings - with the command + with the command</para> <informalexample> <screen>&prompt.root; <userinput>stty -a -f /dev/ttyd1</userinput></screen> - </informalexample></para> + </informalexample> <para>When you change the settings to this device, the settings are in effect until the device is closed. When it is reopened, it goes back to the default set. To make changes to the default set, you can open and adjust the settings of the <quote>initial state</quote> device. For example, to turn on <acronym>CLOCAL</acronym> mode, 8 bits, and - <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do: + <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do:</para> <informalexample> <screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen> - </informalexample></para> + </informalexample> <para>A good place to do this is in <filename>/etc/rc.serial</filename>. Now, an application will have @@ -18574,11 +18599,11 @@ XkbKeymap "xfree86(ru)" <para>You can also prevent certain settings from being changed by an application by making adjustments to the <quote>lock state</quote> device. For example, to lock the speed of <filename>ttyd5</filename> to 57600 - bps, do + bps, do</para> <informalexample> <screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen> - </informalexample></para> + </informalexample> <para>Now, an application that opens <filename>ttyd5</filename> and tries to change the speed of the port will be stuck with 57600 @@ -18630,7 +18655,7 @@ XkbKeymap "xfree86(ru)" <para>For FreeBSD, there are three kinds of terminals:</para> - <para> + <itemizedlist> <listitem> @@ -18647,7 +18672,7 @@ XkbKeymap "xfree86(ru)" </listitem> </itemizedlist> - </para> + <para>The remaining subsections describe each kind.</para> @@ -18774,7 +18799,7 @@ XkbKeymap "xfree86(ru)" <para>If you like making your own cables, here is a table showing a recommended way to construct a null-modem cable for use with terminals. This table shows the RS-232C signal names - and the pin numbers on a DB-25 connector. + and the pin numbers on a DB-25 connector.</para> <informaltable frame="none"> <tgroup cols="5"> @@ -18857,7 +18882,7 @@ XkbKeymap "xfree86(ru)" </row> </tbody> </tgroup> - </informaltable></para> + </informaltable> </sect4> @@ -18910,7 +18935,8 @@ XkbKeymap "xfree86(ru)" <para>In FreeBSD, you access each serial port through an entry in the <filename>/dev</filename> directory. There are two - different kinds of entries: + different kinds of entries:</para> + <itemizedlist> <listitem> @@ -18924,14 +18950,13 @@ XkbKeymap "xfree86(ru)" </listitem> </itemizedlist> - </para> <para>See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for more information.</para> <para>If you have connected a terminal to the first serial port - (COM1 in DOS parlance), then you want to use + (<devicename>COM1</devicename> in DOS parlance), then you want to use <filename>/dev/ttyd0</filename> to refer to the terminal. If - it is on the second serial port (also known as COM2), it is + it is on the second serial port (also known as <devicename>COM2</devicename>), it is <filename>/dev/ttyd1</filename>, and so forth.</para> <para>Note that you may have to configure your kernel to support @@ -19039,12 +19064,12 @@ XkbKeymap "xfree86(ru)" port, <filename>ttyd1</filename>, which is already in the file. We need to add an entry for the 286 PC connected to the sixth serial port. Here is an excerpt of the - <filename>/etc/ttys</filename> file after we add the new entry: + <filename>/etc/ttys</filename> file after we add the new entry:</para> <programlisting> ttyd1 "/usr/libexec/getty std.9600" unknown off secure ttyd5 - </programlisting></para> + </programlisting> </sect3> @@ -19056,12 +19081,12 @@ ttyd5 <para>Next, we need to specify what program will be run to handle the logins on a terminal. For FreeBSD, the standard program to do that is <filename>/usr/libexec/getty</filename>. It is what - provides the <emphasis remap=tt>login:</emphasis> prompt.</para> + provides the <prompt>login:</prompt> prompt.</para> <para>The program <command>getty</command> takes one (optional) parameter on its command line, the - <emphasis><emphasis remap=tt>getty</emphasis> type</emphasis>. - A <emphasis remap=tt>getty</emphasis> type tells about + <replaceable>getty</replaceable> type. + A <replaceable>getty</replaceable> type tells about characteristics on the terminal line, like bps rate and parity. The <command>getty</command> program reads these characteristics from the file @@ -19074,19 +19099,21 @@ ttyd5 115200. Of course, you can add your own entries to this file. The manual page <citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> provides more information.</para> - <para>When setting the <emphasis remap=tt>getty</emphasis> type in + <para>When setting the <replaceable>getty</replaceable> type in the <filename>/etc/ttys</filename> file, make sure that the communications settings on the terminal match.</para> <para>For our example, the Wyse-50 uses no parity and connects at 38400 bps. The 286 PC uses no parity and connects at 19200 bps. Here is the <filename>/etc/ttys</filename> file so far (showing - just the two terminals in which we are interested): + just the two terminals in which we are interested):</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" unknown off secure ttyd5 "/usr/libexec/getty std.19200" - </programlisting> Note that the second field---where we specify + </programlisting> + + <para>Note that the second field---where we specify what program to run---appears in quotes. This is important, otherwise the type argument to <command>getty</command> might be interpreted as the next field.</para> @@ -19105,8 +19132,7 @@ ttyd5 "/usr/libexec/getty std.19200" For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field.</para> - <para>Users will usually use the <emphasis - remap=tt>tset</emphasis> program in their + <para>Users will usually use the <command>tset</command> program in their <filename>.login</filename> or <filename>.profile</filename> files to check the terminal type and prompt for one if necessary. By setting a terminal type in the @@ -19122,12 +19148,12 @@ ttyd5 "/usr/libexec/getty std.19200" (although it can emulate others, we will leave it in Wyse-50 mode). The 286 PC is running Procomm which will be set to emulate a VT-100. Here are the pertinent yet unfinished entries - from the <filename>/etc/ttys</filename> file: + from the <filename>/etc/ttys</filename> file:</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 off secure ttyd5 "/usr/libexec/getty std.19200" vt100 - </programlisting></para> + </programlisting> </sect3> @@ -19137,19 +19163,19 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 <para>The next field in <filename>/etc/ttys</filename>, the fourth field, tells whether to enable the port. Putting <literal>on</literal> here will have the <command>init</command> process start the program in the - second field, <emphasis remap=tt>getty</emphasis>, which will + second field, <command>getty</command>, which will prompt for a login. If you put <literal>off</literal> in the fourth field, there will be no <command>getty</command>, and hence no logins on the port.</para> <para>So, naturally, you want an <literal>on</literal> in this field. Here again is the <filename>/etc/ttys</filename> - file. We have turned each port <literal>on</literal>. + file. We have turned each port <literal>on</literal>.</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 on secure ttyd5 "/usr/libexec/getty std.19200" vt100 on - </programlisting></para> + </programlisting> </sect3> @@ -19178,10 +19204,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on command.</para> <para>Because of this, you will have two records to help track - down possible compromises of root privileges: both the login and - the <emphasis remap=tt>su</emphasis> command make records in the - system log (and logins are also recorded in the <emphasis - remap=tt>wtmp</emphasis> file).</para> + down possible compromises of root privileges: both the <command>login</command> and + the <command>su</command> command make records in the + system log (and logins are also recorded in the <filename>wtmp</filename> file).</para> <para>By marking a port as secure, the terminal will allow root in. People who know the root password will just login as root. @@ -19197,12 +19222,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on <para>Here finally are the completed entries in the <filename>/etc/ttys</filename> file, with comments added to - describe where the terminals are: + describe where the terminals are:</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 on insecure # Kitchen ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - </programlisting></para> + </programlisting> </sect3> @@ -19221,7 +19246,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom signal.</para> <para>So, after you have saved your changes to - <filename>/etc/ttys</filename>, send SIGHUP to <command>init</command> by typing: + <filename>/etc/ttys</filename>, send <literal>SIGHUP</literal> to <command>init</command> by typing: <informalexample> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> </informalexample> (The <command>init</command> @@ -19242,7 +19267,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom could still go wrong while setting up a terminal. Here is a list of symptoms and some suggested fixes.</para> - <para> + <variablelist> <varlistentry><term>No login prompt appears</term> <listitem> @@ -19263,10 +19288,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>Make sure that a <command>getty</command> process is running and serving the terminal. Type + <informalexample> <screen>&prompt.root; <userinput>ps -axww|grep getty</userinput></screen> </informalexample> to get a list of running <command>getty</command> processes. You should see an entry for the terminal. For example, the display + <informalexample> <screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1</screen> </informalexample> shows that a <command>getty</command> is running on the second @@ -19287,7 +19314,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <listitem> <para>Make sure the terminal and FreeBSD agree on the bps rate and parity settings. Check the getty processes to - make sure the correct <emphasis remap=tt>getty</emphasis> + make sure the correct <replaceable>getty</replaceable> type is in use. If not, edit <filename>/etc/ttys</filename> and run <command>kill -HUP 1</command>.</para> @@ -19304,7 +19331,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -19343,8 +19370,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>First, it is assumed that you are using FreeBSD version 1.1 or higher (including versions 2.x). FreeBSD version 1.0 included two different serial drivers, which complicates the - situation. Also, the serial device driver (<emphasis - remap=tt>sio</emphasis>) has improved in every release of + situation. Also, the serial device driver (<devicename>sio</devicename>) has improved in every release of FreeBSD, so more recent versions of FreeBSD are assumed to have better and more efficient drivers than earlier versions.</para> @@ -19355,7 +19381,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>A quick rundown of terminology:</para> - <para> + <variablelist> <varlistentry><term>bps</term> <listitem> @@ -19387,7 +19413,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </varlistentry> </variablelist> - </para> + <para>If you need more information about these terms and data communications in general, the author remembers reading that @@ -19395,10 +19421,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom a good reference.</para> <para>When talking about communications data rates, the author - does not use the term <emphasis remap=bf>baud</emphasis>. Baud + does not use the term <quote>baud</quote>. Baud refers to the number of electrical state transitions that may be - made in a period of time, while <emphasis - remap=bf>bps</emphasis> (bits per second) is the <quote>correct</quote> + made in a period of time, while <quote>bps</quote> (bits per second) is the <quote>correct</quote> term to use (at least it does not seem to bother the curmudgeons quite a much).</para> @@ -19428,7 +19453,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>A background knowledge of these items is assumed</para> - <para> + <itemizedlist> <listitem> @@ -19449,7 +19474,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </itemizedlist> - </para> + <para>The first, connecting your modem, is usually simple - most straight-through serial cables work without any problems. You @@ -19457,7 +19482,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom male or female) on each end, and the cable must be a DCE-to-DTE cable with these signals wired:</para> - <para> + <itemizedlist> <listitem> @@ -19493,7 +19518,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </itemizedlist> - </para> + <para>FreeBSD needs the <abbrev>RTS</abbrev> and <abbrev>CTS</abbrev> signals for flow-control at speeds above @@ -19552,15 +19577,16 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom example). The command <command>ps ax</command> might show this:</para> - <para> + <informalexample> <screen> 4850 ?? I 0:00.09 /usr/libexec/getty V19200 ttyd0</screen> - </informalexample></para> + </informalexample> <para>When a user dials the modem's line and the modems connect, the <abbrev>CD</abbrev> line is asserted by the modem. The kernel - notices that carrier has been detected and completes <command>getty</command>'s open of the port. <command>getty</command> sends a <emphasis - remap=tt>login:</emphasis> prompt at the specified initial line + notices that carrier has been detected and completes + <command>getty</command>'s open of the + port. <command>getty</command> sends a <prompt>login:</prompt> prompt at the specified initial line speed. <command>getty</command> watches to see if legitimate characters are received, and, in a typical configuration, if it finds junk (probably due to the modem's @@ -19568,7 +19594,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom it receives reasonable characters.</para> <para>We hope <command>getty</command> finds the correct - speed and the user sees a <emphasis remap=tt>login:</emphasis> + speed and the user sees a <prompt>login:</prompt> prompt. After the user enters his/her login name, <command>getty</command> executes <filename>/usr/bin/login</filename>, which completes the login by asking for the user's password and then starting the user's @@ -19583,9 +19609,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>FreeBSD kernels typically come prepared to search for four serial ports, known in the PC-DOS world as - <filename>COM1:</filename>, <filename>COM2:</filename>, - <filename>COM3:</filename>, and <filename - remap="tt">COM4:</filename>. FreeBSD can presently also handle + <devicename>COM1:</devicename>, <devicename>COM2:</devicename>, + <devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle <quote>dumb</quote> multiport serial interface cards, such as the Boca Board 1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information if you have a multiport serial card). The default kernel only @@ -19593,20 +19618,20 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>To see if your kernel recognizes any of your serial ports, watch for messages while the kernel is booting, or use the - <emphasis remap="tt">/sbin/dmesg</emphasis> command to replay the + <command>/sbin/dmesg</command> command to replay the kernel's boot messages. In particular, look for messages that start with the characters <literal>sio</literal>. Hint: to view just the messages that have the word <literal>sio</literal>, use the command:</para> - <para> + <informalexample> <screen>&prompt.root; <userinput>/sbin/dmesg | grep 'sio'</userinput></screen> - </informalexample></para> + </informalexample> <para>For example, on a system with four serial ports, these are the serial-port specific kernel boot messages:</para> - <para> + <informalexample> <screen>sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -19616,7 +19641,7 @@ sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A</screen> - </informalexample></para> + </informalexample> <para>If your kernel does not recognize all of your serial ports, you will probably need to configure a custom FreeBSD kernel for @@ -19630,7 +19655,7 @@ sio3: type 16550A</screen> <filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> for example being <filename>i386</filename>] for more information on configuring and building kernels. You may have to unpack the kernel source distribution if have not installed the system sources already (<filename>srcdist/srcsys.??</filename> in FreeBSD 1.1, <filename>srcdist/sys.??</filename> in FreeBSD 1.1.5.1, or the entire source distribution in FreeBSD 2.0) to be able to configure and build kernels.</para> <para>Create a kernel configuration file for your system (if you - have not already) by <emphasis remap=tt>cd</emphasis>ing to + have not already) by <command>cd</command>ing to <filename>/sys/i386/conf</filename>. Then, if you are creating a new custom configuration file, copy the file <filename>GENERICAH</filename> (or <filename>GENERICBT</filename>, @@ -19662,8 +19687,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <symbol>IO_COM4</symbol> is <literal>0x2e8</literal>, which are fairly common port addresses for their respective serial ports; interrupts 4, 3, 5, and 9 are fairly common interrupt request - lines. Also note that regular serial ports <emphasis - remap=bf>cannot</emphasis> share interrupts on ISA-bus PCs + lines. Also note that regular serial ports <emphasis>cannot</emphasis> share interrupts on ISA-bus PCs (multiport boards have on-board electronics that allow all the 16550A's on the board to share one or two interrupt request lines).</para> @@ -19683,18 +19707,17 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <para>Most devices in the kernel are accessed through <quote>device special files</quote>, which are located in the - <filename>/dev</filename> directory. The <emphasis - remap=tt>sio</emphasis> devices are accessed through the - <filename>/dev/ttyd?</filename> (dial-in) and - <filename>/dev/cua0?</filename> (call-out) devices. On FreeBSD + <filename>/dev</filename> directory. The <devicename>sio</devicename> devices are accessed through the + <filename>/dev/ttyd<replaceable>?</replaceable></filename> (dial-in) and + <filename>/dev/cua0<replaceable>?</replaceable></filename> (call-out) devices. On FreeBSD version 1.1.5 and higher, there are also initialization devices - (<filename>/dev/ttyid?</filename> and - <filename>/dev/cuai0?</filename>) and locking devices - (<filename>/dev/ttyld?</filename> and - <filename>/dev/cual0?</filename>). The initialization devices are + (<filename>/dev/ttyid<replaceable>?</replaceable></filename> and + <filename>/dev/cuai0<replaceable>?</replaceable></filename>) and locking devices + (<filename>/dev/ttyld<replaceable>?</replaceable></filename> and + <filename>/dev/cual0<replaceable>?</replaceable></filename>). The initialization devices are used to initialize communications port parameters each time a port - is opened, such as <emphasis remap=tt>crtscts</emphasis> for - modems which use <filename>CTS/RTS</filename> signaling for flow + is opened, such as <literal remap="tt">crtscts</literal> for + modems which use <literal>CTS/RTS</literal> signaling for flow control. The locking devices are used to lock flags on ports to prevent users or programs changing certain parameters; see the manual pages <citerefentry><refentrytitle>termios</refentrytitle><manvolnum>4</manvolnum></citerefentry>, <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry>, and <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for @@ -19705,23 +19728,23 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <sect3> <title>Making Device Special Files</title> - <para>A shell script called <filename>MAKEDEV</filename> in the + <para>A shell script called <command>MAKEDEV</command> in the <filename>/dev</filename> directory manages the device special files. (The manual page for <citerefentry><refentrytitle>MAKEDEV</refentrytitle><manvolnum>8</manvolnum></citerefentry> on FreeBSD 1.1.5 is fairly bogus in its discussion of <acronym>COM</acronym> ports, so ignore it.) To use - <filename>MAKEDEV</filename> to make dialup device special files - for <filename>COM1:</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue + <command>MAKEDEV</command> to make dialup device special files + for <devicename>COM1:</devicename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue the command <command>MAKEDEV ttyd0</command>. Likewise, to make dialup device special files for - <filename>COM2:</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> + <devicename>COM2:</devicename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> - <para><filename>MAKEDEV</filename> not only creates the - <filename>/dev/ttyd?</filename> device special files, but also - creates the <filename>/dev/cua0?</filename> (and all of the + <para><command>MAKEDEV</command> not only creates the + <filename>/dev/ttyd<replaceable>?</replaceable></filename> device special files, but also + creates the <filename>/dev/cua0<replaceable>?</replaceable></filename> (and all of the initializing and locking special files under FreeBSD 1.1.5 and up) and removes the hardwired terminal special file - <filename>/dev/tty0?</filename>, if it exists.</para> + <filename>/dev/tty0<replaceable>?</replaceable></filename>, if it exists.</para> <para>After making new device special files, be sure to check the permissions on the files (especially the @@ -19738,9 +19761,8 @@ crw-rw---- 1 uucp dialer 28, 161 Feb 15 14:38 /dev/cuai01 crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> </informalexample> - <para>These permissions allow the user <emphasis - remap=tt>uucp</emphasis> and users in the group <emphasis - remap=tt>dialer</emphasis> to use the call-out devices.</para> + <para>These permissions allow the user <username>uucp</username> + and users in the group <username>dialer</username> to use the call-out devices.</para> </sect3> </sect2> @@ -19754,9 +19776,8 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> <filename>/etc/gettytab</filename>, contains configuration information for the <filename>/usr/libexec/getty</filename> daemon. Second, <filename>/etc/ttys</filename> holds information - that tells <filename>/sbin/init</filename> what <emphasis - remap=tt>tty</emphasis> devices should have <emphasis - remap=tt>getty</emphasis> processes running on them. Lastly, + that tells <filename>/sbin/init</filename> what + <filename>tty</filename> devices should have <command>getty</command> processes running on them. Lastly, you can place port initialization commands in the <filename>/etc/rc.serial</filename> script if you have FreeBSD 1.1.5.1 or higher; otherwise, you can initialize ports in the @@ -19778,14 +19799,14 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> the modem run its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the modem's RS-232 interface run at 2400 bps. Because <command>getty</command> does not understand - any particular modem's connection speed reporting, <command>getty</command> gives a <emphasis - remap=tt>login:</emphasis> message at an initial speed and + any particular modem's connection speed reporting, + <command>getty</command> gives a <prompt>login:</prompt> message at an initial speed and watches the characters that come back in response. If the user sees junk, it is assumed that they know they should press the - <emphasis remap=tt><Enter></emphasis> key until they see a + <literal><Enter></literal> key until they see a recognizable prompt. If the data rates do not match, <command>getty</command> sees anything the user types as - <quote>junk</quote>, tries going to the next speed and gives the <emphasis - remap=tt>login:</emphasis> prompt again. This procedure can + <quote>junk</quote>, tries going to the next speed and gives the + <prompt>login:</prompt> prompt again. This procedure can continue ad nauseum, but normally only takes a keystroke or two before the user sees a good prompt. Obviously, this login sequence does not look as clean as the former <quote>locked-speed</quote> method, but @@ -19861,8 +19882,8 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ </programlisting> <para>On FreeBSD 1.1.5 and later, this will result in 8-bit, no - parity connections. Under FreeBSD 1.1, add <literal>:np:</literal> parameters to the <emphasis - remap=tt>std.<replaceable>xxx</replaceable></emphasis> + parity connections. Under FreeBSD 1.1, add + <literal>:np:</literal> parameters to the <literal>std.<replaceable>xxx</replaceable></literal> entries at the top of the file for 8 bits, no parity; otherwise, the default is 7 bits, even parity.</para> @@ -19870,10 +19891,10 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ Kbps (for a V.32bis connection), then cycles through 9600 bps (for V.32), 2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate cycling is implemented with the - <literal>nx=</literal> (<emphasis remap=bf>next - table</emphasis>) capability. Each of the lines uses a - <literal>tc=</literal> (<emphasis remap=bf>table - continuation</emphasis>) entry to pick up the rest of the + <literal>nx=</literal> (<quote>next + table</quote>) capability. Each of the lines uses a + <literal>tc=</literal> (<quote>table + continuation</quote>) entry to pick up the rest of the <quote>standard</quote> settings for a particular data rate.</para> <para>If you have a 28.8 Kbps modem and/or you want to take @@ -19910,12 +19931,11 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ id="dialup-ttys"> <title><filename>/etc/ttys</filename></title> - <para><filename>/etc/ttys</filename> is the list of <emphasis - remap=tt>ttys</emphasis> for <command>init</command> to monitor. + <para><filename>/etc/ttys</filename> is the list of <filename>ttys</filename> for <command>init</command> to monitor. <filename>/etc/ttys</filename> also provides security information to <command>login</command> (user - <emphasis remap=tt>root</emphasis> may only login on ttys marked - <emphasis remap=tt>secure</emphasis>). See the manual page for + <username>root</username> may only login on ttys marked + <literal>secure</literal>). See the manual page for <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more information.</para> @@ -19933,14 +19953,14 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <para>The first item in the above line is the device special file for this entry - <literal>ttyd0</literal> means <filename>/dev/ttyd0</filename> is the file that this <command>getty</command> will be watching. The second item, - <filename>"/usr/libexec/getty - <replaceable>xxx</replaceable>"</filename> - (<emphasis>xxx</emphasis> will be replaced by the initial - <emphasis remap=tt>gettytab</emphasis> capability) is the + <literal>"/usr/libexec/getty + <replaceable>xxx</replaceable>"</literal> + (<replaceable>xxx</replaceable> will be replaced by the initial + <filename>gettytab</filename> capability) is the process <command>init</command> will run on the device. The third item, <literal>dialup</literal>, - is the default terminal type. The fourth parameter, <literal>on</literal>, indicates to <emphasis - remap=tt>init</emphasis> that the line is operational. There + is the default terminal type. The fourth parameter, + <literal>on</literal>, indicates to <command>init</command> that the line is operational. There can be a fifth parameter, <literal>secure</literal>, but it should only be used for terminals which are physically secure (such as the system console).</para> @@ -19957,13 +19977,13 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <para>After you have made changes to <filename>/etc/ttys</filename>, you may send the <command>init</command> process a <acronym>HUP</acronym> - signal to re-read the file. You can use the command</para> + signal to re-read the file. You can use the command <informalexample> <screen>&prompt.root; <userinput>kill -1 1</userinput></screen> </informalexample> - <para>to send the signal. If this is your first time setting up + to send the signal. If this is your first time setting up the system, though, you may want to wait until your modem(s) are properly configured and connected before signaling <command>init</command>.</para> @@ -19971,19 +19991,16 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <sect4> <title>Locked-Speed Config</title> - <para>For a locked-speed configuration, your <emphasis - remap=tt>ttys</emphasis> entry needs to have a fixed-speed - entry provided to <emphasis remap=tt>getty</emphasis>. For a - modem whose port speed is locked at 19.2 Kbps, the <emphasis - remap=tt>ttys</emphasis> entry might look like this:</para> + <para>For a locked-speed configuration, your <filename>ttys</filename> entry needs to have a fixed-speed + entry provided to <command>getty</command>. For a + modem whose port speed is locked at 19.2 Kbps, the <filename>ttys</filename> entry might look like this:</para> <programlisting> ttyd0 "/usr/libexec/getty std.19200" dialup on </programlisting> <para>If your modem is locked at a different data rate, - substitute the appropriate name for the <emphasis - remap=tt>std.<replaceable>speed</replaceable></emphasis> + substitute the appropriate name for the <literal>std.<replaceable>speed</replaceable></literal> entry for <literal>std.19200</literal> from <filename>/etc/gettytab</filename> for your modem's data rate.</para> @@ -19993,14 +20010,13 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on <sect4> <title>Matching-Speed Config</title> - <para>In a matching-speed configuration, your <emphasis - remap=tt>ttys</emphasis> entry needs to reference the + <para>In a matching-speed configuration, your <filename>ttys</filename> entry needs to reference the appropriate beginning <quote>auto-baud</quote> (sic) entry in <filename>/etc/gettytab</filename>. For example, if you added the above suggested entry for a matching-speed modem that - starts at 19.2 Kbps (the <emphasis - remap=tt>gettytab</emphasis> entry containing the <literal>V19200</literal> starting point), your <emphasis - remap=tt>ttys</emphasis> entry might look like this:</para> + starts at 19.2 Kbps (the <filename>gettytab</filename> entry + containing the <literal>V19200</literal> starting point), your + <filename>ttys</filename> entry might look like this:</para> <programlisting> ttyd0 "/usr/libexec/getty V19200" dialup on @@ -20032,14 +20048,13 @@ stty -f /dev/ttyid1 crtscts stty -f /dev/cuai01 crtscts </programlisting> - <para>which sets the <emphasis remap=tt>termios</emphasis> flag - <emphasis remap=tt>crtscts</emphasis> on serial port #1's - (<emphasis remap=tt>COM2:</emphasis>) dialin and dialout + <para>This sets the <literal>termios</literal> flag + <literal>crtscts</literal> on serial port #1's + (<devicename>COM2:</devicename>) dialin and dialout initialization devices.</para> <para>On an old FreeBSD 1.1 system, these entries were added to - <filename>/etc/rc.local</filename> to set the <emphasis - remap=tt>crtscts</emphasis> flag on the devices:</para> + <filename>/etc/rc.local</filename> to set the <literal>crtscts</literal> flag on the devices:</para> <programlisting> # Set serial ports to use RTS/CTS flow control @@ -20067,7 +20082,7 @@ stty -f /dev/ttyd3 crtscts same communications speed as the initial speed <command>getty</command> will use and configure the modem's non-volatile RAM to match these requirements:</para> - <para> + <itemizedlist> <listitem> @@ -20100,7 +20115,7 @@ stty -f /dev/ttyd3 crtscts </listitem> </itemizedlist> - </para> + <para>Please read the documentation for your modem to find out what commands and/or DIP switch settings you need to give it.</para> @@ -20123,7 +20138,7 @@ AT&C1&D2&H1&I0&R2&W switches that need to be set; for other modems, perhaps you can use these settings as an example:</para> - <para> + <itemizedlist> <listitem> @@ -20160,11 +20175,11 @@ AT&C1&D2&H1&I0&R2&W </listitem> </itemizedlist> - </para> + <para>Result codes should be disabled/suppressed for dialup modems - to avoid problems that can occur if <command>getty</command> mistakenly gives a <emphasis - remap=tt>login:</emphasis> prompt to a modem that is in command + to avoid problems that can occur if <command>getty</command> + mistakenly gives a <prompt>login:</prompt> prompt to a modem that is in command mode and the modem echoes the command or returns a result code. I have heard this sequence can result in a extended, silly conversation between <command>getty</command> and the @@ -20210,11 +20225,11 @@ AT&B2&W <para>Most high-speed modems provide commands to view the modem's current operating parameters in a somewhat human-readable fashion. On the USR Sportster 14,400 external modems, the - command <emphasis remap=tt>ATI5</emphasis> displays the settings + command <command>ATI5</command> displays the settings that are stored in the non-volatile RAM. To see the true operating parameters of the modem (as influenced by the USR's DIP switch settings), use the commands <command>ATZ</command> - and then <emphasis remap=tt>ATI4</emphasis>.</para> + and then <command>ATI4</command>.</para> <para>If you have a different brand of modem, check your modem's manual to see how to double-check your modem's configuration @@ -20236,7 +20251,7 @@ AT&B2&W <para>Hook up your modem to your FreeBSD system, boot the system, and, if your modem has status indication lights, watch to see whether the modem's <abbrev>DTR</abbrev> indicator lights when - the <emphasis remap=tt>login:</emphasis> prompt appears on the + the <prompt>login:</prompt> prompt appears on the system's console - if it lights up, that should mean that FreeBSD has started a <command>getty</command> process on the appropriate communications port and is waiting @@ -20253,13 +20268,13 @@ AT&B2&W 115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen> </informalexample> - <para>If you see something different, like this:</para> + <para>If you see something different, like this: <informalexample> <screen> 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyd0</screen> </informalexample> - <para>and the modem has not accepted a call yet, this means that + and the modem has not accepted a call yet, this means that <command>getty</command> has completed its open on the communications port. This could indicate a problem with the cabling or a mis-configured modem, because <command>getty</command> should not be able to open the @@ -20267,7 +20282,7 @@ AT&B2&W has been asserted by the modem.</para> <para>If you do not see any <command>getty</command> - processes waiting to open the desired <filename>ttyd?</filename> + processes waiting to open the desired <filename>ttyd<replaceable>?</replaceable></filename> port, double-check your entries in <filename>/etc/ttys</filename> to see if there are any mistakes there. Also, check the log file @@ -20288,21 +20303,19 @@ AT&B2&W <para>Try dialing into the system; be sure to use 8 bits, no parity, 1 stop bit on the remote system. If you do not get a - prompt right away, or get garbage, try pressing <emphasis - remap=tt><Enter></emphasis> about once per second. If - you still do not see a <emphasis remap=tt>login:</emphasis> + prompt right away, or get garbage, try pressing <literal><Enter></literal> about once per second. If + you still do not see a <prompt>login:</prompt> prompt after a while, try sending a <command>BREAK</command>. If you are using a high-speed modem to do the dialing, try dialing again after locking the dialing modem's interface speed - (via <emphasis remap=tt>AT&B1</emphasis> on a USR Sportster, + (via <command>AT&B1</command> on a USR Sportster, for example).</para> - <para>If you still cannot get a <emphasis - remap=tt>login:</emphasis> prompt, check + <para>If you still cannot get a <prompt>login:</prompt> prompt, check <filename>/etc/gettytab</filename> again and double-check that</para> - <para> + <itemizedlist> <listitem> @@ -20322,7 +20335,7 @@ AT&B2&W </listitem> </itemizedlist> - </para> + <para>If you dial but the modem on the FreeBSD system will not answer, make sure that the modem is configured to answer the @@ -20345,7 +20358,7 @@ AT&B2&W <para>Thanks to these people for comments and advice:</para> - <para> + <variablelist> <varlistentry><term>&a.kelly;</term> <listitem> @@ -20353,7 +20366,7 @@ AT&B2&W </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -28080,7 +28093,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # Date created: 5 December 1994 # Whom: asami # -# $Id: book.sgml,v 1.39 1998-10-21 22:02:39 nik Exp $ +# $Id: book.sgml,v 1.40 1998-10-21 22:05:23 nik Exp $ # DISTNAME= oneko-1.1b diff --git a/en_US.ISO_8859-1/books/handbook/book.sgml b/en_US.ISO_8859-1/books/handbook/book.sgml index c62020ea09..4b74e46c0e 100644 --- a/en_US.ISO_8859-1/books/handbook/book.sgml +++ b/en_US.ISO_8859-1/books/handbook/book.sgml @@ -15316,7 +15316,7 @@ disk wd3 at wdc1 drive 1 jargon in use to abbreviate the different bus types. A small list:</para> - <para> + <itemizedlist> <listitem> @@ -15340,7 +15340,7 @@ disk wd3 at wdc1 drive 1 </listitem> </itemizedlist> - </para> + <para>With a minor amount of imagination one can usually imagine what is meant.</para> @@ -15604,8 +15604,7 @@ disk wd3 at wdc1 drive 1 the highest SCSI ID will win. This also means that the SCSI host adapter usually uses target ID 7. Note however that the lower 8 IDs have higher priorities than the higher 8 IDs on a - wide-SCSI bus. Thus, the order of target IDs is: <emphasis - remap=tt>[7 6 .. 1 0 15 14 .. 9 8]</emphasis> on a wide-SCSI + wide-SCSI bus. Thus, the order of target IDs is: [7 6 .. 1 0 15 14 .. 9 8] on a wide-SCSI system. (If you you are wondering why the lower 8 have higher priority, read the previous paragraph for a hint.)</para> @@ -15643,7 +15642,7 @@ disk wd3 at wdc1 drive 1 ultimately the reliability of it all are tightly related to linear bus rule.</para> - <para><emphasis remap=bf>Stick to the linear bus + <para><emphasis>Stick to the linear bus rule!</emphasis></para> </sect4> @@ -15708,9 +15707,8 @@ disk wd3 at wdc1 drive 1 of a jumper or software setup selection, to switch the translation the SCSI BIOS uses.</para> - <para>It is very important that <emphasis - remap=bf>all</emphasis> operating systems on the disk use - the <emphasis remap=bf>same translation</emphasis> to get the + <para>It is very important that <emphasis>all</emphasis> operating systems on the disk use + the <emphasis>same translation</emphasis> to get the right idea about where to find the relevant partitions. So, when installing FreeBSD you must answer any questions about heads/cylinders etc using the translated values your host @@ -15721,7 +15719,7 @@ disk wd3 at wdc1 drive 1 others partitions. Using fdisk you should be able to see all partitions.</para> - <para>You might have heard some talk of 'lying' devices? Older + <para>You might have heard some talk of <quote>lying</quote> devices? Older FreeBSD kernels used to report the geometry of SCSI disks when booting. An example from one of my systems:</para> @@ -15730,12 +15728,12 @@ disk wd3 at wdc1 drive 1 sd0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512</screen> </informalexample> - <para>Newer kernels usually do not report this information. e.g. + <para>Newer kernels usually do not report this information. e.g.</para> <informalexample> <screen>(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen> - </informalexample></para> + </informalexample> <para>Why has this changed?</para> @@ -15812,7 +15810,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen> </note> <para>An example loosely based on the FreeBSD 2.2.5-Release - kernel config file LINT with some added comments (between + kernel config file <filename>LINT</filename> with some added comments (between []):</para> <programlisting> @@ -15861,9 +15859,9 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <emphasis>only</emphasis> attach them when they match the target ID and LUN specified on the corresponding bus.</para> - <para>Wired down devices get 'first shot' at the unit numbers so - the first non 'wired down' device, is allocated the unit - number one greater than the highest 'wired down' unit number + <para>Wired down devices get <quote>first shot</quote> at the unit numbers so + the first non <quote>wired down</quote> device, is allocated the unit + number one greater than the highest <quote>wired down</quote> unit number for that kind of device. So, if you had a SCSI tape at target ID 2 it would be configured as st2, as the tape at target ID 6 is wired down to unit number 1.</para> @@ -15880,7 +15878,7 @@ device cd0 at scbus? [the first ever CD-ROM found, no wiring] <para>Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first - example is that devices are not 'wired down'. 'Wired down' + example is that devices are not <quote>wired down</quote>. <quote>Wired down</quote> means that you specify which SCSI target belongs to which device.</para> @@ -15921,13 +15919,13 @@ device cd0 #Only need one of these, the code dynamically grows devices of a specific type (e.g. sd disks) are found than are configured in the booting kernel, the system will simply allocate more devices, incrementing the unit number starting - at the last number 'wired down'. If there are no 'wired down' + at the last number <quote>wired down</quote>. If there are no <quote>wired down</quote> devices then counting starts at unit 0.</para> - <para>Use <emphasis remap=tt>man 4 scsi</emphasis> to check for + <para>Use <command>man 4 scsi</command> to check for the latest info on the SCSI subsystem. For more detailed info - on host adapter drivers use eg <emphasis remap=tt>man 4 - ahc</emphasis> for info on the Adaptec 294x driver.</para> + on host adapter drivers use eg <command>man 4 + ahc</command> for info on the Adaptec 294x driver.</para> </sect4> @@ -15969,7 +15967,7 @@ options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device correctly is no easy task. Some vendors do a better job then others.</para> - <para>This is exactly where the 'rogue' devices come into view. + <para>This is exactly where the <quote>rogue</quote> devices come into view. Rogues are devices that are recognized by the FreeBSD kernel as behaving slightly (...) non-standard. Rogue devices are reported by the kernel when booting. An example for two of my @@ -16000,7 +15998,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> this is done.</para> <para>This scheme works fine, but keep in mind that it of course - only works for devices that are KNOWN to be weird. If you are + only works for devices that are known to be weird. If you are the first to connect your bogus Mumbletech SCSI CD-ROM you might be the one that has to define which workaround is needed.</para> @@ -16027,14 +16025,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> around this problem you must add an appropriate entry in /sys/scsi/scsiconf.c and rebuild your kernel.</para> - <para>Look for a struct that is initialized like below: + <para>Look for a struct that is initialized like below:</para> <programlisting> { T_DIRECT, T_FIXED, "MAXTOR", "XT-4170S", "B5A", "mx1", SC_ONE_LU } - </programlisting></para> + </programlisting> <para>For you Mumbletech BRIDGE2000 that has more than one LUN, acts as a SCSI disk and has firmware revision 123 you would @@ -16067,13 +16065,13 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen> TCQ function is indispensable to take advantage of the device's inherent parallelism.</para> - <para>Each I/O request is uniquely identified by a 'tag' (hence + <para>Each I/O request is uniquely identified by a <quote>tag</quote> (hence the name tagged command queuing) and this tag is used by FreeBSD to see which I/O in the device drivers queue is reported as complete by the device.</para> <para>It should be noted however that TCQ requires device driver - support and that some devices implemented it 'not quite right' + support and that some devices implemented it <quote>not quite right</quote> in their firmware. This problem bit me once, and it leads to highly mysterious problems. In such cases, try to disable TCQ.</para> @@ -16126,7 +16124,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed most common SCSI problems and their solutions. It is by no means complete.</para> - <para> + <itemizedlist> <listitem> @@ -16170,22 +16168,22 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <listitem> <para>If you can compile a kernel, make one with the - SCSIDEBUG option, and try accessing the device with + <literal>SCSIDEBUG</literal> option, and try accessing the device with debugging turned on for that device. If your device does not even probe at startup, you may have to define the address of the device that is failing, and the desired debug level in <filename>/sys/scsi/scsidebug.h</filename>. If it probes but just does not work, you can use the <citerefentry><refentrytitle>scsi</refentrytitle><manvolnum>8</manvolnum></citerefentry> command to dynamically set a - debug level to it in a running kernel (if SCSIDEBUG is - defined). This will give you COPIOUS debugging output with - which to confuse the gurus. see <emphasis remap=tt>man 4 - scsi</emphasis> for more exact information. Also look at - <emphasis remap=tt>man 8 scsi</emphasis>.</para> + debug level to it in a running kernel (if <literal>SCSIDEBUG</literal> is + defined). This will give you <emphasis>copious</emphasis> debugging output with + which to confuse the gurus. see <command>man 4 + scsi</command> for more exact information. Also look at + <command>man 8 scsi</command>.</para> </listitem> </itemizedlist> - </para> + </sect3> @@ -16197,18 +16195,37 @@ options "TUNE_1542" #dynamic tune of bus DMA speed want to have the official standard at hand:</para> <para>Approved American National Standards can be purchased from - ANSI at 11 West 42nd Street, 13th Floor, New York, NY 10036, - Sales Dept: (212) 642-4900. You can also buy many ANSI + ANSI at + + <address> + <otheraddr>13th Floor</otheraddr> + <street>11 West 42nd Street</street> + <city>New York</city> + <state>NY</state> <postcode>10036</postcode> + Sales Dept: <phone>(212) 642-4900</phone> + </address> + </para> + + <para>You can also buy many ANSI standards and most committee draft documents from Global - Engineering Documents, 15 Inverness Way East, Englewood, CO - 80112-5704, Phone: (800) 854-7179, Outside USA and Canada: (303) - 792-2181, FAX: (303) 792- 2192.</para> + Engineering Documents, + + <address> + <street>15 Inverness Way East</street> + <city>Englewood</city> + <state>CO</state>, <postcode>80112-5704</postcode> + Phone: <phone>(800) 854-7179</phone> + Outside USA and Canada: <phone>(303) 792-2181</phone> + Fax: <fax>(303) 792- 2192</fax> + </address> + </para> <para>Many X3T10 draft documents are available electronically on - the SCSI BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous + the SCSI BBS (719-574-0424) and on the <hostid role="fqdn">ncrinfo.ncr.com</hostid> anonymous ftp site.</para> - <para>Latest X3T10 committee documents are: + <para>Latest X3T10 committee documents are:</para> + <itemizedlist> <listitem> @@ -16236,8 +16253,11 @@ options "TUNE_1542" #dynamic tune of bus DMA speed Interface Module (CAM) [X3T10/792D Rev 11]</para> </listitem> - </itemizedlist> Other publications that might provide you with - additional information are: + </itemizedlist> + + <para>Other publications that might provide you with + additional information are:</para> + <itemizedlist> <listitem> @@ -16281,7 +16301,6 @@ options "TUNE_1542" #dynamic tune of bus DMA speed </listitem> </itemizedlist> - </para> <para>On Usenet the newsgroups <ulink URL="news:comp.periphs.scsi">comp.periphs.scsi</ulink> and @@ -16477,10 +16496,9 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <title> General tape access commands</title> <para><citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> provides generic access to the tape - drives. Some of the more common commands are <emphasis - remap=tt>rewind</emphasis>, <emphasis - remap=tt>erase</emphasis>, and <emphasis - remap=tt>status</emphasis>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> + drives. Some of the more common commands are + <command>rewind</command>, <command>erase</command>, and + <command>status</command>. See the <citerefentry><refentrytitle>mt</refentrytitle><manvolnum>1</manvolnum></citerefentry> manual page for a detailed description.</para> </sect3> @@ -16717,7 +16735,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>This drive was repackaged by Sun Microsystems as model 411.</para> - <para>Reported by: Bob Bishop rb@gid.co.uk</para> + <para>Reported by: Bob Bishop <email>rb@gid.co.uk</email></para> </sect4> @@ -16738,7 +16756,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> - <para>Reported by: Philippe Regnauld regnauld@hsc.fr</para> + <para>Reported by: Philippe Regnauld <email>regnauld@hsc.fr</email></para> </sect4> @@ -16778,10 +16796,10 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> <para>Reported by: Pedro A M Vazquez - vazquez@IQM.Unicamp.BR</para> + <email>vazquez@IQM.Unicamp.BR</email></para> <para>Mike Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -16826,7 +16844,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive uses QIC-80 tape cartridges.</para> - <para>Reported by: Mark Hannon mark@seeware.DIALix.oz.au</para> + <para>Reported by: Mark Hannon <email>mark@seeware.DIALix.oz.au</email></para> </sect4> @@ -16846,7 +16864,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive uses QIC-3080 tape cartridges.</para> - <para>Reported by: Thomas S. Traylor tst@titan.cs.mci.com</para> + <para>Reported by: Thomas S. Traylor <email>tst@titan.cs.mci.com</email></para> </sect4> @@ -16924,7 +16942,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Right now, this drive cannot really be recommended for FreeBSD.</para> - <para>Reported by: Bob Beaulieu ez@eztravel.com</para> + <para>Reported by: Bob Beaulieu <email>ez@eztravel.com</email></para> </sect4> @@ -16953,7 +16971,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Production of this drive has been discontinued.</para> <para>Reported by: Mike Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -16971,7 +16989,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Data transfer rate is 300kB/s.</para> - <para>Reported by: Greg Lehey grog@lemis.de</para> + <para>Reported by: Greg Lehey <email>grog@lemis.de</email></para> </sect4> @@ -16993,7 +17011,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>Data transfer rate is 300kB/s.</para> - <para>Reported by: Glen Foster gfoster@gfoster.com</para> + <para>Reported by: Glen Foster <email>gfoster@gfoster.com</email></para> </sect4> @@ -17019,7 +17037,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed <para>The drive has a block of 8 dip switches. The proper settings for FreeBSD are: 1 ON; 2 ON; 3 OFF; 4 ON; 5 ON; 6 ON; - 7 ON; 8 ON. + 7 ON; 8 ON.</para> <informaltable frame="none"> <tgroup cols="3"> @@ -17061,7 +17079,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed </row> </tbody> </tgroup> - </informaltable></para> + </informaltable> <para>Switch 3 controls MRS (Media Recognition System). MRS tapes have stripes on the transparent leader. These identify @@ -17113,7 +17131,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed nearing the end of its useful life, steady indicates an hard fault. (factory service required?)</para> - <para>Reported by Gary Crutcher gcrutchr@nightflight.com</para> + <para>Reported by Gary Crutcher <email>gcrutchr@nightflight.com</email></para> </sect4> @@ -17206,7 +17224,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Data transfer rate is 160kB/s.</para> <para>Reported by: mark thompson - mark.a.thompson@pobox.com</para> + <email>mark.a.thompson@pobox.com</email></para> </sect4> @@ -17236,7 +17254,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" returned 5 of these drives. None lasted more than 9 months.</para> - <para>Reported by: David Dawes dawes@rf900.physics.usyd.edu.au + <para>Reported by: David Dawes <email>dawes@rf900.physics.usyd.edu.au</email> (9 09)</para> </sect4> @@ -17340,7 +17358,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" firmware EPROM of these units will solve the problem.</para> <para>Reported by: Michael Smith - msmith@atrad.adelaide.edu.au</para> + <email>msmith@atrad.adelaide.edu.au</email></para> </sect4> @@ -17418,8 +17436,8 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Other firmware revisions that are known to work are: M75D</para> - <para>Reported by: Marc van Kempen marc@bowtie.nl <literal>REV73R1</literal> - Andrew Gordon Andrew.Gordon@net-tel.co.uk <literal>M75D</literal></para> + <para>Reported by: Marc van Kempen <email>marc@bowtie.nl</email> <literal>REV73R1</literal> + Andrew Gordon <email>Andrew.Gordon@net-tel.co.uk</email> <literal>M75D</literal></para> </sect4> @@ -17438,7 +17456,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>Data transfer rate is 150kB/s.</para> - <para>Reported by: Tony Kimball alk@Think.COM</para> + <para>Reported by: Tony Kimball <email>alk@Think.COM</email></para> </sect4> </sect3> @@ -17658,11 +17676,12 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <para>The first time that you try to read or write a new, completely blank tape, the operation will fail. The console - messages should be similar to: + messages should be similar to:</para> + <informalexample> <screen>st0(ncr1:4:0): NOT READY asc:4,1 st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> - </informalexample></para> + </informalexample> <para>The tape does not contain an Identifier Block (block number 0). All QIC tape drives since the adoption of QIC-525 standard @@ -17676,10 +17695,9 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <para>Re-insert the tape and <citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> data to the tape.</para> - <para><citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> will report <emphasis - remap=tt>DUMP: End of tape detected</emphasis> and the console - will show: <emphasis remap=tt>HARDWARE FAILURE info:280 - asc:80,96</emphasis></para> + <para><citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry> will report <errorname>DUMP: End of tape detected</errorname> and the console + will show: <errorname>HARDWARE FAILURE info:280 + asc:80,96</errorname></para> <para>rewind the tape using: <command>mt rewind</command></para> @@ -17724,7 +17742,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> rely upon <citerefentry><refentrytitle>rcmd</refentrytitle><manvolnum>3</manvolnum></citerefentry> and <citerefentry><refentrytitle>ruserok</refentrytitle><manvolnum>3</manvolnum></citerefentry> to access the remote tape drive. Therefore, the user performing the backup must have - <emphasis remap=tt>rhosts</emphasis> access to the remote + <filename>rhosts</filename> access to the remote computer. The arguments to <citerefentry><refentrytitle>rdump</refentrytitle><manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rrestore</refentrytitle><manvolnum>8</manvolnum></citerefentry> must suitable to use on the remote computer. (e.g. When <command>rdump</command>'ing from a FreeBSD computer to an @@ -17733,8 +17751,7 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <informalexample> <screen>&prompt.root; <userinput>/sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</userinput></screen> </informalexample>) Beware: - there are security implications to allowing <emphasis - remap=tt>rhosts</emphasis> commands. Evaluate your + there are security implications to allowing <filename>rhosts</filename> commands. Evaluate your situation carefully.</para> </sect4> @@ -17881,14 +17898,18 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> <para>There are only four steps that you need to perform in preparation for any disaster that may occur.</para> - - <para>First, print the disklabel from each of your disks - (<command>e.g. disklabel sd0 | lpr</command>), your + + <procedure> + <step> + <para>Print the disklabel from each of your disks + (e.g., <command>disklabel sd0 | lpr</command>), your filesystem table (<filename>/etc/fstab</filename>) and all boot messages, two copies of each.</para> - - <para>Second, determine the boot and fixit floppies (boot.flp - and fixit.flp) have all your devices. The easiest way to + </step> + + <step> + <para>Determine the boot and fixit floppies (<filename>boot.flp</filename> + and <filename>fixit.flp</filename>) have all your devices. The easiest way to check is to reboot your machine with the boot floppy in the floppy drive and check the boot messages. If all your devices are listed and functional, skip on to step three.</para> @@ -17901,12 +17922,16 @@ st0(ncr1:4:0): Logical unit is in process of becoming ready</screen> whichever backup program you use. These programs must be statically linked. If you use <citerefentry><refentrytitle>dump</refentrytitle><manvolnum>8</manvolnum></citerefentry>, the floppy must contain <citerefentry><refentrytitle>restore</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para> - - <para>Third, create backup tapes regularly. Any changes that you + </step> + + <step> + <para>Create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. Write-protect the backup tapes.</para> - - <para>Fourth, test the floppies (either boot.flp and fixit.flp + </step> + + <step> + <para>Test the floppies (either <filename>boot.flp</filename> and <filename>fixit.flp</filename> or the two custom bootable floppies you made in step two.) and backup tapes. Make notes of the procedure. Store these notes with the bootable floppy, the printouts and the backup @@ -18078,7 +18103,8 @@ chmod 644 /mnt/etc/passwd # /sbin/umount /mnt </programlisting></para> - + </step> + </procedure> </sect4> <sect4> @@ -18093,13 +18119,13 @@ chmod 644 /mnt/etc/passwd <para>If your hardware is okay, check your floppies. If you are using a custom boot floppy, boot single-user (type <option>-s</option> at the - "boot:" prompt). Skip the following paragraph.</para> + <prompt>boot:</prompt> prompt). Skip the following paragraph.</para> <para>If you are using the boot.flp and fixit.flp floppies, keep reading. Insert the boot.flp floppy in the first floppy drive and boot the computer. The original install menu will be displayed on the screen. Select the "Fixit--Repair mode with - CDROM or floppy." option. Insert the fixit.flp when prompted. + CDROM or floppy." option. Insert the <filename>fixit.flp</filename> when prompted. <command>restore</command> and the other programs that you need are located in <filename>/mnt2/stand</filename>.</para> @@ -18168,10 +18194,10 @@ chmod 644 /mnt/etc/passwd id="russian-console"> <title>Console Setup</title> - <para> - <orderedlist> + + <procedure> - <listitem> + <step> <para>Add following line to your kernel configuration file: <programlisting> @@ -18179,9 +18205,9 @@ options "SC_MOUSE_CHAR=0x03" </programlisting> to move character codes used for mouse cursor off KOI8-R pseudographics range.</para> - </listitem> + </step> - <listitem> + <step> <para>Russian console entry in <filename>/etc/rc.conf</filename> should looks like @@ -18202,19 +18228,18 @@ font8x8=cp866-8x8 <para>This tuning means KOI8-R keyboard with Alternative screen font mapped to KOI8-R encoding to preserve - pseudographics, <emphasis remap=it>Gray Delete</emphasis> + pseudographics, <literal>Gray Delete</literal> key remapped to match Russian <citerefentry><refentrytitle>termcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry for FreeBSD console.</para> - <para>RUS/LAT switch will be <emphasis - remap=bf>CapsLock</emphasis>. Old CapsLock function still - available via <emphasis remap=bf>Shift+CapsLock</emphasis>. + <para>RUS/LAT switch will be <literal>CapsLock</literal>. Old CapsLock function still + available via <literal>Shift+CapsLock</literal>. CapsLock LED will indicate RUS mode, not CapsLock mode.</para> - </listitem> + </step> - <listitem> - <para>For each <emphasis remap=tt>ttyv?</emphasis> entry in + <step> + <para>For each <literal>ttyv?</literal> entry in <filename>/etc/ttys</filename> change terminal type from <literal>cons25</literal> to <literal>cons25r</literal>, i.e. each entry should looks like @@ -18222,10 +18247,10 @@ font8x8=cp866-8x8 <programlisting> ttyv0 "/usr/libexec/getty Pc" cons25r on secure </programlisting></para> - </listitem> + </step> - </orderedlist> - </para> + </procedure> + </sect2> @@ -18234,7 +18259,8 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure <title>Locale Setup</title> <para><anchor id="russian-env"> There is two environment variables - for locale setup: + for locale setup:</para> + <itemizedlist> <listitem> @@ -18248,10 +18274,9 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure </listitem> </itemizedlist> - </para> - + <para>The best way is using <filename>/etc/login.conf</filename> - <emphasis remap=tt>russian</emphasis> user's login class in + <literal>russian</literal> user's login class in <citerefentry><refentrytitle>passwd</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry login class position. See <citerefentry><refentrytitle>login.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details.</para> @@ -18262,15 +18287,15 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure <title>Login Class Method</title> <para>First of all check your <filename>/etc/login.conf</filename> - have <emphasis remap=tt>russian</emphasis> login class, this - entry may looks like: + have <literal>russian</literal> login class, this + entry may looks like:</para> <programlisting> russian:Russian Users Accounts:\ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R:\ :tc=default: - </programlisting></para> + </programlisting> <sect4> @@ -18278,11 +18303,11 @@ russian:Russian Users Accounts:\ <para>If you use <citerefentry><refentrytitle>vipw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users, <filename>/etc/master.passwd</filename> entry should - looks like: + looks like:</para> <programlisting> user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh - </programlisting></para> + </programlisting> </sect4> @@ -18300,19 +18325,17 @@ user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh defaultclass = russian </programlisting> in <filename>/etc/adduser.conf</filename> (you must enter - <emphasis remap=tt>default</emphasis> class for all - non-Russian users in this case);<!-- <br> --><!-- <br> - --></para> + <literal>default</literal> class for all + non-Russian users in this case);</para> </listitem> <listitem> - <para>Alternative variant will be answering <emphasis - remap=tt>russian</emphasis> each time when you see + <para>Alternative variant will be answering <literal>russian</literal> each time when you see <informalexample> <screen><prompt>Enter login class:</prompt> default []:</screen> </informalexample> prompt from - <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;<!-- <br> --><!-- <br> --></para> + <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para> </listitem> <listitem> @@ -18333,11 +18356,11 @@ defaultclass = russian <title>How to do it with <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry></title> <para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users, - call it in this form: + call it in this form:</para> <informalexample> <screen>&prompt.root; <userinput>pw useradd user_name -L russian</userinput></screen> - </informalexample></para> + </informalexample> </sect4> </sect3> @@ -18349,29 +18372,30 @@ defaultclass = russian <xref linkend="russian-class" remap="login class method"> for some reasons, just set this <xref linkend="russian-env" remap="two environment variables"> - in the following shell startup files: + in the following shell startup files:</para> + <itemizedlist> <listitem> - <para><filename>/etc/profile</filename>: + <para><filename>/etc/profile</filename>:</para> <programlisting> LANG=ru_RU.KOI8-R; export LANG MM_CHARSET=KOI8-R; export MM_CHARSET - </programlisting></para> + </programlisting> </listitem> <listitem> - <para><filename>/etc/csh.login</filename>: + <para><filename>/etc/csh.login</filename>:</para> <programlisting> setenv LANG ru_RU.KOI8-R setenv MM_CHARSET KOI8-R - </programlisting></para> + </programlisting> </listitem> </itemizedlist> - </para> + <para>Alternatively you can add this instructions to <itemizedlist> @@ -18405,13 +18429,15 @@ setenv MM_CHARSET KOI8-R -> CP866 conversion. Such filter installed by default as <filename>/usr/libexec/lpr/ru/koi2alt</filename>. So, Russian printer <filename>/etc/printcap</filename> entry should looks - like: + like:</para> <programlisting> lp|Russian local line printer:\ :sh:of=/usr/libexec/lpr/ru/koi2alt:\ :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs: - </programlisting> see <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para> + </programlisting> + + <para>See <citerefentry><refentrytitle>printcap</refentrytitle><manvolnum>5</manvolnum></citerefentry> for detailed description.</para> </sect2> @@ -18420,11 +18446,13 @@ lp|Russian local line printer:\ <title>MSDOS FS and Russian file names</title> <para>Look at following example <citerefentry><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry> entry to enable support for Russian - file names in MSDOS FS: + file names in MSDOS FS:</para> <programlisting> /dev/sd0s1 /dos/c msdos rw,-W=koi2dos,-L=ru_RU.KOI8-R 0 0 - </programlisting> see + </programlisting> + + <para>See <citerefentry><refentrytitle>mount_msdos</refentrytitle><manvolnum>8</manvolnum></citerefentry>for detailed description of <option>-W</option> and <option>-L</option> options.</para> @@ -18434,10 +18462,11 @@ lp|Russian local line printer:\ id="russian-xwindow"> <title>X Window Setup</title> - <para>Step by step instructions: - <orderedlist> + <para>Step by step instructions:</para> + + <procedure> - <listitem> + <step> <para>Do <xref linkend="russian-locale" remap="non-X locale setup"> first as described.</para> @@ -18453,9 +18482,9 @@ lp|Russian local line printer:\ (check XFree86 version number not less than 3.3 first).</para> </note> - </listitem> + </step> - <listitem> + <step> <para>Go to <filename>/usr/ports/russian/X.language</filename> directory and say @@ -18468,19 +18497,19 @@ lp|Russian local line printer:\ <para>Check find <literal>"Files"</literal> section in your <filename>/etc/XF86Config</filename>, following lines must be before any other <literal>FontPath</literal> - entries: + entries:</para> <programlisting> FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/misc" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi" - </programlisting></para> + </programlisting> <para>If you use high resolution video mode, swap 75 dpi and 100 dpi lines.</para> - </listitem> + </step> - <listitem> + <step> <para>To activate Russian keyboard add <programlisting> @@ -18505,12 +18534,10 @@ XkbKeymap "xfree86(ru)" call <emphasis remap=bf>XtSetLanguageProc</emphasis> (NULL, NULL, NULL); function early in the program.</para> </note> - </listitem> + </step> - </orderedlist> + </procedure> - </para> - </sect2> </sect1> @@ -18521,8 +18548,6 @@ XkbKeymap "xfree86(ru)" <para>Slaven Rezic <emphasis remap=tt><ulink URL="mailto:eserte@cs.tu-berlin.de"><eserte@cs.tu-berlin.de></ulink></emphasis> wrote a tutorial how to use umlauts on a FreeBSD machine. The tutorial is written in German and available at <ulink URL="http://www.de.freebsd.org/de/umlaute/">http://www.de.freebsd.org/de/umlaute/</ulink>.</para> - <para></para> - </sect1> </chapter> </part> @@ -18545,26 +18570,26 @@ XkbKeymap "xfree86(ru)" serial ports. If you do not find what you want here, check into the Terminal and Dialup sections of the handbook.</para> - <para>The <filename>ttydX</filename> (or <filename>cuaaX</filename>) + <para>The <filename>ttyd<replaceable>X</replaceable></filename> (or <filename>cuaa<replaceable>X</replaceable></filename>) device is the regular device you will want to open for your applications. When a process opens the device, it will have a default set of terminal I/O settings. You can see these settings - with the command + with the command</para> <informalexample> <screen>&prompt.root; <userinput>stty -a -f /dev/ttyd1</userinput></screen> - </informalexample></para> + </informalexample> <para>When you change the settings to this device, the settings are in effect until the device is closed. When it is reopened, it goes back to the default set. To make changes to the default set, you can open and adjust the settings of the <quote>initial state</quote> device. For example, to turn on <acronym>CLOCAL</acronym> mode, 8 bits, and - <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do: + <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do:</para> <informalexample> <screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen> - </informalexample></para> + </informalexample> <para>A good place to do this is in <filename>/etc/rc.serial</filename>. Now, an application will have @@ -18574,11 +18599,11 @@ XkbKeymap "xfree86(ru)" <para>You can also prevent certain settings from being changed by an application by making adjustments to the <quote>lock state</quote> device. For example, to lock the speed of <filename>ttyd5</filename> to 57600 - bps, do + bps, do</para> <informalexample> <screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen> - </informalexample></para> + </informalexample> <para>Now, an application that opens <filename>ttyd5</filename> and tries to change the speed of the port will be stuck with 57600 @@ -18630,7 +18655,7 @@ XkbKeymap "xfree86(ru)" <para>For FreeBSD, there are three kinds of terminals:</para> - <para> + <itemizedlist> <listitem> @@ -18647,7 +18672,7 @@ XkbKeymap "xfree86(ru)" </listitem> </itemizedlist> - </para> + <para>The remaining subsections describe each kind.</para> @@ -18774,7 +18799,7 @@ XkbKeymap "xfree86(ru)" <para>If you like making your own cables, here is a table showing a recommended way to construct a null-modem cable for use with terminals. This table shows the RS-232C signal names - and the pin numbers on a DB-25 connector. + and the pin numbers on a DB-25 connector.</para> <informaltable frame="none"> <tgroup cols="5"> @@ -18857,7 +18882,7 @@ XkbKeymap "xfree86(ru)" </row> </tbody> </tgroup> - </informaltable></para> + </informaltable> </sect4> @@ -18910,7 +18935,8 @@ XkbKeymap "xfree86(ru)" <para>In FreeBSD, you access each serial port through an entry in the <filename>/dev</filename> directory. There are two - different kinds of entries: + different kinds of entries:</para> + <itemizedlist> <listitem> @@ -18924,14 +18950,13 @@ XkbKeymap "xfree86(ru)" </listitem> </itemizedlist> - </para> <para>See the <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page for more information.</para> <para>If you have connected a terminal to the first serial port - (COM1 in DOS parlance), then you want to use + (<devicename>COM1</devicename> in DOS parlance), then you want to use <filename>/dev/ttyd0</filename> to refer to the terminal. If - it is on the second serial port (also known as COM2), it is + it is on the second serial port (also known as <devicename>COM2</devicename>), it is <filename>/dev/ttyd1</filename>, and so forth.</para> <para>Note that you may have to configure your kernel to support @@ -19039,12 +19064,12 @@ XkbKeymap "xfree86(ru)" port, <filename>ttyd1</filename>, which is already in the file. We need to add an entry for the 286 PC connected to the sixth serial port. Here is an excerpt of the - <filename>/etc/ttys</filename> file after we add the new entry: + <filename>/etc/ttys</filename> file after we add the new entry:</para> <programlisting> ttyd1 "/usr/libexec/getty std.9600" unknown off secure ttyd5 - </programlisting></para> + </programlisting> </sect3> @@ -19056,12 +19081,12 @@ ttyd5 <para>Next, we need to specify what program will be run to handle the logins on a terminal. For FreeBSD, the standard program to do that is <filename>/usr/libexec/getty</filename>. It is what - provides the <emphasis remap=tt>login:</emphasis> prompt.</para> + provides the <prompt>login:</prompt> prompt.</para> <para>The program <command>getty</command> takes one (optional) parameter on its command line, the - <emphasis><emphasis remap=tt>getty</emphasis> type</emphasis>. - A <emphasis remap=tt>getty</emphasis> type tells about + <replaceable>getty</replaceable> type. + A <replaceable>getty</replaceable> type tells about characteristics on the terminal line, like bps rate and parity. The <command>getty</command> program reads these characteristics from the file @@ -19074,19 +19099,21 @@ ttyd5 115200. Of course, you can add your own entries to this file. The manual page <citerefentry><refentrytitle>gettytab</refentrytitle><manvolnum>5</manvolnum></citerefentry> provides more information.</para> - <para>When setting the <emphasis remap=tt>getty</emphasis> type in + <para>When setting the <replaceable>getty</replaceable> type in the <filename>/etc/ttys</filename> file, make sure that the communications settings on the terminal match.</para> <para>For our example, the Wyse-50 uses no parity and connects at 38400 bps. The 286 PC uses no parity and connects at 19200 bps. Here is the <filename>/etc/ttys</filename> file so far (showing - just the two terminals in which we are interested): + just the two terminals in which we are interested):</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" unknown off secure ttyd5 "/usr/libexec/getty std.19200" - </programlisting> Note that the second field---where we specify + </programlisting> + + <para>Note that the second field---where we specify what program to run---appears in quotes. This is important, otherwise the type argument to <command>getty</command> might be interpreted as the next field.</para> @@ -19105,8 +19132,7 @@ ttyd5 "/usr/libexec/getty std.19200" For hardwired terminals, the terminal type does not change, so you can put a real terminal type in this field.</para> - <para>Users will usually use the <emphasis - remap=tt>tset</emphasis> program in their + <para>Users will usually use the <command>tset</command> program in their <filename>.login</filename> or <filename>.profile</filename> files to check the terminal type and prompt for one if necessary. By setting a terminal type in the @@ -19122,12 +19148,12 @@ ttyd5 "/usr/libexec/getty std.19200" (although it can emulate others, we will leave it in Wyse-50 mode). The 286 PC is running Procomm which will be set to emulate a VT-100. Here are the pertinent yet unfinished entries - from the <filename>/etc/ttys</filename> file: + from the <filename>/etc/ttys</filename> file:</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 off secure ttyd5 "/usr/libexec/getty std.19200" vt100 - </programlisting></para> + </programlisting> </sect3> @@ -19137,19 +19163,19 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 <para>The next field in <filename>/etc/ttys</filename>, the fourth field, tells whether to enable the port. Putting <literal>on</literal> here will have the <command>init</command> process start the program in the - second field, <emphasis remap=tt>getty</emphasis>, which will + second field, <command>getty</command>, which will prompt for a login. If you put <literal>off</literal> in the fourth field, there will be no <command>getty</command>, and hence no logins on the port.</para> <para>So, naturally, you want an <literal>on</literal> in this field. Here again is the <filename>/etc/ttys</filename> - file. We have turned each port <literal>on</literal>. + file. We have turned each port <literal>on</literal>.</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 on secure ttyd5 "/usr/libexec/getty std.19200" vt100 on - </programlisting></para> + </programlisting> </sect3> @@ -19178,10 +19204,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on command.</para> <para>Because of this, you will have two records to help track - down possible compromises of root privileges: both the login and - the <emphasis remap=tt>su</emphasis> command make records in the - system log (and logins are also recorded in the <emphasis - remap=tt>wtmp</emphasis> file).</para> + down possible compromises of root privileges: both the <command>login</command> and + the <command>su</command> command make records in the + system log (and logins are also recorded in the <filename>wtmp</filename> file).</para> <para>By marking a port as secure, the terminal will allow root in. People who know the root password will just login as root. @@ -19197,12 +19222,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on <para>Here finally are the completed entries in the <filename>/etc/ttys</filename> file, with comments added to - describe where the terminals are: + describe where the terminals are:</para> <programlisting> ttyd1 "/usr/libexec/getty std.38400" wy50 on insecure # Kitchen ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom - </programlisting></para> + </programlisting> </sect3> @@ -19221,7 +19246,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom signal.</para> <para>So, after you have saved your changes to - <filename>/etc/ttys</filename>, send SIGHUP to <command>init</command> by typing: + <filename>/etc/ttys</filename>, send <literal>SIGHUP</literal> to <command>init</command> by typing: <informalexample> <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen> </informalexample> (The <command>init</command> @@ -19242,7 +19267,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom could still go wrong while setting up a terminal. Here is a list of symptoms and some suggested fixes.</para> - <para> + <variablelist> <varlistentry><term>No login prompt appears</term> <listitem> @@ -19263,10 +19288,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>Make sure that a <command>getty</command> process is running and serving the terminal. Type + <informalexample> <screen>&prompt.root; <userinput>ps -axww|grep getty</userinput></screen> </informalexample> to get a list of running <command>getty</command> processes. You should see an entry for the terminal. For example, the display + <informalexample> <screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1</screen> </informalexample> shows that a <command>getty</command> is running on the second @@ -19287,7 +19314,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <listitem> <para>Make sure the terminal and FreeBSD agree on the bps rate and parity settings. Check the getty processes to - make sure the correct <emphasis remap=tt>getty</emphasis> + make sure the correct <replaceable>getty</replaceable> type is in use. If not, edit <filename>/etc/ttys</filename> and run <command>kill -HUP 1</command>.</para> @@ -19304,7 +19331,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -19343,8 +19370,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>First, it is assumed that you are using FreeBSD version 1.1 or higher (including versions 2.x). FreeBSD version 1.0 included two different serial drivers, which complicates the - situation. Also, the serial device driver (<emphasis - remap=tt>sio</emphasis>) has improved in every release of + situation. Also, the serial device driver (<devicename>sio</devicename>) has improved in every release of FreeBSD, so more recent versions of FreeBSD are assumed to have better and more efficient drivers than earlier versions.</para> @@ -19355,7 +19381,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>A quick rundown of terminology:</para> - <para> + <variablelist> <varlistentry><term>bps</term> <listitem> @@ -19387,7 +19413,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </varlistentry> </variablelist> - </para> + <para>If you need more information about these terms and data communications in general, the author remembers reading that @@ -19395,10 +19421,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom a good reference.</para> <para>When talking about communications data rates, the author - does not use the term <emphasis remap=bf>baud</emphasis>. Baud + does not use the term <quote>baud</quote>. Baud refers to the number of electrical state transitions that may be - made in a period of time, while <emphasis - remap=bf>bps</emphasis> (bits per second) is the <quote>correct</quote> + made in a period of time, while <quote>bps</quote> (bits per second) is the <quote>correct</quote> term to use (at least it does not seem to bother the curmudgeons quite a much).</para> @@ -19428,7 +19453,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>A background knowledge of these items is assumed</para> - <para> + <itemizedlist> <listitem> @@ -19449,7 +19474,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </itemizedlist> - </para> + <para>The first, connecting your modem, is usually simple - most straight-through serial cables work without any problems. You @@ -19457,7 +19482,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom male or female) on each end, and the cable must be a DCE-to-DTE cable with these signals wired:</para> - <para> + <itemizedlist> <listitem> @@ -19493,7 +19518,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom </listitem> </itemizedlist> - </para> + <para>FreeBSD needs the <abbrev>RTS</abbrev> and <abbrev>CTS</abbrev> signals for flow-control at speeds above @@ -19552,15 +19577,16 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom example). The command <command>ps ax</command> might show this:</para> - <para> + <informalexample> <screen> 4850 ?? I 0:00.09 /usr/libexec/getty V19200 ttyd0</screen> - </informalexample></para> + </informalexample> <para>When a user dials the modem's line and the modems connect, the <abbrev>CD</abbrev> line is asserted by the modem. The kernel - notices that carrier has been detected and completes <command>getty</command>'s open of the port. <command>getty</command> sends a <emphasis - remap=tt>login:</emphasis> prompt at the specified initial line + notices that carrier has been detected and completes + <command>getty</command>'s open of the + port. <command>getty</command> sends a <prompt>login:</prompt> prompt at the specified initial line speed. <command>getty</command> watches to see if legitimate characters are received, and, in a typical configuration, if it finds junk (probably due to the modem's @@ -19568,7 +19594,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom it receives reasonable characters.</para> <para>We hope <command>getty</command> finds the correct - speed and the user sees a <emphasis remap=tt>login:</emphasis> + speed and the user sees a <prompt>login:</prompt> prompt. After the user enters his/her login name, <command>getty</command> executes <filename>/usr/bin/login</filename>, which completes the login by asking for the user's password and then starting the user's @@ -19583,9 +19609,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>FreeBSD kernels typically come prepared to search for four serial ports, known in the PC-DOS world as - <filename>COM1:</filename>, <filename>COM2:</filename>, - <filename>COM3:</filename>, and <filename - remap="tt">COM4:</filename>. FreeBSD can presently also handle + <devicename>COM1:</devicename>, <devicename>COM2:</devicename>, + <devicename>COM3:</devicename>, and <devicename>COM4:</devicename>. FreeBSD can presently also handle <quote>dumb</quote> multiport serial interface cards, such as the Boca Board 1008 and 2016 (please see the manual page <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry> for kernel configuration information if you have a multiport serial card). The default kernel only @@ -19593,20 +19618,20 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom <para>To see if your kernel recognizes any of your serial ports, watch for messages while the kernel is booting, or use the - <emphasis remap="tt">/sbin/dmesg</emphasis> command to replay the + <command>/sbin/dmesg</command> command to replay the kernel's boot messages. In particular, look for messages that start with the characters <literal>sio</literal>. Hint: to view just the messages that have the word <literal>sio</literal>, use the command:</para> - <para> + <informalexample> <screen>&prompt.root; <userinput>/sbin/dmesg | grep 'sio'</userinput></screen> - </informalexample></para> + </informalexample> <para>For example, on a system with four serial ports, these are the serial-port specific kernel boot messages:</para> - <para> + <informalexample> <screen>sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A @@ -19616,7 +19641,7 @@ sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A</screen> - </informalexample></para> + </informalexample> <para>If your kernel does not recognize all of your serial ports, you will probably need to configure a custom FreeBSD kernel for @@ -19630,7 +19655,7 @@ sio3: type 16550A</screen> <filename>/sys/<replaceable>arch</replaceable>/conf/options.<replaceable>arch</replaceable></filename>, with <emphasis>arch</emphasis> for example being <filename>i386</filename>] for more information on configuring and building kernels. You may have to unpack the kernel source distribution if have not installed the system sources already (<filename>srcdist/srcsys.??</filename> in FreeBSD 1.1, <filename>srcdist/sys.??</filename> in FreeBSD 1.1.5.1, or the entire source distribution in FreeBSD 2.0) to be able to configure and build kernels.</para> <para>Create a kernel configuration file for your system (if you - have not already) by <emphasis remap=tt>cd</emphasis>ing to + have not already) by <command>cd</command>ing to <filename>/sys/i386/conf</filename>. Then, if you are creating a new custom configuration file, copy the file <filename>GENERICAH</filename> (or <filename>GENERICBT</filename>, @@ -19662,8 +19687,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <symbol>IO_COM4</symbol> is <literal>0x2e8</literal>, which are fairly common port addresses for their respective serial ports; interrupts 4, 3, 5, and 9 are fairly common interrupt request - lines. Also note that regular serial ports <emphasis - remap=bf>cannot</emphasis> share interrupts on ISA-bus PCs + lines. Also note that regular serial ports <emphasis>cannot</emphasis> share interrupts on ISA-bus PCs (multiport boards have on-board electronics that allow all the 16550A's on the board to share one or two interrupt request lines).</para> @@ -19683,18 +19707,17 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <para>Most devices in the kernel are accessed through <quote>device special files</quote>, which are located in the - <filename>/dev</filename> directory. The <emphasis - remap=tt>sio</emphasis> devices are accessed through the - <filename>/dev/ttyd?</filename> (dial-in) and - <filename>/dev/cua0?</filename> (call-out) devices. On FreeBSD + <filename>/dev</filename> directory. The <devicename>sio</devicename> devices are accessed through the + <filename>/dev/ttyd<replaceable>?</replaceable></filename> (dial-in) and + <filename>/dev/cua0<replaceable>?</replaceable></filename> (call-out) devices. On FreeBSD version 1.1.5 and higher, there are also initialization devices - (<filename>/dev/ttyid?</filename> and - <filename>/dev/cuai0?</filename>) and locking devices - (<filename>/dev/ttyld?</filename> and - <filename>/dev/cual0?</filename>). The initialization devices are + (<filename>/dev/ttyid<replaceable>?</replaceable></filename> and + <filename>/dev/cuai0<replaceable>?</replaceable></filename>) and locking devices + (<filename>/dev/ttyld<replaceable>?</replaceable></filename> and + <filename>/dev/cual0<replaceable>?</replaceable></filename>). The initialization devices are used to initialize communications port parameters each time a port - is opened, such as <emphasis remap=tt>crtscts</emphasis> for - modems which use <filename>CTS/RTS</filename> signaling for flow + is opened, such as <literal remap="tt">crtscts</literal> for + modems which use <literal>CTS/RTS</literal> signaling for flow control. The locking devices are used to lock flags on ports to prevent users or programs changing certain parameters; see the manual pages <citerefentry><refentrytitle>termios</refentrytitle><manvolnum>4</manvolnum></citerefentry>, <citerefentry><refentrytitle>sio</refentrytitle><manvolnum>4</manvolnum></citerefentry>, and <citerefentry><refentrytitle>stty</refentrytitle><manvolnum>1</manvolnum></citerefentry> for @@ -19705,23 +19728,23 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr <sect3> <title>Making Device Special Files</title> - <para>A shell script called <filename>MAKEDEV</filename> in the + <para>A shell script called <command>MAKEDEV</command> in the <filename>/dev</filename> directory manages the device special files. (The manual page for <citerefentry><refentrytitle>MAKEDEV</refentrytitle><manvolnum>8</manvolnum></citerefentry> on FreeBSD 1.1.5 is fairly bogus in its discussion of <acronym>COM</acronym> ports, so ignore it.) To use - <filename>MAKEDEV</filename> to make dialup device special files - for <filename>COM1:</filename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue + <command>MAKEDEV</command> to make dialup device special files + for <devicename>COM1:</devicename> (port 0), <command>cd</command> to <filename>/dev</filename> and issue the command <command>MAKEDEV ttyd0</command>. Likewise, to make dialup device special files for - <filename>COM2:</filename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> + <devicename>COM2:</devicename> (port 1), use <command>MAKEDEV ttyd1</command>.</para> - <para><filename>MAKEDEV</filename> not only creates the - <filename>/dev/ttyd?</filename> device special files, but also - creates the <filename>/dev/cua0?</filename> (and all of the + <para><command>MAKEDEV</command> not only creates the + <filename>/dev/ttyd<replaceable>?</replaceable></filename> device special files, but also + creates the <filename>/dev/cua0<replaceable>?</replaceable></filename> (and all of the initializing and locking special files under FreeBSD 1.1.5 and up) and removes the hardwired terminal special file - <filename>/dev/tty0?</filename>, if it exists.</para> + <filename>/dev/tty0<replaceable>?</replaceable></filename>, if it exists.</para> <para>After making new device special files, be sure to check the permissions on the files (especially the @@ -19738,9 +19761,8 @@ crw-rw---- 1 uucp dialer 28, 161 Feb 15 14:38 /dev/cuai01 crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> </informalexample> - <para>These permissions allow the user <emphasis - remap=tt>uucp</emphasis> and users in the group <emphasis - remap=tt>dialer</emphasis> to use the call-out devices.</para> + <para>These permissions allow the user <username>uucp</username> + and users in the group <username>dialer</username> to use the call-out devices.</para> </sect3> </sect2> @@ -19754,9 +19776,8 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> <filename>/etc/gettytab</filename>, contains configuration information for the <filename>/usr/libexec/getty</filename> daemon. Second, <filename>/etc/ttys</filename> holds information - that tells <filename>/sbin/init</filename> what <emphasis - remap=tt>tty</emphasis> devices should have <emphasis - remap=tt>getty</emphasis> processes running on them. Lastly, + that tells <filename>/sbin/init</filename> what + <filename>tty</filename> devices should have <command>getty</command> processes running on them. Lastly, you can place port initialization commands in the <filename>/etc/rc.serial</filename> script if you have FreeBSD 1.1.5.1 or higher; otherwise, you can initialize ports in the @@ -19778,14 +19799,14 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen> the modem run its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the modem's RS-232 interface run at 2400 bps. Because <command>getty</command> does not understand - any particular modem's connection speed reporting, <command>getty</command> gives a <emphasis - remap=tt>login:</emphasis> message at an initial speed and + any particular modem's connection speed reporting, + <command>getty</command> gives a <prompt>login:</prompt> message at an initial speed and watches the characters that come back in response. If the user sees junk, it is assumed that they know they should press the - <emphasis remap=tt><Enter></emphasis> key until they see a + <literal><Enter></literal> key until they see a recognizable prompt. If the data rates do not match, <command>getty</command> sees anything the user types as - <quote>junk</quote>, tries going to the next speed and gives the <emphasis - remap=tt>login:</emphasis> prompt again. This procedure can + <quote>junk</quote>, tries going to the next speed and gives the + <prompt>login:</prompt> prompt again. This procedure can continue ad nauseum, but normally only takes a keystroke or two before the user sees a good prompt. Obviously, this login sequence does not look as clean as the former <quote>locked-speed</quote> method, but @@ -19861,8 +19882,8 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ </programlisting> <para>On FreeBSD 1.1.5 and later, this will result in 8-bit, no - parity connections. Under FreeBSD 1.1, add <literal>:np:</literal> parameters to the <emphasis - remap=tt>std.<replaceable>xxx</replaceable></emphasis> + parity connections. Under FreeBSD 1.1, add + <literal>:np:</literal> parameters to the <literal>std.<replaceable>xxx</replaceable></literal> entries at the top of the file for 8 bits, no parity; otherwise, the default is 7 bits, even parity.</para> @@ -19870,10 +19891,10 @@ uq|V19200|High Speed Modem at 19200,8-bit:\ Kbps (for a V.32bis connection), then cycles through 9600 bps (for V.32), 2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate cycling is implemented with the - <literal>nx=</literal> (<emphasis remap=bf>next - table</emphasis>) capability. Each of the lines uses a - <literal>tc=</literal> (<emphasis remap=bf>table - continuation</emphasis>) entry to pick up the rest of the + <literal>nx=</literal> (<quote>next + table</quote>) capability. Each of the lines uses a + <literal>tc=</literal> (<quote>table + continuation</quote>) entry to pick up the rest of the <quote>standard</quote> settings for a particular data rate.</para> <para>If you have a 28.8 Kbps modem and/or you want to take @@ -19910,12 +19931,11 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\ id="dialup-ttys"> <title><filename>/etc/ttys</filename></title> - <para><filename>/etc/ttys</filename> is the list of <emphasis - remap=tt>ttys</emphasis> for <command>init</command> to monitor. + <para><filename>/etc/ttys</filename> is the list of <filename>ttys</filename> for <command>init</command> to monitor. <filename>/etc/ttys</filename> also provides security information to <command>login</command> (user - <emphasis remap=tt>root</emphasis> may only login on ttys marked - <emphasis remap=tt>secure</emphasis>). See the manual page for + <username>root</username> may only login on ttys marked + <literal>secure</literal>). See the manual page for <citerefentry><refentrytitle>ttys</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more information.</para> @@ -19933,14 +19953,14 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <para>The first item in the above line is the device special file for this entry - <literal>ttyd0</literal> means <filename>/dev/ttyd0</filename> is the file that this <command>getty</command> will be watching. The second item, - <filename>"/usr/libexec/getty - <replaceable>xxx</replaceable>"</filename> - (<emphasis>xxx</emphasis> will be replaced by the initial - <emphasis remap=tt>gettytab</emphasis> capability) is the + <literal>"/usr/libexec/getty + <replaceable>xxx</replaceable>"</literal> + (<replaceable>xxx</replaceable> will be replaced by the initial + <filename>gettytab</filename> capability) is the process <command>init</command> will run on the device. The third item, <literal>dialup</literal>, - is the default terminal type. The fourth parameter, <literal>on</literal>, indicates to <emphasis - remap=tt>init</emphasis> that the line is operational. There + is the default terminal type. The fourth parameter, + <literal>on</literal>, indicates to <command>init</command> that the line is operational. There can be a fifth parameter, <literal>secure</literal>, but it should only be used for terminals which are physically secure (such as the system console).</para> @@ -19957,13 +19977,13 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <para>After you have made changes to <filename>/etc/ttys</filename>, you may send the <command>init</command> process a <acronym>HUP</acronym> - signal to re-read the file. You can use the command</para> + signal to re-read the file. You can use the command <informalexample> <screen>&prompt.root; <userinput>kill -1 1</userinput></screen> </informalexample> - <para>to send the signal. If this is your first time setting up + to send the signal. If this is your first time setting up the system, though, you may want to wait until your modem(s) are properly configured and connected before signaling <command>init</command>.</para> @@ -19971,19 +19991,16 @@ ttyd0 "/usr/libexec/getty xxx" dialup on <sect4> <title>Locked-Speed Config</title> - <para>For a locked-speed configuration, your <emphasis - remap=tt>ttys</emphasis> entry needs to have a fixed-speed - entry provided to <emphasis remap=tt>getty</emphasis>. For a - modem whose port speed is locked at 19.2 Kbps, the <emphasis - remap=tt>ttys</emphasis> entry might look like this:</para> + <para>For a locked-speed configuration, your <filename>ttys</filename> entry needs to have a fixed-speed + entry provided to <command>getty</command>. For a + modem whose port speed is locked at 19.2 Kbps, the <filename>ttys</filename> entry might look like this:</para> <programlisting> ttyd0 "/usr/libexec/getty std.19200" dialup on </programlisting> <para>If your modem is locked at a different data rate, - substitute the appropriate name for the <emphasis - remap=tt>std.<replaceable>speed</replaceable></emphasis> + substitute the appropriate name for the <literal>std.<replaceable>speed</replaceable></literal> entry for <literal>std.19200</literal> from <filename>/etc/gettytab</filename> for your modem's data rate.</para> @@ -19993,14 +20010,13 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on <sect4> <title>Matching-Speed Config</title> - <para>In a matching-speed configuration, your <emphasis - remap=tt>ttys</emphasis> entry needs to reference the + <para>In a matching-speed configuration, your <filename>ttys</filename> entry needs to reference the appropriate beginning <quote>auto-baud</quote> (sic) entry in <filename>/etc/gettytab</filename>. For example, if you added the above suggested entry for a matching-speed modem that - starts at 19.2 Kbps (the <emphasis - remap=tt>gettytab</emphasis> entry containing the <literal>V19200</literal> starting point), your <emphasis - remap=tt>ttys</emphasis> entry might look like this:</para> + starts at 19.2 Kbps (the <filename>gettytab</filename> entry + containing the <literal>V19200</literal> starting point), your + <filename>ttys</filename> entry might look like this:</para> <programlisting> ttyd0 "/usr/libexec/getty V19200" dialup on @@ -20032,14 +20048,13 @@ stty -f /dev/ttyid1 crtscts stty -f /dev/cuai01 crtscts </programlisting> - <para>which sets the <emphasis remap=tt>termios</emphasis> flag - <emphasis remap=tt>crtscts</emphasis> on serial port #1's - (<emphasis remap=tt>COM2:</emphasis>) dialin and dialout + <para>This sets the <literal>termios</literal> flag + <literal>crtscts</literal> on serial port #1's + (<devicename>COM2:</devicename>) dialin and dialout initialization devices.</para> <para>On an old FreeBSD 1.1 system, these entries were added to - <filename>/etc/rc.local</filename> to set the <emphasis - remap=tt>crtscts</emphasis> flag on the devices:</para> + <filename>/etc/rc.local</filename> to set the <literal>crtscts</literal> flag on the devices:</para> <programlisting> # Set serial ports to use RTS/CTS flow control @@ -20067,7 +20082,7 @@ stty -f /dev/ttyd3 crtscts same communications speed as the initial speed <command>getty</command> will use and configure the modem's non-volatile RAM to match these requirements:</para> - <para> + <itemizedlist> <listitem> @@ -20100,7 +20115,7 @@ stty -f /dev/ttyd3 crtscts </listitem> </itemizedlist> - </para> + <para>Please read the documentation for your modem to find out what commands and/or DIP switch settings you need to give it.</para> @@ -20123,7 +20138,7 @@ AT&C1&D2&H1&I0&R2&W switches that need to be set; for other modems, perhaps you can use these settings as an example:</para> - <para> + <itemizedlist> <listitem> @@ -20160,11 +20175,11 @@ AT&C1&D2&H1&I0&R2&W </listitem> </itemizedlist> - </para> + <para>Result codes should be disabled/suppressed for dialup modems - to avoid problems that can occur if <command>getty</command> mistakenly gives a <emphasis - remap=tt>login:</emphasis> prompt to a modem that is in command + to avoid problems that can occur if <command>getty</command> + mistakenly gives a <prompt>login:</prompt> prompt to a modem that is in command mode and the modem echoes the command or returns a result code. I have heard this sequence can result in a extended, silly conversation between <command>getty</command> and the @@ -20210,11 +20225,11 @@ AT&B2&W <para>Most high-speed modems provide commands to view the modem's current operating parameters in a somewhat human-readable fashion. On the USR Sportster 14,400 external modems, the - command <emphasis remap=tt>ATI5</emphasis> displays the settings + command <command>ATI5</command> displays the settings that are stored in the non-volatile RAM. To see the true operating parameters of the modem (as influenced by the USR's DIP switch settings), use the commands <command>ATZ</command> - and then <emphasis remap=tt>ATI4</emphasis>.</para> + and then <command>ATI4</command>.</para> <para>If you have a different brand of modem, check your modem's manual to see how to double-check your modem's configuration @@ -20236,7 +20251,7 @@ AT&B2&W <para>Hook up your modem to your FreeBSD system, boot the system, and, if your modem has status indication lights, watch to see whether the modem's <abbrev>DTR</abbrev> indicator lights when - the <emphasis remap=tt>login:</emphasis> prompt appears on the + the <prompt>login:</prompt> prompt appears on the system's console - if it lights up, that should mean that FreeBSD has started a <command>getty</command> process on the appropriate communications port and is waiting @@ -20253,13 +20268,13 @@ AT&B2&W 115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen> </informalexample> - <para>If you see something different, like this:</para> + <para>If you see something different, like this: <informalexample> <screen> 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyd0</screen> </informalexample> - <para>and the modem has not accepted a call yet, this means that + and the modem has not accepted a call yet, this means that <command>getty</command> has completed its open on the communications port. This could indicate a problem with the cabling or a mis-configured modem, because <command>getty</command> should not be able to open the @@ -20267,7 +20282,7 @@ AT&B2&W has been asserted by the modem.</para> <para>If you do not see any <command>getty</command> - processes waiting to open the desired <filename>ttyd?</filename> + processes waiting to open the desired <filename>ttyd<replaceable>?</replaceable></filename> port, double-check your entries in <filename>/etc/ttys</filename> to see if there are any mistakes there. Also, check the log file @@ -20288,21 +20303,19 @@ AT&B2&W <para>Try dialing into the system; be sure to use 8 bits, no parity, 1 stop bit on the remote system. If you do not get a - prompt right away, or get garbage, try pressing <emphasis - remap=tt><Enter></emphasis> about once per second. If - you still do not see a <emphasis remap=tt>login:</emphasis> + prompt right away, or get garbage, try pressing <literal><Enter></literal> about once per second. If + you still do not see a <prompt>login:</prompt> prompt after a while, try sending a <command>BREAK</command>. If you are using a high-speed modem to do the dialing, try dialing again after locking the dialing modem's interface speed - (via <emphasis remap=tt>AT&B1</emphasis> on a USR Sportster, + (via <command>AT&B1</command> on a USR Sportster, for example).</para> - <para>If you still cannot get a <emphasis - remap=tt>login:</emphasis> prompt, check + <para>If you still cannot get a <prompt>login:</prompt> prompt, check <filename>/etc/gettytab</filename> again and double-check that</para> - <para> + <itemizedlist> <listitem> @@ -20322,7 +20335,7 @@ AT&B2&W </listitem> </itemizedlist> - </para> + <para>If you dial but the modem on the FreeBSD system will not answer, make sure that the modem is configured to answer the @@ -20345,7 +20358,7 @@ AT&B2&W <para>Thanks to these people for comments and advice:</para> - <para> + <variablelist> <varlistentry><term>&a.kelly;</term> <listitem> @@ -20353,7 +20366,7 @@ AT&B2&W </listitem> </varlistentry> </variablelist> - </para> + </sect2> </sect1> @@ -28080,7 +28093,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # Date created: 5 December 1994 # Whom: asami # -# $Id: book.sgml,v 1.39 1998-10-21 22:02:39 nik Exp $ +# $Id: book.sgml,v 1.40 1998-10-21 22:05:23 nik Exp $ # DISTNAME= oneko-1.1b |