os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Close tags with </foo> instead of </>.

Browse source 
PR:		20183
Submitted by:	Udo Erdelhoff <ue@nathan.ruhr.de>
This commit is contained in:
Jim Mock 2000-07-26 18:24:50 +00:00
parent 4aab8cc9fc
commit 82d7459043
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7733
12 changed files with 590 additions and 590 deletions
en_US.ISO8859-1/articles
fonts
article.sgml
formatting-media
article.sgml
mh
article.sgml
multi-os
article.sgml
new-users
article.sgml
programming-tools
article.sgml
en_US.ISO_8859-1/articles
fonts
article.sgml
formatting-media
article.sgml
mh
article.sgml
multi-os
article.sgml
new-users
article.sgml
programming-tools
article.sgml

38
en_US.ISO8859-1/articles/fonts/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v 1.7 1999/10/10 18:35:50 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v 1.8 2000/06/20 11:30:11 alex Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
@ -77,7 +77,7 @@
<variablelist>
<varlistentry>
<term><filename>.pfa</>, <filename>.pfb</></term>
<term><filename>.pfa</filename>, <filename>.pfb</filename></term>
<listitem>
<para>Postscript type 1 fonts. The
@ -89,7 +89,7 @@
</varlistentry>
<varlistentry>
<term><filename>.afm</></term>
<term><filename>.afm</filename></term>
<listitem>
<para>The font metrics associated with a type 1 font.</para>
@ -97,7 +97,7 @@
</varlistentry>
<varlistentry>
<term><filename>.pfm</></term>
<term><filename>.pfm</filename></term>
<listitem>
<para>The printer font metrics associated with a type 1
@ -106,7 +106,7 @@
</varlistentry>
<varlistentry>
<term><filename>.ttf</></term>
<term><filename>.ttf</filename></term>
<listitem>
<para>A TrueType font</para>
@ -114,7 +114,7 @@
</varlistentry>
<varlistentry>
<term><filename>.fot</></term>
<term><filename>.fot</filename></term>
<listitem>
<para>An indirect reference to a TrueType font (not an
@ -123,7 +123,7 @@
</varlistentry>
<varlistentry>
<term><filename>.fon</>, <filename>.fnt</></term>
<term><filename>.fon</filename>, <filename>.fnt</filename></term>
<listitem>
<para>Bitmapped screen fonts</para>
@ -157,7 +157,7 @@
<term>syscons</term>
<listitem>
<para><filename>.fnt</></para>
<para><filename>.fnt</filename></para>
</listitem>
</varlistentry>
</variablelist>
@ -271,7 +271,7 @@
is cross referenced to its X11 name by the contents of the
<filename>fonts.dir</filename> file in each directory.</para>
<para>There is already a directory named <filename>Type1</>. The
<para>There is already a directory named <filename>Type1</filename>. The
most straight forward way to add a new font is to put it into
this directory. A better way is to keep all new fonts in a
separate directory and use a symbolic link to the additional
@ -364,7 +364,7 @@ end readonly def
<listitem>
<para>Lets just name all the new fonts
<literal>type1</>.</para>
<literal>type1</literal>.</para>
</listitem>
</varlistentry>
@ -381,7 +381,7 @@ end readonly def
<listitem>
<para>Normal, bold, medium, semibold, etc. From the
<citerefentry><refentrytitle>strings</><manvolnum>1</></>
<citerefentry><refentrytitle>strings</refentrytitle><manvolnum>1</manvolnum></citerefentry>
output above, it appears that this font has a weight of
<emphasis>medium</emphasis>.</para>
</listitem>
@ -441,7 +441,7 @@ end readonly def
</informalexample>
as the name, and then use
<citerefentry><refentrytitle>xfontsel</><manvolnum>1</></> to
<citerefentry><refentrytitle>xfontsel</refentrytitle><manvolnum>1</manvolnum></citerefentry> to
examine it and adjust the name based on the appearance of the
font.</para>
@ -477,7 +477,7 @@ bash$ <userinput>xfontsel -pattern -type1-*</>
</informalexample>
<para>References: &man.xfontsel.1;, &man.xset.1;, <citetitle>The X
Windows System in a Nutshell</>, <ulink
Windows System in a Nutshell</citetitle>, <ulink
URL="http://www.ora.com/">O'Reilly &amp;
Associates</ulink>.</para>
</sect1>
@ -485,7 +485,7 @@ bash$ <userinput>xfontsel -pattern -type1-*</>
<sect1>
<title>Using type 1 fonts with Ghostscript</title>
<para>Ghostscript references a font via its <filename>Fontmap</>
<para>Ghostscript references a font via its <filename>Fontmap</filename>
file. This must be modified in a similar way to the X11
<filename>fonts.dir</filename> file. Ghostscript can use either
the <filename>.pfa</filename> or the <filename>.pfb</filename>
@ -541,7 +541,7 @@ GS&gt;<userinput>quit</>
<filename>/usr/share/groff_font/devps/SHOWBOAT</filename>. The
file must be created using tools provided by groff.</para>
<para>The first tool is <command>afmtodit</>. This is not
<para>The first tool is <command>afmtodit</command>. This is not
normally installed, so it must be retrieved from the source
distribution. I found I had to change the first line of the
file, so I did:</para>
@ -582,10 +582,10 @@ bash$ <userinput>/tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate
printer in order for the font to be used (unless the printer
happens to have the showboat font built in or on an accessible
font disk.) The final step is to create a down loadable font.
The <command>pfbtops</> tool is used to create the
The <command>pfbtops</command> tool is used to create the
<filename>.pfa</filename> format of the font, and the
<filename>download</> file is modified to reference the new
font. The <filename>download</> file must reference the
<filename>download</filename> file is modified to reference the new
font. The <filename>download</filename> file must reference the
internal name of the font. This can easily be determined from
the groff font file as illustrated:</para>
@ -686,7 +686,7 @@ bash$ <userinput>lpr -Ppostscript example.ps</>
<itemizedlist>
<listitem>
<para><filename>GS_TTF.PS</filename></para
<para><filename>GS_TTF.PS</filename></para>
</listitem>
<listitem>

6
en_US.ISO8859-1/articles/formatting-media/article.sgml
View file

@ -2,7 +2,7 @@
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
]>
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/formatting-media/article.sgml,v 1.12 1999/10/10 19:21:10 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/formatting-media/article.sgml,v 1.13 1999/10/30 18:10:14 dwhite Exp $ -->
<article>
<artheader>
<title>Formatting Media For Use With FreeBSD 2.2-RELEASE</title>
@ -151,7 +151,7 @@ now. -->
quite possible to destroy the contents of other disks in your
system if the proper precautions are not taken.</para>
<para><emphasis>Check your work carefully.</> It is very simple
<para><emphasis>Check your work carefully.</emphasis> It is very simple
to destroy the incorrect disk when working with these
commands. When in doubt consult the kernel boot output for
the proper device.</para>
@ -535,7 +535,7 @@ swapon: added /dev/sd0b as swap space
<para>To create a new CCD, execute the following commands. This
describes how to add three disks together; simply add or
remove devices as necessary. Remember that the disks to be
striped must be <emphasis>identical.</></para>
striped must be <emphasis>identical.</emphasis></para>
<para>Before executing these commands, make sure you add the line

