Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
4. Neither the name of The NetBSD Foundation nor the names of its
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below. .(enum Configuring
p If you or the installation software haven't done any configuration of
a /etc/rc.conf c ( sysinst usually will), the system will drop you into single user mode on first reboot with the message
p .Dl /etc/rc.conf is not configured. Multiuser boot aborted.
p and with the root file system
q Pa / mounted read-only. When the system asks you to choose a shell, simply press .Key RETURN to get to a
a /bin/sh prompt. If you are asked for a terminal type, respond with . . c \*[termtype] for a local console, or whatever is appropriate for your serial console. .\} c \*[termtype] (or whatever is appropriate for your terminal type) .\} the correct terminal type as discussed in the .Sx Once you've booted the diskimage section. .\} c \*[termtype] for a local console, or whatever is appropriate for your serial console (some systems display garbage with a c \*[termtype] terminal type, you may need to use c sun-ss5 ) .\} c \*[termtype] (or whatever is appropriate for your terminal type) .\} .\} .\} .\} and press .Key RETURN . You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: .Dl # Ic "stty erase '^h'" .Dl # Ic "stty erase '^?'" At this point, you need to configure at least one file in the
a /etc directory. You will need to mount your root file system read/write with: .Dl # Ic "/sbin/mount -u -w /" Change to the
a /etc directory and take a look at the
a /etc/rc.conf file. Modify it to your tastes, making sure that you set .Li rc_configured=YES so that your changes will be enabled and a multi-user boot can proceed. Default values for the various programs can be found in
a /etc/defaults/rc.conf , where some in-line documentation may be found. More complete documentation can be found in .Xr rc.conf 5 .
p If your
a /usr directory is on a separate partition and you do not know how to use c ed , you will have to mount your
a /usr partition to gain access to c ex or c vi . Do the following:
p .Dl # Ic "mount /usr" .Dl # Ic "export TERM=\*[termtype]"
p If you have
a /var on a separate partition, you need to repeat that step for it. After that, you can edit
a /etc/rc.conf with .Xr vi 1 . When you have finished, type c exit at the prompt to leave the single-user shell and continue with the multi-user boot.
p Other values that need to be set in
a /etc/rc.conf for a networked environment are .Ar hostname and possibly .Ar defaultroute , furthermore add an .Ar ifconfig_int for your .Aq int network interface, where your on-board, NuBus or PDS interface may be .Li ae0 , .Li mc0 or .Li sn0 . For example: .\} where your on-board interfaces may be one of .Li mc0 , .Li bm0 , .Li de0 or .Li gm0 . For example: .\} .\}
p . . .Dl ifconfig_\*[IFname]="inet 123.45.67.89 netmask 255.255.255.0"
p or, if you have .Ar myname.my.dom in
p .Dl ifconfig_\*[IFname]="inet myname.my.dom netmask 255.255.255.0"
p To enable proper hostname resolution, you will also want to add an
a /etc/resolv.conf file or (if you are feeling a little more adventurous) run .Xr named 8 . See .Xr resolv.conf 5 or .Xr named 8 for more information.
p Other files in
a /etc that may require modification or setting up include
a /etc/mailer.conf and
a /etc/nsswitch.conf . .\}
a /etc/mailer.conf ,
a /etc/nsswitch.conf , and
a /etc/wscons.conf . .\}
p For Digital DNARD machines you will need to edit
a /etc/ttys and change the console terminal type from vt100 to pc3. .\} t Select the proper terminal devices
p You will have to edit the
a /etc/ttys file. If you don't have a Milan, you must disable the
a ttyEx devices. For the Milan, you will have to disable the
a ttyex devices. This is easy, just change 'on' to 'off' on the corresponding lines. .\}
p For the .Xr savecore 8 facility to work with the a.out and elf kernel images supplied with \*M installations you will need to set .Li savecore_flags="-z -N /netbsd" .\} t Logging in
p After reboot, you can log in as .Li root at the login prompt. Unless you've set a password in c sysinst , there is no initial password. If you're using the machine in a networked environment, you should create an account for yourself (see below) and protect it and the .Dq root account with good passwords. By default, root login from the network is disabled (even via .Xr ssh 1 ) . One way to become root over the network is to log in as a different user that belongs to group .Dq wheel (see .Xr group 5 ) and use .Xr su 1 to become root.
p Unless you have connected an unusual terminal device as the console you can just press .Key RETURN when it prompts for .Li Terminal type? [...] . t Adding accounts
p Use the .Xr useradd 8 command to add accounts to your system; .Em do not edit
a /etc/passwd directly. See .Xr useradd 8 for more information on how to add a new user to the system. t The X Window System
p If you have installed the X Window System, look at the files in
a /usr/X11R6/lib/X11/doc for information. Also, you may want to read through the .Nx*M FAQ entry on X11.
.Lk http://www.netbsd.org/Ports/faq.html#x11 .\} Also, you may want to read through the .Nx*M X11R6 FAQ.
.Lk http://www.netbsd.org/Ports/macppc/x11.html .\} .\} \" ! !\n[next68k]
p You will need to set up a configuration file, see
a /usr/X11R6/lib/X11/XF86Config.eg for an example. The .Xr xf86config 1 utility can interactively create a first version of such a configuration file for you. .(tag [Color_X] t [Color_X] Some systems are capable of supporting a color X Server in either thousands or millions of colors. The \*M port does not support resolution switching at this time. If your system is capable of running the color X Server it can be installed at this point and the Booter options can be modified to match the resolution depth. .\} See .Lk http://www.xfree86.org/ and the XFree86 manual page for more information. .\}
p Don't forget to add
a /usr/X11R6/bin to your path in your shell's dot file so that you have access to the X binaries. t Installing third party packages
p If you wish to install any of the software freely available for l systems you are strongly advised to first check the .Nx package system. This automatically handles any changes necessary to make the software run on .Nx , retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
p .(bullet More information on the package system is at .Lk http://www.netbsd.org/Documentation/software/packages.html t A list of available packages suitable for browsing is at .Lk ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/README.html t Precompiled binaries can be found at .Lk ftp://ftp.netbsd.org/pub/NetBSD/packages , usually in the
a \*V/\*M/All subdir. You can install them with the following commands:
p d -unfilled c # PKG_PATH=ftp://ftp.netbsd.org/pub/NetBSD/packages/\*V/\*M/All c # export PKG_PATH c # pkg_add -v tcsh c # pkg_add -v apache c # pkg_add -v perl ... .Ed
p The above commands will install the tcsh shell, the Apache web server and the perl programming language as well as all the packages they depend on. t Package sources for compiling packages on your own can be obtained by retrieving the file .Lk ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz They are typically extracted into
a /usr/pkgsrc (though other locations work fine), with the commands:
p .Dl # Ic "mkdir /usr/pkgsrc" .Dl # Ic "( cd /usr/pkgsrc ; tar -zxpf - ) \*< pkgsrc.tar.gz"
p After extracting, then see the
a README file in the extraction directory (e.g.
a /usr/pkgsrc/README ) for more information. .bullet) t Misc .(bullet Edit
a /etc/mail/aliases to forward root mail to the right place. Don't forget to run .Xr newaliases 1 afterwards. t The
a /etc/mail/sendmail.cf file will almost definitely need to be adjusted; files aiding in this can be found in
a /usr/share/sendmail . See the .Li Tn README file there for more information. t Edit
a /etc/rc.local to run any local daemons you use. t Many of the
a /etc files are documented in section 5 of the manual; so just invoking
p .Dl # Ic man 5 Ar filename
p is likely to give you more information on these files. .bullet) .enum)