Date: Wed, 23 Jul 2003 23:42:17 +0200 (CEST) From: Lukas Ertl <l.ertl@univie.ac.at> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/54789: [PATCH] brush up the "New Users" article Message-ID: <200307232142.h6NLgH7s035091@korben.in.tern> Resent-Message-ID: <200307232150.h6NLoLCL097888@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 54789
>Category: docs
>Synopsis: [PATCH] brush up the "New Users" article
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jul 23 14:50:21 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Lukas Ertl
>Release: FreeBSD 5.1-CURRENT i386
>Organization:
Vienna University Computer Center
>Environment:
System: FreeBSD korben 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Mon Jul 21 12:23:17 CEST 2003 le@korben:/usr/obj/usr/src/sys/KORBEN i386
>Description:
The "New Users" article is a bit out of date. What I changed:
*) change "FreeBSD" and "Unix" to "&os;" and "&unix;"
*) tag usernames properly
*) proper SGML formatting
*) remove parts that seem to be out of date
>How-To-Repeat:
>Fix:
--- newusers.diff begins here ---
Index: en_US.ISO8859-1/articles/new-users/article.sgml
===================================================================
RCS file: /usr/local/bsdcvs/doc/en_US.ISO8859-1/articles/new-users/article.sgml,v
retrieving revision 1.36
diff -u -u -r1.36 article.sgml
--- en_US.ISO8859-1/articles/new-users/article.sgml 13 Jul 2003 15:38:43 -0000 1.36
+++ en_US.ISO8859-1/articles/new-users/article.sgml 23 Jul 2003 21:34:15 -0000
@@ -12,7 +12,7 @@
<article>
<articleinfo>
- <title>For People New to Both FreeBSD and &unix;</title>
+ <title>For People New to Both &os; and &unix;</title>
<authorgroup>
<author>
@@ -29,11 +29,11 @@
<pubdate>August 15, 1997</pubdate>
<abstract>
- <para>Congratulations on installing FreeBSD! This introduction
- is for people new to both FreeBSD <emphasis>and</emphasis>
- Un*x—so it starts with basics. It assumes you are using
- version 2.0.5 or later of FreeBSD as distributed by BSDi
- or FreeBSD.org, your system (for now) has a single user
+ <para>Congratulations on installing &os;! This introduction
+ is for people new to both &os; <emphasis>and</emphasis>
+ &unix;—so it starts with basics. It assumes you are
+ using version 2.0.5 or later of &os; as distributed from
+ FreeBSD.org, your system (for now) has a single user
(you)—and you are probably pretty good with DOS/Windows
or OS/2.</para>
</abstract>
@@ -42,23 +42,24 @@
<sect1>
<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 <firstterm>root</firstterm>.
- (Your FreeBSD installation will already have an account for
- root; root 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 root.</para>
+ <para>Log in (when you see <prompt>login:</prompt>) as a user you
+ created during installation or as <username>root</username>.
+ (Your &os; installation will already have an account for
+ <username>root</username>; <username>root</username> 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 <username>root</username>.</para>
- <para>To log out (and get a new <prompt >login:</prompt> prompt)
+ <para>To log out (and get a new <prompt>login:</prompt> prompt)
type</para>
<informalexample>
<screen>&prompt.root; <userinput>exit</userinput></screen>
</informalexample>
- <para>as often as necessary. Yes, press <keysym>enter</keysym>
+ <para>as often as necessary. Yes, press <keycap>Enter</keycap>
after commands, and remember that &unix; is
case-sensitive—<command>exit</command>, not
<command>EXIT</command>.</para>
@@ -84,7 +85,7 @@
<para>You can also reboot with
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo>.
Give it a little time to do its work. This is equivalent to
- <command>/sbin/reboot</command> in recent releases of FreeBSD
+ <command>/sbin/reboot</command> in recent releases of &os;
and is much, much better than hitting the reset button. You
do not want to have to reinstall this thing, do you?</para>
</sect1>
@@ -92,57 +93,60 @@
<sect1>
<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 root, 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 <username>root</username>, you
+ should probably create a user now with</para>
<informalexample>
<screen>&prompt.root; <userinput>adduser</userinput></screen>
</informalexample>
- <para>The first time you use adduser, 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 <username>jack</username> with
- full name <emphasis>Jack Benimble</emphasis>. Give jack 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
- jack into other groups, type <groupname>wheel</groupname></para>
+ full name <emphasis>Jack Benimble</emphasis>. Give
+ <username>jack</username> 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 <username>jack</username> into
+ other groups, type <groupname>wheel</groupname>:</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
- <username>jack</username> and use the &man.su.1;
- command to become root. Then you will not get scolded any more for
- logging in as root.</para>
+ <username>jack</username> and use the &man.su.1; command to
+ become <username>root</username>. Then you will not get scolded
+ any more for logging in as <username>root</username>.</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 (jill?) so that when you edit jack's login
- files, you will have a hot spare in case something goes
- wrong.</para>
+ a second new user (<username>jill</username>?) so that when you
+ edit <username>jack</username>'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 <username>jack</username>.
In general, it is a good idea to do as much work as possible as
an ordinary user who does not have the power—and
- risk—of root.</para>
+ risk—of <username>root</username>.</para>
<para>If you already created a user and you want the user to be
- able to <command>su</command> to root, you can log in as root
- and edit the file <filename>/etc/group</filename>, adding jack
- to the first line (the group <groupname>wheel</groupname>). But
- first you need to practice &man.vi.1;, the text editor—or
- use the simpler text editor, &man.ee.1;, installed on recent
- version of FreeBSD.</para>
+ able to <command>su</command> to <username>root</username>, you
+ can log in as <username>root</username> and edit the file
+ <filename>/etc/group</filename>, adding
+ <username>jack</username> to the first line (the group
+ <groupname>wheel</groupname>). But first you need to practice
+ &man.vi.1;, the text editor—or use the simpler text
+ editor, &man.ee.1;, installed on recent version of
+ &os;.</para>
<para>To delete a user, use the <command>rmuser</command>
command.</para>
@@ -153,7 +157,7 @@
<para>Logged in as an ordinary user, look around and try out some
commands that will access the sources of help and information
- within FreeBSD.</para>
+ within &os;.</para>
<para>Here are some commands and what they do:</para>
@@ -208,8 +212,9 @@
<listitem>
<para>Lists hidden <quote>dot</quote> files with the others.
- If you are root, the <quote>dot</quote> files show up
- without the <option>-a</option> switch.</para>
+ If you are <username>root</username>, the
+ <quote>dot</quote> files show up without the
+ <option>-a</option> switch.</para>
</listitem>
</varlistentry>
@@ -221,7 +226,7 @@
<parameter>..</parameter></command> backs up one level;
note the space after <command>cd</command>. <command>cd
<parameter>/usr/local</parameter></command> goes there.
- <command>cd <parameter>~</parameter></command> goes to the
+ <command>cd</command> (without any options) goes to the
home directory of the person logged in—e.g.,
<filename>/usr/home/jack</filename>. Try <command>cd
<parameter>/cdrom</parameter></command>, and then
@@ -298,7 +303,7 @@
<listitem>
<para>The manual page for <replaceable>text</replaceable>. The
- major source of documentation for Un*x systems.
+ major source of documentation for &unix; systems.
<command>man <parameter>ls</parameter></command> will tell
you all the ways to use the <command>ls</command> command.
Press <keycap>Enter</keycap> to move through text,
@@ -371,10 +376,11 @@
<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
+ going to be left on over the weekend (and running &os;), you
might want to run the commands for daily, weekly, and monthly
- maintenance now and then. Run them as root and give each one
- time to finish before you start the next one, for now.</para>
+ maintenance now and then. Run them as <username>root</username>
+ and give each one time to finish before you start the next one,
+ for now.</para>
<informalexample>
<screen>&prompt.root; <userinput>periodic daily</userinput>
@@ -399,15 +405,15 @@
<para>Running such commands is part of system
administration—and as a single user of a Unix system,
you are your own system administrator. Virtually everything you
- need to be root 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)—the second edition with the red cover; or
- Æleen Frisch's <citetitle>Essential System
+ need to be <username>root</username> 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)—the second edition with the red cover;
+ or Æleen Frisch's <citetitle>Essential System
Administration</citetitle> (O'Reilly & Associates, 1993,
ISBN 0-937175-80-3). I used Nemeth.</para>
</sect1>
@@ -417,14 +423,13 @@
<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 root 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
+ <username>root</username> 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 that installed; otherwise you can get it by FTP to
- <hostid>ftp.cdrom.com</hostid> in the directory
- FreeBSD/FreeBSD-current/src/contrib/nvi/docs/tutorial.</para>
+ have the system sources installed.</para>
<para>Before you edit a file, you should probably back it up.
Suppose you want to edit <filename>/etc/rc.conf</filename>. You
@@ -598,50 +603,50 @@
<command>:w</command>) when you need to.</para>
<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</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>
+ <filename>/etc</filename>, <command>su</command> to
+ <username>root</username>, use <command>vi</command> to edit the
+ file <filename>/etc/group</filename>, and add a user to
+ <groupname>wheel</groupname> so the user has
+ <username>root</username> 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>
</sect1>
<sect1>
- <title>Printing Files from DOS</title>
+ <title>Printing Files from Windows</title>
<para>At this point you probably do not have the printer working,
so here is a way to create a file from a manual page, move it to a
- floppy, and then print it from DOS. Suppose you want to read
+ floppy, and then print it from Windows. Suppose you want to read
carefully about changing permissions on files (pretty
important). You can use <command>man chmod</command> to read
about it. The command</para>
<informalexample>
- <screen>&prompt.user; <userinput>man chmod | col -b > chmod.txt</></screen>
+ <screen>&prompt.user; <userinput>man chmod | col -b > chmod.txt</userinput></screen>
</informalexample>
<para>will remove formatting codes and send the manual 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</command> to root, and type</para>
+ drive <devicename>a</devicename>, <command>su</command> to
+ <username>root</username>, and type</para>
<informalexample>
- <screen>&prompt.root; <userinput>/sbin/mount -t msdos /dev/fd0 /mnt</></screen>
+ <screen>&prompt.root; <userinput>/sbin/mount -t msdos /dev/fd0 /mnt</userinput></screen>
</informalexample>
<para>to mount the floppy drive on
<filename>/mnt</filename>.</para>
- <para>Now (you no longer need to be root, and you can type
- <command>exit</command> to get back to being user jack) you can
- go to the directory where you created
+ <para>Now you can go to the directory where you created
<filename>chmod.txt</filename> and copy the file to the floppy
with:</para>
<informalexample>
- <screen>&prompt.user; <userinput>cp chmod.txt /mnt</></screen>
+ <screen>&prompt.root; <userinput>cp chmod.txt /mnt</userinput></screen>
</informalexample>
<para>and use <command>ls /mnt</command> to get a directory
@@ -652,47 +657,48 @@
<filename>/sbin/dmesg</filename> by typing</para>
<informalexample>
- <screen>&prompt.user; <userinput>/sbin/dmesg > dmesg.txt</></screen>
+ <screen>&prompt.user; <userinput>/sbin/dmesg > dmesg.txt</userinput></screen>
</informalexample>
<para>and copying <filename>dmesg.txt</filename> to the floppy.
<command>/sbin/dmesg</command> is the boot log record, and it is
- useful to understand it because it shows what FreeBSD found when
+ useful to understand it because it shows what &os; found when
it booted up. If you ask questions on the &a.questions; or on a USENET
- group—like <quote>FreeBSD is not finding my tape drive,
+ group—like <quote>&os; is not finding my tape drive,
what do I do?</quote>—people will want to know what
<command>dmesg</command> has to say.</para>
- <para>You can now dismount the floppy drive (as root) to get the
- disk out with</para>
+ <para>You can now unmount the floppy drive (as
+ <username>root</username>) to get the disk out with</para>
<informalexample>
- <screen>&prompt.root; <userinput>/sbin/umount /mnt</></screen>
+ <screen>&prompt.root; <userinput>/sbin/umount /mnt</userinput></screen>
</informalexample>
- <para>and reboot to go to DOS. Copy these files to a DOS
- directory, call them up with DOS EDIT, Windows Notepad or
- 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! manual pages come out best if printed
- 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>
+ <para>and reboot to go to Windows. Copy these files to a Windows
+ directory, call them up with Notepad or Wordpad, or a word
+ processor, make a minor change so the file has to be saved, and
+ print as you normally would from Windows. Hope it works!
+ Manual pages come out best if printed with the DOS
+ <command>print</command> command. (Copying files from &os;
+ to a mounted DOS partition is in some cases still a little
+ risky.)</para>
- <para>Getting the printer printing from FreeBSD involves creating
+ <para>Getting the printer printing from &os; involves creating
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</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</filename> by typing: <command>mkdir
+ <devicename>lpt0</devicename> (what Windows calls
+ <devicename>LPT1</devicename>), you may only need to go to
+ <filename>/var/spool/output</filename> and (as
+ <username>root</username>) create the directory
+ <filename>lpd</filename> by typing: <command>mkdir
lpd</command>, if it does not already exist. Then the printer
should respond if it is turned on when the system is booted, and
<command>lp</command> or <command>lpr</command> 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="../../books/handbook/index.html">FreeBSD
+ URL="../../books/handbook/index.html">&os;
handbook.</ulink></para>
</sect1>
@@ -751,7 +757,8 @@
<term><command>passwd</command></term>
<listitem>
- <para>to change user's password (or root's password)</para>
+ <para>to change user's password (or
+ <username>root</username> password)</para>
</listitem>
</varlistentry>
@@ -769,7 +776,7 @@
with</para>
<informalexample>
- <screen>&prompt.user; <userinput>find /usr -name "<replaceable>filename</>"</></screen>
+ <screen>&prompt.user; <userinput>find /usr -name "<replaceable>filename</>"</userinput></screen>
</informalexample>
<para>You can use <literal>*</literal> as a wildcard in
@@ -780,12 +787,11 @@
file(s) on all mounted filesystems, including the CDROM and the
DOS partition.</para>
- <para>An excellent book that explains Unix commands and utilities
+ <para>An excellent book that explains &unix; commands and utilities
is Abrahams & Larson, <citetitle>Unix for the
Impatient</citetitle> (2nd ed., Addison-Wesley, 1996).
- There is also a lot of Unix information on the Internet. Try the
- <ulink URL="http://www.geek-girl.com/unix.html">Unix Reference
- Desk</ulink>.</para>
+ There is also a lot of &unix; information on the Internet. Try
+ searching with your favourite search engine.</para>
</sect1>
<sect1>
@@ -793,9 +799,9 @@
<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
+ a great deal of information in the &os; handbook (which is
probably on your hard drive) and <ulink
- URL="../../../../index.html">FreeBSD's web site</ulink>. A
+ URL="http://www.freebsd.org">&os;'s web site</ulink>. 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
@@ -803,117 +809,19 @@
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>,
- <filename>cdrom/packages/index.txt</filename>, and
- <filename>cdrom/ports/index</filename>, with fuller descriptions
+ <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
- <literal>*</literal>s represent subdirectories of kinds of
+ <literal>*</literal> represents subdirectories of kinds of
programs and program names respectively.</para>
- <para>If you find the handbook too sophisticated (what with
- <command>lndir</command> and all) on installing ports from the
- CDROM, here is what usually works:</para>
-
- <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>
-
- <informalexample>
- <screen>&prompt.root; <userinput>cp -R /cdrom/ports/comm/kermit /usr/local</></screen>
- </informalexample>
+ <para>If you already have a working internet connection, you can
+ also add a package with <command>pkg_add -r
+ <replaceable>packagename</replaceable></command>. This will
+ fetch the desired package from an FTP server and install
+ it.</para>
- <para>This should result in a
- <filename>/usr/local/kermit</filename> subdirectory that has all
- the files that the <command>kermit</command> subdirectory on the
- CDROM has.</para>
-
- <para>Next, create the directory
- <filename>/usr/ports/distfiles</filename> if it does not already
- exist using <command>mkdir</command>. Now check
- <filename>/cdrom/ports/distfiles</filename> for a file with a
- name that indicates it is 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</command>, there is no distfile.</para>
-
- <para>Then <command>cd</command> to the subdirectory of
- <filename>/usr/local/kermit</filename> that has the file
- <filename>Makefile</filename>. Type</para>
-
- <informalexample>
- <screen>&prompt.root; <userinput>make all install</></screen>
- </informalexample>
-
- <para>During this process the port will FTP to get any compressed
- files it needs that it did not find on the CDROM or in
- <filename>/usr/ports/distfiles</filename>. If you do not have
- your network running yet and there was no file for the port in
- <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</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 will 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</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
- installation stops with a message <errorname>can't find
- unzip</errorname> or whatever, you might need to install the
- package or port for unzip before you continue.</para>
-
- <para>Once it is installed type <command>rehash</command> to make
- FreeBSD reread the files in the path so it knows what is there.
- (If you 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, except the current directory is not (by
- default) in the path for security reasons; if the command you
- want is in the directory you are in, you need to type
- <filename>./</filename> before the command to make it work; no
- space after the slash.)</para>
-
- <para>You might want to get the most recent version of Netscape
- from their <ulink URL="ftp://ftp.netscape.com/">FTP site</ulink>.
- (Netscape requires the X Window System.) There is now a FreeBSD
- version, so look around carefully. Just use <command>gunzip
- <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</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
- <command>csh</command> start-up file:</para>
-
- <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</filename>
- and the directory <filename>nls</filename> are in
- <filename>/usr/X11R6/lib/X11</filename>; if they are not, find
- them and put them there.</para>
-
- <para>If you originally got Netscape as a port using the CDROM (or
- FTP), do not replace <filename>/usr/local/bin/netscape</filename>
- with the new netscape binary; this is just a shell script that
- sets up the environment variables for you. Instead rename the
- new binary to <filename>netscape.bin</filename> and replace the
- old binary, which is
- <filename>/usr/local/netscape/netscape</filename>.</para>
</sect1>
<sect1>
@@ -927,89 +835,88 @@
files: a series of commands to be run without your
intervention.</para>
- <para>Two shells come installed with FreeBSD:
+ <para>Two shells come installed with &os;:
<command>csh</command> and <command>sh</command>.
<command>csh</command> is good for command-line work, but
scripts should be written with <command>sh</command> (or
<command>bash</command>). You can find out what shell you have
by typing <command>echo $SHELL</command>.</para>
- <para>The <command>csh</command> shell is okay, but
- <command>tcsh</command> does everything <command>csh</command>
- does and more. It allows you to recall commands with the arrow
+ <para>The <command>csh</command> shell is okay, but you might want
+ to use <command>bash</command>, as many users might find it more
+ comfortable. 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
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
+ prompt with <command>bash</command>. It makes life a lot
easier.</para>
- <para>Here are the three steps for installing a new shell:</para>
+ <para>Here are the two steps for installing a new shell:</para>
<procedure>
<step>
<para>Install the shell as a port or a package, just as you
would any other port or package. Use
- <command>rehash</command> and <command>which tcsh</command>
- (assuming you are installing <command>tcsh</command>) to make
+ <command>rehash</command> and <command>which bash</command>
+ (assuming you are installing <command>bash</command>) to make
sure it got installed.</para>
</step>
<step>
- <para>As root, edit <filename>/etc/shells</filename>, adding a
- line in the file for the new shell, in this case
- <filename>/usr/local/bin/tcsh</filename>, and save the file.
- (Some ports may do this for you.)</para>
- </step>
-
- <step>
<para>Use the <command>chsh</command> command to change your
- shell to <command>tcsh</command> permanently, or type
- <command>tcsh</command> at the prompt to change your shell
+ shell to <command>bash</command> permanently, or type
+ <command>bash</command> at the prompt to change your shell
without logging in again.</para>
</step>
</procedure>
<note>
- <para>It can be dangerous to change root'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
- single user mode. The solution is to use <command>su
- -m</command> to become root, which will give you the
- <command>tcsh</command> 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:</para>
- <programlisting>alias su su -m</programlisting>
+ <para>It can be dangerous to change <username>root</username>'s
+ shell to something other than <command>sh</command> or
+ <command>csh</command> on early versions of &os; 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
+ <username>root</username>, which will give you the
+ <command>bash</command> as <username>root</username>, because
+ the shell is part of the environment. You can make this
+ permanent by adding it to your <filename>.profile</filename>
+ file 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
- <filename>.tcshrc</filename>.</para>
+ <para>When <command>bash</command> starts up, it reads a variety
+ of configuration files like <filename>/etc/profile</filename>,
+ <filename>.bash_profile</filename>,
+ <filename>.bash_login</filename> …, depending on if it is
+ invoked as a login shell or not. A safe way to make sure that
+ <command>bash</command> executes the commands you want whenever
+ it starts up is to put them into your
+ <filename>.profile</filename> and create a symbolic link from
+ <filename>.bashrc</filename> to <filename>.profile</filename>
+ like this:</para>
+
+ <informalexample>
+ <screen>&prompt.user; <userinput>ln -s .profile .bashrc</userinput></screen>
+ </informalexample>
- <para>Now that you have installed <command>tcsh</command>, you can
+ <para>Now that you have installed <command>bash</command>, you can
adjust your prompt. You can find the details in the manual page
- for <command>tcsh</command>, but here is a line to put in your
- <filename>.tcshrc</filename> that will tell you how many
+ for <command>bash</command>, but here is a line to put in your
+ <filename>.profile</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>></literal> if you are an
- ordinary user and a <literal>#</literal> if you are root, 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
- <command>source .tcshrc</command>.</para>
+ are in. It also produces a <literal>$</literal> if you are
+ an ordinary user and a <literal>#</literal> if you are
+ <username>root</username>:</para>
+
+ <programlisting>PS1='\! \A \w \$ '; export PS1</programlisting>
+
+ <para>Just append this line to <filename>.profile</filename> Do
+ not forget the spaces and quotes. You can get the
+ <filename>.profile</filename> reread by typing <command>source
+ .profile</command>.</para>
<para>You can get a listing of other environmental variables that
have been set by typing <command>env</command> at the prompt.
@@ -1017,21 +924,22 @@
terminal type, among possibly many others. A useful command if
you log in from a remote location and can not run a program
because the terminal is not capable is <command>setenv TERM
- vt100</command>.</para>
+ vt100</command> (for <command>csh</command>) or <command>export
+ TERM=vt100</command> (for <command>bash</command>).</para>
</sect1>
<sect1>
<title>Other</title>
- <para>As root, you can dismount the CDROM with
+ <para>As <username>root</username>, 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
+ <devicename>cd0a</devicename> is the device name for your CDROM
+ drive. The most recent versions of &os; let you mount the
CDROM with just <command>/sbin/mount /cdrom</command>.</para>
- <para>Using the live filesystem—the second of FreeBSD's
+ <para>Using the live filesystem—the second of &os;'s
CDROM disks—is useful if you have got limited space. What
is on the live filesystem varies from release to release. You
might try playing games from the CDROM. This involves using
--- newusers.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307232142.h6NLgH7s035091>