298
en_US.ISO8859-1/articles/mh/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/mh/article.sgml,v 1.6 1999/10/10 19:29:59 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/mh/article.sgml,v 1.7 1999/10/10 20:20:38 jhb Exp $ -->
<!-- FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -35,7 +35,7 @@
initial philosophies behind MH were developed. MH isn't so much
a monolithic email program but a philosophy about how best to
develop tools for reading email. The MH developers have done a
great job adhering to the <acronym>KISS</> principle: Keep It
great job adhering to the <acronym>KISS</acronym> principle: Keep It
Simple Stupid. Rather than have one large program for reading,
sending and handling email they have written specialized
programs for each part of your email life. One might liken MH to
@ -64,9 +64,9 @@
</screen>
</informalexample>
You will notice that it created a <filename>/usr/local/lib/mh</>
You will notice that it created a <filename>/usr/local/lib/mh</filename>
directory for you as well as adding several binaries to the
<filename>/usr/local/bin</> directory. If you would prefer to
<filename>/usr/local/bin</filename> directory. If you would prefer to
compile it yourself then you can anonymous ftp it from <ulink
URL="ftp://ftp.ics.uci.edu/">ftp.ics.uci.edu</ulink> or <ulink
URL="ftp://louie.udel.edu/">louie.udel.edu</ulink>.</para>
@ -85,33 +85,33 @@
<sect1>
<title>Reading Mail</title>
<para>This section covers how to use <command>inc</>,
<command>show</>, <command>scan</>, <command>next</>,
<command>prev</>, <command>rmm</>, <command>rmf</>, and
<command>msgchk</>. One of the best things about MH is the
<para>This section covers how to use <command>inc</command>,
<command>show</command>, <command>scan</command>, <command>next</command>,
<command>prev</command>, <command>rmm</command>, <command>rmf</command>, and
<command>msgchk</command>. One of the best things about MH is the
consistent interface between programs. A few things to keep in
mind when using these commands is how to specify message lists.
In the case of <command>inc</> this doesn't really make any
sense but with commands like <command>show</> it is useful to
In the case of <command>inc</command> this doesn't really make any
sense but with commands like <command>show</command> it is useful to
know. </para>
<para>A message list can consist of something like <parameter>23
20 16</> which will act on messages 23, 20 and 16. This is
20 16</parameter> which will act on messages 23, 20 and 16. This is
fairly simple but you can do more useful things like
<parameter>23-30</> which will act on all the messages between
<parameter>23-30</parameter> which will act on all the messages between
23 and 30. You can also specify something like
<parameter>cur:10</> which will act on the current message and
the next 9 messages. The <parameter>cur</>, <parameter>last</>,
and <parameter>first</> messages are special messages that refer
<parameter>cur:10</parameter> which will act on the current message and
the next 9 messages. The <parameter>cur</parameter>, <parameter>last</parameter>,
and <parameter>first</parameter> messages are special messages that refer
to the current, last or first message in the folder.</para>
<sect2 id="inc">
<title><command>inc</>, <command>msgchk</>&mdash;read in your
<title><command>inc</command>, <command>msgchk</command>&mdash;read in your
new email or check it</title>
<para>If you just type in <userinput>inc</> and hit
<keycap>return</> you will be well on your way to getting
started with MH. The first time you run <command>inc</> it
<para>If you just type in <userinput>inc</userinput> and hit
<keycap>return</keycap> you will be well on your way to getting
started with MH. The first time you run <command>inc</command> it
will setup your account to use all the MH defaults and ask you
about creating a Mail directory. If you have mail waiting to
be downloaded you will see something that looks like:</para>
@ -126,45 +126,45 @@
</informalexample>
<para>This is the same thing you will see from a
<command>scan</> (see <xref linkend="scan">). If you just run
<command>inc</> with no arguments it will look on your
<command>scan</command> (see <xref linkend="scan">). If you just run
<command>inc</command> with no arguments it will look on your
computer for email that is supposed to be coming to
you.</para>
<para>A lot of people like to use POP for grabbing their email.
MH can do POP to grab your email. You will need to give
<command>inc</> a few command line arguments.</para>
<command>inc</command> a few command line arguments.</para>
<informalexample>
<screen>&prompt.user; <userinput>inc -host mail.pop.org -user <replaceable>username</> -norpop</>
</screen>
</informalexample>
<para>That tells <command>inc</> to go to
<parameter>mail.pop.org</> to download your email, and that
your username on their system is <replaceable>username</>. The
<option>-norpop</option> option tells <command>inc</> to use
<para>That tells <command>inc</command> to go to
<parameter>mail.pop.org</parameter> to download your email, and that
your username on their system is <replaceable>username</replaceable>. The
<option>-norpop</option> option tells <command>inc</command> to use
plain POP3 for downloading your email. MH has support for a
few different dialects of POP. More than likely you will never
ever need to use them though. While you can do more complex
things with inc such as audit files and scan format files this
will get you going.</para>
<para>The <command>msgchk</> command is used to get information
on whether or not you have new email. <command>msgchk</> takes
<para>The <command>msgchk</command> command is used to get information
on whether or not you have new email. <command>msgchk</command> takes
the same <option>-host</option> and <option>-user</option>
options that <command>inc</> takes.</para>
options that <command>inc</command> takes.</para>
</sect2>
<sect2 id="show">
<title><command>show</>, <command>next</> and
<command>prev</>&mdash;displaying and moving through
<title><command>show</command>, <command>next</command> and
<command>prev</command>&mdash;displaying and moving through
email</title>
<para><command>show</> is to show a letter in your current
folder. Like <command>inc</>, <command>show</> is a fairly
straightforward command. If you just type <userinput>show</>
and hit <keycap>return</> then it displays the current
<para><command>show</command> is to show a letter in your current
folder. Like <command>inc</command>, <command>show</command> is a fairly
straightforward command. If you just type <userinput>show</userinput>
and hit <keycap>return</keycap> then it displays the current
message. You can also give specific message numbers to
show:</para>
@ -175,23 +175,23 @@
<para>This would display message numbers 32, 45 and 56 right
after each other. Unless you change the default behavior
<command>show</> basically just does a <command>more</> on the
<command>show</command> basically just does a <command>more</command> on the
email message.</para>
<para><command>next</> is used to move onto the next message and
<command>prev</> will go to the previous message. Both
commands have an implied <command>show</> command so that when
<para><command>next</command> is used to move onto the next message and
<command>prev</command> will go to the previous message. Both
commands have an implied <command>show</command> command so that when
you go to the next message it automatically displays
it.</para>
</sect2>
<sect2 id="scan">
<title><command>scan</>&mdash;shows you a scan of your
<title><command>scan</command>&mdash;shows you a scan of your
messages</title>
<para><command>scan</> will display a brief listing of the
<para><command>scan</command> will display a brief listing of the
messages in your current folder. This is an example of what
the <command>scan</> command will give you.</para>
the <command>scan</command> command will give you.</para>
<informalexample>
<screen> 30+ 01/16 "Jordan K. Hubbar Re: FBSD 2.1&lt;&lt;&gt; Do you want a library instead of
@ -205,32 +205,32 @@
configurable. This is the typical default display. It gives
you the message number, the date on the email, the sender, the
subject line, and a sentence fragment from the very beginning
of the email if it can fit it. The <literal>+</> means that
of the email if it can fit it. The <literal>+</literal> means that
message is the current message, so if you do a
<command>show</> it will display that message.</para>
<command>show</command> it will display that message.</para>
<para>One useful option for scan is the
<option>-reverse</option> option. This will list your messages
with the highest message number first and lowest message
number last. Another useful option with <command>scan</> is to
number last. Another useful option with <command>scan</command> is to
have it read from a file. If you want to scan your incoming
mailbox on FreeBSD without having to <command>inc</> it you
mailbox on FreeBSD without having to <command>inc</command> it you
can do <command>scan -file
/var/mail/<replaceable>username</></command>. This can be used
with any file that is in the <database>mbox</> format.</para>
/var/mail/<replaceable>username</replaceable></command>. This can be used
with any file that is in the <database>mbox</database> format.</para>
</sect2>
<sect2 id="rmm">
<title><command>rmm</> and <command>rmf</>&mdash;remove the
<title><command>rmm</command> and <command>rmf</command>&mdash;remove the
current message or folder</title>
<para><command>rmm</> is used to remove a mail message. The
<para><command>rmm</command> is used to remove a mail message. The
default is typically to not actually remove the message but to
rename the file to one that is ignored by the MH commands. You
will need to through periodically and physically delete the
<quote>removed</> messages.</para>
<quote>removed</quote> messages.</para>
<para>The <command>rmf</> command is used to remove folders.
<para>The <command>rmf</command> command is used to remove folders.
This doesn't just rename the files but actually removes the
from the hard drive so you should be careful when you use this
command.</para>
@ -240,8 +240,8 @@
<title>A typical session of reading with MH</title>
<para>The first thing that you will want to do is
<command>inc</> your new mail. So at a shell prompt just type
in <command>inc</> and hit <keycap>return</>.</para>
<command>inc</command> your new mail. So at a shell prompt just type
in <command>inc</command> and hit <keycap>return</keycap>.</para>
<informalexample>
<screen>&prompt.user; <userinput>inc</>
@ -255,7 +255,7 @@ Incorporating new mail into inbox...
</informalexample>
<para>This shows you the new email that has been added to your
mailbox. So the next thing to do is <command>show</> the email
mailbox. So the next thing to do is <command>show</command> the email
and move around.</para>
<informalexample>
@ -298,8 +298,8 @@ which I am probably the guilty party).
</screen>
</informalexample>
<para>The <command>rmm</> removed the current message and the
<command>next</> command moved me on to the next message. Now
<para>The <command>rmm</command> removed the current message and the
<command>next</command> command moved me on to the next message. Now
if I wanted to look at ten most recent messages so I could
read one of them here is what I would do:</para>
@ -320,7 +320,7 @@ which I am probably the guilty party).
</informalexample>
<para>Then if I wanted to read message number 27 I would do a
<userinput>show 27</> and it would be displayed. As you can
<userinput>show 27</userinput> and it would be displayed. As you can
probably tell from this sample session MH is pretty easy to
use and looking through emails and displaying them is fairly
intuitive and easy.</para>
@ -337,19 +337,19 @@ which I am probably the guilty party).
the concept of folders. You have undoubtedly come across the
folders concept using other email programs. MH has folders too.
MH can even do sub-folders of a folder. One thing you should
keep in mind with MH is that when you ran <command>inc</> for
keep in mind with MH is that when you ran <command>inc</command> for
the first time and it asked you if it could create a
<filename>Mail</> directory it began storing everything in that
<filename>Mail</filename> directory it began storing everything in that
directory. If you look at that directory you will find a
directory named <filename>inbox</>. The <filename>inbox</>
directory named <filename>inbox</filename>. The <filename>inbox</filename>
directory houses all of your incoming mail that hasn't been
thrown anywhere else.</para>
<para>Whenever you create a new folder a new directory is going to
be created underneath your MH <filename>Mail</> directory, and
be created underneath your MH <filename>Mail</filename> directory, and
messages in that folder are going to be stored in that
directory. When new email comes in that new email is thrown
into your <filename>inbox</> directory with a file name that is
into your <filename>inbox</filename> directory with a file name that is
equivalent to the message number. So even if you didn't have
any of the MH tools to read your email you could still use
standard UNIX commands to munge around in those directories and
@ -357,28 +357,28 @@ which I am probably the guilty party).
a lot of power with what you can do with your email.</para>
<para>Just as you can use message lists like <parameter>23 16
42</> with most MH commands there is a folder option you can
42</parameter> with most MH commands there is a folder option you can
specify with just about every MH command. If you do a
<command>scan +freebsd</> it will scan your <filename>freebsd</>
<command>scan +freebsd</command> it will scan your <filename>freebsd</filename>
folder, and your current folder will be changed to
<filename>freebsd</>. If you do a <command>show +freebsd 23 16
42</>, <command>show</> is going to switch to your
<filename>freebsd</> folder and display messages 23, 16 and 42.
So remember that <option>+<replaceable>folder</></> syntax. You
<filename>freebsd</filename>. If you do a <command>show +freebsd 23 16
42</command>, <command>show</command> is going to switch to your
<filename>freebsd</filename> folder and display messages 23, 16 and 42.
So remember that <option>+<replaceable>folder</replaceable></option> syntax. You
will need to make sure you use it to make commands process
different folders. Remember you default folder for mail is
<filename>inbox</> so doing a <command>folder +inbox</> should
<filename>inbox</filename> so doing a <command>folder +inbox</command> should
always get you back to your mail. Of course, in MH's infinite
flexibility this can be changed but most places have probably
left it as <command>inbox</>.</para>
left it as <command>inbox</command>.</para>
<sect2>
<title><command>pick</>&mdash;search email that matches certain
<title><command>pick</command>&mdash;search email that matches certain
criteria</title>
<para><command>pick</> is one of the more complex commands in
<para><command>pick</command> is one of the more complex commands in
the MH system. So you might want to read the
<citerefentry><refentrytitle>pick</><manvolnum>1</></> man
<citerefentry><refentrytitle>pick</refentrytitle><manvolnum>1</manvolnum></citerefentry> man
page for a more thorough understanding. At its simplest level
you can do something like</para>
@ -392,12 +392,12 @@ which I am probably the guilty party).
</screen>
</informalexample>
<para>This will tell <command>pick</> to look through every
<para>This will tell <command>pick</command> to look through every
single line in every message in your current folder and tell
you which message numbers it found the word <literal>pci</>
in. You can then <command>show</> those messages and read them
if you wish or <command>rmm</> them. You would have to specify
something like <command>show 15 42 55-57</> to display them
you which message numbers it found the word <literal>pci</literal>
in. You can then <command>show</command> those messages and read them
if you wish or <command>rmm</command> them. You would have to specify
something like <command>show 15 42 55-57</command> to display them
though. A slightly more useful thing to do is this:</para>
<informalexample>
@ -410,16 +410,16 @@ which I am probably the guilty party).
<para>This will show you the same messages you just didn't have
to work as hard to do it. The <option>-seq</option> option is
really an abbreviation of <option>-sequence</option> and
<command>pick</> is just a sequence which contains the message
<command>pick</command> is just a sequence which contains the message
numbers that matched. You can use sequences with just about
any MH command. So you could have done an <command>rmm pick</>
any MH command. So you could have done an <command>rmm pick</command>
and all those messages would be removed instead. You sequence
can be named anything. If you run pick again it will overwrite
the old sequence if you use the same name.</para>
<para>Doing a <command>pick -search</command> can be a bit more
time consuming than just searching for message from someone,
or to someone. So <command>pick</> allows you to use the
or to someone. So <command>pick</command> allows you to use the
following predefined search criteria:</para>
<variablelist>
@ -468,7 +468,7 @@ which I am probably the guilty party).
<listitem>
<para>search for any other component in the header. (i.e.
<option>--reply-to</> to find all emails with a certain
<option>--reply-to</option> to find all emails with a certain
reply-to in the header)</para>
</listitem>
</varlistentry>
@ -482,7 +482,7 @@ which I am probably the guilty party).
</informalexample>
to get a list of all the email send to the FreeBSD hackers
mailing list. <command>pick</> also allows you to group these
mailing list. <command>pick</command> also allows you to group these
criteria in different ways using the following options:</para>
<itemizedlist>
@ -531,42 +531,42 @@ which I am probably the guilty party).
something called operator precedence. Remember in math how you
evaluate from left to right and you do multiplication and
division first and addition and subtraction second? MH has the
same type of rules for <command>pick</>. It's fairly complex
same type of rules for <command>pick</command>. It's fairly complex
so you might want to study the man page. This document is just
to help you get acquainted with MH.</para>
</sect2>
<sect2>
<title><command>folder</>, <command>folders</>,
<command>refile</>&mdash;three useful programs for folder
<title><command>folder</command>, <command>folders</command>,
<command>refile</command>&mdash;three useful programs for folder
maintenance</title>
<para>There are three programs which are primarily just for
manipulating your folders. The <command>folder</> program is
manipulating your folders. The <command>folder</command> program is
used to switch between folders, pack them, and list them. At
its simplest level you can do a <command>folder
+<replaceable>newfolder</></> and you will be switched into
<replaceable>newfolder</>. From there on out all your MH
commands like <command>comp</>, <command>repl</>,
<command>scan</>, and <command>show</> will act on that
<command>newfolder</> folder.</para>
+<replaceable>newfolder</replaceable></command> and you will be switched into
<replaceable>newfolder</replaceable>. From there on out all your MH
commands like <command>comp</command>, <command>repl</command>,
<command>scan</command>, and <command>show</command> will act on that
<command>newfolder</command> folder.</para>
<para>Sometimes when you are reading and deleting messages you
will develop <quote>holes</> in your folders. If you do a
<command>scan</> you might just see messages 34, 35, 36, 43,
will develop <quote>holes</quote> in your folders. If you do a
<command>scan</command> you might just see messages 34, 35, 36, 43,
55, 56, 57, 80. If you do a <command>folder -pack</command>
this will renumber all your messages so that there are no
holes. It doesn't actually delete any messages though. So you
may need to periodically go through and physically delete
<command>rmm</>'d messages.</para>
<command>rmm</command>'d messages.</para>
<para>If you need statistics on your folders you can do a
<command>folders</> or <command>folder -all</command> to list
<command>folders</command> or <command>folder -all</command> to list
all your folders, how many messages they have, what the
current message is in each one and so on. This line of stats
it displays for all your folders is the same one you get when
you change to a folder with <command>folder +foldername</>. A
<command>folders</> command looks like this:</para>
you change to a folder with <command>folder +foldername</command>. A
<command>folders</command> command looks like this:</para>
<informalexample>
<screen> Folder # of messages ( range ); cur msg (other files)
@ -585,17 +585,17 @@ which I am probably the guilty party).
</screen>
</informalexample>
<para>The <command>refile</> command is what you use to move
<para>The <command>refile</command> command is what you use to move
messages between folders. When you do something like
<command>refile 23 +netfuture</> message number 23 is moved
into the <filename>netfuture</> folder. You could also do
something like <command>refile 23 +netfuture/latest</> which
<command>refile 23 +netfuture</command> message number 23 is moved
into the <filename>netfuture</filename> folder. You could also do
something like <command>refile 23 +netfuture/latest</command> which
would put message number 23 in a subfolder called
<filename>latest</> under the <filename>netfuture</> folder.
<filename>latest</filename> under the <filename>netfuture</filename> folder.
If you want to keep a message in the current folder and link
it you can do a <command>refile -link 23 +netfuture</command>
which would keep 23 in your current <filename>inbox</> but
also list in your <filename>netfuture</> folder. You are
which would keep 23 in your current <filename>inbox</filename> but
also list in your <filename>netfuture</filename> folder. You are
probably beginning to realize some of the really powerful
things you can do with MH.</para>
</sect2>
@ -613,29 +613,29 @@ which I am probably the guilty party).
Subject: headers already in it. You are then sent into your
editor where you fill in the header information and then type
the body of your message below the dashed lines in the message.
Then to the <command>whatnow</> program. When you are at the
Then to the <command>whatnow</command> program. When you are at the
<prompt>What now?</prompt> prompt you can tell it to
<command>send</>, <command>list</>, <command>edit</>,
<command>edit</>, <command>push</>, and <command>quit</>. Most
<command>send</command>, <command>list</command>, <command>edit</command>,
<command>edit</command>, <command>push</command>, and <command>quit</command>. Most
of these commands are self-explanatory. So the message sending
process involves copying a component file, editing your email,
and then telling the <command>whatnow</> program what to do with
and then telling the <command>whatnow</command> program what to do with
your email.</para>
<sect2>
<title><command>comp</>, <command>forw</>,
<command>reply</>&mdash;compose, forward or reply to a message
<title><command>comp</command>, <command>forw</command>,
<command>reply</command>&mdash;compose, forward or reply to a message
to someone</title>
<para>The <command>comp</> program has a few useful command line
<para>The <command>comp</command> program has a few useful command line
options. The most important one to know right now is the
<option>-editor</option> option. When MH is installed the
default editor is usually a program called
<command>prompter</> which comes with MH. It's not a very
<command>prompter</command> which comes with MH. It's not a very
exciting editor and basically just gets the job done. So when
you go to compose a message to someone you might want to use
<command>comp -editor /usr/bin/vi/</> or <command>comp -editor
/usr/local/bin/pico/</> instead. Once you have run
<command>comp -editor /usr/bin/vi/</command> or <command>comp -editor
/usr/local/bin/pico/</command> instead. Once you have run
<emphasis>comp</emphasis> you are in your editor and you see
something that looks like this:</para>
@ -648,9 +648,9 @@ Subject:
</informalexample>
<para>You need to put the person you are sending the mail to
after the <literal>To:</> line. It works the same way for the
after the <literal>To:</literal> line. It works the same way for the
other headers also, so you would need to put your subject
after the <literal>Subject:</> line. Then you would just put
after the <literal>Subject:</literal> line. Then you would just put
the body of your message after the dashed lines. It may seem a
bit simplistic since a lot of email programs have special
requesters that ask you for this information but there really
@ -667,55 +667,55 @@ Subject:<userinput>And on the 8th day God created the FreeBSD core team</>
</informalexample>
<para>You can now save this message and exit your editor. You
will see the <prompt>What now?</> prompt and you can type in
<userinput>send</> or <userinput>s</> and hit
<keycap>return</>. Then the FreeBSD core team will receive
will see the <prompt>What now?</prompt> prompt and you can type in
<userinput>send</userinput> or <userinput>s</userinput> and hit
<keycap>return</keycap>. Then the FreeBSD core team will receive
their just rewards. As I mentioned earlier you can also use
other commands, for example <command>quit</> if you don't want
other commands, for example <command>quit</command> if you don't want
to send the message.</para>
<para>The <command>forw</> command is stunningly similar. The
<para>The <command>forw</command> command is stunningly similar. The
big difference being that the message you are forwarding is
automatically included in the outgoing message. When you run
<command>forw</> it will forward your current message. You can
<command>forw</command> it will forward your current message. You can
always tell it to forward something else by doing something
like <command>forw 23</> and then message number 23 will be
like <command>forw 23</command> and then message number 23 will be
put in your outgoing message instead of the current message.
Beyond those small differences <command>forw</> functions
exactly the same as <command>comp</>. You go through the exact
Beyond those small differences <command>forw</command> functions
exactly the same as <command>comp</command>. You go through the exact
same message sending process.</para>
<para>The <command>repl</> command will reply to whatever your
<para>The <command>repl</command> command will reply to whatever your
current message is, unless you give it a different message to
reply to. <command>repl</> will do its best to go ahead and
reply to. <command>repl</command> will do its best to go ahead and
fill in some of the email headers already. So you will notice
that the <literal>To:</> header already has the address of the
recipient in there. Also the <literal>Subject:</> line will
that the <literal>To:</literal> header already has the address of the
recipient in there. Also the <literal>Subject:</literal> line will
already be filled in. You then go about the normal message
composition process and you are done. One useful command line
option to know here is the <option>-cc</option> option. You
can use <parameter>all</>, <parameter>to</>, <parameter>cc</>,
<parameter>me</> after the <option>-cc</option> option to have
<command>repl</> automatically add the various addresses to
can use <parameter>all</parameter>, <parameter>to</parameter>, <parameter>cc</parameter>,
<parameter>me</parameter> after the <option>-cc</option> option to have
<command>repl</command> automatically add the various addresses to
the cc list in the message. You have probably noticed that the
original message isn't included. This is because most MH
setups are configured to do this from the start.</para>
</sect2>
<sect2>
<title><filename>components</>, and
<filename>replcomps</>&mdash;components files for
<command>comp</> and <command>repl</></title>
<title><filename>components</filename>, and
<filename>replcomps</filename>&mdash;components files for
<command>comp</command> and <command>repl</command></title>
<para>The <filename>components</> file is usually in
<para>The <filename>components</filename> file is usually in
<filename>/usr/local/lib/mh</filename>. You can copy that file
into your MH Mail directory and edit to contain what you want
it to contain. It is a fairly basic file. You have various
email headers at the top, a dashed line and then nothing. The
<command>comp</command> command just copies this
<filename>components</> file and then edits it. You can add
<filename>components</filename> file and then edits it. You can add
any kind of valid RFC822 header you want. For instance you
could have something like this in your <filename>components</>
could have something like this in your <filename>components</filename>
file:</para>
<informalexample>
@ -729,13 +729,13 @@ X-Home-Page: http://www.FreeBSD.org/
</informalexample>
<para>MH would then copy this components file and throw you into
your editor. The <filename>components</> file is fairly
your editor. The <filename>components</filename> file is fairly
simple. If you wanted to have a signature on those messages
you would just put your signature in that
<filename>components</> file.</para>
<filename>components</filename> file.</para>
<para>The <filename>replcomps</> file is a bit more complex. The
default <filename>replcomps</> looks like this:</para>
<para>The <filename>replcomps</filename> file is a bit more complex. The
default <filename>replcomps</filename> looks like this:</para>
<informalexample>
<screen>%(lit)%(formataddr %&lt;{reply-to}%?{from}%?{sender}%?{return-path}%&gt;)\
@ -752,12 +752,12 @@ X-Home-Page: http://www.FreeBSD.org/
</informalexample>
<para>It's in the same basic format as the
<filename>components</> file but it contains quite a few extra
formatting codes. The <literal>%(lit)</> command makes room
for the address. The <literal>%(formataddr</> is a function
<filename>components</filename> file but it contains quite a few extra
formatting codes. The <literal>%(lit)</literal> command makes room
for the address. The <literal>%(formataddr</literal> is a function
that returns a proper email address. The next part is
<literal>%&lt;</literal> which means if and the
<literal>{reply-to}</> means the reply-to field in the
<literal>{reply-to}</literal> means the reply-to field in the
original message. So that might be translated this way:</para>
<informalexample>
@ -774,7 +774,7 @@ message</emphasis>, %&gt; <emphasis remap=bf>endif</emphasis>.
variables mean. All of the information on writing these format
strings is in the MH-Format man page. The really nice thing is
that once you have built your customized
<filename>replcomps</> file you won't need to touch it again.
<filename>replcomps</filename> file you won't need to touch it again.
No other email program really gives you the power and
flexibility that MH gives you.</para>
</sect2>

62
en_US.ISO8859-1/articles/multi-os/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/multi-os/article.sgml,v 1.11 1999/10/13 10:51:58 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/multi-os/article.sgml,v 1.12 2000/05/30 22:48:47 nik Exp $ -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
<article>
<artheader>
@ -144,11 +144,11 @@
<itemizedlist>
<listitem>
<para><filename>/dev/wd0</> (first physical hard disk)</para>
<para><filename>/dev/wd0</filename> (first physical hard disk)</para>
</listitem>
<listitem>
<para><filename>/dev/wd1</> (second hard disk)</para>
<para><filename>/dev/wd1</filename> (second hard disk)</para>
</listitem>
</itemizedlist>
@ -157,7 +157,7 @@
<procedure>
<step>
<para>I boot from a MS-DOS or Windows 95 boot disk that
contains the <filename>FDISK.EXE</> utility and make a small
contains the <filename>FDISK.EXE</filename> utility and make a small
50 meg primary partition (35-40 for Windows 95, plus a
little breathing room) on the first disk. Also create a
larger partition on the second hard disk for my Windows
@ -166,7 +166,7 @@
<step>
<para>I reboot and install Windows 95 (easier said than done)
on the <filename>C:</> partition.</para>
on the <filename>C:</filename> partition.</para>
</step>
<step>
@ -191,15 +191,15 @@
1024th cylinder. (The 1024th cylinder is 528 megs into the
disk with our hypothetical 720MB disks). I will use the
rest of the hard drive (about 270 megs) for the
<filename>/usr</> and <filename>/</> slices if I wish. The
<filename>/usr</filename> and <filename>/</filename> slices if I wish. The
rest of the second hard disk (size depends on the amount of
my Windows application/data partition that I created in step
1 can go to the <filename>/usr/src</> slice and swap
1 can go to the <filename>/usr/src</filename> slice and swap
space.</para>
</step>
<step>
<para>When viewed with the Windows 95 <command>fdisk</>
<para>When viewed with the Windows 95 <command>fdisk</command>
utility, my hard drives should now look something like this:
<screen>
@ -238,14 +238,14 @@ Press Esc to continue
<step>
<para>Install FreeBSD. I make sure to boot with my first hard
disk set at <quote>NORMAL</> in the BIOS. If it is not,
disk set at <quote>NORMAL</quote> in the BIOS. If it is not,
I'll have the enter my true disk geometry at boot time (to
get this, boot Windows 95 and consult Microsoft Diagnostics
(<filename>MSD.EXE</>), or check your BIOS) with the
parameter <literal>hd0=1416,16,63</> where
<replaceable>1416</> is the number of cylinders on my hard
disk, <replaceable>16</> is the number of heads per track,
and <replaceable>63</> is the number of sectors per track on
(<filename>MSD.EXE</filename>), or check your BIOS) with the
parameter <literal>hd0=1416,16,63</literal> where
<replaceable>1416</replaceable> is the number of cylinders on my hard
disk, <replaceable>16</replaceable> is the number of heads per track,
and <replaceable>63</replaceable> is the number of sectors per track on
the drive.</para>
</step>
@ -275,7 +275,7 @@ Press Esc to continue
cylinder.</para>
<para>If you install Windows 95 on an existing BSD system, it will
<quote>destroy</> the MBR, and you will have to reinstall your
<quote>destroy</quote> the MBR, and you will have to reinstall your
previous boot manager. Boot Easy can be reinstalled by using
the BOOTINST.EXE utility included in the \TOOLS directory on the
CD-ROM, and via <ulink
@ -305,19 +305,19 @@ Press Esc to continue
<email>jayrich@sysc.com</email>)</emphasis>.</para>
<para>FreeBSD+Win95: If you installed FreeBSD after Windows 95,
you should see <literal>DOS</> on the Boot Easy menu. This is
you should see <literal>DOS</literal> on the Boot Easy menu. This is
Windows 95. If you installed Windows 95 after FreeBSD, read
<xref linkend="ch4"> above. As long as your hard disk does not
have 1024 cylinders you should not have a problem booting. If
one of your partitions goes beyond the 1024th cylinder however,
and you get messages like <errorname>invalid system disk</>
and you get messages like <errorname>invalid system disk</errorname>
under DOS (Windows 95) and FreeBSD will not boot, try looking
for a setting in your BIOS called <quote>&gt; 1024 cylinder
support</> or <quote>NORMAL/LBA</> mode. DOS may need LBA
support</quote> or <quote>NORMAL/LBA</quote> mode. DOS may need LBA
(Logical Block Addressing) in order to boot correctly. If the
idea of switching BIOS settings every time you boot up doesn't
appeal to you, you can boot FreeBSD through DOS via the
<filename>FBSDBOOT.EXE</> utility on the CD (It should find your
<filename>FBSDBOOT.EXE</filename> utility on the CD (It should find your
FreeBSD partition and boot it.)</para>
<para>FreeBSD+OS/2+Win95: Nothing new here. OS/2's boot manger
@ -399,7 +399,7 @@ Press Esc to continue
<informalexample>
<para>(# of cylinders) &times; (# heads) &times; (63
sectors/track) &times; (512 bytes/sect)</>
sectors/track) &times; (512 bytes/sect)</para>
</informalexample>
<para>For example, on my 1.6 Gig Western Digital AC31600 EIDE hard
@ -419,9 +419,9 @@ Press Esc to continue
though: if you're using BIOS LBA (see <xref
linkend="limits">), you can't use just any program to get
the physical geometry. This is because many programs (e.g.
<filename>MSD.EXE</> or FreeBSD fdisk) don't identify the
<filename>MSD.EXE</filename> or FreeBSD fdisk) don't identify the
physical disk geometry; they instead report the
<firstterm>translated geometry</> (virtual numbers from using
<firstterm>translated geometry</firstterm> (virtual numbers from using
LBA). Stay tuned for what that means.</para>
<para>One other useful thing about these terms. Given 3
@ -434,9 +434,9 @@ Press Esc to continue
<para>For those that are interested in more technical details,
information on disk geometry, boot sectors, BIOSes, etc. can
be found all over the net. Query Lycos, Yahoo, etc. for
<literal>boot sector</> or <literal>master boot record</>.
<literal>boot sector</literal> or <literal>master boot record</literal>.
Among the useful info you'll find are Hale Landis's
<citetitle>How It Works</> document pack. See the <xref
<citetitle>How It Works</citetitle> document pack. See the <xref
linkend="sources"> section for a few pointers to this
pack.</para>
@ -449,21 +449,21 @@ Press Esc to continue
<para>On the first sector of your disk (Cyl 0, Head 0, Sector 1)
lives the Master Boot Record (MBR). It contains a map of your
disk. It identifies up to 4 <firstterm>partitions</>, each of
disk. It identifies up to 4 <firstterm>partitions</firstterm>, each of
which is a contiguous chunk of that disk. FreeBSD calls
partitions <firstterm>slices</> to avoid confusion with it's
partitions <firstterm>slices</firstterm> to avoid confusion with it's
own partitions, but we won't do that here. Each partition can
contain its own operating system.</para>
<para>Each partition entry in the MBR has a <firstterm>Partition
ID</>, a <firstterm>Start Cylinder/Head/Sector</>, and an
<firstterm>End Cylinder/Head/Sector</>. The Partition ID
ID</firstterm>, a <firstterm>Start Cylinder/Head/Sector</firstterm>, and an
<firstterm>End Cylinder/Head/Sector</firstterm>. The Partition ID
tells what type of partition it is (what OS) and the Start/End
tells where it is. <xref linkend="tbl-pid"> lists a
smattering of some common Partition IDs.</para>
<table id="tbl-pid">
<title>Partition IDs</>
<title>Partition IDs</title>
<tgroup cols="2">
<thead>
@ -515,7 +515,7 @@ Press Esc to continue
<para>Note that not all partitions are bootable (e.g. Extended
DOS). Some are&mdash;some aren't. What makes a partition
bootable is the configuration of the <firstterm>Partition Boot
Sector</> that exists at the beginning of each
Sector</firstterm> that exists at the beginning of each
partition.</para>
<para>When you configure your favorite boot manager, it looks up
@ -577,7 +577,7 @@ Press Esc to continue
</listitem>
<listitem>
<para>64 sectors/track, max (actually 63, <literal>0</>
<para>64 sectors/track, max (actually 63, <literal>0</literal>
isn't available)</para>
</listitem>
</itemizedlist>

126
en_US.ISO8859-1/articles/new-users/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/new-users/article.sgml,v 1.12 1999/10/12 12:41:51 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/new-users/article.sgml,v 1.13 2000/06/27 02:48:51 kevlo Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -565,7 +565,7 @@
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</><keycap>L</></keycombo></term>
<term><keycombo><keycap>Ctrl</keycap><keycap>L</keycap></keycombo></term>
<listitem>
<para>to redraw the screen</para>
@ -573,36 +573,36 @@
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</><keycap>b</></> and
<keycombo><keycap>Ctrl</><keycap>f</></></term>
<term><keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> and
<keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo></term>
<listitem>
<para>go back and forward a screen, as they do with
<command>more</> and <command>view</>.</para>
<command>more</command> and <command>view</command>.</para>
</listitem>
</varlistentry>
</variablelist>
<para>Practice with <command>vi</> in your home directory by
creating a new file with <command>vi <replaceable>filename</></>
<para>Practice with <command>vi</command> in your home directory by
creating a new file with <command>vi <replaceable>filename</replaceable></command>
and adding and deleting text, saving the file, and calling it up
again. <command>vi</> delivers some surprises because it's
again. <command>vi</command> delivers some surprises because it's
really quite complex, and sometimes you'll inadvertently issue a
command that will do something you don't expect. (Some people
actually like <command>vi</>&mdash;it's more powerful than DOS
EDIT&mdash;find out about the <command>:r</> command.) Use
<keycap>Esc</> one or more times to be sure you're in command
actually like <command>vi</command>&mdash;it's more powerful than DOS
EDIT&mdash;find out about the <command>:r</command> command.) Use
<keycap>Esc</keycap> one or more times to be sure you're in command
mode and proceed from there when it gives you trouble, save
often with <command>:w</>, and use <command>:q!</> to get out
and start over (from your last <command>:w</>) when you need
often with <command>:w</command>, and use <command>:q!</command> to get out
and start over (from your last <command>:w</command>) when you need
to.</para>
<para>Now you can <command>cd</> to <filename>/etc</filename>,
<command>su</> to root, use <command>vi</> to edit the file
<para>Now you can <command>cd</command> to <filename>/etc</filename>,
<command>su</command> to root, use <command>vi</command> to edit the file
<filename>/etc/group</filename>, and add a user to wheel so the
user has root privileges. Just add a comma and the user's login
name to the end of the first line in the file, press
<keycap>Esc</>, and use <command>:wq</> to write the file to
<keycap>Esc</keycap>, and use <command>:wq</command> to write the file to
disk and quit. Instantly effective. (You didn't put a space
after the comma, did you?)</para>
</sect1>
@ -625,7 +625,7 @@
<para>will remove formatting codes and send the man page to the
<filename>chmod.txt</filename> file instead of showing it on
your screen. Now put a dos-formatted diskette in your floppy
drive a, <command>su</> to root, and type</para>
drive a, <command>su</command> to root, and type</para>
<informalexample>
<screen>&prompt.root; <userinput>/sbin/mount -t msdos /dev/fd0 /mnt</>
@ -636,7 +636,7 @@
<filename>/mnt</filename>.</para>
<para>Now (you no longer need to be root, and you can type
<command>exit</> to get back to being user jack) you can go to
<command>exit</command> to get back to being user jack) you can go to
the directory where you created chmod.txt and copy the file to
the floppy with:</para>
@ -661,10 +661,10 @@
<command>/sbin/dmesg</command> is the boot log record, and it's
useful to understand it because it shows what FreeBSD found when
it booted up. If you ask questions on
<email>freebsd-questions@FreeBSD.org</> or on a USENET
<email>freebsd-questions@FreeBSD.org</email> or on a USENET
group&mdash;like <quote>FreeBSD isn't finding my tape drive,
what do I do?</quote>&mdash;people will want to know what
<command>dmesg</> has to say.</para>
<command>dmesg</command> has to say.</para>
<para>You can now dismount the floppy drive (as root) to get the
disk out with</para>
@ -679,7 +679,7 @@
Wordpad, or a word processor, make a minor change so the file
has to be saved, and print as you normally would from DOS or
Windows. Hope it works! man pages come out best if printed
with the dos <command>print</> command. (Copying files from
with the dos <command>print</command> command. (Copying files from
FreeBSD to a mounted dos partition is in some cases still a
little risky.)</para>
@ -687,15 +687,15 @@
an appropriate entry in <filename>/etc/printcap</filename> and
creating a matching spool directory in
<filename>/var/spool/output</filename>. If your printer is on
<hardware>lpt0</> (what dos calls <hardware>LPT1</>), you may
<hardware>lpt0</hardware> (what dos calls <hardware>LPT1</hardware>), you may
only need to go to <filename>/var/spool/output</filename> and
(as root) create the directory <filename>lpd</> by typing:
(as root) create the directory <filename>lpd</filename> by typing:
<command> mkdir lpd</command>, if it doesn't already exist.
Then the printer should respond if it's turned on when the
system is booted, and lp or lpr should send a file to the
printer. Whether or not the file actually prints depends on
configuring it, which is covered in the <ulink
URL="../../handbook/handbook.html">FreeBSD handbook.</></para>
URL="../../handbook/handbook.html">FreeBSD handbook.</ulink></para>
</sect1>
<sect1>
@ -703,7 +703,7 @@
<variablelist>
<varlistentry>
<term><command>df</></term>
<term><command>df</command></term>
<listitem>
<para>shows file space and mounted systems.</para>
@ -711,27 +711,27 @@
</varlistentry>
<varlistentry>
<term><command>ps aux</></term>
<term><command>ps aux</command></term>
<listitem>
<para>shows processes running. <command>ps ax</> is a
<para>shows processes running. <command>ps ax</command> is a
narrower form.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rm <replaceable>filename</></></term>
<term><command>rm <replaceable>filename</replaceable></command></term>
<listitem>
<para>remove <replaceable>filename</>.</para>
<para>remove <replaceable>filename</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rm -R <replaceable>dir</></></term>
<term><command>rm -R <replaceable>dir</replaceable></command></term>
<listitem>
<para>removes a directory <replaceable>dir</> and all
<para>removes a directory <replaceable>dir</replaceable> and all
subdirectories&mdash;careful!</para>
</listitem>
</varlistentry>
@ -750,7 +750,7 @@
</varlistentry>
<varlistentry>
<term><command>passwd</></term>
<term><command>passwd</command></term>
<listitem>
<para>to change user's password (or root's password)</para>
@ -758,7 +758,7 @@
</varlistentry>
<varlistentry>
<term><command>man hier</></term>
<term><command>man hier</command></term>
<listitem>
<para>man page on the Unix file system</para>
@ -766,7 +766,7 @@
</varlistentry>
</variablelist>
<para>Use <command>find</> to locate filename in
<para>Use <command>find</command> to locate filename in
<filename>/usr</filename> or any of its subdirectories
with</para>
@ -776,7 +776,7 @@
</informalexample>
<para>You can use <literal>*</literal> as a wildcard in
<parameter>"<replaceable>filename</>"</> (which should be in
<parameter>"<replaceable>filename</replaceable>"</parameter> (which should be in
quotes). If you tell find to search in <filename>/</filename>
instead of <filename>/usr</filename> it will look for the
file(s) on all mounted file systems, including the CDROM and the
@ -802,7 +802,7 @@
URL="http://www.cdrom.com/">Walnut Creek</ulink> CDROM as well
as the web site. The handbook tells you more about how to use
them (get the package if it exists, with <command>pkg_add
/cdrom/packages/All/<replaceable>packagename</></>, where
/cdrom/packages/All/<replaceable>packagename</replaceable></command>, where
<replaceable>packagename</replaceable> is the filename of the
package). The cdrom has lists of the packages and ports with
brief descriptions in <filename>cdrom/packages/index</filename>,
@ -813,10 +813,10 @@
programs and program names respectively.</para>
<para>If you find the handbook too sophisticated (what with
<command>lndir</> and all) on installing ports from the cdrom,
<command>lndir</command> and all) on installing ports from the cdrom,
here's what usually works:</para>
<para>Find the port you want, say <command>kermit</>. There will
<para>Find the port you want, say <command>kermit</command>. There will
be a directory for it on the cdrom. Copy the subdirectory to
<filename>/usr/local</filename> (a good place for software you
add that should be available to all users) with:</para>
@ -833,16 +833,16 @@
<para>Next, create the directory
<filename>/usr/ports/distfiles</filename> if it doesn't already
exist using <command>mkdir</>. Now check check
exist using <command>mkdir</command>. Now check check
<filename>/cdrom/ports/distfiles</filename> for a file with a
name that indicates it's the port you want. Copy that file to
<filename>/usr/ports/distfiles</filename>; in recent versions
you can skip this step, as FreeBSD will do it for you. In the
case of <command>kermit</>, there is no distfile.</para>
case of <command>kermit</command>, there is no distfile.</para>
<para>Then <command>cd</> to the subdirectory of
<para>Then <command>cd</command> to the subdirectory of
<filename>/usr/local/kermit</filename> that has the file
<filename>Makefile</>. Type</para>
<filename>Makefile</filename>. Type</para>
<informalexample>
<screen>&prompt.root; <userinput>make all install</>
@ -856,17 +856,17 @@
<filename>/cdrom/ports/distfiles</filename>, you will have to
get the distfile using another machine and copy it to
<filename>/usr/ports/distfiles</filename> from a floppy or your
dos partition. Read <filename>Makefile</> (with <command>cat</>
or <command>more</> or <command>view</>) to find out where to go
dos partition. Read <filename>Makefile</filename> (with <command>cat</command>
or <command>more</command> or <command>view</command>) to find out where to go
(the master distribution site) to get the file and what its name
is. Its name will be truncated when downloaded to DOS, and
after you get it into <filename>/usr/ports/distfiles</filename>
you'll have to rename it (with the <command>mv</> command) to
you'll have to rename it (with the <command>mv</command> command) to
its original name so it can be found. (Use binary file
transfers!) Then go back to
<filename>/usr/local/kermit</filename>, find the directory with
<filename>Makefile</>, and type <command>make all
install</>.</para>
<filename>Makefile</filename>, and type <command>make all
install</command>.</para>
<para>The other thing that happens when installing ports or
packages is that some other program is needed. If the
@ -874,10 +874,10 @@
unzip</errorname> or whatever, you might need to install the
package or port for unzip before you continue.</para>
<para>Once it's installed type <command>rehash</> to make FreeBSD
<para>Once it's installed type <command>rehash</command> to make FreeBSD
reread the files in the path so it knows what's there. (If you
get a lot of <errorname>path not found</> messages when you use
<command>whereis</> or which, you might want to make additions
get a lot of <errorname>path not found</errorname> messages when you use
<command>whereis</command> or which, you might want to make additions
to the list of directories in the path statement in
<filename>.cshrc</filename> in your home directory. The path
statement in Unix does the same kind of work it does in DOS,
@ -890,10 +890,10 @@
from their <ulink URL="ftp://ftp.netscape.com">ftp site</ulink>.
(Netscape requires the X Window System.) There's now a FreeBSD
version, so look around carefully. Just use <command>gunzip
<replaceable>filename</></> and <command>tar xvf
<replaceable>filename</></> on it, move the binary to
<replaceable>filename</replaceable></command> and <command>tar xvf
<replaceable>filename</replaceable></command> on it, move the binary to
<filename>/usr/local/bin</filename> or some other place binaries
are kept, <command>rehash</>, and then put the following lines
are kept, <command>rehash</command>, and then put the following lines
in <filename>.cshrc</filename> in each user's home directory or
(easier) in <filename>/etc/csh.cshrc</filename>, the
system-wide csh start-up file:</para>
@ -901,11 +901,11 @@
<informalexample>
<programlisting>setenv XKEYSYMDB /usr/X11R6/lib/X11/XKeysymDB
setenv XNLSPATH /usr/X11R6/lib/X11/nls
</>
</programlisting>
</informalexample>
<para>This assumes that the file <filename>XKeysymDB</> and the
directory <filename>nls</> are in
<para>This assumes that the file <filename>XKeysymDB</filename> and the
directory <filename>nls</filename> are in
<filename>/usr/X11R6/lib/X11</filename>; if they're not, find
them and put them there.</para>
@ -977,7 +977,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
you the tcsh as root, because the shell is part of the
environment. You can make this permanent by adding it to your
<filename>.tcshrc</filename> file as an alias with
<programlisting>alias su su -m.</></para>
<programlisting>alias su su -m.</programlisting></para>
</note>
<para>When tcsh starts up, it will read the
@ -1020,10 +1020,10 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
<title>Other</title>
<para>As root, you can dismount the CDROM with
<command>/sbin/umount /cdrom</>, take it out of the drive,
<command>/sbin/umount /cdrom</command>, take it out of the drive,
insert another one, and mount it with
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</> assuming
<hardware>cd0a</> is the device name for your CDROM drive. The
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</command> assuming
<hardware>cd0a</hardware> is the device name for your CDROM drive. The
most recent versions of FreeBSD let you mount the cdrom with
just <command>/sbin/mount /cdrom</command>.</para>
@ -1031,12 +1031,12 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
CDROM disks&mdash;is useful if you've got limited space. What
is on the live file system varies from release to release. You
might try playing games from the cdrom. This involves using
<command>lndir</>, which gets installed with the X Window
<command>lndir</command>, which gets installed with the X Window
System, to tell the program(s) where to find the necessary
files, because they're in the <filename>/cdrom</filename> file
system instead of in <filename>/usr</filename> and its
subdirectories, which is where they're expected to be. Read
<command>man lndir</>.</para>
<command>man lndir</command>.</para>
</sect1>
<sect1>
@ -1049,6 +1049,6 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
Fieber for helpful comments.</para>
<para>Annelise Anderson,
<email>andrsn@andrsn.stanford.edu</></para>
<email>andrsn@andrsn.stanford.edu</email></para>
</sect1>
</article>

