AFTERBOOT(8) NetBSD System Manager's Manual AFTERBOOT(8)
NAME
afterboot - things to check after the first complete boot
DESCRIPTION
Starting Out This document attempts to list items for the system administrator to check and set up after the installation and first complete boot of the system. The idea is to create a list of items that can be checked off so that you have a warm fuzzy feeling that something obvious has not been missed. A basic knowledge of UNIX is assumed. Complete instructions for correcting and fixing items is not provided. There are manual pages and other methodologies available for doing that. For example, to view the man page for the ls(1) command, type: man 1 ls Administrators will rapidly become more familiar with NetBSD if they get used to using the manual pages. Security alerts By the time that you have installed your system, it is quite likely that bugs in the release have been found. All significant and easily fixed problems will be reported at http://www.NetBSD.org/Security/. It is rec- ommended that you check this page regularly. Login Login as ``root''. You can do so on the console, or over the network using ssh(1). If you wish to allow root logins over the network (if you have enabled the ssh daemon), edit the /etc/ssh/sshd_config file and set PermitRootLogin to ``yes'' (see sshd(8)). The default is to not permit root logins over the network after fresh install in NetBSD. Note defaults on other operating systems might be different. Upon successful login on the console, you may see the message ``We recommend creating a non-root account...''. For security reasons, it is bad practice to login as root during regular use and maintenance of the system. Instead, administrators are encouraged to add a ``regular'' user, add said user to the ``wheel'' group, then use the su and sudo com- mands when root privileges are required. This process is described in more detail later. Root password Change the password for the root user. (Note that throughout the docu- mentation, the term ``superuser'' is a synonym for the root user.) Choose a password that has numbers, digits, and special characters (not space) as well as from the upper and lower case alphabet. Do not choose any word in any language. It is common for an intruder to use dictionary attacks. Type the command /usr/bin/passwd to change it. It is a good idea to always specify the full path name for both the passwd(1) and su(1) commands as this inhibits the possibility of files placed in your execution PATH for most shells. Furthermore, the supe- ruser's PATH should never contain the current directory (``.''). System date Check the system date with the date(1) command. If needed, change the date, and/or change the symbolic link of /etc/localtime to appropriate time zone in the /usr/share/zoneinfo directory. Examples: date 200205101820 Set the current date to May 10th, 2002 6:20pm. ln -fs /usr/share/zoneinfo/Europe/Helsinki /etc/localtime Set the time zone to Eastern Europe Summer Time. Console settings One of the first things you will likely need to do is to set up your key- board map (and maybe some other aspects about the system console). To change your keyboard encoding, edit the ``encoding'' variable found in /etc/wscons.conf. wscons.conf(5) contains more information about this file. Check hostname Use the hostname command to verify that the name of your machine is cor- rect. See the man page for hostname(1) if it needs to be changed. You will also need to change the contents of the ``hostname'' variable in /etc/rc.conf or edit the /etc/myname file to have it stick around for the next reboot. Note that hostname is supposed to be FQDN commonly and should not be confused with YP domainname(1). Verify network interface configuration The first thing to do is an ifconfig -a to see if the network interfaces are properly configured. Correct by editing /etc/ifconfig.interface (where interface is the interface name, e.g., ``le0'') and then using ifconfig(8) to manually configure it if you do not wish to reboot. Read the ifconfig.if(5) man page for more information on the format of /etc/ifconfig.interface files. The loopback interface will look some- thing like: lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32972 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 an Ethernet interface something like: le0: flags=9863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> inet 192.168.4.52 netmask 0xffffff00 broadcast 192.168.4.255 inet6 fe80::5ef0:f0f0%le0 prefixlen 64 scopeid 0x1 and, a PPP interface something like: ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> inet 203.3.131.108 --> 198.181.0.253 netmask 0xffff0000 See mrouted(8) for instructions on configuring multicast routing. See dhcpd(8) for instructions on configuring interfaces with DHCP. Check routing tables Issue a netstat -rn command. The output will look something like: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Interface default 192.168.4.254 UGS 0 11098028 - le0 127 127.0.0.1 UGRS 0 0 - lo0 127.0.0.1 127.0.0.1 UH 3 24 - lo0 192.168.4 link#1 UC 0 0 - le0 192.168.4.52 8:0:20:73:b8:4a UHL 1 6707 - le0 192.168.4.254 0:60:3e:99:67:ea UHL 1 0 - le0 Internet6: Destination Gateway Flags Refs Use Mtu Interface ::/96 ::1 UGRS 0 0 32972 lo0 => ::1 ::1 UH 4 0 32972 lo0 ::ffff:0.0.0.0/96 ::1 UGRS 0 0 32972 lo0 fc80::/10 ::1 UGRS 0 0 32972 lo0 fe80::/10 ::1 UGRS 0 0 32972 lo0 fe80::%le0/64 link#1 UC 0 0 1500 le0 fe80::%lo0/64 fe80::1%lo0 U 0 0 32972 lo0 ff01::/32 ::1 U 0 0 32972 lo0 ff02::%le0/32 link#1 UC 0 0 1500 le0 ff02::%lo0/32 fe80::1%lo0 UC 0 0 32972 lo0 The default gateway address is stored in the ``defaultroute'' variable /etc/rc.conf, or in the file /etc/mygate. If you need to edit this file, a painless way to reconfigure the network afterwards is to issue /etc/rc.d/network restart Or, you may prefer to manually configure using a series of route add and route delete commands (see route(8)). If you run dhclient(8) you will have to kill it by running /etc/rc.d/dhclient stop after you flush the routes. If you wish to route packets between interfaces, add the directive net.inet.ip.forwarding=1 and/or net.inet6.ip6.forwarding=1 to /etc/sysctl.conf, or compile a new kernel with the GATEWAY option. Packets are not forwarded by default, due to RFC requirements. You can add new ``virtual interfaces'' by adding the required entries to /etc/ifconfig.if. Secure Shell (ssh) By default, all services are disabled (and ssh is no exception). You may wish to enable it so you can remotely control your system. Set "sshd=yes" in /etc/rc.conf and then starting the server with the command /etc/rc.d/sshd start The first time the server is started, it will generate a new keypair, which will be stored inside the directory /etc/ssh. BIND Name Server (DNS) If you are using the BIND Name Server, check the /etc/resolv.conf file. It may look something like: domain some.thing.dom nameserver 192.168.0.1 nameserver 192.168.4.55 search some.thing.dom. thing.dom. For further details, see resolv.conf(5). Note the name service lookup order is set via nsswitch.conf(5) mechanism. If using a caching name server add the line "nameserver 127.0.0.1" first. To get a local caching name server to run you will need to set "named=yes" in /etc/rc.conf and create the named.conf file in the appro- priate place for named(8), usually in /etc/namedb. The same holds true if the machine is going to be a name server for your domain. In both these cases, make sure that named(8) is running (otherwise there are long waits for resolver timeouts). YP Setup Check the YP domain name with the domainname(1) command. If necessary, correct it by editing the /etc/defaultdomain file or by setting the ``domainname'' variable in /etc/rc.conf. The /etc/rc.d/network script reads this file on bootup to determine and set the domain name. You may also set the running system's domain name with the domainname(1) command. To start YP client services, simply run ypbind, then perform the remain- ing YP activation as described in passwd(5) and group(5). In particular, to enable YP passwd support, you'd need to update /etc/nsswitch.conf to include ``nis'' for the ``passwd'' entry. A tradi- tional way to accomplish the same thing is to add following entry to local passwd database via vipw(8): +:*:::::::: Note this entry has to be the very last one. This traditional way works with the default nsswitch.conf(5) setting of ``passwd'', which is ``compat''. You can find more information by starting with yp(8). Check disk mounts Check that the disks are mounted correctly by comparing the /etc/fstab file against the output of the mount(8) and df(1) commands. Example: # cat /etc/fstab /dev/sd0a / ffs rw 1 1 /dev/sd0b none swap sw 0 0 /dev/sd0e /usr ffs rw 1 2 /dev/sd0f /var ffs rw 1 3 /dev/sd0g /tmp ffs rw 1 4 /dev/sd0h /home ffs rw 1 5 # mount /dev/sd0a on / type ffs (local) /dev/sd0e on /usr type ffs (local) /dev/sd0f on /var type ffs (local) /dev/sd0g on /tmp type ffs (local) /dev/sd0h on /home type ffs (local) # df Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/sd0a 22311 14589 6606 69% / /dev/sd0e 203399 150221 43008 78% /usr /dev/sd0f 10447 682 9242 7% /var /dev/sd0g 18823 2 17879 0% /tmp /dev/sd0h 7519 5255 1888 74% /home # pstat -s Device 512-blocks Used Avail Capacity Priority /dev/sd0b 131072 84656 46416 65% 0 Edit /etc/fstab and use the mount(8) and umount(8) commands as appropri- ate. Refer to the above example and fstab(5) for information on the for- mat of this file. You may wish to do NFS mounts now too, or you can do them later. Concatenated disks (ccd) If you are using ccd(4) concatenated disks, edit /etc/ccd.conf. You may wish to take a look to ccdconfig(8) for more information about this file. Use the ccdconfig -U command to unload and the ccdconfig -C command to create tables internal to the kernel for the concatenated disks. You then mount(8), umount(8), and edit /etc/fstab as needed. CHANGING /etc FILES The system should be usable now, but you may wish to do more customiza- tion, such as adding users, etc. Many of the following sections may be skipped if you are not using that package (for example, skip the Kerberos section if you won't be using Kerberos). We suggest that you cd /etc and edit most of the files in that directory. Note that the /etc/motd file is modified by /etc/rc.d/motd whenever the system is booted. To keep any custom message intact, ensure that you leave two blank lines at the top, or your message will be overwritten. Sushi Since NetBSD 1.6, a new tool for configuring the system has been included, called sushi(8). It will allow you to set up many aspects of the system from interactive menus. You can launch it typing: sushi Add new users There are useradd(8) and groupadd(8) scripts. You may use vipw(8) to add users to the /etc/passwd file and edit /etc/group by hand to add new groups. The manual page for su(1), tells you to make sure to put people in the `wheel' group if they need root access (non-Kerberos). For exam- ple: wheel:*:0:root,myself Follow instructions for kerberos(8) if using Kerberos for authentication. rc.conf, rc.local Check for any local changes needed in the files /etc/rc.conf, and /etc/rc.local. rc.conf(5) contains configuration for various daemons included with the system. Script /etc/rc.local is run as the last thing during multiuser boot, and is provided to allow any other local hooks necessary for the system. You can take a look to /etc/defaults/rc.conf to see a list of default system variables, which you can override in /etc/rc.conf. Note you are not supposed to change /etc/defaults/rc.conf directly, edit only /etc/rc.conf. See rc.conf(5) for further information. The directory /etc/rc.d contains a serie of scripts used at startup/shut- down, called by /etc/rc. If you've installed X, you may want to turn on xdm(1), the X Display Man- ager. To do this, set the variable xdm to yes, i.e., "xdm=yes", in /etc/rc.conf. Printers Edit /etc/printcap and /etc/hosts.lpd to get any printers set up. Con- sult lpd(8) and printcap(5) if needed. Tighten up security In /etc/inetd.conf comment out any extra entries you do not need, and only add things that are really needed. Note that by default all ser- vices are disabled for security reasons. Kerberos If you are going to use kerberos(8) for authentication, and you already have a Kerberos master, change directory to /etc/kerberosIV or /etc/kerberosV and configure. Remember to get a srvtab from the master so that the remote commands work. Mail Aliases Check /etc/mail/aliases and update appropriately if you want e-mail to be routed to non-local address or to different users. Run newaliases(1) after changes. Sendmail NetBSD ships with default /etc/mail/sendmail.cf and /etc/mail/submit.cf files that will work for simple installations; they were generated from netbsd-proto.mc and netbsd-msp.mc in /usr/share/sendmail/cf. Please see /usr/share/sendmail/README and /usr/share/doc/smm/08.sendmailop/op.me for information on generating your own sendmail configuration files. /etc/mailer.conf is configured to use Sendmail binaries by default and sendmail(8) will start by default if no other changes to the mail system are made. See mailer.conf(5) and rc.conf(5) for more details. Postfix NetBSD comes also with Postfix in the base system. You may wish to set it up in favor of sendmail. Take a look to /etc/postfix/main.cf and enable the daemon in /etc/rc.conf using "postfix=yes". It is very impor- tant to configure /etc/mailer.conf to point to Postfix binaries. DHCP server If this is a DHCP server, edit /etc/dhcpd.conf and /etc/dhcpd.interfaces as needed. You will have to make sure /etc/rc.conf has "dhcpd=yes" or run dhcpd(8) manually. Bootparam server If this is a Bootparam server, edit /etc/bootparams as needed. You will have to turn it on in /etc/rc.conf by adding "bootparamd=yes". NFS server If this is an NFS server, make sure /etc/rc.conf has: nfs_server=yes mountd=yes rpcbind=yes Edit /etc/exports and get it correct. After this, you can start the server by issuing: /etc/rc.d/nfsd start which will also start dependancies. HP remote boot server Edit /etc/rbootd.conf if needed for remote booting. If you do not have HP computers doing remote booting, do not enable this. Daily, weekly, monthly scripts Look at and possibly edit the /etc/daily.conf, /etc/weekly.conf, and /etc/monthly.conf configuration files. You can check which values you can set by looking to their matching files in /etc/defaults. Your site specific things should go into /etc/daily.local, /etc/weekly.local, and /etc/monthly.local. These scripts have been limited so as to keep the system running without filling up disk space from normal running processes and database updates. (You probably do not need to understand them.) Other files in /etc Look at the other files in /etc and edit them as needed. (Do not edit files ending in .db -- like pwd.db, spwd.db, nor localtime, nor rmt, nor any directories.) Crontab (background running processes) Check what is running by typing crontab -l as root and see if anything unexpected is present. Do you need anything else? Do you wish to change things? e.g., if you do not like root getting standard output of the daily scripts, and want only the security scripts that are mailed inter- nally, you can type crontab -e and change some of the lines to read: 30 1 * * * /bin/sh /etc/daily 2>&1 > /var/log/daily.out 30 3 * * 6 /bin/sh /etc/weekly 2>&1 > /var/log/weekly.out 30 5 1 * * /bin/sh /etc/monthly 2>&1 > /var/log/monthly.out See crontab(5). Next day cleanup After the first night's security run, change ownerships and permissions on files, directories, and devices; root should have received mail with subject: "<hostname> daily insecurity output.". This mail contains a set of security recommendations, presented as a list looking like this: var/mail: permissions (0755, 0775) etc/daily: user (0, 3) The best bet is to follow the advice in that list. The recommended set- ting is the first item in parentheses, while the current setting is the second one. This list is generated by mtree(8) using /etc/mtree/special. Use chmod(1), chgrp(1), and chown(8) as needed. Packages Install your own packages. The NetBSD package collection includes a large set of Third-Party software. A lot of it is available as binary packages that you can download from ftp://ftp.NetBSD.org/ or a mirror, and install using pkg_add(1). See http://www.NetBSD.org/Documentation/software/ and packages(7) for more details. Copy vendor binaries and install them. You will need to install any shared libraries, etc. (Hint: man -k compat to find out how to install and use compatibility mode.) There is also other Third-Party Software that is available in source form only, either because it has not been ported to NetBSD yet, because licensing restrictions make binary redistribution impossible, or simply because you want to build your own binaries. This group is called pkgsrc. Sometimes checking the mailing lists for past problems that peo- ple have encountered will result in a fix posted. COMPILING A KERNEL First, review the system message buffer using the dmesg(8) command to find out information on your system's devices as probed by the kernel at boot. In particular, note which devices were not configured. This information will prove useful when editing kernel configuration files. To compile a kernel inside a writable source tree, do the following: # cd /usr/src/sys/arch/SOMEARCH/conf # cp GENERIC SOMEFILE (only the first time) # vi SOMEFILE (adapt to your needs) # config SOMEFILE # cd ../compile/SOMEFILE # make depend # make where SOMEARCH is the architecture (e.g., i386), and SOMEFILE should be a name indicative of a particular configuration (often that of the host- name). If you are building your kernel again, before you do a make you should do a make clean after making changes to your kernel options. After either of these two methods, you can place the new kernel (called netbsd) in / (i.e., /netbsd) by issuing make install and the system will boot it next time. The old kernel is stored as /onetbsd so you can boot it in case of failure. If you are using toolchain to build your kernel, you will also need to build a new set of toolchain binaries. You can do it by entering /usr/src and issuing ./build.sh tools
SEE ALSO
chgrp(1), chmod(1), crontab(1), date(1), df(1), domainname(1), hostname(1), make(1), man(1), netstat(1), newaliases(1), passwd(1), su(1), ccd(4), aliases(5), crontab(5), exports(5), fstab(5), group(5), krb.conf(5), krb.realms(5), mailer.conf(5), passwd(5), rc.conf(5), resolv.conf(5), hostname(7), packages(7), adduser(8), amd(8), bootparamd(8), ccdconfig(8), chown(8), config(8), dhcpd(8), ifconfig(8), inetd(8), kerberos(8), mount(8), mrouted(8), mtree(8), named(8), rbootd(8), rc(8), rmt(8), route(8), sushi(8), umount(8), vipw(8), ypbind(8)
HISTORY
This document first appeared in OpenBSD 2.2. It has been adapted to NetBSD and first appeared in NetBSD 2.0. NetBSD 2.0.2 March 10, 2003 NetBSD 2.0.2
Powered by man-cgi (2024-08-26). Maintained for NetBSD by Kimmo Suominen. Based on man-cgi by Panagiotis Christias.