<title>For People New to Both FreeBSD and &unix;</title>

    <title>For People New to Both &os; and &unix;</title>

      <para>Congratulations on installing FreeBSD! This introduction

      <para>Congratulations on installing &os;! This introduction

	is for people new to both FreeBSD <emphasis>and</emphasis>

	is for people new to both &os; <emphasis>and</emphasis>

	Un*x—so it starts with basics.  It assumes you are using

	&unix;—so it starts with basics.  It assumes you are

	version 2.0.5 or later of FreeBSD as distributed by BSDi

	using version 2.0.5 or later of &os; as distributed from

	or FreeBSD.org, your system (for now) has a single user

	FreeBSD.org, your system (for now) has a single user

    <para>Log in (when you see <prompt >login:</prompt>) as a user you

    <para>Log in (when you see <prompt>login:</prompt>) as a user you

      created during installation or as <firstterm>root</firstterm>.

      created during installation or as <username>root</username>.

      (Your FreeBSD installation will already have an account for

      (Your &os; installation will already have an account for

      root; root can go anywhere and do anything, including deleting

      <username>root</username>; <username>root</username> can go

      essential files, so be careful!) The symbols &prompt.user; and

      anywhere and do anything, including deleting essential files, so

      &prompt.root; in the following stand for the prompt (yours may

      be careful!) The symbols &prompt.user; and &prompt.root; in the

      be different), with &prompt.user; indicating an ordinary user

      following stand for the prompt (yours may be different), with

      and &prompt.root; indicating root.</para>

      &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)

    <para>as often as necessary.  Yes, press <keysym>enter</keysym>

    <para>as often as necessary.  Yes, press <keycap>Enter</keycap>

      <command>/sbin/reboot</command> in recent releases of FreeBSD

      <command>/sbin/reboot</command> in recent releases of &os;

    <para>If you did not create any users when you installed the system

    <para>If you did not create any users when you installed the

      and are thus logged in as root, you should probably create a

      system and are thus logged in as <username>root</username>, you

      user now with</para>

      should probably create a user now with</para>

    <para>The first time you use adduser, it might ask for some

    <para>The first time you use <command>adduser</command>, it might

      defaults to save.  You might want to make the default shell

      ask for some defaults to save.  You might want to make the

      &man.csh.1; instead of &man.sh.1;, if it suggests

      default shell &man.csh.1; instead of &man.sh.1;, if it suggests

      full name <emphasis>Jack Benimble</emphasis>.  Give jack a

      full name <emphasis>Jack Benimble</emphasis>.  Give

      password if security (even kids around who might pound on the

      <username>jack</username> a password if security (even kids

      keyboard) is an issue.  When it asks you if you want to invite

      around who might pound on the keyboard) is an issue.  When it

      jack into other groups, type <groupname>wheel</groupname></para>

      asks you if you want to invite <username>jack</username> into

      other groups, type <groupname>wheel</groupname>:</para>

      <username>jack</username> and use the &man.su.1;

      <username>jack</username> and use the &man.su.1; command to

      command to become root.  Then you will not get scolded any more for

      become <username>root</username>.  Then you will not get scolded

      logging in as root.</para>

      any more for logging in as <username>root</username>.</para>

      a second new user (jill?) so that when you edit jack's login

      a second new user (<username>jill</username>?) so that when you

      files, you will have a hot spare in case something goes

      edit <username>jack</username>'s login files, you will have a

      wrong.</para>

      hot spare in case something goes wrong.</para>

      risk&mdash;of root.</para>

      risk&mdash;of <username>root</username>.</para>

      able to <command>su</command> to root, you can log in as root

      able to <command>su</command> to <username>root</username>, you

      and edit the file <filename>/etc/group</filename>, adding jack

      can log in as <username>root</username> and edit the file

      to the first line (the group <groupname>wheel</groupname>).  But

      <filename>/etc/group</filename>, adding

      first you need to practice &man.vi.1;, the text editor—or

      <username>jack</username> to the first line (the group

      use the simpler text editor, &man.ee.1;, installed on recent

      <groupname>wheel</groupname>).  But first you need to practice

      version of FreeBSD.</para>

      &man.vi.1;, the text editor—or use the simpler text

      editor, &man.ee.1;, installed on recent version of

      &os;.</para>

      within FreeBSD.</para>

      within &os;.</para>

	    If you are root, the <quote>dot</quote> files show up

	    If you are <username>root</username>, the

	    without the <option>-a</option> switch.</para>

	    <quote>dot</quote> files show up without the

	    <option>-a</option> switch.</para>

	    <command>cd <parameter>~</parameter></command> goes to the

	    <command>cd</command> (without any options) goes to the

	    major source of documentation for Un*x systems.

	    major source of documentation for &unix; systems.

      going to be left on over the weekend (and running FreeBSD), you

      going to be left on over the weekend (and running &os;), you

      maintenance now and then.  Run them as root and give each one

      maintenance now and then.  Run them as <username>root</username>

      time to finish before you start the next one, for now.</para>

      and give each one time to finish before you start the next one,

      for now.</para>

      need to be root to do is system administration.  Such

      need to be <username>root</username> to do is system

      responsibilities are not covered very well even in those big fat

      administration.  Such responsibilities are not covered very well

      books on Unix, which seem to devote a lot of space to pulling

      even in those big fat books on Unix, which seem to devote a lot

      down menus in windows managers.  You might want to get one of

      of space to pulling down menus in windows managers.  You might

      the two leading books on systems administration, either Evi

      want to get one of the two leading books on systems

      Nemeth et.al.'s <citetitle>UNIX System Administration

      administration, either Evi Nemeth et.al.'s <citetitle>UNIX

      Handbook</citetitle> (Prentice-Hall, 1995, ISBN

      System Administration Handbook</citetitle> (Prentice-Hall, 1995,

      0-13-15051-7)—the second edition with the red cover; or

      ISBN 0-13-15051-7)—the second edition with the red cover;

      &AElig;leen Frisch's <citetitle>Essential System

      or &AElig;leen Frisch's <citetitle>Essential System

      you will need to <command>su</command> to root to be able to

      you will need to <command>su</command> to

      change them.  You can use the easy <command>ee</command>, but in

      <username>root</username> to be able to change them.  You can

      the long run the text editor <command>vi</command> is worth

      use the easy <command>ee</command>, but in the long run the text

      learning.  There is an excellent tutorial on vi in

      editor <command>vi</command> is worth learning.  There is an

      excellent tutorial on vi in

      have that installed; otherwise you can get it by FTP to

      have the system sources installed.</para>

      <hostid>ftp.cdrom.com</hostid> in the directory

      FreeBSD/FreeBSD-current/src/contrib/nvi/docs/tutorial.</para>

      <filename>/etc</filename>, <command>su</command> to root, use

      <filename>/etc</filename>, <command>su</command> to

      <command>vi</command> to edit the file

      <username>root</username>, use <command>vi</command> to edit the

      <filename>/etc/group</filename>, and add a user to wheel so the

      file <filename>/etc/group</filename>, and add a user to

      user has root privileges.  Just add a comma and the user's login

      <groupname>wheel</groupname> so the user has

      name to the end of the first line in the file, press

      <username>root</username> privileges.  Just add a comma and the

      <keycap>Esc</keycap>, and use <command>:wq</command> to write

      user's login name to the end of the first line in the file,

      the file to disk and quit.  Instantly effective.  (You did not

      press <keycap>Esc</keycap>, and use <command>:wq</command> to

      put a space after the comma, did you?)</para>

      write the file to disk and quit.  Instantly effective.  (You did

      not put a space after the comma, did you?)</para>

    <title>Printing Files from DOS</title>

    <title>Printing Files from Windows</title>

      floppy, and then print it from DOS.  Suppose you want to read

      floppy, and then print it from Windows.  Suppose you want to read

      <screen>&prompt.user; <userinput>man chmod | col -b &gt; chmod.txt</></screen>

      <screen>&prompt.user; <userinput>man chmod | col -b &gt; chmod.txt</userinput></screen>

      drive a, <command>su</command> to root, and type</para>

      drive <devicename>a</devicename>, <command>su</command> to

      <username>root</username>, and type</para>

      <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>

    <para>Now (you no longer need to be root, and you can type

    <para>Now you can go to the directory where you created

      <command>exit</command> to get back to being user jack) you can

      go to the directory where you created

      <screen>&prompt.user; <userinput>cp chmod.txt /mnt</></screen>

      <screen>&prompt.root; <userinput>cp chmod.txt /mnt</userinput></screen>

      <screen>&prompt.user; <userinput>/sbin/dmesg &gt; dmesg.txt</></screen>

      <screen>&prompt.user; <userinput>/sbin/dmesg &gt; dmesg.txt</userinput></screen>

      useful to understand it because it shows what FreeBSD found when

      useful to understand it because it shows what &os; found when

      group&mdash;like <quote>FreeBSD is not finding my tape drive,

      group&mdash;like <quote>&os; is not finding my tape drive,

    <para>You can now dismount the floppy drive (as root) to get the

    <para>You can now unmount the floppy drive (as

      disk out with</para>

      <username>root</username>) to get the disk out with</para>

      <screen>&prompt.root; <userinput>/sbin/umount /mnt</></screen>

      <screen>&prompt.root; <userinput>/sbin/umount /mnt</userinput></screen>

    <para>and reboot to go to DOS.  Copy these files to a DOS

    <para>and reboot to go to Windows.  Copy these files to a Windows

      directory, call them up with DOS EDIT, Windows Notepad or

      directory, call them up with Notepad or Wordpad, or a word

      Wordpad, or a word processor, make a minor change so the file

      processor, make a minor change so the file has to be saved, and

      has to be saved, and print as you normally would from DOS or

      print as you normally would from Windows.  Hope it works!

      Windows.  Hope it works!  manual pages come out best if printed

      Manual pages come out best if printed with the DOS

      with the DOS <command>print</command> command.  (Copying files

      <command>print</command> command.  (Copying files from &os;

      from FreeBSD to a mounted DOS partition is in some cases still a

      to a mounted DOS partition is in some cases still a little

      little risky.)</para>

      risky.)</para>

    <para>Getting the printer printing from FreeBSD involves creating

    <para>Getting the printer printing from &os; involves creating

      <hardware>lpt0</hardware> (what DOS calls

      <devicename>lpt0</devicename> (what Windows calls

      <hardware>LPT1</hardware>), you may only need to go to

      <devicename>LPT1</devicename>), you may only need to go to

      <filename>/var/spool/output</filename> and (as root) create the

      <filename>/var/spool/output</filename> and (as

      directory <filename>lpd</filename> by typing: <command>mkdir

      <username>root</username>) create the directory

      <filename>lpd</filename> by typing: <command>mkdir

      URL="../../books/handbook/index.html">FreeBSD

      URL="../../books/handbook/index.html">&os;

	  <para>to change user's password (or root's password)</para>

	  <para>to change user's password (or

	    <username>root</username> password)</para>

      <screen>&prompt.user; <userinput>find /usr -name "<replaceable>filename</>"</></screen>

      <screen>&prompt.user; <userinput>find /usr -name "<replaceable>filename</>"</userinput></screen>

    <para>An excellent book that explains Unix commands and utilities

    <para>An excellent book that explains &unix; commands and utilities

      There is also a lot of Unix information on the Internet.  Try the

      There is also a lot of &unix; information on the Internet.  Try

      <ulink URL="http://www.geek-girl.com/unix.html">Unix Reference

      searching with your favourite search engine.</para>

	Desk</ulink>.</para>

      a great deal of information in the FreeBSD handbook (which is

      a great deal of information in the &os; handbook (which is

      URL="../../../../index.html">FreeBSD's web site</ulink>.  A

      URL="http://www.freebsd.org">&os;'s web site</ulink>.  A

      <filename>cdrom/packages/index</filename>,

      <filename>/cdrom/packages/index</filename>,

      <filename>cdrom/packages/index.txt</filename>, and

      <filename>/cdrom/packages/index.txt</filename>, and

      <filename>cdrom/ports/index</filename>, with fuller descriptions

      <filename>/cdrom/ports/index</filename>, with fuller descriptions

      <literal>*</literal>s represent subdirectories of kinds of

      <literal>*</literal> represents subdirectories of kinds of

    <para>If you find the handbook too sophisticated (what with

    <para>If you already have a working internet connection, you can

      <command>lndir</command> and all) on installing ports from the

      also add a package with <command>pkg_add -r

      CDROM, here is what usually works:</para>

      <replaceable>packagename</replaceable></command>. This will

      fetch the desired package from an FTP server and install

    <para>Find the port you want, say <command>kermit</command>.

      it.</para>

      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>Two shells come installed with FreeBSD:

    <para>Two shells come installed with &os;:

    <para>The <command>csh</command> shell is okay, but

    <para>The <command>csh</command> shell is okay, but you might want

      <command>tcsh</command> does everything <command>csh</command>

      to use <command>bash</command>, as many users might find it more

      does and more.  It allows you to recall commands with the arrow

      comfortable.  It allows you to recall commands with the arrow

      prompt with <command>tcsh</command>.  It makes life a lot

      prompt with <command>bash</command>.  It makes life a lot

    <para>Here are the three steps for installing a new shell:</para>

    <para>Here are the two steps for installing a new shell:</para>

	  <command>rehash</command> and <command>which tcsh</command>

	  <command>rehash</command> and <command>which bash</command>

	  (assuming you are installing <command>tcsh</command>) to make

	  (assuming you are installing <command>bash</command>) to make

	  shell to <command>tcsh</command> permanently, or type

	  shell to <command>bash</command> permanently, or type

	  <command>tcsh</command> at the prompt to change your shell

	  <command>bash</command> at the prompt to change your shell

      <para>It can be dangerous to change root's shell to something

      <para>It can be dangerous to change <username>root</username>'s

	other than <command>sh</command> or <command>csh</command> on

	shell to something other than <command>sh</command> or

	early versions of FreeBSD and many other versions of Unix; you

	<command>csh</command> on early versions of &os; and many

	may not have a working shell when the system puts you into

	other versions of &unix;; you may not have a working shell when

	single user mode.  The solution is to use <command>su

	the system puts you into single user mode.  The solution is to

	-m</command> to become root, which will give you the

	use <command>su -m</command> to become

	<command>tcsh</command> as root, because the shell is part of

	<username>root</username>, which will give you the

	the environment.  You can make this permanent by adding it to

	<command>bash</command> as <username>root</username>, because

	your <filename>.tcshrc</filename> file as an alias with:</para>

	the shell is part of the environment.  You can make this

	<programlisting>alias su su -m</programlisting>

	permanent by adding it to your <filename>.profile</filename>

	file as an alias with:</para>

      <programlisting>alias su='su -m'</programlisting>

    <para>When <command>tcsh</command> starts up, it will read the

    <para>When <command>bash</command> starts up, it reads a variety

      <filename>/etc/csh.cshrc</filename> and

      of configuration files like <filename>/etc/profile</filename>,

      <filename>/etc/csh.login</filename> files, as does

      <filename>.bash_profile</filename>,

      <command>csh</command>.  It will also read the

      <filename>.bash_login</filename> &hellip;, depending on if it is

      <filename>.login</filename> file in your home directory and the

      invoked as a login shell or not.  A safe way to make sure that

      <filename>.cshrc</filename> file as well, unless you provide a

      <command>bash</command> executes the commands you want whenever

      <filename>.tcshrc</filename> file.  This you can do by simply

      it starts up is to put them into your

      copying <filename>.cshrc</filename> to

      <filename>.profile</filename> and create a symbolic link from

      <filename>.tcshrc</filename>.</para>

      <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

      for <command>tcsh</command>, but here is a line to put in your

      for <command>bash</command>, but here is a line to put in your

      <filename>.tcshrc</filename> that will tell you how many

      <filename>.profile</filename> that will tell you how many

      are in.  It also produces a <literal>></literal> if you are an

      are in.  It also produces a <literal>$</literal> if you are

      ordinary user and a <literal>#</literal> if you are root, but

      an ordinary user and a <literal>#</literal> if you are

      tsch will do that in any case:</para>

      <username>root</username>:</para>

    <para>set prompt = "%h %t %~ %# "</para>

    <programlisting>PS1='\! \A \w \$ '; export PS1</programlisting>

    <para>This should go in the same place as the existing set prompt

    <para>Just append this line to <filename>.profile</filename>  Do

      line if there is one, or under "if($?prompt) then" if not.

      not forget the spaces and quotes.  You can get the

      Comment out the old line; you can always switch back to it if

      <filename>.profile</filename> reread by typing <command>source

      you prefer it.  Do not forget the spaces and quotes.  You can get

      .profile</command>.</para>

      the <filename>.tcshrc</filename> reread by typing

      <command>source .tcshrc</command>.</para>

      vt100</command>.</para>

      vt100</command> (for <command>csh</command>) or <command>export

      TERM=vt100</command> (for <command>bash</command>).</para>

    <para>As root, you can dismount the CDROM with

    <para>As <username>root</username>, you can unmount the CDROM with

      <hardware>cd0a</hardware> is the device name for your CDROM

      <devicename>cd0a</devicename> is the device name for your CDROM

      drive.  The most recent versions of FreeBSD let you mount the

      drive.  The most recent versions of &os; let you mount the

    <para>Using the live filesystem&mdash;the second of FreeBSD's

    <para>Using the live filesystem&mdash;the second of &os;'s