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

Wrap overlong lines, remove redundant markup and words, change to proper

Browse source 
capitalization.
This commit is contained in:
Benedict Reuschling 2018-08-16 13:55:09 +00:00
parent 90901ed261
commit aa6f4dc4d1
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=52136
1 changed files with 197 additions and 149 deletions

346
en_US.ISO8859-1/articles/new-users/article.xml
View file

@ -3,14 +3,22 @@
"http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd">
<!-- $FreeBSD$ -->
<!-- The FreeBSD Documentation Project -->
<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<info><title>For People New to Both FreeBSD and &unix;</title>
<article xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:lang="en">
<info>
<title>For People New to Both FreeBSD and &unix;</title>
<authorgroup>
<author><personname><firstname>Annelise</firstname><surname>Anderson</surname></personname><affiliation>
<author>
<personname>
<firstname>Annelise</firstname>
<surname>Anderson</surname>
</personname>
<affiliation>
<address><email>andrsn@andrsn.stanford.edu</email></address>
</affiliation></author>
</affiliation>
</author>
</authorgroup>
<pubdate>1997-08-15</pubdate>
@ -36,13 +44,16 @@
<title>Logging in and Getting Out</title>
<para>Log in (when you see <prompt>login:</prompt>) as a user you
created during installation or as <systemitem class="username">root</systemitem>.
(Your FreeBSD installation will already have an account for
<systemitem class="username">root</systemitem>; who can go anywhere and do anything, including deleting
essential files, so be careful!) The symbols &prompt.user; and
&prompt.root; in the following stand for the prompt (yours may
be different), with &prompt.user; indicating an ordinary user
and &prompt.root; indicating <systemitem class="username">root</systemitem>.</para>
created during installation or as <systemitem
class="username">root</systemitem>. (Your FreeBSD
installation will already have an account for <systemitem
class="username">root</systemitem>; who can go anywhere and do
anything, including deleting essential files, so be careful!)
The symbols &prompt.user; and &prompt.root; in the following
stand for the prompt (yours may be different), with
&prompt.user; indicating an ordinary user and &prompt.root;
indicating <systemitem
class="username">root</systemitem>.</para>
<para>To log out (and get a new <prompt>login:</prompt> prompt)
type</para>
@ -83,62 +94,71 @@
</sect1>
<sect1 xml:id="adding-a-user">
<title>Adding A User with Root Privileges</title>
<title>Adding a User with Root Privileges</title>
<para>If you did not create any users when you installed the system
and are thus logged in as <systemitem class="username">root</systemitem>, you should probably create a
user now with</para>
<para>If you did not create any users when you installed the
system and are thus logged in as <systemitem
class="username">root</systemitem>, you should probably create
a user now with</para>
<informalexample>
<screen>&prompt.root; <userinput>adduser</userinput></screen>
</informalexample>
<para>The first time you use <command>adduser</command>, it might ask for some
defaults to save. You might want to make the default shell
&man.csh.1; instead of &man.sh.1;, if it suggests
<para>The first time you use <command>adduser</command>, it might
ask for some defaults to save. You might want to make the
default shell &man.csh.1; instead of &man.sh.1;, if it suggests
<command>sh</command> as the default. Otherwise just press
enter to accept each default. These defaults are saved in
<filename>/etc/adduser.conf</filename>, an editable file.</para>
<para>Suppose you create a user <systemitem class="username">jack</systemitem> with
full name <emphasis>Jack Benimble</emphasis>. Give <systemitem class="username">jack</systemitem> a
password if security (even kids around who might pound on the
keyboard) is an issue. When it asks you if you want to invite
<systemitem class="username">jack</systemitem> into other groups, type <systemitem class="groupname">wheel</systemitem></para>
<para>Suppose you create a user <systemitem
class="username">jack</systemitem> with full name
<emphasis>Jack Benimble</emphasis>. Give <systemitem
class="username">jack</systemitem> a password if security
(even kids around who might pound on the keyboard) is an issue.
When it asks you if you want to invite <systemitem
class="username">jack</systemitem> into other groups, type
<systemitem class="groupname">wheel</systemitem></para>
<informalexample>
<screen>Login group is ``jack''. Invite jack into other groups: <userinput>wheel</userinput></screen>
</informalexample>
<para>This will make it possible to log in as
<systemitem class="username">jack</systemitem> and use the &man.su.1;
command to become <systemitem class="username">root</systemitem>. Then you will not get scolded any more for
logging in as <systemitem class="username">root</systemitem>.</para>
<para>This will make it possible to log in as <systemitem
class="username">jack</systemitem> and use the &man.su.1;
command to become <systemitem
class="username">root</systemitem>. Then you will not get
scolded any more for logging in as <systemitem
class="username">root</systemitem>.</para>
<para>You can quit <command>adduser</command> any time by typing
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>,
and at the end you will have a chance to approve your new user or
simply type <keycap>n</keycap> for no. You might want to create
a second new user so that when you edit <systemitem class="username">jack</systemitem>'s login
files, you will have a hot spare in case something goes
wrong.</para>
and at the end you will have a chance to approve your new user
or simply type <keycap>n</keycap> for no. You might want to
create a second new user so that when you edit <systemitem
class="username">jack</systemitem>'s login files, you will
have a hot spare in case something goes wrong.</para>
<para>Once you have done this, use <command>exit</command> to get
back to a login prompt and log in as <systemitem class="username">jack</systemitem>.
In general, it is a good idea to do as much work as possible as
an ordinary user who does not have the power&mdash;and
risk&mdash;of <systemitem class="username">root</systemitem>.</para>
back to a login prompt and log in as <systemitem
class="username">jack</systemitem>. In general, it is a good
idea to do as much work as possible as an ordinary user who does
not have the power&mdash;and risk&mdash;of <systemitem
class="username">root</systemitem>.</para>
<para>If you already created a user and you want the user to be
able to <command>su</command> to <systemitem class="username">root</systemitem>, you can log in as <systemitem class="username">root</systemitem>
and edit the file <filename>/etc/group</filename>, adding <systemitem class="username">jack</systemitem>
to the first line (the group <systemitem class="groupname">wheel</systemitem>). But
able to <command>su</command> to <systemitem
class="username">root</systemitem>, you can log in as
<systemitem class="username">root</systemitem> and edit the file
<filename>/etc/group</filename>, adding <systemitem
class="username">jack</systemitem> to the first line (the
group <systemitem class="groupname">wheel</systemitem>). But
first you need to practice &man.vi.1;, the text editor&mdash;or
use the simpler text editor, &man.ee.1;, installed on recent
versions of FreeBSD.</para>
<para>To delete a user, use the <command>rmuser</command>
command.</para>
<para>To delete a user, use <command>rmuser</command>.</para>
</sect1>
<sect1 xml:id="looking-around">
@ -201,8 +221,9 @@
<listitem>
<para>Lists hidden <quote>dot</quote> files with the others.
If you are <systemitem class="username">root</systemitem>, the <quote>dot</quote> files show up
without the <option>-a</option> switch.</para>
If you are <systemitem class="username">root</systemitem>,
the <quote>dot</quote> files show up without the
<option>-a</option> switch.</para>
</listitem>
</varlistentry>
@ -210,14 +231,12 @@
<term><command>cd</command></term>
<listitem>
<para>Changes directories. <command>cd
..</command> backs up one level;
note the space after <command>cd</command>. <command>cd
/usr/local</command> goes there.
<command>cd ~</command> goes to the
home directory of the person logged in&mdash;e.g.,
<filename>/usr/home/jack</filename>. Try <command>cd
/cdrom</command>, and then
<para>Changes directories. <command>cd ..</command> backs
up one level; note the space after <command>cd</command>.
<command>cd /usr/local</command> goes there. <command>cd
~</command> goes to the home directory of the person
logged in&mdash;e.g., <filename>/usr/home/jack</filename>.
Try <command>cd /cdrom</command>, and then
<command>ls</command>, to find out if your CDROM is
mounted and working.</para>
</listitem>
@ -289,11 +308,11 @@
<replaceable>text</replaceable></command></term>
<listitem>
<para>The manual page for <replaceable>text</replaceable>. The
major source of documentation for &unix; systems.
<command>man ls</command> will tell
you all the ways to use the <command>ls</command> command.
Press <keycap>Enter</keycap> to move through text,
<para>The manual page for <replaceable>text</replaceable>.
The major source of documentation for &unix; systems.
<command>man ls</command> will tell you all the ways to
use <command>ls</command>. Press <keycap>Enter</keycap>
to move through text,
<keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo>
to go back a page,
<keycombo><keycap>Ctrl</keycap><keycap>F</keycap></keycombo>
@ -361,11 +380,12 @@
<literal>w</literal>.</para>
<para>Are some of these not working very well? Both
&man.locate.1; and &man.whatis.1; depend
on a database that is rebuilt weekly. If your machine is not
going to be left on over the weekend (and running FreeBSD), you
might want to run the commands for daily, weekly, and monthly
maintenance now and then. Run them as <systemitem class="username">root</systemitem> and, for now, give each one
&man.locate.1; and &man.whatis.1; depend on a database that is
rebuilt weekly. If your machine is not going to be left on over
the weekend (and running FreeBSD), you might want to run the
commands for daily, weekly, and monthly maintenance now and
then. Run them as <systemitem
class="username">root</systemitem> and, for now, give each one
time to finish before you start the next one.</para>
<informalexample>
@ -391,16 +411,16 @@
<para>Running such commands is part of system
administration&mdash;and as a single user of a &unix; system,
you are your own system administrator. Virtually everything you
need to be <systemitem class="username">root</systemitem> to do is system administration. Such
responsibilities are not covered very well even in those big fat
books on &unix;, which seem to devote a lot of space to pulling
down menus in windows managers. You might want to get one of
the two leading books on systems administration, either Evi
Nemeth et.al.'s <citetitle>UNIX System Administration
Handbook</citetitle> (Prentice-Hall, 1995, ISBN
0-13-15051-7)&mdash;the second edition with the red cover; or
&AElig;leen Frisch's <citetitle>Essential System
Administration</citetitle> (O'Reilly &amp; Associates, 2002,
need to be <systemitem class="username">root</systemitem> to do
is system administration. Such responsibilities are not covered
very well even in those big fat books on &unix;, which seem to
devote a lot of space to pulling down menus in windows managers.
You might want to get one of the two leading books on systems
administration, either Evi Nemeth et.al.'s <citetitle>UNIX
System Administration Handbook</citetitle> (Prentice-Hall,
1995, ISBN 0-13-15051-7)&mdash;the second edition with the red
cover; or &AElig;leen Frisch's <citetitle>Essential System
Administration</citetitle> (O'Reilly &amp; Associates, 2002,
ISBN 0-596-00343-9). I used Nemeth.</para>
</sect1>
@ -409,10 +429,11 @@
<para>To configure your system, you need to edit text files. Most
of them will be in the <filename>/etc</filename> directory; and
you will need to <command>su</command> to <systemitem class="username">root</systemitem> to be able to
change them. You can use the easy <command>ee</command>, but in
the long run the text editor <command>vi</command> is worth
learning. There is an excellent tutorial on vi in
you will need to <command>su</command> to <systemitem
class="username">root</systemitem> to be able to change them.
You can use the easy <command>ee</command>, but in the long run
the text editor <command>vi</command> is worth learning. There
is an excellent tutorial on vi in
<filename>/usr/src/contrib/nvi/docs/tutorial</filename>, if you
have the system sources installed.</para>
@ -436,8 +457,8 @@
&prompt.root; <userinput>cp rc.conf.orig rc.conf</userinput></screen>
</informalexample>
<para>because the <command>mv</command> command preserves the
original date and owner of the file. You can now edit
<para>because <command>mv</command> preserves the original date
and owner of the file. You can now edit
<filename>rc.conf</filename>. If you want the original back,
you would then <userinput>mv rc.conf rc.conf.myedit</userinput>
(assuming you want to preserve your edited version) and
@ -562,37 +583,49 @@
</varlistentry>
<varlistentry>
<term><keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> and
<keycombo><keycap>Ctrl</keycap><keycap>f</keycap></keycombo></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</command> and <command>view</command>.</para>
<command>more</command> and
<command>view</command>.</para>
</listitem>
</varlistentry>
</variablelist>
<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
<replaceable>filename</replaceable></command> and adding and
deleting text, saving the file, and calling it up again.
<command>vi</command> delivers some surprises because it is
really quite complex, and sometimes you will inadvertently issue a
command that will do something you do not expect. (Some people
actually like <command>vi</command>&mdash;it is 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 are in command mode and proceed from there when it gives you
trouble, save 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>
really quite complex, and sometimes you will inadvertently issue
a command that will do something you do not expect. (Some
people actually like <command>vi</command>&mdash;it is more
powerful than DOS EDIT&mdash;find out about
<command>:r</command>.) Use <keycap>Esc</keycap> one or more
times to be sure you are in command mode and proceed from there
when it gives you trouble, save 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</command> to
<filename>/etc</filename>, <command>su</command> to <systemitem class="username">root</systemitem>, use
<command>vi</command> to edit the file
<filename>/etc/group</filename>, and add a user to <systemitem class="groupname">wheel</systemitem> 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
<filename>/etc</filename>, <command>su</command> to <systemitem
class="username">root</systemitem>, use <command>vi</command>
to edit the file <filename>/etc/group</filename>, and add a user
to <systemitem class="groupname">wheel</systemitem> 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</keycap>, and use <command>:wq</command> to write
the file to disk and quit. Instantly effective. (You did not
put a space after the comma, did you?)</para>
@ -614,13 +647,17 @@
<term><command>ps aux</command></term>
<listitem>
<para>shows processes running. <command>ps ax</command> is a
narrower form.</para>
<para>shows processes running. <command>ps ax</command> is
a narrower form.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>rm <replaceable>filename</replaceable></command></term>
<term>
<command>rm
<replaceable>filename</replaceable>
</command>
</term>
<listitem>
<para>remove <replaceable>filename</replaceable>.</para>
@ -628,11 +665,15 @@
</varlistentry>
<varlistentry>
<term><command>rm -R <replaceable>dir</replaceable></command></term>
<term>
<command>rm -R
<replaceable>dir</replaceable>
</command>
</term>
<listitem>
<para>removes a directory <replaceable>dir</replaceable> and all
subdirectories&mdash;careful!</para>
<para>removes a directory <replaceable>dir</replaceable> and
all subdirectories&mdash;careful!</para>
</listitem>
</varlistentry>
@ -653,7 +694,8 @@
<term><command>passwd</command></term>
<listitem>
<para>to change user's password (or <systemitem class="username">root</systemitem>'s password)</para>
<para>to change user's password (or <systemitem
class="username">root</systemitem>'s password)</para>
</listitem>
</varlistentry>
@ -666,9 +708,9 @@
</varlistentry>
</variablelist>
<para>Use <command>find</command> to locate <filename>filename</filename> in
<filename>/usr</filename> or any of its subdirectories
with</para>
<para>Use <command>find</command> to locate
<filename>filename</filename> in <filename>/usr</filename> or
any of its subdirectories with</para>
<informalexample>
<screen>&prompt.user; <userinput>find /usr -name "<replaceable>filename</replaceable>"</userinput></screen>
@ -682,10 +724,10 @@
file(s) on all mounted filesystems, including the CDROM and the
DOS partition.</para>
<para>An excellent book that explains &unix; commands and utilities
is Abrahams &amp; Larson, <citetitle>Unix for the
Impatient</citetitle> (2nd ed., Addison-Wesley, 1996).
There is also a lot of &unix; information on the Internet.</para>
<para>An excellent book that explains &unix; commands and
utilities is Abrahams &amp; Larson, <citetitle>Unix for the
Impatient</citetitle> (2nd ed., Addison-Wesley, 1996). There
is also a lot of &unix; information on the Internet.</para>
</sect1>
<sect1 xml:id="next-steps">
@ -694,15 +736,15 @@
<para>You should now have the tools you need to get around and
edit files, so you can get everything up and running. There is
a great deal of information in the FreeBSD handbook (which is
probably on your hard drive) and <link xlink:href="&url.base;/index.html">FreeBSD's web site</link>. A
wide variety of packages and ports are on the CDROM as well as
probably on your hard drive) and <link
xlink:href="&url.base;/index.html">FreeBSD's web site</link>.
A wide variety of packages and ports are on the 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
<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>,
<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>,
<filename>cdrom/packages/index.txt</filename>, and
<filename>cdrom/ports/index</filename>, with fuller descriptions
in <filename>/cdrom/ports/*/*/pkg/DESCR</filename>, where the
@ -783,7 +825,7 @@
<command>tcsh</command> does everything <command>csh</command>
does and more. It allows you to recall commands with the arrow
keys and edit them. It has tab-key completion of filenames
(<command>csh</command> uses the <keycap>Esc</keycap> key), and
(<command>csh</command> uses <keycap>Esc</keycap>), and
it lets you switch to the directory you were last in with
<command>cd -</command>. It is also much easier to alter your
prompt with <command>tcsh</command>. It makes life a lot
@ -798,34 +840,39 @@
</step>
<step>
<para>Use the <command>chsh</command> command to change your
shell to <command>tcsh</command> permanently, or type
<para>Use <command>chsh</command> to change your shell to
<command>tcsh</command> permanently, or type
<command>tcsh</command> at the prompt to change your shell
without logging in again.</para>
</step>
</procedure>
<note>
<para>It can be dangerous to change <systemitem class="username">root</systemitem>'s shell to something
<para>It can be dangerous to change <systemitem
class="username">root</systemitem>'s shell to something
other than <command>sh</command> or <command>csh</command> on
early versions of FreeBSD and many other versions of &unix;; you
may not have a working shell when the system puts you into
early versions of FreeBSD and many other versions of &unix;;
you may not have a working shell when the system puts you into
single user mode. The solution is to use <command>su
-m</command> to become <systemitem class="username">root</systemitem>, which will give you the
<command>tcsh</command> as <systemitem class="username">root</systemitem>, 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:</para>
<programlisting>alias su su -m</programlisting>
-m</command> to become <systemitem
class="username">root</systemitem>, which will give you the
<command>tcsh</command> as <systemitem
class="username">root</systemitem>, because the shell is
part of the environment. You can make this permanent by
adding it to your <filename>.tcshrc</filename> as an alias
with:</para>
<programlisting>alias su su -m</programlisting>
</note>
<para>When <command>tcsh</command> starts up, it will read the
<filename>/etc/csh.cshrc</filename> and
<filename>/etc/csh.login</filename> files, as does
<command>csh</command>. It will also read the
<filename>.login</filename> file in your home directory and the
<filename>.cshrc</filename> file as well, unless you provide a
<filename>.tcshrc</filename> file. This you can do by simply
copying <filename>.cshrc</filename> to
<command>csh</command>. It will also read
<filename>.login</filename> in your home directory and
<filename>.cshrc</filename> as well, unless you provide a
<filename>.tcshrc</filename>. This you can do by simply copying
<filename>.cshrc</filename> to
<filename>.tcshrc</filename>.</para>
<para>Now that you have installed <command>tcsh</command>, you can
@ -833,34 +880,35 @@
for <command>tcsh</command>, but here is a line to put in your
<filename>.tcshrc</filename> that will tell you how many
commands you have typed, what time it is, and what directory you
are in. It also produces a <literal>&gt;</literal> if you are an
ordinary user and a <literal>#</literal> if you are <systemitem class="username">root</systemitem>, but
tsch will do that in any case:</para>
are in. It also produces a <literal>&gt;</literal> if you are
an ordinary user and a <literal>#</literal> if you are
<systemitem class="username">root</systemitem>, but tsch will do
that in any case:</para>
<para>set prompt = "%h %t %~ %# "</para>
<para>This should go in the same place as the existing set prompt
line if there is one, or under "if($?prompt) then" if not.
Comment out the old line; you can always switch back to it if
you prefer it. Do not forget the spaces and quotes. You can get
the <filename>.tcshrc</filename> reread by typing
you prefer it. Do not forget the spaces and quotes. You can
get the <filename>.tcshrc</filename> reread by typing
<command>source .tcshrc</command>.</para>
<para>You can get a listing of other environmental variables that
have been set by typing <command>env</command> at the prompt.
The result will show you your default editor, pager, and
terminal type, among possibly many others. A useful command if
you log in from a remote location and can not run a program
you log in from a remote location and cannot run a program
because the terminal is not capable is <command>setenv TERM
vt100</command>.</para>
vt100</command>.</para>
</sect1>
<sect1 xml:id="other">
<title>Other</title>
<para>As <systemitem class="username">root</systemitem>, you can unmount the CDROM with
<command>/sbin/umount /cdrom</command>, take it out of the
drive, insert another one, and mount it with
<para>As <systemitem class="username">root</systemitem>, you can
unmount the CDROM with <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</command> assuming
<hardware>cd0a</hardware> is the device name for your CDROM
drive. The most recent versions of FreeBSD let you mount the
@ -872,22 +920,22 @@
might try playing games from the CDROM. This involves using
<command>lndir</command>, which gets installed with the X Window
System, to tell the program(s) where to find the necessary
files, because they are in the <filename>/cdrom</filename> file
system instead of in <filename>/usr</filename> and its
subdirectories, which is where they are expected to be. Read
<command>man lndir</command>.</para>
files, because they are in <filename>/cdrom</filename> instead
of in <filename>/usr</filename> and its subdirectories, which is
where they are expected to be. Read <command>man
lndir</command>.</para>
</sect1>
<sect1 xml:id="comments-welcome">
<title>Comments Welcome</title>
<para>If you use this guide I would be interested in knowing where it
was unclear and what was left out that you think should be
<para>If you use this guide I would be interested in knowing where
it was unclear and what was left out that you think should be
included, and if it was helpful. My thanks to Eugene W. Stark,
professor of computer science at SUNY-Stony Brook, and John
Fieber for helpful comments.</para>
<para>Annelise Anderson,
<email>andrsn@andrsn.stanford.edu</email></para>
<email>andrsn@andrsn.stanford.edu</email></para>
</sect1>
</article>