60
en_US.ISO8859-1/articles/programming-tools/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v 1.10 1999/10/13 01:45:20 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v 1.11 2000/06/14 13:18:43 alex Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -44,10 +44,10 @@
<para>FreeBSD offers an excellent development environment.
Compilers for C, C++, and Fortran and an assembler come with the
basic system, not to mention a Perl interpreter and classic Unix
tools such as <command>sed</> and <command>awk</>. If that is
tools such as <command>sed</command> and <command>awk</command>. If that is
not enough, there are many more compilers and interpreters in
the Ports collection. FreeBSD is very compatible with standards
such as <acronym>POSIX</> and <acronym>ANSI</> C, as well with
such as <acronym>POSIX</acronym> and <acronym>ANSI</acronym> C, as well with
its own BSD heritage, so it is possible to write applications
that will compile and run with little or no modification on a
wide range of platforms.</para>
@ -73,8 +73,8 @@
instruction. This section gives an overview of the two main
ways in which you can give these instructions, or
<quote>commands</quote> as they are usually called. One way
uses an <firstterm>interpreter</>, the other a
<firstterm>compiler</>. As human languages are too difficult for
uses an <firstterm>interpreter</firstterm>, the other a
<firstterm>compiler</firstterm>. As human languages are too difficult for
a computer to understand in an unambiguous way, commands are
usually written in one or other languages specially designed for
the purpose.</para>
@ -105,10 +105,10 @@
start if you have not done any programming before. This kind
of environment is typically found with languages like Lisp,
Smalltalk, Perl and Basic. It could also be argued that the
Unix shell (<command>sh</>, <command>csh</>) is itself an
Unix shell (<command>sh</command>, <command>csh</command>) is itself an
interpreter, and many people do in fact write shell
<quote>scripts</quote> to help with various
<quote>housekeeping</> tasks on their machine. Indeed, part
<quote>housekeeping</quote> tasks on their machine. Indeed, part
of the original Unix philosophy was to provide lots of small
utility programs that could be linked together in shell
scripts to perform useful tasks.</para>
@ -135,16 +135,16 @@
<variablelist>
<varlistentry>
<term><acronym>BASIC</></term>
<term><acronym>BASIC</acronym></term>
<listitem>
<para>Short for Beginner's All-purpose Symbolic
Instruction Code. Developed in the 1950s for teaching
University students to program and provided with every
self-respecting personal computer in the 1980s,
<acronym>BASIC</> has been the first programming
<acronym>BASIC</acronym> has been the first programming
language for many programmers. It's also the foundation
for <trademark>Visual Basic</>.</para>
for <trademark>Visual Basic</trademark>.</para>
<para>The <ulink
URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/bwbasic-2.10.tgz">Bywater
@ -184,7 +184,7 @@
<listitem>
<para>Very popular with system administrators for writing
scripts; also often used on World Wide Web servers for
writing <acronym>CGI</> scripts.</para>
writing <acronym>CGI</acronym> scripts.</para>
<para>The latest version (version 5) comes with FreeBSD.</para>
</listitem>
@ -284,7 +284,7 @@
using separate programs, many commercial compiler makers have
produced Integrated Development Environments
(<acronym>IDE</acronym>s for short). FreeBSD does not have an
<acronym>IDE</> as such; however it is possible to use Emacs
<acronym>IDE</acronym> as such; however it is possible to use Emacs
for this purpose. This is discussed in <xref
linkend="emacs">.</para>
</sect2>
@ -295,7 +295,7 @@
<para>This section deals only with the GNU compiler for C and C++,
since that comes with the base FreeBSD system. It can be
invoked by either <command>cc</> or <command>gcc</>. The
invoked by either <command>cc</command> or <command>gcc</command>. The
details of producing a program with an interpreter vary
considerably between interpreters, and are usually well covered
in the documentation and on-line help for the
@ -324,9 +324,9 @@
understandable by humans. Allegedly.
<footnote>
<para>To be strictly accurate, <command>cc</> converts the
<para>To be strictly accurate, <command>cc</command> converts the
source code into its own, machine-independent
<firstterm>p-code</> instead of assembly language at
<firstterm>p-code</firstterm> instead of assembly language at
this stage.</para>
</footnote></para>
</step>
@ -361,20 +361,20 @@
</step>
</procedure>
<para>The word <firstterm>compiling</> is often used to refer to
<para>The word <firstterm>compiling</firstterm> is often used to refer to
just steps 1 to 4&mdash;the others are referred to as
<firstterm>linking</>. Sometimes step 1 is referred to as
<firstterm>pre-processing</> and steps 3-4 as
<firstterm>assembling</>.</para>
<firstterm>linking</firstterm>. Sometimes step 1 is referred to as
<firstterm>pre-processing</firstterm> and steps 3-4 as
<firstterm>assembling</firstterm>.</para>
<para>Fortunately, almost all this detail is hidden from you, as
<command>cc</> is a front end that manages calling all these
<command>cc</command> is a front end that manages calling all these
programs with the right arguments for you; simply typing</para>
<screen>&prompt.user; <userinput>cc foobar.c</>
</screen>
<para>will cause <filename>foobar.c</> to be compiled by all the
<para>will cause <filename>foobar.c</filename> to be compiled by all the
steps above. If you have more than one file to compile, just do
something like</para>
@ -393,18 +393,18 @@
isn't.</para>
</footnote></para>
<para>There are lots and lots of options for <command>cc</>, which
<para>There are lots and lots of options for <command>cc</command>, which
are all in the man page. Here are a few of the most important
ones, with examples of how to use them.</para>
<variablelist>
<varlistentry>
<term><option>-o <replaceable>filename</replaceable></></term>
<term><option>-o <replaceable>filename</replaceable></option></term>
<listitem>
<para>The output name of the file. If you do not use this
option, <command>cc</> will produce an executable called
<filename>a.out</>.
option, <command>cc</command> will produce an executable called
<filename>a.out</filename>.
<footnote>
<para>The reasons for this are buried in the mists of
@ -432,7 +432,7 @@
</screen>
</informalexample>
<para>This will produce an <firstterm>object file</> (not an
<para>This will produce an <firstterm>object file</firstterm> (not an
executable) called <filename>foobar.o</filename>. This
can be linked together with other object files into an
executable.</para>
@ -525,7 +525,7 @@
<listitem>
<para>Turn off most, but not all, of the
non-<acronym>ANSI</>&nbsp;C features provided by
non-<acronym>ANSI</acronym>&nbsp;C features provided by
<command>cc</command>. Despite the name, it does not
guarantee strictly that your code will comply to the
standard.</para>
@ -537,7 +537,7 @@
<listitem>
<para>Turn off <emphasis>all</emphasis>
<command>cc</command>'s non-<acronym>ANSI</>&nbsp;C
<command>cc</command>'s non-<acronym>ANSI</acronym>&nbsp;C
features.</para>
</listitem>
</varlistentry>
@ -1478,7 +1478,7 @@ main() {
listings of core files and sweat over machine code manuals,
but now life is a bit easier. Incidentally, under FreeBSD and
other 4.4BSD systems, a core file is called
<filename><replaceable>progname</>.core</> instead of just
<filename><replaceable>progname</replaceable>.core</filename> instead of just
<filename>core</filename>, to make it clearer which program a
core file belongs to.</para>
@ -1771,7 +1771,7 @@ else if (pid == 0) { /* child */
<itemizedlist>
<listitem>
<para>Everything beginning with a <literal>;</> is a comment
<para>Everything beginning with a <literal>;</literal> is a comment
and is ignored by Emacs.</para>
</listitem>

38
en_US.ISO_8859-1/articles/fonts/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v 1.7 1999/10/10 18:35:50 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v 1.8 2000/06/20 11:30:11 alex Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
@ -77,7 +77,7 @@
<variablelist>
<varlistentry>
<term><filename>.pfa</>, <filename>.pfb</></term>
<term><filename>.pfa</filename>, <filename>.pfb</filename></term>
<listitem>
<para>Postscript type 1 fonts. The
@ -89,7 +89,7 @@
</varlistentry>
<varlistentry>
<term><filename>.afm</></term>
<term><filename>.afm</filename></term>
<listitem>
<para>The font metrics associated with a type 1 font.</para>
@ -97,7 +97,7 @@
</varlistentry>
<varlistentry>
<term><filename>.pfm</></term>
<term><filename>.pfm</filename></term>
<listitem>
<para>The printer font metrics associated with a type 1
@ -106,7 +106,7 @@
</varlistentry>
<varlistentry>
<term><filename>.ttf</></term>
<term><filename>.ttf</filename></term>
<listitem>
<para>A TrueType font</para>
@ -114,7 +114,7 @@
</varlistentry>
<varlistentry>
<term><filename>.fot</></term>
<term><filename>.fot</filename></term>
<listitem>
<para>An indirect reference to a TrueType font (not an
@ -123,7 +123,7 @@
</varlistentry>
<varlistentry>
<term><filename>.fon</>, <filename>.fnt</></term>
<term><filename>.fon</filename>, <filename>.fnt</filename></term>
<listitem>
<para>Bitmapped screen fonts</para>
@ -157,7 +157,7 @@
<term>syscons</term>
<listitem>
<para><filename>.fnt</></para>
<para><filename>.fnt</filename></para>
</listitem>
</varlistentry>
</variablelist>
@ -271,7 +271,7 @@
is cross referenced to its X11 name by the contents of the
<filename>fonts.dir</filename> file in each directory.</para>
<para>There is already a directory named <filename>Type1</>. The
<para>There is already a directory named <filename>Type1</filename>. The
most straight forward way to add a new font is to put it into
this directory. A better way is to keep all new fonts in a
separate directory and use a symbolic link to the additional
@ -364,7 +364,7 @@ end readonly def
<listitem>
<para>Lets just name all the new fonts
<literal>type1</>.</para>
<literal>type1</literal>.</para>
</listitem>
</varlistentry>
@ -381,7 +381,7 @@ end readonly def
<listitem>
<para>Normal, bold, medium, semibold, etc. From the
<citerefentry><refentrytitle>strings</><manvolnum>1</></>
<citerefentry><refentrytitle>strings</refentrytitle><manvolnum>1</manvolnum></citerefentry>
output above, it appears that this font has a weight of
<emphasis>medium</emphasis>.</para>
</listitem>
@ -441,7 +441,7 @@ end readonly def
</informalexample>
as the name, and then use
<citerefentry><refentrytitle>xfontsel</><manvolnum>1</></> to
<citerefentry><refentrytitle>xfontsel</refentrytitle><manvolnum>1</manvolnum></citerefentry> to
examine it and adjust the name based on the appearance of the
font.</para>
@ -477,7 +477,7 @@ bash$ <userinput>xfontsel -pattern -type1-*</>
</informalexample>
<para>References: &man.xfontsel.1;, &man.xset.1;, <citetitle>The X
Windows System in a Nutshell</>, <ulink
Windows System in a Nutshell</citetitle>, <ulink
URL="http://www.ora.com/">O'Reilly &amp;
Associates</ulink>.</para>
</sect1>
@ -485,7 +485,7 @@ bash$ <userinput>xfontsel -pattern -type1-*</>
<sect1>
<title>Using type 1 fonts with Ghostscript</title>
<para>Ghostscript references a font via its <filename>Fontmap</>
<para>Ghostscript references a font via its <filename>Fontmap</filename>
file. This must be modified in a similar way to the X11
<filename>fonts.dir</filename> file. Ghostscript can use either
the <filename>.pfa</filename> or the <filename>.pfb</filename>
@ -541,7 +541,7 @@ GS&gt;<userinput>quit</>
<filename>/usr/share/groff_font/devps/SHOWBOAT</filename>. The
file must be created using tools provided by groff.</para>
<para>The first tool is <command>afmtodit</>. This is not
<para>The first tool is <command>afmtodit</command>. This is not
normally installed, so it must be retrieved from the source
distribution. I found I had to change the first line of the
file, so I did:</para>
@ -582,10 +582,10 @@ bash$ <userinput>/tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate
printer in order for the font to be used (unless the printer
happens to have the showboat font built in or on an accessible
font disk.) The final step is to create a down loadable font.
The <command>pfbtops</> tool is used to create the
The <command>pfbtops</command> tool is used to create the
<filename>.pfa</filename> format of the font, and the
<filename>download</> file is modified to reference the new
font. The <filename>download</> file must reference the
<filename>download</filename> file is modified to reference the new
font. The <filename>download</filename> file must reference the
internal name of the font. This can easily be determined from
the groff font file as illustrated:</para>
@ -686,7 +686,7 @@ bash$ <userinput>lpr -Ppostscript example.ps</>
<itemizedlist>
<listitem>
<para><filename>GS_TTF.PS</filename></para
<para><filename>GS_TTF.PS</filename></para>
</listitem>
<listitem>

6
en_US.ISO_8859-1/articles/formatting-media/article.sgml
View file

@ -2,7 +2,7 @@
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
]>
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/formatting-media/article.sgml,v 1.12 1999/10/10 19:21:10 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/formatting-media/article.sgml,v 1.13 1999/10/30 18:10:14 dwhite Exp $ -->
<article>
<artheader>
<title>Formatting Media For Use With FreeBSD 2.2-RELEASE</title>
@ -151,7 +151,7 @@ now. -->
quite possible to destroy the contents of other disks in your
system if the proper precautions are not taken.</para>
<para><emphasis>Check your work carefully.</> It is very simple
<para><emphasis>Check your work carefully.</emphasis> It is very simple
to destroy the incorrect disk when working with these
commands. When in doubt consult the kernel boot output for
the proper device.</para>
@ -535,7 +535,7 @@ swapon: added /dev/sd0b as swap space
<para>To create a new CCD, execute the following commands. This
describes how to add three disks together; simply add or
remove devices as necessary. Remember that the disks to be
striped must be <emphasis>identical.</></para>
striped must be <emphasis>identical.</emphasis></para>
<para>Before executing these commands, make sure you add the line

298
en_US.ISO_8859-1/articles/mh/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/mh/article.sgml,v 1.6 1999/10/10 19:29:59 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/mh/article.sgml,v 1.7 1999/10/10 20:20:38 jhb Exp $ -->
<!-- FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -35,7 +35,7 @@
initial philosophies behind MH were developed. MH isn't so much
a monolithic email program but a philosophy about how best to
develop tools for reading email. The MH developers have done a
great job adhering to the <acronym>KISS</> principle: Keep It
great job adhering to the <acronym>KISS</acronym> principle: Keep It
Simple Stupid. Rather than have one large program for reading,
sending and handling email they have written specialized
programs for each part of your email life. One might liken MH to
@ -64,9 +64,9 @@
</screen>
</informalexample>
You will notice that it created a <filename>/usr/local/lib/mh</>
You will notice that it created a <filename>/usr/local/lib/mh</filename>
directory for you as well as adding several binaries to the
<filename>/usr/local/bin</> directory. If you would prefer to
<filename>/usr/local/bin</filename> directory. If you would prefer to
compile it yourself then you can anonymous ftp it from <ulink
URL="ftp://ftp.ics.uci.edu/">ftp.ics.uci.edu</ulink> or <ulink
URL="ftp://louie.udel.edu/">louie.udel.edu</ulink>.</para>
@ -85,33 +85,33 @@
<sect1>
<title>Reading Mail</title>
<para>This section covers how to use <command>inc</>,
<command>show</>, <command>scan</>, <command>next</>,
<command>prev</>, <command>rmm</>, <command>rmf</>, and
<command>msgchk</>. One of the best things about MH is the
<para>This section covers how to use <command>inc</command>,
<command>show</command>, <command>scan</command>, <command>next</command>,
<command>prev</command>, <command>rmm</command>, <command>rmf</command>, and
<command>msgchk</command>. One of the best things about MH is the
consistent interface between programs. A few things to keep in
mind when using these commands is how to specify message lists.
In the case of <command>inc</> this doesn't really make any
sense but with commands like <command>show</> it is useful to
In the case of <command>inc</command> this doesn't really make any
sense but with commands like <command>show</command> it is useful to
know. </para>
<para>A message list can consist of something like <parameter>23
20 16</> which will act on messages 23, 20 and 16. This is
20 16</parameter> which will act on messages 23, 20 and 16. This is
fairly simple but you can do more useful things like
<parameter>23-30</> which will act on all the messages between
<parameter>23-30</parameter> which will act on all the messages between
23 and 30. You can also specify something like
<parameter>cur:10</> which will act on the current message and
the next 9 messages. The <parameter>cur</>, <parameter>last</>,
and <parameter>first</> messages are special messages that refer
<parameter>cur:10</parameter> which will act on the current message and
the next 9 messages. The <parameter>cur</parameter>, <parameter>last</parameter>,
and <parameter>first</parameter> messages are special messages that refer
to the current, last or first message in the folder.</para>
<sect2 id="inc">
<title><command>inc</>, <command>msgchk</>&mdash;read in your
<title><command>inc</command>, <command>msgchk</command>&mdash;read in your
new email or check it</title>
<para>If you just type in <userinput>inc</> and hit
<keycap>return</> you will be well on your way to getting
started with MH. The first time you run <command>inc</> it
<para>If you just type in <userinput>inc</userinput> and hit
<keycap>return</keycap> you will be well on your way to getting
started with MH. The first time you run <command>inc</command> it
will setup your account to use all the MH defaults and ask you
about creating a Mail directory. If you have mail waiting to
be downloaded you will see something that looks like:</para>
@ -126,45 +126,45 @@
</informalexample>
<para>This is the same thing you will see from a
<command>scan</> (see <xref linkend="scan">). If you just run
<command>inc</> with no arguments it will look on your
<command>scan</command> (see <xref linkend="scan">). If you just run
<command>inc</command> with no arguments it will look on your
computer for email that is supposed to be coming to
you.</para>
<para>A lot of people like to use POP for grabbing their email.
MH can do POP to grab your email. You will need to give
<command>inc</> a few command line arguments.</para>
<command>inc</command> a few command line arguments.</para>
<informalexample>
<screen>&prompt.user; <userinput>inc -host mail.pop.org -user <replaceable>username</> -norpop</>
</screen>
</informalexample>
<para>That tells <command>inc</> to go to
<parameter>mail.pop.org</> to download your email, and that
your username on their system is <replaceable>username</>. The
<option>-norpop</option> option tells <command>inc</> to use
<para>That tells <command>inc</command> to go to
<parameter>mail.pop.org</parameter> to download your email, and that
your username on their system is <replaceable>username</replaceable>. The
<option>-norpop</option> option tells <command>inc</command> to use
plain POP3 for downloading your email. MH has support for a
few different dialects of POP. More than likely you will never
ever need to use them though. While you can do more complex
things with inc such as audit files and scan format files this
will get you going.</para>
<para>The <command>msgchk</> command is used to get information
on whether or not you have new email. <command>msgchk</> takes
<para>The <command>msgchk</command> command is used to get information
on whether or not you have new email. <command>msgchk</command> takes
the same <option>-host</option> and <option>-user</option>
options that <command>inc</> takes.</para>
options that <command>inc</command> takes.</para>
</sect2>
<sect2 id="show">
<title><command>show</>, <command>next</> and
<command>prev</>&mdash;displaying and moving through
<title><command>show</command>, <command>next</command> and
<command>prev</command>&mdash;displaying and moving through
email</title>
<para><command>show</> is to show a letter in your current
folder. Like <command>inc</>, <command>show</> is a fairly
straightforward command. If you just type <userinput>show</>
and hit <keycap>return</> then it displays the current
<para><command>show</command> is to show a letter in your current
folder. Like <command>inc</command>, <command>show</command> is a fairly
straightforward command. If you just type <userinput>show</userinput>
and hit <keycap>return</keycap> then it displays the current
message. You can also give specific message numbers to
show:</para>
@ -175,23 +175,23 @@
<para>This would display message numbers 32, 45 and 56 right
after each other. Unless you change the default behavior
<command>show</> basically just does a <command>more</> on the
<command>show</command> basically just does a <command>more</command> on the
email message.</para>
<para><command>next</> is used to move onto the next message and
<command>prev</> will go to the previous message. Both
commands have an implied <command>show</> command so that when
<para><command>next</command> is used to move onto the next message and
<command>prev</command> will go to the previous message. Both
commands have an implied <command>show</command> command so that when
you go to the next message it automatically displays
it.</para>
</sect2>
<sect2 id="scan">
<title><command>scan</>&mdash;shows you a scan of your
<title><command>scan</command>&mdash;shows you a scan of your
messages</title>
<para><command>scan</> will display a brief listing of the
<para><command>scan</command> will display a brief listing of the
messages in your current folder. This is an example of what
the <command>scan</> command will give you.</para>
the <command>scan</command> command will give you.</para>
<informalexample>
<screen> 30+ 01/16 "Jordan K. Hubbar Re: FBSD 2.1&lt;&lt;&gt; Do you want a library instead of
@ -205,32 +205,32 @@
configurable. This is the typical default display. It gives
you the message number, the date on the email, the sender, the
subject line, and a sentence fragment from the very beginning
of the email if it can fit it. The <literal>+</> means that
of the email if it can fit it. The <literal>+</literal> means that
message is the current message, so if you do a
<command>show</> it will display that message.</para>
<command>show</command> it will display that message.</para>
<para>One useful option for scan is the
<option>-reverse</option> option. This will list your messages
with the highest message number first and lowest message
number last. Another useful option with <command>scan</> is to
number last. Another useful option with <command>scan</command> is to
have it read from a file. If you want to scan your incoming
mailbox on FreeBSD without having to <command>inc</> it you
mailbox on FreeBSD without having to <command>inc</command> it you
can do <command>scan -file
/var/mail/<replaceable>username</></command>. This can be used
with any file that is in the <database>mbox</> format.</para>
/var/mail/<replaceable>username</replaceable></command>. This can be used
with any file that is in the <database>mbox</database> format.</para>
</sect2>
<sect2 id="rmm">
<title><command>rmm</> and <command>rmf</>&mdash;remove the
<title><command>rmm</command> and <command>rmf</command>&mdash;remove the
current message or folder</title>
<para><command>rmm</> is used to remove a mail message. The
<para><command>rmm</command> is used to remove a mail message. The
default is typically to not actually remove the message but to
rename the file to one that is ignored by the MH commands. You
will need to through periodically and physically delete the
<quote>removed</> messages.</para>
<quote>removed</quote> messages.</para>
<para>The <command>rmf</> command is used to remove folders.
<para>The <command>rmf</command> command is used to remove folders.
This doesn't just rename the files but actually removes the
from the hard drive so you should be careful when you use this
command.</para>
@ -240,8 +240,8 @@
<title>A typical session of reading with MH</title>
<para>The first thing that you will want to do is
<command>inc</> your new mail. So at a shell prompt just type
in <command>inc</> and hit <keycap>return</>.</para>
<command>inc</command> your new mail. So at a shell prompt just type
in <command>inc</command> and hit <keycap>return</keycap>.</para>
<informalexample>
<screen>&prompt.user; <userinput>inc</>
@ -255,7 +255,7 @@ Incorporating new mail into inbox...
</informalexample>
<para>This shows you the new email that has been added to your
mailbox. So the next thing to do is <command>show</> the email
mailbox. So the next thing to do is <command>show</command> the email
and move around.</para>
<informalexample>
@ -298,8 +298,8 @@ which I am probably the guilty party).
</screen>
</informalexample>
<para>The <command>rmm</> removed the current message and the
<command>next</> command moved me on to the next message. Now
<para>The <command>rmm</command> removed the current message and the
<command>next</command> command moved me on to the next message. Now
if I wanted to look at ten most recent messages so I could
read one of them here is what I would do:</para>
@ -320,7 +320,7 @@ which I am probably the guilty party).
</informalexample>
<para>Then if I wanted to read message number 27 I would do a
<userinput>show 27</> and it would be displayed. As you can
<userinput>show 27</userinput> and it would be displayed. As you can
probably tell from this sample session MH is pretty easy to
use and looking through emails and displaying them is fairly
intuitive and easy.</para>
@ -337,19 +337,19 @@ which I am probably the guilty party).
the concept of folders. You have undoubtedly come across the
folders concept using other email programs. MH has folders too.
MH can even do sub-folders of a folder. One thing you should
keep in mind with MH is that when you ran <command>inc</> for
keep in mind with MH is that when you ran <command>inc</command> for
the first time and it asked you if it could create a
<filename>Mail</> directory it began storing everything in that
<filename>Mail</filename> directory it began storing everything in that
directory. If you look at that directory you will find a
directory named <filename>inbox</>. The <filename>inbox</>
directory named <filename>inbox</filename>. The <filename>inbox</filename>
directory houses all of your incoming mail that hasn't been
thrown anywhere else.</para>
<para>Whenever you create a new folder a new directory is going to
be created underneath your MH <filename>Mail</> directory, and
be created underneath your MH <filename>Mail</filename> directory, and
messages in that folder are going to be stored in that
directory. When new email comes in that new email is thrown
into your <filename>inbox</> directory with a file name that is
into your <filename>inbox</filename> directory with a file name that is
equivalent to the message number. So even if you didn't have
any of the MH tools to read your email you could still use
standard UNIX commands to munge around in those directories and
@ -357,28 +357,28 @@ which I am probably the guilty party).
a lot of power with what you can do with your email.</para>
<para>Just as you can use message lists like <parameter>23 16
42</> with most MH commands there is a folder option you can
42</parameter> with most MH commands there is a folder option you can
specify with just about every MH command. If you do a
<command>scan +freebsd</> it will scan your <filename>freebsd</>
<command>scan +freebsd</command> it will scan your <filename>freebsd</filename>
folder, and your current folder will be changed to
<filename>freebsd</>. If you do a <command>show +freebsd 23 16
42</>, <command>show</> is going to switch to your
<filename>freebsd</> folder and display messages 23, 16 and 42.
So remember that <option>+<replaceable>folder</></> syntax. You
<filename>freebsd</filename>. If you do a <command>show +freebsd 23 16
42</command>, <command>show</command> is going to switch to your
<filename>freebsd</filename> folder and display messages 23, 16 and 42.
So remember that <option>+<replaceable>folder</replaceable></option> syntax. You
will need to make sure you use it to make commands process
different folders. Remember you default folder for mail is
<filename>inbox</> so doing a <command>folder +inbox</> should
<filename>inbox</filename> so doing a <command>folder +inbox</command> should
always get you back to your mail. Of course, in MH's infinite
flexibility this can be changed but most places have probably
left it as <command>inbox</>.</para>
left it as <command>inbox</command>.</para>
<sect2>
<title><command>pick</>&mdash;search email that matches certain
<title><command>pick</command>&mdash;search email that matches certain
criteria</title>
<para><command>pick</> is one of the more complex commands in
<para><command>pick</command> is one of the more complex commands in
the MH system. So you might want to read the
<citerefentry><refentrytitle>pick</><manvolnum>1</></> man
<citerefentry><refentrytitle>pick</refentrytitle><manvolnum>1</manvolnum></citerefentry> man
page for a more thorough understanding. At its simplest level
you can do something like</para>
@ -392,12 +392,12 @@ which I am probably the guilty party).
</screen>
</informalexample>
<para>This will tell <command>pick</> to look through every
<para>This will tell <command>pick</command> to look through every
single line in every message in your current folder and tell
you which message numbers it found the word <literal>pci</>
in. You can then <command>show</> those messages and read them
if you wish or <command>rmm</> them. You would have to specify
something like <command>show 15 42 55-57</> to display them
you which message numbers it found the word <literal>pci</literal>
in. You can then <command>show</command> those messages and read them
if you wish or <command>rmm</command> them. You would have to specify
something like <command>show 15 42 55-57</command> to display them
though. A slightly more useful thing to do is this:</para>
<informalexample>
@ -410,16 +410,16 @@ which I am probably the guilty party).
<para>This will show you the same messages you just didn't have
to work as hard to do it. The <option>-seq</option> option is
really an abbreviation of <option>-sequence</option> and
<command>pick</> is just a sequence which contains the message
<command>pick</command> is just a sequence which contains the message
numbers that matched. You can use sequences with just about
any MH command. So you could have done an <command>rmm pick</>
any MH command. So you could have done an <command>rmm pick</command>
and all those messages would be removed instead. You sequence
can be named anything. If you run pick again it will overwrite
the old sequence if you use the same name.</para>
<para>Doing a <command>pick -search</command> can be a bit more
time consuming than just searching for message from someone,
or to someone. So <command>pick</> allows you to use the
or to someone. So <command>pick</command> allows you to use the
following predefined search criteria:</para>
<variablelist>
@ -468,7 +468,7 @@ which I am probably the guilty party).
<listitem>
<para>search for any other component in the header. (i.e.
<option>--reply-to</> to find all emails with a certain
<option>--reply-to</option> to find all emails with a certain
reply-to in the header)</para>
</listitem>
</varlistentry>
@ -482,7 +482,7 @@ which I am probably the guilty party).
</informalexample>
to get a list of all the email send to the FreeBSD hackers
mailing list. <command>pick</> also allows you to group these
mailing list. <command>pick</command> also allows you to group these
criteria in different ways using the following options:</para>
<itemizedlist>
@ -531,42 +531,42 @@ which I am probably the guilty party).
something called operator precedence. Remember in math how you
evaluate from left to right and you do multiplication and
division first and addition and subtraction second? MH has the
same type of rules for <command>pick</>. It's fairly complex
same type of rules for <command>pick</command>. It's fairly complex
so you might want to study the man page. This document is just
to help you get acquainted with MH.</para>
</sect2>
<sect2>
<title><command>folder</>, <command>folders</>,
<command>refile</>&mdash;three useful programs for folder
<title><command>folder</command>, <command>folders</command>,
<command>refile</command>&mdash;three useful programs for folder
maintenance</title>
<para>There are three programs which are primarily just for
manipulating your folders. The <command>folder</> program is
manipulating your folders. The <command>folder</command> program is
used to switch between folders, pack them, and list them. At
its simplest level you can do a <command>folder
+<replaceable>newfolder</></> and you will be switched into
<replaceable>newfolder</>. From there on out all your MH
commands like <command>comp</>, <command>repl</>,
<command>scan</>, and <command>show</> will act on that
<command>newfolder</> folder.</para>
+<replaceable>newfolder</replaceable></command> and you will be switched into
<replaceable>newfolder</replaceable>. From there on out all your MH
commands like <command>comp</command>, <command>repl</command>,
<command>scan</command>, and <command>show</command> will act on that
<command>newfolder</command> folder.</para>
<para>Sometimes when you are reading and deleting messages you
will develop <quote>holes</> in your folders. If you do a
<command>scan</> you might just see messages 34, 35, 36, 43,
will develop <quote>holes</quote> in your folders. If you do a
<command>scan</command> you might just see messages 34, 35, 36, 43,
55, 56, 57, 80. If you do a <command>folder -pack</command>
this will renumber all your messages so that there are no
holes. It doesn't actually delete any messages though. So you
may need to periodically go through and physically delete
<command>rmm</>'d messages.</para>
<command>rmm</command>'d messages.</para>
<para>If you need statistics on your folders you can do a
<command>folders</> or <command>folder -all</command> to list
<command>folders</command> or <command>folder -all</command> to list
all your folders, how many messages they have, what the
current message is in each one and so on. This line of stats
it displays for all your folders is the same one you get when
you change to a folder with <command>folder +foldername</>. A
<command>folders</> command looks like this:</para>
you change to a folder with <command>folder +foldername</command>. A
<command>folders</command> command looks like this:</para>
<informalexample>
<screen> Folder # of messages ( range ); cur msg (other files)
@ -585,17 +585,17 @@ which I am probably the guilty party).
</screen>
</informalexample>
<para>The <command>refile</> command is what you use to move
<para>The <command>refile</command> command is what you use to move
messages between folders. When you do something like
<command>refile 23 +netfuture</> message number 23 is moved
into the <filename>netfuture</> folder. You could also do
something like <command>refile 23 +netfuture/latest</> which
<command>refile 23 +netfuture</command> message number 23 is moved
into the <filename>netfuture</filename> folder. You could also do
something like <command>refile 23 +netfuture/latest</command> which
would put message number 23 in a subfolder called
<filename>latest</> under the <filename>netfuture</> folder.
<filename>latest</filename> under the <filename>netfuture</filename> folder.
If you want to keep a message in the current folder and link
it you can do a <command>refile -link 23 +netfuture</command>
which would keep 23 in your current <filename>inbox</> but
also list in your <filename>netfuture</> folder. You are
which would keep 23 in your current <filename>inbox</filename> but
also list in your <filename>netfuture</filename> folder. You are
probably beginning to realize some of the really powerful
things you can do with MH.</para>
</sect2>
@ -613,29 +613,29 @@ which I am probably the guilty party).
Subject: headers already in it. You are then sent into your
editor where you fill in the header information and then type
the body of your message below the dashed lines in the message.
Then to the <command>whatnow</> program. When you are at the
Then to the <command>whatnow</command> program. When you are at the
<prompt>What now?</prompt> prompt you can tell it to
<command>send</>, <command>list</>, <command>edit</>,
<command>edit</>, <command>push</>, and <command>quit</>. Most
<command>send</command>, <command>list</command>, <command>edit</command>,
<command>edit</command>, <command>push</command>, and <command>quit</command>. Most
of these commands are self-explanatory. So the message sending
process involves copying a component file, editing your email,
and then telling the <command>whatnow</> program what to do with
and then telling the <command>whatnow</command> program what to do with
your email.</para>
<sect2>
<title><command>comp</>, <command>forw</>,
<command>reply</>&mdash;compose, forward or reply to a message
<title><command>comp</command>, <command>forw</command>,
<command>reply</command>&mdash;compose, forward or reply to a message
to someone</title>
<para>The <command>comp</> program has a few useful command line
<para>The <command>comp</command> program has a few useful command line
options. The most important one to know right now is the
<option>-editor</option> option. When MH is installed the
default editor is usually a program called
<command>prompter</> which comes with MH. It's not a very
<command>prompter</command> which comes with MH. It's not a very
exciting editor and basically just gets the job done. So when
you go to compose a message to someone you might want to use
<command>comp -editor /usr/bin/vi/</> or <command>comp -editor
/usr/local/bin/pico/</> instead. Once you have run
<command>comp -editor /usr/bin/vi/</command> or <command>comp -editor
/usr/local/bin/pico/</command> instead. Once you have run
<emphasis>comp</emphasis> you are in your editor and you see
something that looks like this:</para>
@ -648,9 +648,9 @@ Subject:
</informalexample>
<para>You need to put the person you are sending the mail to
after the <literal>To:</> line. It works the same way for the
after the <literal>To:</literal> line. It works the same way for the
other headers also, so you would need to put your subject
after the <literal>Subject:</> line. Then you would just put
after the <literal>Subject:</literal> line. Then you would just put
the body of your message after the dashed lines. It may seem a
bit simplistic since a lot of email programs have special
requesters that ask you for this information but there really
@ -667,55 +667,55 @@ Subject:<userinput>And on the 8th day God created the FreeBSD core team</>
</informalexample>
<para>You can now save this message and exit your editor. You
will see the <prompt>What now?</> prompt and you can type in
<userinput>send</> or <userinput>s</> and hit
<keycap>return</>. Then the FreeBSD core team will receive
will see the <prompt>What now?</prompt> prompt and you can type in
<userinput>send</userinput> or <userinput>s</userinput> and hit
<keycap>return</keycap>. Then the FreeBSD core team will receive
their just rewards. As I mentioned earlier you can also use
other commands, for example <command>quit</> if you don't want
other commands, for example <command>quit</command> if you don't want
to send the message.</para>
<para>The <command>forw</> command is stunningly similar. The
<para>The <command>forw</command> command is stunningly similar. The
big difference being that the message you are forwarding is
automatically included in the outgoing message. When you run
<command>forw</> it will forward your current message. You can
<command>forw</command> it will forward your current message. You can
always tell it to forward something else by doing something
like <command>forw 23</> and then message number 23 will be
like <command>forw 23</command> and then message number 23 will be
put in your outgoing message instead of the current message.
Beyond those small differences <command>forw</> functions
exactly the same as <command>comp</>. You go through the exact
Beyond those small differences <command>forw</command> functions
exactly the same as <command>comp</command>. You go through the exact
same message sending process.</para>
<para>The <command>repl</> command will reply to whatever your
<para>The <command>repl</command> command will reply to whatever your
current message is, unless you give it a different message to
reply to. <command>repl</> will do its best to go ahead and
reply to. <command>repl</command> will do its best to go ahead and
fill in some of the email headers already. So you will notice
that the <literal>To:</> header already has the address of the
recipient in there. Also the <literal>Subject:</> line will
that the <literal>To:</literal> header already has the address of the
recipient in there. Also the <literal>Subject:</literal> line will
already be filled in. You then go about the normal message
composition process and you are done. One useful command line
option to know here is the <option>-cc</option> option. You
can use <parameter>all</>, <parameter>to</>, <parameter>cc</>,
<parameter>me</> after the <option>-cc</option> option to have
<command>repl</> automatically add the various addresses to
can use <parameter>all</parameter>, <parameter>to</parameter>, <parameter>cc</parameter>,
<parameter>me</parameter> after the <option>-cc</option> option to have
<command>repl</command> automatically add the various addresses to
the cc list in the message. You have probably noticed that the
original message isn't included. This is because most MH
setups are configured to do this from the start.</para>
</sect2>
<sect2>
<title><filename>components</>, and
<filename>replcomps</>&mdash;components files for
<command>comp</> and <command>repl</></title>
<title><filename>components</filename>, and
<filename>replcomps</filename>&mdash;components files for
<command>comp</command> and <command>repl</command></title>
<para>The <filename>components</> file is usually in
<para>The <filename>components</filename> file is usually in
<filename>/usr/local/lib/mh</filename>. You can copy that file
into your MH Mail directory and edit to contain what you want
it to contain. It is a fairly basic file. You have various
email headers at the top, a dashed line and then nothing. The
<command>comp</command> command just copies this
<filename>components</> file and then edits it. You can add
<filename>components</filename> file and then edits it. You can add
any kind of valid RFC822 header you want. For instance you
could have something like this in your <filename>components</>
could have something like this in your <filename>components</filename>
file:</para>
<informalexample>
@ -729,13 +729,13 @@ X-Home-Page: http://www.FreeBSD.org/
</informalexample>
<para>MH would then copy this components file and throw you into
your editor. The <filename>components</> file is fairly
your editor. The <filename>components</filename> file is fairly
simple. If you wanted to have a signature on those messages
you would just put your signature in that
<filename>components</> file.</para>
<filename>components</filename> file.</para>
<para>The <filename>replcomps</> file is a bit more complex. The
default <filename>replcomps</> looks like this:</para>
<para>The <filename>replcomps</filename> file is a bit more complex. The
default <filename>replcomps</filename> looks like this:</para>
<informalexample>
<screen>%(lit)%(formataddr %&lt;{reply-to}%?{from}%?{sender}%?{return-path}%&gt;)\
@ -752,12 +752,12 @@ X-Home-Page: http://www.FreeBSD.org/
</informalexample>
<para>It's in the same basic format as the
<filename>components</> file but it contains quite a few extra
formatting codes. The <literal>%(lit)</> command makes room
for the address. The <literal>%(formataddr</> is a function
<filename>components</filename> file but it contains quite a few extra
formatting codes. The <literal>%(lit)</literal> command makes room
for the address. The <literal>%(formataddr</literal> is a function
that returns a proper email address. The next part is
<literal>%&lt;</literal> which means if and the
<literal>{reply-to}</> means the reply-to field in the
<literal>{reply-to}</literal> means the reply-to field in the
original message. So that might be translated this way:</para>
<informalexample>
@ -774,7 +774,7 @@ message</emphasis>, %&gt; <emphasis remap=bf>endif</emphasis>.
variables mean. All of the information on writing these format
strings is in the MH-Format man page. The really nice thing is
that once you have built your customized
<filename>replcomps</> file you won't need to touch it again.
<filename>replcomps</filename> file you won't need to touch it again.
No other email program really gives you the power and
flexibility that MH gives you.</para>
</sect2>

62
en_US.ISO_8859-1/articles/multi-os/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/multi-os/article.sgml,v 1.11 1999/10/13 10:51:58 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/multi-os/article.sgml,v 1.12 2000/05/30 22:48:47 nik Exp $ -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
<article>
<artheader>
@ -144,11 +144,11 @@
<itemizedlist>
<listitem>
<para><filename>/dev/wd0</> (first physical hard disk)</para>
<para><filename>/dev/wd0</filename> (first physical hard disk)</para>
</listitem>
<listitem>
<para><filename>/dev/wd1</> (second hard disk)</para>
<para><filename>/dev/wd1</filename> (second hard disk)</para>
</listitem>
</itemizedlist>
@ -157,7 +157,7 @@
<procedure>
<step>
<para>I boot from a MS-DOS or Windows 95 boot disk that
contains the <filename>FDISK.EXE</> utility and make a small
contains the <filename>FDISK.EXE</filename> utility and make a small
50 meg primary partition (35-40 for Windows 95, plus a
little breathing room) on the first disk. Also create a
larger partition on the second hard disk for my Windows
@ -166,7 +166,7 @@
<step>
<para>I reboot and install Windows 95 (easier said than done)
on the <filename>C:</> partition.</para>
on the <filename>C:</filename> partition.</para>
</step>
<step>
@ -191,15 +191,15 @@
1024th cylinder. (The 1024th cylinder is 528 megs into the
disk with our hypothetical 720MB disks). I will use the
rest of the hard drive (about 270 megs) for the
<filename>/usr</> and <filename>/</> slices if I wish. The
<filename>/usr</filename> and <filename>/</filename> slices if I wish. The
rest of the second hard disk (size depends on the amount of
my Windows application/data partition that I created in step
1 can go to the <filename>/usr/src</> slice and swap
1 can go to the <filename>/usr/src</filename> slice and swap
space.</para>
</step>
<step>
<para>When viewed with the Windows 95 <command>fdisk</>
<para>When viewed with the Windows 95 <command>fdisk</command>
utility, my hard drives should now look something like this:
<screen>
@ -238,14 +238,14 @@ Press Esc to continue
<step>
<para>Install FreeBSD. I make sure to boot with my first hard
disk set at <quote>NORMAL</> in the BIOS. If it is not,
disk set at <quote>NORMAL</quote> in the BIOS. If it is not,
I'll have the enter my true disk geometry at boot time (to
get this, boot Windows 95 and consult Microsoft Diagnostics
(<filename>MSD.EXE</>), or check your BIOS) with the
parameter <literal>hd0=1416,16,63</> where
<replaceable>1416</> is the number of cylinders on my hard
disk, <replaceable>16</> is the number of heads per track,
and <replaceable>63</> is the number of sectors per track on
(<filename>MSD.EXE</filename>), or check your BIOS) with the
parameter <literal>hd0=1416,16,63</literal> where
<replaceable>1416</replaceable> is the number of cylinders on my hard
disk, <replaceable>16</replaceable> is the number of heads per track,
and <replaceable>63</replaceable> is the number of sectors per track on
the drive.</para>
</step>
@ -275,7 +275,7 @@ Press Esc to continue
cylinder.</para>
<para>If you install Windows 95 on an existing BSD system, it will
<quote>destroy</> the MBR, and you will have to reinstall your
<quote>destroy</quote> the MBR, and you will have to reinstall your
previous boot manager. Boot Easy can be reinstalled by using
the BOOTINST.EXE utility included in the \TOOLS directory on the
CD-ROM, and via <ulink
@ -305,19 +305,19 @@ Press Esc to continue
<email>jayrich@sysc.com</email>)</emphasis>.</para>
<para>FreeBSD+Win95: If you installed FreeBSD after Windows 95,
you should see <literal>DOS</> on the Boot Easy menu. This is
you should see <literal>DOS</literal> on the Boot Easy menu. This is
Windows 95. If you installed Windows 95 after FreeBSD, read
<xref linkend="ch4"> above. As long as your hard disk does not
have 1024 cylinders you should not have a problem booting. If
one of your partitions goes beyond the 1024th cylinder however,
and you get messages like <errorname>invalid system disk</>
and you get messages like <errorname>invalid system disk</errorname>
under DOS (Windows 95) and FreeBSD will not boot, try looking
for a setting in your BIOS called <quote>&gt; 1024 cylinder
support</> or <quote>NORMAL/LBA</> mode. DOS may need LBA
support</quote> or <quote>NORMAL/LBA</quote> mode. DOS may need LBA
(Logical Block Addressing) in order to boot correctly. If the
idea of switching BIOS settings every time you boot up doesn't
appeal to you, you can boot FreeBSD through DOS via the
<filename>FBSDBOOT.EXE</> utility on the CD (It should find your
<filename>FBSDBOOT.EXE</filename> utility on the CD (It should find your
FreeBSD partition and boot it.)</para>
<para>FreeBSD+OS/2+Win95: Nothing new here. OS/2's boot manger
@ -399,7 +399,7 @@ Press Esc to continue
<informalexample>
<para>(# of cylinders) &times; (# heads) &times; (63
sectors/track) &times; (512 bytes/sect)</>
sectors/track) &times; (512 bytes/sect)</para>
</informalexample>
<para>For example, on my 1.6 Gig Western Digital AC31600 EIDE hard
@ -419,9 +419,9 @@ Press Esc to continue
though: if you're using BIOS LBA (see <xref
linkend="limits">), you can't use just any program to get
the physical geometry. This is because many programs (e.g.
<filename>MSD.EXE</> or FreeBSD fdisk) don't identify the
<filename>MSD.EXE</filename> or FreeBSD fdisk) don't identify the
physical disk geometry; they instead report the
<firstterm>translated geometry</> (virtual numbers from using
<firstterm>translated geometry</firstterm> (virtual numbers from using
LBA). Stay tuned for what that means.</para>
<para>One other useful thing about these terms. Given 3
@ -434,9 +434,9 @@ Press Esc to continue
<para>For those that are interested in more technical details,
information on disk geometry, boot sectors, BIOSes, etc. can
be found all over the net. Query Lycos, Yahoo, etc. for
<literal>boot sector</> or <literal>master boot record</>.
<literal>boot sector</literal> or <literal>master boot record</literal>.
Among the useful info you'll find are Hale Landis's
<citetitle>How It Works</> document pack. See the <xref
<citetitle>How It Works</citetitle> document pack. See the <xref
linkend="sources"> section for a few pointers to this
pack.</para>
@ -449,21 +449,21 @@ Press Esc to continue
<para>On the first sector of your disk (Cyl 0, Head 0, Sector 1)
lives the Master Boot Record (MBR). It contains a map of your
disk. It identifies up to 4 <firstterm>partitions</>, each of
disk. It identifies up to 4 <firstterm>partitions</firstterm>, each of
which is a contiguous chunk of that disk. FreeBSD calls
partitions <firstterm>slices</> to avoid confusion with it's
partitions <firstterm>slices</firstterm> to avoid confusion with it's
own partitions, but we won't do that here. Each partition can
contain its own operating system.</para>
<para>Each partition entry in the MBR has a <firstterm>Partition
ID</>, a <firstterm>Start Cylinder/Head/Sector</>, and an
<firstterm>End Cylinder/Head/Sector</>. The Partition ID
ID</firstterm>, a <firstterm>Start Cylinder/Head/Sector</firstterm>, and an
<firstterm>End Cylinder/Head/Sector</firstterm>. The Partition ID
tells what type of partition it is (what OS) and the Start/End
tells where it is. <xref linkend="tbl-pid"> lists a
smattering of some common Partition IDs.</para>
<table id="tbl-pid">
<title>Partition IDs</>
<title>Partition IDs</title>
<tgroup cols="2">
<thead>
@ -515,7 +515,7 @@ Press Esc to continue
<para>Note that not all partitions are bootable (e.g. Extended
DOS). Some are&mdash;some aren't. What makes a partition
bootable is the configuration of the <firstterm>Partition Boot
Sector</> that exists at the beginning of each
Sector</firstterm> that exists at the beginning of each
partition.</para>
<para>When you configure your favorite boot manager, it looks up
@ -577,7 +577,7 @@ Press Esc to continue
</listitem>
<listitem>
<para>64 sectors/track, max (actually 63, <literal>0</>
<para>64 sectors/track, max (actually 63, <literal>0</literal>
isn't available)</para>
</listitem>
</itemizedlist>

126
en_US.ISO_8859-1/articles/new-users/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/new-users/article.sgml,v 1.12 1999/10/12 12:41:51 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/new-users/article.sgml,v 1.13 2000/06/27 02:48:51 kevlo Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -565,7 +565,7 @@
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</><keycap>L</></keycombo></term>
<term><keycombo><keycap>Ctrl</keycap><keycap>L</keycap></keycombo></term>
<listitem>
<para>to redraw the screen</para>
@ -573,36 +573,36 @@
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</><keycap>b</></> and
<keycombo><keycap>Ctrl</><keycap>f</></></term>
<term><keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> and
<keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo></term>
<listitem>
<para>go back and forward a screen, as they do with
<command>more</> and <command>view</>.</para>
<command>more</command> and <command>view</command>.</para>
</listitem>
</varlistentry>
</variablelist>
<para>Practice with <command>vi</> in your home directory by
creating a new file with <command>vi <replaceable>filename</></>
<para>Practice with <command>vi</command> in your home directory by
creating a new file with <command>vi <replaceable>filename</replaceable></command>
and adding and deleting text, saving the file, and calling it up
again. <command>vi</> delivers some surprises because it's
again. <command>vi</command> delivers some surprises because it's
really quite complex, and sometimes you'll inadvertently issue a
command that will do something you don't expect. (Some people
actually like <command>vi</>&mdash;it's more powerful than DOS
EDIT&mdash;find out about the <command>:r</> command.) Use
<keycap>Esc</> one or more times to be sure you're in command
actually like <command>vi</command>&mdash;it's more powerful than DOS
EDIT&mdash;find out about the <command>:r</command> command.) Use
<keycap>Esc</keycap> one or more times to be sure you're in command
mode and proceed from there when it gives you trouble, save
often with <command>:w</>, and use <command>:q!</> to get out
and start over (from your last <command>:w</>) when you need
often with <command>:w</command>, and use <command>:q!</command> to get out
and start over (from your last <command>:w</command>) when you need
to.</para>
<para>Now you can <command>cd</> to <filename>/etc</filename>,
<command>su</> to root, use <command>vi</> to edit the file
<para>Now you can <command>cd</command> to <filename>/etc</filename>,
<command>su</command> to root, use <command>vi</command> to edit the file
<filename>/etc/group</filename>, and add a user to wheel so the
user has root privileges. Just add a comma and the user's login
name to the end of the first line in the file, press
<keycap>Esc</>, and use <command>:wq</> to write the file to
<keycap>Esc</keycap>, and use <command>:wq</command> to write the file to
disk and quit. Instantly effective. (You didn't put a space
after the comma, did you?)</para>
</sect1>
@ -625,7 +625,7 @@
<para>will remove formatting codes and send the man page to the
<filename>chmod.txt</filename> file instead of showing it on
your screen. Now put a dos-formatted diskette in your floppy
drive a, <command>su</> to root, and type</para>
drive a, <command>su</command> to root, and type</para>
<informalexample>
<screen>&prompt.root; <userinput>/sbin/mount -t msdos /dev/fd0 /mnt</>
@ -636,7 +636,7 @@
<filename>/mnt</filename>.</para>
<para>Now (you no longer need to be root, and you can type
<command>exit</> to get back to being user jack) you can go to
<command>exit</command> to get back to being user jack) you can go to
the directory where you created chmod.txt and copy the file to
the floppy with:</para>
@ -661,10 +661,10 @@
<command>/sbin/dmesg</command> is the boot log record, and it's
useful to understand it because it shows what FreeBSD found when
it booted up. If you ask questions on
<email>freebsd-questions@FreeBSD.org</> or on a USENET
<email>freebsd-questions@FreeBSD.org</email> or on a USENET
group&mdash;like <quote>FreeBSD isn't finding my tape drive,
what do I do?</quote>&mdash;people will want to know what
<command>dmesg</> has to say.</para>
<command>dmesg</command> has to say.</para>
<para>You can now dismount the floppy drive (as root) to get the
disk out with</para>
@ -679,7 +679,7 @@
Wordpad, or a word processor, make a minor change so the file
has to be saved, and print as you normally would from DOS or
Windows. Hope it works! man pages come out best if printed
with the dos <command>print</> command. (Copying files from
with the dos <command>print</command> command. (Copying files from
FreeBSD to a mounted dos partition is in some cases still a
little risky.)</para>
@ -687,15 +687,15 @@
an appropriate entry in <filename>/etc/printcap</filename> and
creating a matching spool directory in
<filename>/var/spool/output</filename>. If your printer is on
<hardware>lpt0</> (what dos calls <hardware>LPT1</>), you may
<hardware>lpt0</hardware> (what dos calls <hardware>LPT1</hardware>), you may
only need to go to <filename>/var/spool/output</filename> and
(as root) create the directory <filename>lpd</> by typing:
(as root) create the directory <filename>lpd</filename> by typing:
<command> mkdir lpd</command>, if it doesn't already exist.
Then the printer should respond if it's turned on when the
system is booted, and lp or lpr should send a file to the
printer. Whether or not the file actually prints depends on
configuring it, which is covered in the <ulink
URL="../../handbook/handbook.html">FreeBSD handbook.</></para>
URL="../../handbook/handbook.html">FreeBSD handbook.</ulink></para>
</sect1>
<sect1>
@ -703,7 +703,7 @@
<variablelist>
<varlistentry>
<term><command>df</></term>
<term><command>df</command></term>
<listitem>
<para>shows file space and mounted systems.</para>
@ -711,27 +711,27 @@
</varlistentry>
<varlistentry>
<term><command>ps aux</></term>
<term><command>ps aux</command></term>
<listitem>
<para>shows processes running. <command>ps ax</> is a
<para>shows processes running. <command>ps ax</command> is a
narrower form.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rm <replaceable>filename</></></term>
<term><command>rm <replaceable>filename</replaceable></command></term>
<listitem>
<para>remove <replaceable>filename</>.</para>
<para>remove <replaceable>filename</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rm -R <replaceable>dir</></></term>
<term><command>rm -R <replaceable>dir</replaceable></command></term>
<listitem>
<para>removes a directory <replaceable>dir</> and all
<para>removes a directory <replaceable>dir</replaceable> and all
subdirectories&mdash;careful!</para>
</listitem>
</varlistentry>
@ -750,7 +750,7 @@
</varlistentry>
<varlistentry>
<term><command>passwd</></term>
<term><command>passwd</command></term>
<listitem>
<para>to change user's password (or root's password)</para>
@ -758,7 +758,7 @@
</varlistentry>
<varlistentry>
<term><command>man hier</></term>
<term><command>man hier</command></term>
<listitem>
<para>man page on the Unix file system</para>
@ -766,7 +766,7 @@
</varlistentry>
</variablelist>
<para>Use <command>find</> to locate filename in
<para>Use <command>find</command> to locate filename in
<filename>/usr</filename> or any of its subdirectories
with</para>
@ -776,7 +776,7 @@
</informalexample>
<para>You can use <literal>*</literal> as a wildcard in
<parameter>"<replaceable>filename</>"</> (which should be in
<parameter>"<replaceable>filename</replaceable>"</parameter> (which should be in
quotes). If you tell find to search in <filename>/</filename>
instead of <filename>/usr</filename> it will look for the
file(s) on all mounted file systems, including the CDROM and the
@ -802,7 +802,7 @@
URL="http://www.cdrom.com/">Walnut Creek</ulink> CDROM as well
as the web site. The handbook tells you more about how to use
them (get the package if it exists, with <command>pkg_add
/cdrom/packages/All/<replaceable>packagename</></>, where
/cdrom/packages/All/<replaceable>packagename</replaceable></command>, where
<replaceable>packagename</replaceable> is the filename of the
package). The cdrom has lists of the packages and ports with
brief descriptions in <filename>cdrom/packages/index</filename>,
@ -813,10 +813,10 @@
programs and program names respectively.</para>
<para>If you find the handbook too sophisticated (what with
<command>lndir</> and all) on installing ports from the cdrom,
<command>lndir</command> and all) on installing ports from the cdrom,
here's what usually works:</para>
<para>Find the port you want, say <command>kermit</>. There will
<para>Find the port you want, say <command>kermit</command>. There will
be a directory for it on the cdrom. Copy the subdirectory to
<filename>/usr/local</filename> (a good place for software you
add that should be available to all users) with:</para>
@ -833,16 +833,16 @@
<para>Next, create the directory
<filename>/usr/ports/distfiles</filename> if it doesn't already
exist using <command>mkdir</>. Now check check
exist using <command>mkdir</command>. Now check check
<filename>/cdrom/ports/distfiles</filename> for a file with a
name that indicates it's the port you want. Copy that file to
<filename>/usr/ports/distfiles</filename>; in recent versions
you can skip this step, as FreeBSD will do it for you. In the
case of <command>kermit</>, there is no distfile.</para>
case of <command>kermit</command>, there is no distfile.</para>
<para>Then <command>cd</> to the subdirectory of
<para>Then <command>cd</command> to the subdirectory of
<filename>/usr/local/kermit</filename> that has the file
<filename>Makefile</>. Type</para>
<filename>Makefile</filename>. Type</para>
<informalexample>
<screen>&prompt.root; <userinput>make all install</>
@ -856,17 +856,17 @@
<filename>/cdrom/ports/distfiles</filename>, you will have to
get the distfile using another machine and copy it to
<filename>/usr/ports/distfiles</filename> from a floppy or your
dos partition. Read <filename>Makefile</> (with <command>cat</>
or <command>more</> or <command>view</>) to find out where to go
dos partition. Read <filename>Makefile</filename> (with <command>cat</command>
or <command>more</command> or <command>view</command>) to find out where to go
(the master distribution site) to get the file and what its name
is. Its name will be truncated when downloaded to DOS, and
after you get it into <filename>/usr/ports/distfiles</filename>
you'll have to rename it (with the <command>mv</> command) to
you'll have to rename it (with the <command>mv</command> command) to
its original name so it can be found. (Use binary file
transfers!) Then go back to
<filename>/usr/local/kermit</filename>, find the directory with
<filename>Makefile</>, and type <command>make all
install</>.</para>
<filename>Makefile</filename>, and type <command>make all
install</command>.</para>
<para>The other thing that happens when installing ports or
packages is that some other program is needed. If the
@ -874,10 +874,10 @@
unzip</errorname> or whatever, you might need to install the
package or port for unzip before you continue.</para>
<para>Once it's installed type <command>rehash</> to make FreeBSD
<para>Once it's installed type <command>rehash</command> to make FreeBSD
reread the files in the path so it knows what's there. (If you
get a lot of <errorname>path not found</> messages when you use
<command>whereis</> or which, you might want to make additions
get a lot of <errorname>path not found</errorname> messages when you use
<command>whereis</command> or which, you might want to make additions
to the list of directories in the path statement in
<filename>.cshrc</filename> in your home directory. The path
statement in Unix does the same kind of work it does in DOS,
@ -890,10 +890,10 @@
from their <ulink URL="ftp://ftp.netscape.com">ftp site</ulink>.
(Netscape requires the X Window System.) There's now a FreeBSD
version, so look around carefully. Just use <command>gunzip
<replaceable>filename</></> and <command>tar xvf
<replaceable>filename</></> on it, move the binary to
<replaceable>filename</replaceable></command> and <command>tar xvf
<replaceable>filename</replaceable></command> on it, move the binary to
<filename>/usr/local/bin</filename> or some other place binaries
are kept, <command>rehash</>, and then put the following lines
are kept, <command>rehash</command>, and then put the following lines
in <filename>.cshrc</filename> in each user's home directory or
(easier) in <filename>/etc/csh.cshrc</filename>, the
system-wide csh start-up file:</para>
@ -901,11 +901,11 @@
<informalexample>
<programlisting>setenv XKEYSYMDB /usr/X11R6/lib/X11/XKeysymDB
setenv XNLSPATH /usr/X11R6/lib/X11/nls
</>
</programlisting>
</informalexample>
<para>This assumes that the file <filename>XKeysymDB</> and the
directory <filename>nls</> are in
<para>This assumes that the file <filename>XKeysymDB</filename> and the
directory <filename>nls</filename> are in
<filename>/usr/X11R6/lib/X11</filename>; if they're not, find
them and put them there.</para>
@ -977,7 +977,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
you the tcsh as root, because the shell is part of the
environment. You can make this permanent by adding it to your
<filename>.tcshrc</filename> file as an alias with
<programlisting>alias su su -m.</></para>
<programlisting>alias su su -m.</programlisting></para>
</note>
<para>When tcsh starts up, it will read the
@ -1020,10 +1020,10 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
<title>Other</title>
<para>As root, you can dismount the CDROM with
<command>/sbin/umount /cdrom</>, take it out of the drive,
<command>/sbin/umount /cdrom</command>, take it out of the drive,
insert another one, and mount it with
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</> assuming
<hardware>cd0a</> is the device name for your CDROM drive. The
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</command> assuming
<hardware>cd0a</hardware> is the device name for your CDROM drive. The
most recent versions of FreeBSD let you mount the cdrom with
just <command>/sbin/mount /cdrom</command>.</para>
@ -1031,12 +1031,12 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
CDROM disks&mdash;is useful if you've got limited space. What
is on the live file system varies from release to release. You
might try playing games from the cdrom. This involves using
<command>lndir</>, which gets installed with the X Window
<command>lndir</command>, which gets installed with the X Window
System, to tell the program(s) where to find the necessary
files, because they're in the <filename>/cdrom</filename> file
system instead of in <filename>/usr</filename> and its
subdirectories, which is where they're expected to be. Read
<command>man lndir</>.</para>
<command>man lndir</command>.</para>
</sect1>
<sect1>
@ -1049,6 +1049,6 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls
Fieber for helpful comments.</para>
<para>Annelise Anderson,
<email>andrsn@andrsn.stanford.edu</></para>
<email>andrsn@andrsn.stanford.edu</email></para>
</sect1>
</article>

60
en_US.ISO_8859-1/articles/programming-tools/article.sgml
View file

@ -1,4 +1,4 @@
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v 1.10 1999/10/13 01:45:20 jhb Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v 1.11 2000/06/14 13:18:43 alex Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
@ -44,10 +44,10 @@
<para>FreeBSD offers an excellent development environment.
Compilers for C, C++, and Fortran and an assembler come with the
basic system, not to mention a Perl interpreter and classic Unix
tools such as <command>sed</> and <command>awk</>. If that is
tools such as <command>sed</command> and <command>awk</command>. If that is
not enough, there are many more compilers and interpreters in
the Ports collection. FreeBSD is very compatible with standards
such as <acronym>POSIX</> and <acronym>ANSI</> C, as well with
such as <acronym>POSIX</acronym> and <acronym>ANSI</acronym> C, as well with
its own BSD heritage, so it is possible to write applications
that will compile and run with little or no modification on a
wide range of platforms.</para>
@ -73,8 +73,8 @@
instruction. This section gives an overview of the two main
ways in which you can give these instructions, or
<quote>commands</quote> as they are usually called. One way
uses an <firstterm>interpreter</>, the other a
<firstterm>compiler</>. As human languages are too difficult for
uses an <firstterm>interpreter</firstterm>, the other a
<firstterm>compiler</firstterm>. As human languages are too difficult for
a computer to understand in an unambiguous way, commands are
usually written in one or other languages specially designed for
the purpose.</para>
@ -105,10 +105,10 @@
start if you have not done any programming before. This kind
of environment is typically found with languages like Lisp,
Smalltalk, Perl and Basic. It could also be argued that the
Unix shell (<command>sh</>, <command>csh</>) is itself an
Unix shell (<command>sh</command>, <command>csh</command>) is itself an
interpreter, and many people do in fact write shell
<quote>scripts</quote> to help with various
<quote>housekeeping</> tasks on their machine. Indeed, part
<quote>housekeeping</quote> tasks on their machine. Indeed, part
of the original Unix philosophy was to provide lots of small
utility programs that could be linked together in shell
scripts to perform useful tasks.</para>
@ -135,16 +135,16 @@
<variablelist>
<varlistentry>
<term><acronym>BASIC</></term>
<term><acronym>BASIC</acronym></term>
<listitem>
<para>Short for Beginner's All-purpose Symbolic
Instruction Code. Developed in the 1950s for teaching
University students to program and provided with every
self-respecting personal computer in the 1980s,
<acronym>BASIC</> has been the first programming
<acronym>BASIC</acronym> has been the first programming
language for many programmers. It's also the foundation
for <trademark>Visual Basic</>.</para>
for <trademark>Visual Basic</trademark>.</para>
<para>The <ulink
URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/bwbasic-2.10.tgz">Bywater
@ -184,7 +184,7 @@
<listitem>
<para>Very popular with system administrators for writing
scripts; also often used on World Wide Web servers for
writing <acronym>CGI</> scripts.</para>
writing <acronym>CGI</acronym> scripts.</para>
<para>The latest version (version 5) comes with FreeBSD.</para>
</listitem>
@ -284,7 +284,7 @@
using separate programs, many commercial compiler makers have
produced Integrated Development Environments
(<acronym>IDE</acronym>s for short). FreeBSD does not have an
<acronym>IDE</> as such; however it is possible to use Emacs
<acronym>IDE</acronym> as such; however it is possible to use Emacs
for this purpose. This is discussed in <xref
linkend="emacs">.</para>
</sect2>
@ -295,7 +295,7 @@
<para>This section deals only with the GNU compiler for C and C++,
since that comes with the base FreeBSD system. It can be
invoked by either <command>cc</> or <command>gcc</>. The
invoked by either <command>cc</command> or <command>gcc</command>. The
details of producing a program with an interpreter vary
considerably between interpreters, and are usually well covered
in the documentation and on-line help for the
@ -324,9 +324,9 @@
understandable by humans. Allegedly.
<footnote>
<para>To be strictly accurate, <command>cc</> converts the
<para>To be strictly accurate, <command>cc</command> converts the
source code into its own, machine-independent
<firstterm>p-code</> instead of assembly language at
<firstterm>p-code</firstterm> instead of assembly language at
this stage.</para>
</footnote></para>
</step>
@ -361,20 +361,20 @@
</step>
</procedure>
<para>The word <firstterm>compiling</> is often used to refer to
<para>The word <firstterm>compiling</firstterm> is often used to refer to
just steps 1 to 4&mdash;the others are referred to as
<firstterm>linking</>. Sometimes step 1 is referred to as
<firstterm>pre-processing</> and steps 3-4 as
<firstterm>assembling</>.</para>
<firstterm>linking</firstterm>. Sometimes step 1 is referred to as
<firstterm>pre-processing</firstterm> and steps 3-4 as
<firstterm>assembling</firstterm>.</para>
<para>Fortunately, almost all this detail is hidden from you, as
<command>cc</> is a front end that manages calling all these
<command>cc</command> is a front end that manages calling all these
programs with the right arguments for you; simply typing</para>
<screen>&prompt.user; <userinput>cc foobar.c</>
</screen>
<para>will cause <filename>foobar.c</> to be compiled by all the
<para>will cause <filename>foobar.c</filename> to be compiled by all the
steps above. If you have more than one file to compile, just do
something like</para>
@ -393,18 +393,18 @@
isn't.</para>
</footnote></para>
<para>There are lots and lots of options for <command>cc</>, which
<para>There are lots and lots of options for <command>cc</command>, which
are all in the man page. Here are a few of the most important
ones, with examples of how to use them.</para>
<variablelist>
<varlistentry>
<term><option>-o <replaceable>filename</replaceable></></term>
<term><option>-o <replaceable>filename</replaceable></option></term>
<listitem>
<para>The output name of the file. If you do not use this
option, <command>cc</> will produce an executable called
<filename>a.out</>.
option, <command>cc</command> will produce an executable called
<filename>a.out</filename>.
<footnote>
<para>The reasons for this are buried in the mists of
@ -432,7 +432,7 @@
</screen>
</informalexample>
<para>This will produce an <firstterm>object file</> (not an
<para>This will produce an <firstterm>object file</firstterm> (not an
executable) called <filename>foobar.o</filename>. This
can be linked together with other object files into an
executable.</para>
@ -525,7 +525,7 @@
<listitem>
<para>Turn off most, but not all, of the
non-<acronym>ANSI</>&nbsp;C features provided by
non-<acronym>ANSI</acronym>&nbsp;C features provided by
<command>cc</command>. Despite the name, it does not
guarantee strictly that your code will comply to the
standard.</para>
@ -537,7 +537,7 @@
<listitem>
<para>Turn off <emphasis>all</emphasis>
<command>cc</command>'s non-<acronym>ANSI</>&nbsp;C
<command>cc</command>'s non-<acronym>ANSI</acronym>&nbsp;C
features.</para>
</listitem>
</varlistentry>
@ -1478,7 +1478,7 @@ main() {
listings of core files and sweat over machine code manuals,
but now life is a bit easier. Incidentally, under FreeBSD and
other 4.4BSD systems, a core file is called
<filename><replaceable>progname</>.core</> instead of just
<filename><replaceable>progname</replaceable>.core</filename> instead of just
<filename>core</filename>, to make it clearer which program a
core file belongs to.</para>
@ -1771,7 +1771,7 @@ else if (pid == 0) { /* child */
<itemizedlist>
<listitem>
<para>Everything beginning with a <literal>;</> is a comment
<para>Everything beginning with a <literal>;</literal> is a comment
and is ignored by Emacs.</para>
</listitem>