head 1.24; access; symbols netbsd-11-0-RC4:1.24 netbsd-11-0-RC3:1.24 netbsd-11-0-RC2:1.24 netbsd-11-0-RC1:1.24 perseant-exfatfs-base-20250801:1.24 netbsd-11:1.24.0.116 netbsd-11-base:1.24 netbsd-10-1-RELEASE:1.24 perseant-exfatfs-base-20240630:1.24 perseant-exfatfs:1.24.0.114 perseant-exfatfs-base:1.24 netbsd-8-3-RELEASE:1.24 netbsd-9-4-RELEASE:1.24 netbsd-10-0-RELEASE:1.24 netbsd-10-0-RC6:1.24 netbsd-10-0-RC5:1.24 netbsd-10-0-RC4:1.24 netbsd-10-0-RC3:1.24 netbsd-10-0-RC2:1.24 netbsd-10-0-RC1:1.24 netbsd-10:1.24.0.112 netbsd-10-base:1.24 netbsd-9-3-RELEASE:1.24 cjep_sun2x-base1:1.24 cjep_sun2x:1.24.0.110 cjep_sun2x-base:1.24 cjep_staticlib_x-base1:1.24 netbsd-9-2-RELEASE:1.24 cjep_staticlib_x:1.24.0.108 cjep_staticlib_x-base:1.24 netbsd-9-1-RELEASE:1.24 phil-wifi-20200421:1.24 phil-wifi-20200411:1.24 is-mlppp:1.24.0.106 is-mlppp-base:1.24 phil-wifi-20200406:1.24 netbsd-8-2-RELEASE:1.24 netbsd-9-0-RELEASE:1.24 netbsd-9-0-RC2:1.24 netbsd-9-0-RC1:1.24 phil-wifi-20191119:1.24 netbsd-9:1.24.0.104 netbsd-9-base:1.24 phil-wifi-20190609:1.24 netbsd-8-1-RELEASE:1.24 netbsd-8-1-RC1:1.24 pgoyette-compat-merge-20190127:1.24 pgoyette-compat-20190127:1.24 pgoyette-compat-20190118:1.24 pgoyette-compat-1226:1.24 pgoyette-compat-1126:1.24 pgoyette-compat-1020:1.24 pgoyette-compat-0930:1.24 pgoyette-compat-0906:1.24 netbsd-7-2-RELEASE:1.24 pgoyette-compat-0728:1.24 netbsd-8-0-RELEASE:1.24 phil-wifi:1.24.0.102 phil-wifi-base:1.24 pgoyette-compat-0625:1.24 netbsd-8-0-RC2:1.24 pgoyette-compat-0521:1.24 pgoyette-compat-0502:1.24 pgoyette-compat-0422:1.24 netbsd-8-0-RC1:1.24 pgoyette-compat-0415:1.24 pgoyette-compat-0407:1.24 pgoyette-compat-0330:1.24 pgoyette-compat-0322:1.24 pgoyette-compat-0315:1.24 netbsd-7-1-2-RELEASE:1.24 pgoyette-compat:1.24.0.100 pgoyette-compat-base:1.24 netbsd-7-1-1-RELEASE:1.24 matt-nb8-mediatek:1.24.0.98 matt-nb8-mediatek-base:1.24 perseant-stdc-iso10646:1.24.0.96 perseant-stdc-iso10646-base:1.24 netbsd-8:1.24.0.94 netbsd-8-base:1.24 prg-localcount2-base3:1.24 prg-localcount2-base2:1.24 prg-localcount2-base1:1.24 prg-localcount2:1.24.0.92 prg-localcount2-base:1.24 pgoyette-localcount-20170426:1.24 bouyer-socketcan-base1:1.24 pgoyette-localcount-20170320:1.24 netbsd-7-1:1.24.0.90 netbsd-7-1-RELEASE:1.24 netbsd-7-1-RC2:1.24 netbsd-7-nhusb-base-20170116:1.24 bouyer-socketcan:1.24.0.88 bouyer-socketcan-base:1.24 pgoyette-localcount-20170107:1.24 netbsd-7-1-RC1:1.24 pgoyette-localcount-20161104:1.24 netbsd-7-0-2-RELEASE:1.24 localcount-20160914:1.24 netbsd-7-nhusb:1.24.0.86 netbsd-7-nhusb-base:1.24 pgoyette-localcount-20160806:1.24 pgoyette-localcount-20160726:1.24 pgoyette-localcount:1.24.0.84 pgoyette-localcount-base:1.24 netbsd-7-0-1-RELEASE:1.24 netbsd-7-0:1.24.0.82 netbsd-7-0-RELEASE:1.24 netbsd-7-0-RC3:1.24 netbsd-7-0-RC2:1.24 netbsd-7-0-RC1:1.24 netbsd-5-2-3-RELEASE:1.24 netbsd-5-1-5-RELEASE:1.24 netbsd-6-0-6-RELEASE:1.24 netbsd-6-1-5-RELEASE:1.24 netbsd-7:1.24.0.80 netbsd-7-base:1.24 yamt-pagecache-base9:1.24 yamt-pagecache-tag8:1.24 netbsd-6-1-4-RELEASE:1.24 netbsd-6-0-5-RELEASE:1.24 tls-earlyentropy:1.24.0.78 tls-earlyentropy-base:1.24 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.24 riastradh-drm2-base3:1.24 netbsd-6-1-3-RELEASE:1.24 netbsd-6-0-4-RELEASE:1.24 netbsd-5-2-2-RELEASE:1.24 netbsd-5-1-4-RELEASE:1.24 netbsd-6-1-2-RELEASE:1.24 netbsd-6-0-3-RELEASE:1.24 netbsd-5-2-1-RELEASE:1.24 netbsd-5-1-3-RELEASE:1.24 netbsd-6-1-1-RELEASE:1.24 riastradh-drm2-base2:1.24 riastradh-drm2-base1:1.24 riastradh-drm2:1.24.0.70 riastradh-drm2-base:1.24 netbsd-6-1:1.24.0.76 netbsd-6-0-2-RELEASE:1.24 netbsd-6-1-RELEASE:1.24 khorben-n900:1.24.0.74 netbsd-6-1-RC4:1.24 netbsd-6-1-RC3:1.24 agc-symver:1.24.0.72 agc-symver-base:1.24 netbsd-6-1-RC2:1.24 netbsd-6-1-RC1:1.24 yamt-pagecache-base8:1.24 netbsd-5-2:1.24.0.68 netbsd-6-0-1-RELEASE:1.24 yamt-pagecache-base7:1.24 netbsd-5-2-RELEASE:1.24 netbsd-5-2-RC1:1.24 matt-nb6-plus-nbase:1.24 yamt-pagecache-base6:1.24 netbsd-6-0:1.24.0.66 netbsd-6-0-RELEASE:1.24 netbsd-6-0-RC2:1.24 tls-maxphys:1.24.0.64 tls-maxphys-base:1.24 matt-nb6-plus:1.24.0.62 matt-nb6-plus-base:1.24 netbsd-6-0-RC1:1.24 yamt-pagecache-base5:1.24 yamt-pagecache-base4:1.24 netbsd-6:1.24.0.60 netbsd-6-base:1.24 netbsd-5-1-2-RELEASE:1.24 netbsd-5-1-1-RELEASE:1.24 yamt-pagecache-base3:1.24 yamt-pagecache-base2:1.24 yamt-pagecache:1.24.0.58 yamt-pagecache-base:1.24 cherry-xenmp:1.24.0.56 cherry-xenmp-base:1.24 bouyer-quota2-nbase:1.24 bouyer-quota2:1.24.0.54 bouyer-quota2-base:1.24 matt-mips64-premerge-20101231:1.24 matt-nb5-mips64-premerge-20101231:1.24 matt-nb5-pq3:1.24.0.52 matt-nb5-pq3-base:1.24 netbsd-5-1:1.24.0.50 netbsd-5-1-RELEASE:1.24 netbsd-5-1-RC4:1.24 matt-nb5-mips64-k15:1.24 netbsd-5-1-RC3:1.24 netbsd-5-1-RC2:1.24 netbsd-5-1-RC1:1.24 netbsd-5-0-2-RELEASE:1.24 matt-nb5-mips64-premerge-20091211:1.24 matt-premerge-20091211:1.24 matt-nb5-mips64-u2-k2-k4-k7-k8-k9:1.24 matt-nb4-mips64-k7-u2a-k9b:1.24 matt-nb5-mips64-u1-k1-k5:1.24 matt-nb5-mips64:1.24.0.48 netbsd-5-0-1-RELEASE:1.24 jym-xensuspend-nbase:1.24 netbsd-5-0:1.24.0.46 netbsd-5-0-RELEASE:1.24 netbsd-5-0-RC4:1.24 netbsd-5-0-RC3:1.24 netbsd-5-0-RC2:1.24 jym-xensuspend:1.24.0.44 jym-xensuspend-base:1.24 netbsd-5-0-RC1:1.24 netbsd-5:1.24.0.42 netbsd-5-base:1.24 matt-mips64-base2:1.24 matt-mips64:1.24.0.40 netbsd-4-0-1-RELEASE:1.24 wrstuden-revivesa-base-3:1.24 wrstuden-revivesa-base-2:1.24 wrstuden-fixsa-newbase:1.24 wrstuden-revivesa-base-1:1.24 yamt-pf42-base4:1.24 yamt-pf42-base3:1.24 hpcarm-cleanup-nbase:1.24 yamt-pf42-baseX:1.24 yamt-pf42-base2:1.24 wrstuden-revivesa:1.24.0.38 wrstuden-revivesa-base:1.24 yamt-pf42:1.24.0.36 yamt-pf42-base:1.24 mjf-devfs2:1.24.0.34 mjf-devfs2-base:1.24 keiichi-mipv6:1.24.0.32 keiichi-mipv6-base:1.24 mjf-devfs:1.24.0.30 mjf-devfs-base:1.24 matt-armv6-nbase:1.24 matt-armv6-prevmlocking:1.24 wrstuden-fixsa-base-1:1.24 netbsd-4-0:1.24.0.28 netbsd-4-0-RELEASE:1.24 cube-autoconf:1.24.0.26 cube-autoconf-base:1.24 netbsd-4-0-RC5:1.24 netbsd-4-0-RC4:1.24 netbsd-4-0-RC3:1.24 netbsd-4-0-RC2:1.24 netbsd-4-0-RC1:1.24 matt-armv6:1.24.0.24 matt-armv6-base:1.24 matt-mips64-base:1.24 hpcarm-cleanup:1.24.0.22 hpcarm-cleanup-base:1.24 netbsd-3-1-1-RELEASE:1.24 netbsd-3-0-3-RELEASE:1.24 wrstuden-fixsa:1.24.0.20 wrstuden-fixsa-base:1.24 abandoned-netbsd-4-base:1.24 abandoned-netbsd-4:1.24.0.14 netbsd-3-1:1.24.0.16 netbsd-3-1-RELEASE:1.24 netbsd-3-0-2-RELEASE:1.24 netbsd-3-1-RC4:1.24 netbsd-3-1-RC3:1.24 netbsd-3-1-RC2:1.24 netbsd-3-1-RC1:1.24 netbsd-4:1.24.0.18 netbsd-4-base:1.24 netbsd-3-0-1-RELEASE:1.24 netbsd-3-0:1.24.0.12 netbsd-3-0-RELEASE:1.24 netbsd-3-0-RC6:1.24 netbsd-3-0-RC5:1.24 netbsd-3-0-RC4:1.24 netbsd-3-0-RC3:1.24 netbsd-3-0-RC2:1.24 netbsd-3-0-RC1:1.24 netbsd-2-0-3-RELEASE:1.24 netbsd-2-1:1.24.0.10 netbsd-2-1-RELEASE:1.24 netbsd-2-1-RC6:1.24 netbsd-2-1-RC5:1.24 netbsd-2-1-RC4:1.24 netbsd-2-1-RC3:1.24 netbsd-2-1-RC2:1.24 netbsd-2-1-RC1:1.24 netbsd-2-0-2-RELEASE:1.24 netbsd-3:1.24.0.8 netbsd-3-base:1.24 netbsd-2-0-1-RELEASE:1.24 netbsd-2:1.24.0.6 netbsd-2-base:1.24 netbsd-2-0-RELEASE:1.24 netbsd-2-0-RC5:1.24 netbsd-2-0-RC4:1.24 netbsd-2-0-RC3:1.24 netbsd-2-0-RC2:1.24 netbsd-2-0-RC1:1.24 netbsd-2-0:1.24.0.4 netbsd-2-0-base:1.24 netbsd-1-6-PATCH002-RELEASE:1.24 netbsd-1-6-PATCH002:1.24 netbsd-1-6-PATCH002-RC4:1.24 netbsd-1-6-PATCH002-RC3:1.24 netbsd-1-6-PATCH002-RC2:1.24 netbsd-1-6-PATCH002-RC1:1.24 netbsd-1-6-PATCH001:1.24 netbsd-1-6-PATCH001-RELEASE:1.24 netbsd-1-6-PATCH001-RC3:1.24 netbsd-1-6-PATCH001-RC2:1.24 netbsd-1-6-PATCH001-RC1:1.24 fvdl_fs64_base:1.24 netbsd-1-6-RELEASE:1.24 netbsd-1-6-RC3:1.24 netbsd-1-6-RC2:1.24 netbsd-1-6-RC1:1.24 netbsd-1-6:1.24.0.2 netbsd-1-6-base:1.24 netbsd-1-5-PATCH003:1.22.10.1 netbsd-1-5-PATCH002:1.22.10.1 netbsd-1-5-PATCH001:1.22.10.1 netbsd-1-5-RELEASE:1.22.10.1 netbsd-1-5-BETA2:1.22.10.1 netbsd-1-5-BETA:1.22 netbsd-1-4-PATCH003:1.22 netbsd-1-5-ALPHA2:1.22 netbsd-1-5:1.22.0.10 netbsd-1-5-base:1.22 minoura-xpg4dl:1.22.0.8 minoura-xpg4dl-base:1.22 netbsd-1-4-PATCH002:1.22 wrstuden-devbsize-19991221:1.22 wrstuden-devbsize:1.22.0.6 wrstuden-devbsize-base:1.22 comdex-fall-1999:1.22.0.4 comdex-fall-1999-base:1.22 netbsd-1-4-PATCH001:1.22 netbsd-1-4-RELEASE:1.22 netbsd-1-4:1.22.0.2 netbsd-1-4-base:1.22 netbsd-1-3-PATCH003:1.12.2.5 netbsd-1-3-PATCH003-CANDIDATE2:1.12.2.5 netbsd-1-3-PATCH003-CANDIDATE1:1.12.2.5 netbsd-1-3-PATCH003-CANDIDATE0:1.12.2.5 netbsd-1-3-PATCH002:1.12.2.5 netbsd-1-3-PATCH001:1.12.2.4 netbsd-1-3-RELEASE:1.12.2.4 netbsd-1-3-BETA:1.12 netbsd-1-3:1.12.0.2 netbsd-1-3-base:1.12 netbsd-1-2-PATCH001:1.6.4.2 netbsd-1-2-RELEASE:1.6 netbsd-1-2-BETA:1.6 netbsd-1-2-base:1.6 netbsd-1-2:1.6.0.4 netbsd-1-1-PATCH001:1.5.4.1 netbsd-1-1-RELEASE:1.5.4.1 netbsd-1-1:1.5.0.4 netbsd-1-1-base:1.5 netbsd-1-0-PATCH06:1.5 netbsd-1-0-PATCH05:1.5 netbsd-1-0-PATCH04:1.5 netbsd-1-0-PATCH03:1.5 netbsd-1-0-PATCH02:1.5 netbsd-1-0-PATCH1:1.5 netbsd-1-0-PATCH0:1.5 netbsd-1-0-RELEASE:1.5 netbsd-1-0:1.5.0.2 netbsd-1-0-base:1.5 cgd-940917:1.1.1.1 cgd:1.1.1; locks; strict; comment @# @; 1.24 date 2000.10.10.12.55.18; author lukem; state Exp; branches 1.24.34.1; next 1.23; 1.23 date 2000.10.04.00.33.50; author lukem; state Exp; branches; next 1.22; 1.22 date 99.01.13.07.30.05; author ross; state Exp; branches 1.22.10.1; next 1.21; 1.21 date 98.08.23.12.42.18; author hubertf; state Exp; branches; next 1.20; 1.20 date 98.07.04.18.51.00; author is; state Exp; branches; next 1.19; 1.19 date 98.05.15.15.08.42; author fvdl; state Exp; branches; next 1.18; 1.18 date 98.01.09.18.46.30; author perry; state Exp; branches; next 1.17; 1.17 date 97.12.25.21.45.03; author fvdl; state Exp; branches; next 1.16; 1.16 date 97.12.24.23.12.50; author perry; state Exp; branches; next 1.15; 1.15 date 97.12.19.01.46.16; author fvdl; state Exp; branches; next 1.14; 1.14 date 97.12.19.00.59.56; author fvdl; state Exp; branches; next 1.13; 1.13 date 97.11.30.06.30.32; author perry; state Exp; branches; next 1.12; 1.12 date 97.10.20.05.14.30; author perry; state Exp; branches 1.12.2.1; next 1.11; 1.11 date 97.06.17.08.02.49; author mikel; state Exp; branches; next 1.10; 1.10 date 97.06.14.06.17.25; author perry; state Exp; branches; next 1.9; 1.9 date 97.03.25.06.25.04; author perry; state Exp; branches; next 1.8; 1.8 date 97.03.25.06.09.06; author perry; state Exp; branches; next 1.7; 1.7 date 96.10.09.00.13.36; author jtc; state Exp; branches; next 1.6; 1.6 date 95.11.28.23.58.05; author jtc; state Exp; branches 1.6.4.1; next 1.5; 1.5 date 94.10.18.07.38.46; author cgd; state Exp; branches 1.5.2.1 1.5.4.1; next 1.4; 1.4 date 94.10.18.07.17.04; author glass; state Exp; branches; next 1.3; 1.3 date 94.10.02.18.02.30; author cgd; state Exp; branches; next 1.2; 1.2 date 94.10.02.17.41.53; author cgd; state Exp; branches; next 1.1; 1.1 date 94.09.17.19.03.02; author cgd; state Exp; branches 1.1.1.1; next ; 1.24.34.1 date 2008.10.05.20.10.28; author mjf; state dead; branches; next ; 1.22.10.1 date 2000.11.01.03.48.07; author tv; state Exp; branches; next ; 1.12.2.1 date 97.11.30.06.34.01; author perry; state Exp; branches; next 1.12.2.2; 1.12.2.2 date 97.12.20.21.35.05; author perry; state Exp; branches; next 1.12.2.3; 1.12.2.3 date 97.12.24.23.15.17; author perry; state Exp; branches; next 1.12.2.4; 1.12.2.4 date 97.12.25.22.37.15; author perry; state Exp; branches; next 1.12.2.5; 1.12.2.5 date 98.05.29.03.52.28; author mycroft; state Exp; branches; next ; 1.6.4.1 date 96.09.18.04.01.52; author tls; state Exp; branches; next 1.6.4.2; 1.6.4.2 date 97.03.13.00.49.05; author mycroft; state Exp; branches; next ; 1.5.2.1 date 94.10.18.07.38.46; author cgd; state dead; branches; next 1.5.2.2; 1.5.2.2 date 94.10.18.07.38.47; author cgd; state Exp; branches; next ; 1.5.4.1 date 95.11.25.05.15.20; author perry; state Exp; branches; next ; 1.1.1.1 date 94.09.17.19.03.03; author cgd; state Exp; branches; next ; desc @@ 1.24 log @major terraform (this is MUCH more than a rototill :-), including: - update for 1.5 (still more MD stuff to check) - use new macros in ../common/macros as appropriate - introduce some CONSISTENCY between the various ports' install docs - use various mdoc macros as appropriate, including .Li, .Pa, .Sy, and .Ic. - migrate more stuff into ../common/* - whitespace cleanup - lots of other little things i'm sure... @ text @.\" $NetBSD: install,v 1.23 2000/10/04 00:33:50 lukem Exp $ . .so ../common/sysinst @ 1.24.34.1 log @Sync with HEAD. @ text @d1 1 a1 1 .\" $NetBSD: install,v 1.24 2000/10/10 12:55:18 lukem Exp $ @ 1.23 log @minor knf @ text @d1 2 a2 2 .\" $NetBSD: install,v 1.22 1999/01/13 07:30:05 ross Exp $ .\" @ 1.22 log @Markup for -mdoc and -mdoc2html. @ text @d1 2 a2 1 .\" $NetBSD$ @ 1.22.10.1 log @Sync to HEAD as of 20001101 03:43 GMT [lukem]: Complete rework of install notes for 1.5 from several authors. @ text @d1 1 a1 2 .\" $NetBSD: install,v 1.24 2000/10/10 12:55:18 lukem Exp $ . @ 1.21 log @Add notes about steps to do after installation that are common to all platforms; Thanks to Colin Wood and Simon Burge for their comments. @ text @d1 2 a2 459 $NetBSD: install,v 1.20 1998/07/04 18:51:00 is Exp $ 0. Introduction Using "sysinst", installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details to be complete. Do not let this discourage you, the install program is not hard to use. 0.1 Possible PCMCIA issues There is a serious bug that may make installation of NetBSD on PCMCIA machines difficult. This bug does not make USE of PCMCIA difficult once a machine is installed. If you do not have PCMCIA on your machine (PCMCIA is only really used on laptop machines), you can skip this section, and ignore the "[PCMCIA]" notes. This will explains how to work around the installation problem. It is anticipated that this bug will be fixed by NetBSD 1.4 What is the bug: The kernel keeps careful track of what interrupts and i/o ports are in use during autoconfiguration. It then allows the PCMCIA devices to pick unused interrupts and ports. Unfortunately, not all devices are included in the INSTALL kernels in order to save space. Let's say your laptop has a soundblaster device built in. The INSTALL kernel has no sound support. The PCMCIA code might allocate your soundblaster's IRQ and i/o ports to PCMCIA devices, causing them not to work. This is especially bad if one of the devices in question is your ethernet card. This problem will impact some, but not all, users of PCMCIA. If this bug is hurting you, watch the "[PCMCIA]" notes that will appear in this document. 1. General The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installation system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. 2. Quick install First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to section 3. This section describes a basic installation, using a CD-ROM install as an example. 2.1 What you need. * The distribution sets (in this example, they are on CD). * One 1.44M 3.5" floppy. * A PC with a 386 or newer processor, a CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of 4Mb of memory installed. * The harddisk should have at least 70 + N megabytes of space free, where N is the number of megabytes of main memory in your system. If you wish to install the X window system as well, you will need at least 60Mb more. 2.2 Creating a bootfloppy. * You can create the floppy needed for installation under DOS or Windows. Supposing your 1.44M floppy drive is drive A:, and your CD is drive E: do the following from an MS-DOS command prompt: e: cd \NetBSD-_VER\installation\misc rawrite When asked for a source filename, answer ..\floppy\boot.fs When asked for a destination drive answer a 2.3 The installation * Insert the bootfloppy you just created. Restart the PC. You will be presented with a menu. * If you wish, you can configure some network settings immediately by choosing the "utilities" menu and then "configure network". This isn't needed, but more convenient to do now. Go back to the main menu. * Choose "install" * You will be guided through some steps regarding the setup of your harddisk, and parts to install. When in doubt, refer to the rest of this document for details. * After your disk has been prepared, choose CD-ROM as the medium. The default values for the path and device should be ok. * After all the files have been unpacked, go back to the main menu and select "reboot", after you have removed the bootfloppy from the drive. * NetBSD will now boot. You should log in as root, and set a password for that account. You are also advised to edit the file "/etc/rc.conf" to match your system needs. * Your installation is now complete. * For configuring the X window system, if installed, see the files in /usr/X11R6/lib/X11/doc. Further information can be found on http://www.xfree86.org/ 3. Booting NetBSD [PCMCIA]: unplug your PCMCIA devices, so that they won't be found by NetBSD. Boot your machine using the boot floppy. The boot loader will start, and will print a countdown and begin booting. You will likely see one "file not found" warning from the boot loader -- ignore this as it is normal, and indicates the boot loader failed to find a normal kernel to boot before trying to boot a compressed kernel. If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that. If that doesn't work, try booting after disabling your CPU's internal and external caches (if any). If it still doesn't work, NetBSD probably can't be run on your hardware. This can probably be considered a bug, so you might want to report it. If you do, please include as many details about your system configuration as you can. It will take a while to load the kernel from the floppy, probably around a minute or so. You will then be presented with the NetBSD kernel boot messages. This may take a little while, as NetBSD will be probing for a lot of types of hardware, You may want to read the boot messages, to notice your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell sysinst on which disk to install. The most important thing to know is that 'wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. 'sd0' is your first SCSI disk, sd1 the second, etc. Note that, once the system has finished booting, you need no longer leave the floppy in the disk drive. Earlier version of the NetBSD install floppies mounted the floppy as the system's root partition, but the new installation floppies use a ramdisk file system and are no longer dependent on the floppy once it has booted. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 4. Network configuration [PCMCIA] You can skip this section, as you will only get data from floppy in the first part of the install. If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the utilities menu, and select the "Configure network option". If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using Domain Name Service (DNS), you can give an empty response in reply to answers relating to this. 5. The hard disk to install on and its parameters. To start the installation, select the menu option to install NetBSD from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like "wd0", "wd1", "sd0", or "sd1". sysinst next tries to figure out the real and BIOS geometry of your disk. It will present you with the values it found, if any, and will give you a chance to change them. Please note that if you change the values, sysinst WILL ALSO REINITIALIZE YOUR MBR. You will also be asked if you want to use the last cylinder of the disk. Originally, the last cylinder of the disk was used for diagnostic purposes, but this is usually not a concern anymore these days. You will be able to specify whether you want to skip the last cylinder anyway. Next, depending on whether you are using a "wdX" or a "sdX" disk, you will either be asked for the type of disk (wdX) you are using or you will be asked if you want to specify a fake geometry for your SCSI disk (sdX). The types of disk are be IDE, ST-506 or ESDI. If you're installing on an ST-506 or ESDI drive, you'll be asked if your disk supports automatic sector forwarding. If you are SURE that it does, reply affirmatively. Otherwise, the install program will automatically reserve space for bad144 tables. 6. Partitioning the disk. 6.1 Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these. If you want to use the entire disk for NetBSD, you can skip the following section and go to section 6.3, "Editing the NetBSD disklabel". 6.2 Editing the Master Boot Record. First, you will be prompted to specify the units of size that you want to express the sizes of the partitions in. You can either pick megabytes, cylinders or sectors. After this, you will be presented with the current values stored in the MBR, and will be given the opportunity to change, create or delete partitions. For each partition you can set the type, the start and the size. Setting the type to 'unused' will delete a partition. You can also mark a partition as active, meaning that this is the one that the BIOS will start from at boot time. Be sure to mark the partition you want to boot from as active! After you are done editing the MBR, a sanity check will be done, checking for partitions that overlap. If everything is ok, you can go on to the next step, editing the NetBSD disklabel. 6.3 Editing the NetBSD disklabel. The partition table of a NetBSD part of a disk is called a 'disklabel'. There are 3 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X and Custom. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. The last option lets you specify everything yourself. You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called "4.2BSD". A swap partition has a special type called "swap". You can also specify a partition as type "msdos". This is useful if you share the disk with MS-DOS or Windows95, NetBSD is able to access the files on these partitions. You can use the values from the MBR for the MS-DOS part of the disk to specify the partition of type "msdos" (you don't have to do this now, you can always re-edit the disklabel to add this once you have installed NetBSD). Some partitions in the disklabel have a fixed purpose. Partition 'a' is always the root partition, 'b' is the swap partition, 'c' is the entire NetBSD part of the disk, and 'd' is the whole disk. Partitions 'e'-'h' are available for other use. Traditionally, 'e' is the partition mounted on the /usr directory, but this is historical practice, not a fixed value. You will then be asked to name your disk's disklabel. The default response is "mydisk". For most purposes this will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name. 7. Preparing your hard disk YOU ARE NOW AT THE POINT OF NO RETURN. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, enter "yes" at the prompt. The install program will now label your disk and make the file systems you specified. The filesystems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing 'return'. NOTE: In previous versions of NetBSD, the kernel from the install floppy was copied onto the hard drive in a special step. In the new install system, the kernel on the floppy is unsuited to being copied onto the hard drive. Instead, a new set, "kern", has been added which contains a generic kernel to be unloaded onto the drive. So, you can not boot from your hard drive yet at this point. 8. Getting the distribution sets. [PCMCIA] Load a kernel tar file (i.e. the kern.tgz set file) on to your hard disk, for example by mounting the hard disk first, copying the kern.tgz file from floppy and unpacking it. Example: mount /dev/wd0a /mnt cd /mnt mount -t msdos /dev/fd0a /mnt2 cp /mnt2/kern.* . umount /mnt2 cat kern.* | tar vxzf - Then halt the machine using the 'halt' command. Power the machine down, and re-insert all the PCMCIA devices. Remove any floppy from the floppy drive. Start the machine up. After booting NetBSD, you will be presented with the main sysinst menu. Choose the option to re-install sets. Wait for the filesystem checks that it will do to finish, and then proceed as described below. The NetBSD distribution consists of a number of 'sets', that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to section 9 8.1 Installation using ftp To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press 'return' in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, and the account name and password used to log into that host using ftp. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the ftp server. sysinst will proceed to transfer all the default set files from the remote site to your hard disk. 8.2 Installation using NFS To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press 'return' in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the NFS server. 8.3 Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM player (usually 'cd0'), and directory name on the CD-ROM where the distribution files are. sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 8.4 Installation from floppy Because the installation sets are too big to fit on one floppy, the floppies are expected to be filled with the split set files. The floppies are expected to be in MS-DOS format. You will be asked for a directory where the sets should be reassembled. Then you will be prompted to insert the floppies containing the split sets. This process will continue until all the sets have been loaded from floppy. 8.5 Installation from an unmounted filesystem In order to install from a local filesystem, you will need to specify the device that the filesystem resides on (for example 'wd1e'), the type of the filesystem, and the directory on the specified filesystem where the sets are located. sysinst will then check if it can indeed access the sets at that location. 8.6 Installation from a local directory This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a filesystem that is already accessible. sysinst will ask you for the name of this directory. 9. Extracting the distribution sets After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed ("kern", "base" and "etc"), they will not be shown in this selection menu. Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. 10. Finalizing your installation. Congratulations, you have successfully installed NetBSD _VER. You can now reboot the machine, and boot from harddisk. @ 1.20 log @Fix typo pointed out by Michael K. Sandersi in PR 5656. @ text @d1 1 a1 1 $NetBSD: install,v 1.19 1998/05/15 15:08:42 fvdl Exp $ a459 22 After reboot, you can log in "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. You should now edit the /etc/rc.conf file to configure the system to suit your needs, and then reboot the system again. Some other files in the NetBSD _VER distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified, as well. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. If you have installed the X window system, look at the files in /usr/X11R6/lib/X11/doc for information. You will need to set up a configuration file. An example of such a file is /usr/X11R6/lib/X11/XF86Config.eg. See http://www.xfree86.org/ and the XFree86 manual page for more information. @ 1.19 log @ Update: system boots fully after install, TERM + mount frobbing to be able to edit rc.conf no longer needed. Add a "Quick Install" section, using CD-ROM as an example. @ text @d1 1 a1 1 $NetBSD: install,v 1.18 1998/01/09 18:46:30 perry Exp $ d437 1 a437 1 After you the install sets containing the NetBSD distribution @ 1.18 log @RCS Id Police. @ text @d1 1 a1 1 $NetBSD$ d50 70 a119 1 2. Booting NetBSD d169 1 a169 1 3. Network configuration d183 1 a183 1 4. The hard disk to install on and its parameters. d215 1 a215 1 5. Partitioning the disk. d217 1 a217 1 5.1 Which portion of the disk to use. d226 1 a226 1 the following section and go to section 5.3, "Editing the d229 1 a229 1 5.2 Editing the Master Boot Record. d250 1 a250 1 5.3 Editing the NetBSD disklabel. d288 1 a288 1 6. Preparing your hard disk d313 1 a313 1 7. Getting the distribution sets. d354 1 a354 1 can continue to section 8 d356 1 a356 1 7.1 Installation using ftp d377 1 a377 1 7.2 Installation using NFS d398 1 a398 1 7.3 Installation from CD-ROM d408 1 a408 1 7.4 Installation from floppy d419 1 a419 1 7.5 Installation from an unmounted filesystem d428 1 a428 1 7.6 Installation from a local directory d435 1 a435 1 8. Extracting the distribution sets d456 1 a456 1 9. Finalizing your installation. d459 1 a459 20 You can now reboot the machine, and boot from harddisk. NetBSD will enter single-user mode, and you will be presented with a shell prompt. You should now edit the /etc/rc.conf file to configure the system to suit your needs. To do this, you might want to first make all local filesystems accessible and set the terminal type, so that, for example, vi will work properly. The following commands will do this: mount -a TERM=pc3 ; export TERM You should at least do the following in /etc/rc.conf: * Change rc_configured=NO to rc_configured=YES * Set the hostname in the 'hostname' line, e.g. hostname="somename" You are advised to take a look at the other items in the /etc/rc.conf file, and change them if you wish. After you have made and saved the changes, reboot the machine again. d466 3 a473 7 Some leftover files from the installation may be on your hard disk, depending on the procedure you followed. If you find any of the files, you should remove them: /.termcap /sysinst d476 6 @ 1.17 log @Don't advise to throw away /.profile. The one used during install will be overwritten by the etc set already. Also, add better instructions on how to configure things once sysinst is done. @ text @d1 2 @ 1.16 log @fix numerous typos, from Brian Baird @ text @d387 8 a394 5 Congratulations, you have successfully installed NetBSD _VER. When you reboot into NetBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. d396 19 a414 1 Some of the files in the NetBSD _VER distribution might need to be a422 1 /.profile @ 1.15 log @Remove extraneous line. @ text @d112 1 a112 1 4. The harddisk to install on and its parameters. d170 1 a170 1 the one that the BIOS will start from at boottime. d192 1 a192 1 block and fragment size, and the mountpoint. The type d217 1 a217 1 6. Preparing your harddisk d245 2 a246 2 on to your harddisk, for example by mounting the harddisk first, copying the kern.tgz file from d275 1 a275 1 load the sets on your harddisk, others will extract the sets d297 1 a297 1 and the accountname and password used to log into that d304 1 a304 1 from the remote site to your harddisk. d330 2 a331 2 the devicename for your CD-ROM player (usually 'cd0'), and directoryname on the CD-ROM where the distribution files are. d357 1 a357 1 7.6 Installation from a local directoy d398 1 a398 1 Some leftover files from the installation may be on your harddisk, @ 1.14 log @Update install docs for new install system. @ text @a0 2 The actual installation ======================= @ 1.13 log @bring closer to reality (but still needs much work) @ text @d1 53 a53 32 Installing NetBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The NetBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) If NetBSD will be sharing the disk with DOS or another operating system, you should have already completed the section of these notes that instructed you on how to prepare your hard disk. You should know the size of the NetBSD area of the disk and its offset from the beginning of the disk. You will need this information when setting up your NetBSD partitions. You should now be ready to install NetBSD. It might be handy for you to have a pencil, some paper, and a calculator handy. The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. d78 10 a87 7 messages. You will want to read them, to determine your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell the install tools what disk to install on. d96 116 a211 26 While booting, you will probably see several warnings. You should be warned that no swap space is present, and that init(8) cannot find /etc/rc. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a shell name, just hit return. You will be asked if you wish to install or upgrade your system or go to a shell prompt. Enter "install". You will be presented with a welcome message and a prompt, asking if you wish to proceed with the installation process. If you wish to proceed, enter "y" and hit return. You will be asked what type of disk driver you have. The valid options are listed by the install program, to make sure you get it right. If you're installing on an ST-506 or ESDI drive, you'll be asked if your disk supports automatic sector forwarding. If you are SURE that it does, reply affirmatively. Otherwise, the install program will automatically reserve space for bad144 tables. The install program will then tell you which disks of that type it can install on, and ask you which it should use. Reply with the name of your disk. (The first disk of the type you selected, either "wd0" for ST-506/ESDI/IDE disks, or "sd0" for SCSI disks, is the default.) d214 6 a219 67 default response is "mywd" or "mysd" depending on the type of your disk, and for most purposes it will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name. You will be prompted for your disk's geometry information, i.e. the number of bytes per sector, cylinders on the disk, tracks per cylinder (heads), and sectors per track. Enter them when they are requested. If you make a mistake, hit Control-C and when you get to the shell prompt, restart the install process by running the "install" command. Once you have entered this data, the install program will tell you the total size of your disk, in both sectors, and cylinders. Remember this number; if you're installing on the whole disk, you'll need it again soon. When describing your partitions, you will have the option of entering data about them in units of disk sectors or cylinders. If you choose to enter the information in units of sectors, remember that, for optimal performance, partitions should begin and end on cylinder boundaries. You will be asked about which units you wish to use, and you should reply with "c" for cylinders, or "s" for sectors. You will be asked for the size of the NetBSD portion of the disk. If you're installing on the whole disk, reply with the size of the disk, as printed earlier by the install program. If you're using only part of the disk, reply with the size that you specified in the partition editor. (Don't forget to enter the size in the units you specified in the last step!) If you are not installing on the whole disk, you will be asked fro the offset of the NetBSD partition from the beginning of the disk. Reply with the appropriate offset (again, in whichever units you specified), as determined by how you set up your disk using the partition editor. You will be asked to enter the size of your NetBSD root partition. It should be at least 13M, but if you are going to be doing development, 14-16M is a more desirable size. This size should be expressed in units of sectors or cylinders, depending on which you said you wanted to use. Next, you will be asked for the size of your swap partition. You should probably allocate twice as much swap space as you have real memory. Systems that will be heavily used should have more swap space allocated, and systems that will be lightly used can get by with less. If you want the system to be able to save crash dumps when it panics, you will need at least as much swap space as you have RAM. Again, this number should be expressed in units of sectors or cylinders, as appropriate. The install program will then ask you for information about the rest of the partitions you want on your disk. For most purposes, you will want only one more partition, "/usr". (Machines used as servers will probably also want /var as a separate partition. That can be done with these installation tools, but is not covered here.) The install program will tell you how much space there is left to be allocated in the NetBSD area of the disk, and, if you only want one more partition ("/usr"), you should enter it at the prompt when the installer asks you how large the next partition should be. It will then ask you for the name of the mount point for that partition. If you're doing a basic installation, that is "/usr". d223 2 a224 5 install NetBSD, your hard drive will be modified, and its contents may be scrambled at the whim of the install program. This is especially likely if you have given the install program incorrect information. If you are sure you want to proceed, enter "yes" at the prompt. d227 1 a227 1 systems you specified. The filesystems will be initialized to d229 6 a234 11 It will also create an /etc/fstab for your system, and mount all of the file systems under /mnt. (In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, and so on.) There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. You will be placed at a shell prompt ("#"). The task is to install the distribution sets. The flow of installation differs depending on your hardware resources, and on what media the distribution sets reside. d241 169 a409 221 be unloaded onto the drive. It must be extracted in addition to "base" and "etc" in order to have a minimally functioning system. To install from floppy: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that if your disk is still mounted under /mnt; you should probably pick a directory under /mnt/usr.) After you have picked a temporary directory, enter the "Load_fd" command, to load the distribution sets from your floppies. You will be asked which floppy drive to use. Enter "0" (zero) if you're using the first floppy drive (i.e. what DOS would call "A:"), or enter "1" if you're using the second (i.e. what DOS would call "B:") You will be prompted to insert a floppy into the drive, to have its contents copied to your hard disk. Do so, and hit return to begin copying. When that is done, read the remainder of the floppies that contain the distribution sets that you want to install, one by one. When the last is read, and you are being prompted for another, hit Control-C. Run the "Extract" command once for each distribution set you wish to install. For instance, if you wish to install the "kern" distribution set, followed by the "base" distribution set, and finally the "etc" distribution set, use the commands: Extract kern Extract base Extract etc For each extraction, it will ask you if the extraction should be verbose. If you reply affirmatively, it will print out the name of each file that's being extracted. (Note: if you know that you will be running low on disk space when installing NetBSD, you can load and extract one distribution set at a time. To do this, load only the floppies which contain the files for the first distribution set, extract them, and then change to the temporary directory and remove them with the command "rm set_name.??".) Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system. To install from tape: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. After you have picked a temporary directory, enter the "Load_tape" command, to load the distribution sets from tape. You will be asked which tape drive to use. The default is "rst0", which is correct if you're using the SCSI tape drive with the lowest SCSI ID number. (For the SCSI tape drive with the next lowest SCSI ID number, you should use "rst1", and so on.) You will be prompted to hit return when you have inserted the tape into the tape drive. When you do, the contents of the tape will be extracted into the temporary directory, and the names of the files being extracted will be printed. After the tape has been extracted, to go the directory containing the first distribution set you wish to install. (Depending on how you made the tape, it's probably a subdirectory of the temporary directory you specified above.) Once there, run the "Set_tmp_dir" command again, and accept its default answer by hitting return at the prompt. Use the "Extract" command to extract the distribution set. For instance, if you're extracting the "base" set, use the command: Extract base You will be asked if you wish the extraction to be verbose. If you reply affirmatively, the name of each file being extracted will be printed. Repeat the previous two steps for each distribution set you wish to install. Change to the set's directory, run "Set_tmp_dir", and then run "Extract " to extract the set. Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system. To install via FTP or NFS: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. Configure the appropriate ethernet interface (e.g. ed0, ep0, etc.) up, with a command like: ifconfig [netmask ] where "" is the interface name, like those listed above, and "" is the numeric IP address of the interface. If the interface has a special netmask, supply the word "netmask" at and that netmask at the end of the command line. (The brackets indicate that those arguments are optional.) For instance, to configure interface ed0 with IP address 129.133.10.10, use the command: ifconfig ed0 129.133.10.10 and to configure interface ep0 with IP address 128.32.240.167 and a special netmask, 0xffffff00, use the command: ifconfig ep0 128.32.240.167 netmask 0xffffff00 If your board selects software selection of the ethernet interface to use, you might have to add special "media" flags to the "ifconfig" command you use to configure your board to use the appropriate connector/media type, as in: ifconfig de0 10BaseT You may determine which media are supported on a given interface by typing "ifconfig -m". If the NFS server or FTP server is not on a directly- connected network, you need to set up a route to it using a command like: route add default where is your gateway's numeric IP address. If you are NFS-mounting the distribution sets, mount them on the temporary directory with a command like: mount -t nfs : where is the server's numeric IP address, is the path to the distribution files on the server, and is the name of the local temporary directory. Once this is done, proceed as if you had loaded the files from tape, changing to the appropriate directories, running "Set_tmp_dir", and running "Extract" as appropriate. If you are retrieving the distribution sets using ftp, change into the temporary directory, and execute the command: ftp where is once again the server's numeric IP address. Get the files with FTP, taking care to use binary mode when transferring the files. Once you have all of the files for the distribution sets that you wish to install, you can proceed using the instructions above, as if you had installed from a floppy. (Note that as with the floppy install, if you're short on disk space, you can transfer only one set at a time, extract it, then delete it, to save space.) Completing your installation: Once you have finished extracting all of the distribution sets that you wish to install, and are back at the "#" prompt, you are ready to configure your system. The configuration utility expects that you have installed the "kern", "base" and "etc" distribution sets. If you have not, you will not be able to run it successfully (nor will you have a functional system, in any case). To configure your newly-installed NetBSD system, run the command "Configure". It will ask you for the system's host name, domain name, and other network configuration information. It will set up your configuration files and make the device nodes for the newly-installed system. Congratulations, you have successfully installed NetBSD _VER. When you reboot into NetBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. Some of the files in the NetBSD _VER distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified, as well. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. @ 1.12 log @12G -> 13 @ text @d228 2 a229 2 install the "kern13" distribution set, followed by the "base13" distribution set, and finally the "etc13" d231 3 a233 3 Extract kern13 Extract base13 Extract etc13 d288 1 a288 1 set. For instance, if you're extracting the "base13" d290 1 a290 1 Extract base13 d339 3 a341 2 special flags to the "ifconfig" command you use. Consult the table below for the appropriate flags: d343 1 a343 14 Interface Type Connector Flags --------- ---- --------- ----- ed with WD/SMC* BNC [none necessary] ed with WD/SMC* UTP [none necessary] ed with WD/SMC* AUI link0 ed with 3c503 BNC [none necessary] ed with 3c503 AUI link0 ep BNC [none necessary] ep AUI link0 ep UTP link0 link1 * Older WD boards do not support software configuration, and must be configured via jumpers. These flags will have no effect on them. d345 2 a346 5 In other words, if, in the last example, the AUI port of the board were being used, you would use the command: ifconfig ep0 128.32.240.167 netmask 0xffffff00 link0 d394 2 a395 2 expects that you have installed the "kern13", "base13" and "etc13" distribution sets. If you have not, you will not be @ 1.12.2.1 log @sync to trunk -- not quite finished yet, though @ text @d228 2 a229 2 install the "kern" distribution set, followed by the "base" distribution set, and finally the "etc" d231 3 a233 3 Extract kern Extract base Extract etc d288 1 a288 1 set. For instance, if you're extracting the "base" d290 1 a290 1 Extract base d339 2 a340 3 special "media" flags to the "ifconfig" command you use to configure your board to use the appropriate connector/media type, as in: d342 14 a355 1 ifconfig de0 10BaseT d357 5 a361 2 You may determine which media are supported on a given interface by typing "ifconfig -m". d409 2 a410 2 expects that you have installed the "kern", "base" and "etc" distribution sets. If you have not, you will not be @ 1.12.2.2 log @pullup from trunk (fvdl) @ text @d1 32 a32 51 0. Introduction Using "sysinst", installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details to be complete. Do not let this discourage you, the install program is not hard to use. 0.1 Possible PCMCIA issues There is a serious bug that may make installation of NetBSD on PCMCIA machines difficult. This bug does not make USE of PCMCIA difficult once a machine is installed. If you do not have PCMCIA on your machine (PCMCIA is only really used on laptop machines), you can skip this section, and ignore the "[PCMCIA]" notes. This will explains how to work around the installation problem. It is anticipated that this bug will be fixed by NetBSD 1.4 What is the bug: The kernel keeps careful track of what interrupts and i/o ports are in use during autoconfiguration. It then allows the PCMCIA devices to pick unused interrupts and ports. Unfortunately, not all devices are included in the INSTALL kernels in order to save space. Let's say your laptop has a soundblaster device built in. The INSTALL kernel has no sound support. The PCMCIA code might allocate your soundblaster's IRQ and i/o ports to PCMCIA devices, causing them not to work. This is especially bad if one of the devices in question is your ethernet card. This problem will impact some, but not all, users of PCMCIA. If this bug is hurting you, watch the "[PCMCIA]" notes that will appear in this document. 1. General The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installation system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. 2. Booting NetBSD [PCMCIA]: unplug your PCMCIA devices, so that they won't be found by NetBSD. d57 7 a63 10 messages. This may take a little while, as NetBSD will be probing for a lot of types of hardware, You may want to read the boot messages, to notice your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell sysinst on which disk to install. The most important thing to know is that 'wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. 'sd0' is your first SCSI disk, sd1 the second, etc. d72 26 a97 116 Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 3. Network configuration [PCMCIA] You can skip this section, as you will only get data from floppy in the first part of the install. If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the utilities menu, and select the "Configure network option". If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using Domain Name Service (DNS), you can give an empty response in reply to answers relating to this. 4. The harddisk to install on and its parameters. To start the installation, select the menu option to install NetBSD from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like "wd0", "wd1", "sd0", or "sd1". sysinst next tries to figure out the real and BIOS geometry of your disk. It will present you with the values it found, if any, and will give you a chance to change them. Please note that if you change the values, sysinst WILL ALSO REINITIALIZE YOUR MBR. You will also be asked if you want to use the last cylinder of the disk. Originally, the last cylinder of the disk was used for diagnostic purposes, but this is usually not a concern anymore these days. You will be able to specify whether you want to skip the last cylinder anyway. Next, depending on whether you are using a "wdX" or a "sdX" disk, you will either be asked for the type of disk (wdX) you are using or you will be asked if you want to specify a fake geometry for your SCSI disk (sdX). The types of disk are be IDE, ST-506 or ESDI. If you're installing on an ST-506 or ESDI drive, you'll be asked if your disk supports automatic sector forwarding. If you are SURE that it does, reply affirmatively. Otherwise, the install program will automatically reserve space for bad144 tables. 5. Partitioning the disk. 5.1 Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these. If you want to use the entire disk for NetBSD, you can skip the following section and go to section 5.3, "Editing the NetBSD disklabel". 5.2 Editing the Master Boot Record. First, you will be prompted to specify the units of size that you want to express the sizes of the partitions in. You can either pick megabytes, cylinders or sectors. After this, you will be presented with the current values stored in the MBR, and will be given the opportunity to change, create or delete partitions. For each partition you can set the type, the start and the size. Setting the type to 'unused' will delete a partition. You can also mark a partition as active, meaning that this is the one that the BIOS will start from at boottime. Be sure to mark the partition you want to boot from as active! After you are done editing the MBR, a sanity check will be done, checking for partitions that overlap. If everything is ok, you can go on to the next step, editing the NetBSD disklabel. 5.3 Editing the NetBSD disklabel. The partition table of a NetBSD part of a disk is called a 'disklabel'. There are 3 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X and Custom. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. The last option lets you specify everything yourself. You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mountpoint. The type that NetBSD uses for normal file storage is called "4.2BSD". A swap partition has a special type called "swap". You can also specify a partition as type "msdos". This is useful if you share the disk with MS-DOS or Windows95, NetBSD is able to access the files on these partitions. You can use the values from the MBR for the MS-DOS part of the disk to specify the partition of type "msdos" (you don't have to do this now, you can always re-edit the disklabel to add this once you have installed NetBSD). Some partitions in the disklabel have a fixed purpose. Partition 'a' is always the root partition, 'b' is the swap partition, 'c' is the entire NetBSD part of the disk, and 'd' is the whole disk. Partitions 'e'-'h' are available for other use. Traditionally, 'e' is the partition mounted on the /usr directory, but this is historical practice, not a fixed value. d100 67 a166 6 default response is "mydisk". For most purposes this will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name. 6. Preparing your harddisk d170 5 a174 2 install NetBSD, your hard drive will be modified. If you are sure you want to proceed, enter "yes" at the prompt. d177 1 a177 1 systems you specified. The filesystems will be initialized to d179 11 a189 6 You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing 'return'. d196 221 a416 169 be unloaded onto the drive. So, you can not boot from your hard drive yet at this point. 7. Getting the distribution sets. [PCMCIA] Load a kernel tar file (i.e. the kern.tgz set file) on to your harddisk, for example by mounting the harddisk first, copying the kern.tgz file from floppy and unpacking it. Example: mount /dev/wd0a /mnt cd /mnt mount -t msdos /dev/fd0a /mnt2 cp /mnt2/kern.* . umount /mnt2 cat kern.* | tar vxzf - Then halt the machine using the 'halt' command. Power the machine down, and re-insert all the PCMCIA devices. Remove any floppy from the floppy drive. Start the machine up. After booting NetBSD, you will be presented with the main sysinst menu. Choose the option to re-install sets. Wait for the filesystem checks that it will do to finish, and then proceed as described below. The NetBSD distribution consists of a number of 'sets', that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your harddisk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to section 8 7.1 Installation using ftp To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press 'return' in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, and the accountname and password used to log into that host using ftp. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the ftp server. sysinst will proceed to transfer all the default set files from the remote site to your harddisk. 7.2 Installation using NFS To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press 'return' in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the NFS server. 7.3 Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the devicename for your CD-ROM player (usually 'cd0'), and directoryname on the CD-ROM where the distribution files are. sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 7.4 Installation from floppy Because the installation sets are too big to fit on one floppy, the floppies are expected to be filled with the split set files. The floppies are expected to be in MS-DOS format. You will be asked for a directory where the sets should be reassembled. Then you will be prompted to insert the floppies containing the split sets. This process will continue until all the sets have been loaded from floppy. 7.5 Installation from an unmounted filesystem In order to install from a local filesystem, you will need to specify the device that the filesystem resides on (for example 'wd1e'), the type of the filesystem, and the directory on the specified filesystem where the sets are located. sysinst will then check if it can indeed access the sets at that location. 7.6 Installation from a local directoy This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a filesystem that is already accessible. sysinst will ask you for the name of this directory. 8. Extracting the distribution sets After you the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed ("kern", "base" and "etc"), they will not be shown in this selection menu. Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. 9. Finalizing your installation. Congratulations, you have successfully installed NetBSD _VER. When you reboot into NetBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. Some of the files in the NetBSD _VER distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified, as well. Some leftover files from the installation may be on your harddisk, depending on the procedure you followed. If you find any of the files, you should remove them: /.profile /.termcap /sysinst If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. @ 1.12.2.3 log @pullup spelling fixes & typos from trunk. @ text @d112 1 a112 1 4. The hard disk to install on and its parameters. d170 1 a170 1 the one that the BIOS will start from at boot time. d192 1 a192 1 block and fragment size, and the mount point. The type d217 1 a217 1 6. Preparing your hard disk d245 2 a246 2 on to your hard disk, for example by mounting the hard disk first, copying the kern.tgz file from d275 1 a275 1 load the sets on your hard disk, others will extract the sets d297 1 a297 1 and the account name and password used to log into that d304 1 a304 1 from the remote site to your hard disk. d330 2 a331 2 the device name for your CD-ROM player (usually 'cd0'), and directory name on the CD-ROM where the distribution files are. d357 1 a357 1 7.6 Installation from a local directory d398 1 a398 1 Some leftover files from the installation may be on your hard disk, @ 1.12.2.4 log @pullup from trunk (fvdl) @ text @d387 5 a391 8 Congratulations, you have successfully installed NetBSD _VER. You can now reboot the machine, and boot from harddisk. NetBSD will enter single-user mode, and you will be presented with a shell prompt. You should now edit the /etc/rc.conf file to configure the system to suit your needs. To do this, you might want to first make all local filesystems accessible and set the terminal type, so that, for example, vi will work properly. The following commands will do this: d393 1 a393 19 mount -a TERM=pc3 ; export TERM You should at least do the following in /etc/rc.conf: * Change rc_configured=NO to rc_configured=YES * Set the hostname in the 'hostname' line, e.g. hostname="somename" You are advised to take a look at the other items in the /etc/rc.conf file, and change them if you wish. After you have made and saved the changes, reboot the machine again. After reboot, you can log in "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. Some other files in the NetBSD _VER distribution might need to be d402 1 @ 1.12.2.5 log @Pull up 1.19, per request of fvdl. @ text @d48 1 a48 70 2. Quick install First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to section 3. This section describes a basic installation, using a CD-ROM install as an example. 2.1 What you need. * The distribution sets (in this example, they are on CD). * One 1.44M 3.5" floppy. * A PC with a 386 or newer processor, a CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of 4Mb of memory installed. * The harddisk should have at least 70 + N megabytes of space free, where N is the number of megabytes of main memory in your system. If you wish to install the X window system as well, you will need at least 60Mb more. 2.2 Creating a bootfloppy. * You can create the floppy needed for installation under DOS or Windows. Supposing your 1.44M floppy drive is drive A:, and your CD is drive E: do the following from an MS-DOS command prompt: e: cd \NetBSD-_VER\installation\misc rawrite When asked for a source filename, answer ..\floppy\boot.fs When asked for a destination drive answer a 2.3 The installation * Insert the bootfloppy you just created. Restart the PC. You will be presented with a menu. * If you wish, you can configure some network settings immediately by choosing the "utilities" menu and then "configure network". This isn't needed, but more convenient to do now. Go back to the main menu. * Choose "install" * You will be guided through some steps regarding the setup of your harddisk, and parts to install. When in doubt, refer to the rest of this document for details. * After your disk has been prepared, choose CD-ROM as the medium. The default values for the path and device should be ok. * After all the files have been unpacked, go back to the main menu and select "reboot", after you have removed the bootfloppy from the drive. * NetBSD will now boot. You should log in as root, and set a password for that account. You are also advised to edit the file "/etc/rc.conf" to match your system needs. * Your installation is now complete. * For configuring the X window system, if installed, see the files in /usr/X11R6/lib/X11/doc. Further information can be found on http://www.xfree86.org/ 3. Booting NetBSD d98 1 a98 1 4. Network configuration d112 1 a112 1 5. The hard disk to install on and its parameters. d144 1 a144 1 6. Partitioning the disk. d146 1 a146 1 6.1 Which portion of the disk to use. d155 1 a155 1 the following section and go to section 6.3, "Editing the d158 1 a158 1 6.2 Editing the Master Boot Record. d179 1 a179 1 6.3 Editing the NetBSD disklabel. d217 1 a217 1 7. Preparing your hard disk d242 1 a242 1 8. Getting the distribution sets. d283 1 a283 1 can continue to section 9 d285 1 a285 1 8.1 Installation using ftp d306 1 a306 1 8.2 Installation using NFS d327 1 a327 1 8.3 Installation from CD-ROM d337 1 a337 1 8.4 Installation from floppy d348 1 a348 1 8.5 Installation from an unmounted filesystem d357 1 a357 1 8.6 Installation from a local directory d364 1 a364 1 9. Extracting the distribution sets d385 1 a385 1 10. Finalizing your installation. d388 20 a407 1 You can now reboot the machine, and boot from harddisk. a413 3 You should now edit the /etc/rc.conf file to configure the system to suit your needs, and then reboot the system again. d419 7 a427 6 If you have installed the X window system, look at the files in /usr/X11R6/lib/X11/doc for information. You will need to set up a configuration file. An example of such a file is /usr/X11R6/lib/X11/XF86Config.eg. See http://www.xfree86.org/ and the XFree86 manual page for more information. @ 1.11 log @use _VER for NetBSD version; note that fileset names must still be updated by hand. @ text @d228 2 a229 2 install the "kern12G" distribution set, followed by the "base12G" distribution set, and finally the "etc12G" d231 3 a233 3 Extract kern12G Extract base12G Extract etc12G d288 1 a288 1 set. For instance, if you're extracting the "base12G" d290 1 a290 1 Extract base12G d409 2 a410 2 expects that you have installed the "kern12G", "base12G" and "etc12G" distribution sets. If you have not, you will not be @ 1.10 log @update for 1.2G @ text @d420 1 a420 1 Congratulations, you have successfully installed NetBSD 1.2G. When you d426 1 a426 1 Some of the files in the NetBSD 1.2G distribution might need to be @ 1.9 log @fix silly typo @ text @d34 6 a39 6 Boot your machine using the appropriate installation floppy. The boot loader will start, and will print a countdown and begin booting. You will likely see one "file not found" warning from the boot loader -- ignore this as it is normal, and indicates the boot loader failed to find a normal kernel to boot before trying to boot a compressed kernel. d78 3 d228 2 a229 2 install the "kern12D" distribution set, followed by the "base12" distribution set, and finally the "etc12" d231 3 a233 3 Extract kern12D Extract base12 Extract etc12 d288 1 a288 1 set. For instance, if you're extracting the "base12" d290 1 a290 1 Extract base12 d409 2 a410 2 expects that you have installed the "kern12D", "base12" and "etc12" distribution sets. If you have not, you will not be d420 1 a420 1 Congratulations, you have successfully installed NetBSD 1.2D. When you d426 1 a426 1 Some of the files in the NetBSD 1.2D distribution might need to be @ 1.8 log @Update for the new ramdisk based install, with the installed kernel implicitly moved into the kern??? set. @ text @d34 6 a39 6 Boot your machine using of the appropriate installation floppy. The boot loader will start, and will print a countdown and begin booting. You will likely see one "file not found" warning from the boot loader -- ignore this as it is normal, and indicates the boot loader failed to find a normal kernel to boot before trying to boot a compressed kernel. @ 1.7 log @merge in 1.2 branch @ text @d34 12 a45 6 Boot your machine using of the appropriate kernel-copy floppy. When presented with the boot prompt (the prompt begins with "Boot" and ends with ":-"), hit return. If the boot prompt does not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the kernel-copy floppy image to a different disk, and using that. d54 1 a54 13 probably around a minute or so. After its loaded, you will be presented with the message: "Insert file system floppy" If you do not see that message after a reasonable time has elapsed, or the spinning cursor has stopped and nothing further has happened, either your boot floppy is bad or you are having hardware problems, and should proceed as outlined above. Once you have reached that prompt, remove the kernel-copy floppy from the floppy drive. Make sure that the installation disk (the "inst-12" floppy) is writable, insert it into the floppy drive, and hit any key. d65 7 d183 13 a195 6 You will be placed at a shell prompt ("#"). The remaining tasks are to copy the kernel from the kernel copy floppy to the hard drive's root filesystem and install the distribution sets. The flow of installation differs depending on your hardware resources, and on what media the distribution sets reside. a197 8 If you only have only one floppy drive, the order of installation is different. Follow the directions in the "Kernel installation" section which will help you install a kernel on the hard drive and then boot off the hard drive, then continue with the rest of the process described here to install the distribution sets from floppy: d212 2 a213 3 you're using the second. (Remember that you CANNOT use the floppy drive that you booted from. If you booted from "A:", you must load from "B:".) d223 6 a228 5 Run the "Extract" command once for each distribution set you wish to install. For instance, if you wish to install the "base12" distribution set, followed by the "man12" distribution set, and finally the "etc12" distribution set, use the commands: a229 1 Extract man12 d402 13 a414 41 Once you have finished extracting all of the distribution sets that you wish to install, and are back at the "#" prompt, you are ready to configure your system. The configuration utility expects that you have installed the "base12" and "etc12" distribution sets. If you have not, you will not be able to run it successfully (nor will you have a functional system, in any case). To configure your newly-installed NetBSD system, run the command "Configure". It will ask you for the system's host name, domain name, and other network configuration information. It will set up your configuration files and make the device nodes for the newly-installed system. Kernel Installation: Enter "halt" at the prompt to halt the system. When the system is halted, remove the "inst-12" floppy from the floppy drive, and replace it with the NetBSD 1.2 kernel-copy floppy that you previously booted from. Reboot with that floppy. with that floppy. Once again, you will be prompted to insert a file system floppy. DO NOT replace the kernel-copy floppy, just hit any key. Again, While booting, you may see several warnings. You may be warned that no swap space is present, that init(8) cannot find /etc/rc, and that one or more databases with names like "pwd.db" cannot be found. Do not be alarmed, as, again, these are completely normal. Hit return at the prompt asking you for a shell name. You will be presented with a shell prompt, at which you should enter the "copy_kernel" command. It will ask you what partition to copy the kernel to, and you should reply with the name of your root partition (e.g. sd0a or wd0a). You will be asked if you are sure that you want to copy the kernel. Reply affirmatively, and it will check the file system on your root partition, mount it, and copy the kernel. Once the kernel is copied, you should use "halt" to halt the system. a415 2 Once the system is halted, remove the kernel-copy floppy from the floppy disk drive, and hit any key to reboot. d417 1 a417 1 Congratulations, you have successfully installed NetBSD 1.2. When you d423 1 a423 1 Some of the files in the NetBSD 1.2 distribution might need to be @ 1.6 log @merge in changes from 1.1 release branch @ text @d59 1 a59 1 disk (the "inst-11" floppy) is writable, insert it into the d226 2 a227 2 install the "base11" distribution set, followed by the "man11" distribution set, and finally the "etc11" d229 3 a231 3 Extract base11 Extract man11 Extract etc11 d286 1 a286 1 set. For instance, if you're extracting the "base11" d288 1 a288 1 Extract base11 d406 1 a406 1 expects that you have installed the "base11" and "etc11" d418 2 a419 2 system is halted, remove the "inst-11" floppy from the floppy drive, and replace it with the NetBSD 1.1 kernel-copy floppy d448 1 a448 1 Congratulations, you have successfully installed NetBSD 1.1. When you d454 1 a454 1 Some of the files in the NetBSD 1.1 distribution might need to be @ 1.6.4.1 log @these should be as ready for the 1.2 release as I can get them, starting at the last minute @ text @d59 1 a59 1 disk (the "inst-12" floppy) is writable, insert it into the d226 2 a227 2 install the "base12" distribution set, followed by the "man12" distribution set, and finally the "etc12" d229 3 a231 3 Extract base12 Extract man12 Extract etc12 d286 1 a286 1 set. For instance, if you're extracting the "base12" d288 1 a288 1 Extract base12 d406 1 a406 1 expects that you have installed the "base12" and "etc12" d418 2 a419 2 system is halted, remove the "inst-12" floppy from the floppy drive, and replace it with the NetBSD 1.2 kernel-copy floppy d448 1 a448 1 Congratulations, you have successfully installed NetBSD 1.2. When you d454 1 a454 1 Some of the files in the NetBSD 1.2 distribution might need to be @ 1.6.4.2 log @1.2 -> 1.2.1, foo12 -> foo121 @ text @d59 1 a59 1 disk (the "inst121" floppy) is writable, insert it into the d226 2 a227 2 install the "base121" distribution set, followed by the "man121" distribution set, and finally the "etc121" d229 3 a231 3 Extract base121 Extract man121 Extract etc121 d286 1 a286 1 set. For instance, if you're extracting the "base121" d288 1 a288 1 Extract base121 d406 1 a406 1 expects that you have installed the "base121" and "etc121" d418 2 a419 2 system is halted, remove the "inst121" floppy from the floppy drive, and replace it with the NetBSD 1.2.1 kernel-copy floppy d448 1 a448 1 Congratulations, you have successfully installed NetBSD 1.2.1. When you d454 1 a454 1 Some of the files in the NetBSD 1.2.1 distribution might need to be @ 1.5 log @clean up adam's work. @ text @d59 1 a59 1 disk (the "inst-10" floppy) is writable, insert it into the d226 2 a227 2 install the "base10" distribution set, followed by the "man10" distribution set, and finally the "etc10" d229 3 a231 3 Extract base10 Extract man10 Extract etc10 d286 1 a286 1 set. For instance, if you're extracting the "base10" d288 1 a288 1 Extract base10 d406 1 a406 1 expects that you have installed the "base10" and "etc10" d418 2 a419 2 system is halted, remove the "inst-10" floppy from the floppy drive, and replace it with the NetBSD 1.0 kernel-copy floppy d448 1 a448 1 Congratulations, you have successfully installed NetBSD 1.0. When you d454 1 a454 1 Some of the files in the NetBSD 1.0 distribution might need to be @ 1.5.2.1 log @file install was added on branch netbsd-1-0 on 1994-10-18 07:38:47 +0000 @ text @d1 459 @ 1.5.2.2 log @clean up adam's work. @ text @a0 459 Installing NetBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The NetBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) If NetBSD will be sharing the disk with DOS or another operating system, you should have already completed the section of these notes that instructed you on how to prepare your hard disk. You should know the size of the NetBSD area of the disk and its offset from the beginning of the disk. You will need this information when setting up your NetBSD partitions. You should now be ready to install NetBSD. It might be handy for you to have a pencil, some paper, and a calculator handy. The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. Boot your machine using of the appropriate kernel-copy floppy. When presented with the boot prompt (the prompt begins with "Boot" and ends with ":-"), hit return. If the boot prompt does not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the kernel-copy floppy image to a different disk, and using that. If that doesn't work, try booting after disabling your CPU's internal and external caches (if any). If it still doesn't work, NetBSD probably can't be run on your hardware. This can probably be considered a bug, so you might want to report it. If you do, please include as many details about your system configuration as you can. It will take a while to load the kernel from the floppy, probably around a minute or so. After its loaded, you will be presented with the message: "Insert file system floppy" If you do not see that message after a reasonable time has elapsed, or the spinning cursor has stopped and nothing further has happened, either your boot floppy is bad or you are having hardware problems, and should proceed as outlined above. Once you have reached that prompt, remove the kernel-copy floppy from the floppy drive. Make sure that the installation disk (the "inst-10" floppy) is writable, insert it into the floppy drive, and hit any key. You will then be presented with the NetBSD kernel boot messages. You will want to read them, to determine your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell the install tools what disk to install on. While booting, you will probably see several warnings. You should be warned that no swap space is present, and that init(8) cannot find /etc/rc. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a shell name, just hit return. You will be presented with a welcome message and a prompt, asking if you wish to proceed with the installation process. If you wish to proceed, enter "y" and hit return. You will be asked what type of disk driver you have. The valid options are listed by the install program, to make sure you get it right. If you're installing on an ST-506 or ESDI drive, you'll be asked if your disk supports automatic sector forwarding. If you are SURE that it does, reply affirmatively. Otherwise, the install program will automatically reserve space for bad144 tables. The install program will then tell you which disks of that type it can install on, and ask you which it should use. Reply with the name of your disk. (The first disk of the type you selected, either "wd0" for ST-506/ESDI/IDE disks, or "sd0" for SCSI disks, is the default.) You will then be asked to name your disk's disklabel. The default response is "mywd" or "mysd" depending on the type of your disk, and for most purposes it will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name. You will be prompted for your disk's geometry information, i.e. the number of bytes per sector, cylinders on the disk, tracks per cylinder (heads), and sectors per track. Enter them when they are requested. If you make a mistake, hit Control-C and when you get to the shell prompt, restart the install process by running the "install" command. Once you have entered this data, the install program will tell you the total size of your disk, in both sectors, and cylinders. Remember this number; if you're installing on the whole disk, you'll need it again soon. When describing your partitions, you will have the option of entering data about them in units of disk sectors or cylinders. If you choose to enter the information in units of sectors, remember that, for optimal performance, partitions should begin and end on cylinder boundaries. You will be asked about which units you wish to use, and you should reply with "c" for cylinders, or "s" for sectors. You will be asked for the size of the NetBSD portion of the disk. If you're installing on the whole disk, reply with the size of the disk, as printed earlier by the install program. If you're using only part of the disk, reply with the size that you specified in the partition editor. (Don't forget to enter the size in the units you specified in the last step!) If you are not installing on the whole disk, you will be asked fro the offset of the NetBSD partition from the beginning of the disk. Reply with the appropriate offset (again, in whichever units you specified), as determined by how you set up your disk using the partition editor. You will be asked to enter the size of your NetBSD root partition. It should be at least 13M, but if you are going to be doing development, 14-16M is a more desirable size. This size should be expressed in units of sectors or cylinders, depending on which you said you wanted to use. Next, you will be asked for the size of your swap partition. You should probably allocate twice as much swap space as you have real memory. Systems that will be heavily used should have more swap space allocated, and systems that will be lightly used can get by with less. If you want the system to be able to save crash dumps when it panics, you will need at least as much swap space as you have RAM. Again, this number should be expressed in units of sectors or cylinders, as appropriate. The install program will then ask you for information about the rest of the partitions you want on your disk. For most purposes, you will want only one more partition, "/usr". (Machines used as servers will probably also want /var as a separate partition. That can be done with these installation tools, but is not covered here.) The install program will tell you how much space there is left to be allocated in the NetBSD area of the disk, and, if you only want one more partition ("/usr"), you should enter it at the prompt when the installer asks you how large the next partition should be. It will then ask you for the name of the mount point for that partition. If you're doing a basic installation, that is "/usr". YOU ARE NOW AT THE POINT OF NO RETURN. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified, and its contents may be scrambled at the whim of the install program. This is especially likely if you have given the install program incorrect information. If you are sure you want to proceed, enter "yes" at the prompt. The install program will now label your disk and make the file systems you specified. The filesystems will be initialized to contain NetBSD bootstrapping binaries and configuration files. It will also create an /etc/fstab for your system, and mount all of the file systems under /mnt. (In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, and so on.) There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. You will be placed at a shell prompt ("#"). The remaining tasks are to copy the kernel from the kernel copy floppy to the hard drive's root filesystem and install the distribution sets. The flow of installation differs depending on your hardware resources, and on what media the distribution sets reside. To install from floppy: If you only have only one floppy drive, the order of installation is different. Follow the directions in the "Kernel installation" section which will help you install a kernel on the hard drive and then boot off the hard drive, then continue with the rest of the process described here to install the distribution sets from floppy: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that if your disk is still mounted under /mnt; you should probably pick a directory under /mnt/usr.) After you have picked a temporary directory, enter the "Load_fd" command, to load the distribution sets from your floppies. You will be asked which floppy drive to use. Enter "0" (zero) if you're using the first floppy drive (i.e. what DOS would call "A:"), or enter "1" if you're using the second. (Remember that you CANNOT use the floppy drive that you booted from. If you booted from "A:", you must load from "B:".) You will be prompted to insert a floppy into the drive, to have its contents copied to your hard disk. Do so, and hit return to begin copying. When that is done, read the remainder of the floppies that contain the distribution sets that you want to install, one by one. When the last is read, and you are being prompted for another, hit Control-C. Run the "Extract" command once for each distribution set you wish to install. For instance, if you wish to install the "base10" distribution set, followed by the "man10" distribution set, and finally the "etc10" distribution set, use the commands: Extract base10 Extract man10 Extract etc10 For each extraction, it will ask you if the extraction should be verbose. If you reply affirmatively, it will print out the name of each file that's being extracted. (Note: if you know that you will be running low on disk space when installing NetBSD, you can load and extract one distribution set at a time. To do this, load only the floppies which contain the files for the first distribution set, extract them, and then change to the temporary directory and remove them with the command "rm set_name.??".) Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system. To install from tape: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. After you have picked a temporary directory, enter the "Load_tape" command, to load the distribution sets from tape. You will be asked which tape drive to use. The default is "rst0", which is correct if you're using the SCSI tape drive with the lowest SCSI ID number. (For the SCSI tape drive with the next lowest SCSI ID number, you should use "rst1", and so on.) You will be prompted to hit return when you have inserted the tape into the tape drive. When you do, the contents of the tape will be extracted into the temporary directory, and the names of the files being extracted will be printed. After the tape has been extracted, to go the directory containing the first distribution set you wish to install. (Depending on how you made the tape, it's probably a subdirectory of the temporary directory you specified above.) Once there, run the "Set_tmp_dir" command again, and accept its default answer by hitting return at the prompt. Use the "Extract" command to extract the distribution set. For instance, if you're extracting the "base10" set, use the command: Extract base10 You will be asked if you wish the extraction to be verbose. If you reply affirmatively, the name of each file being extracted will be printed. Repeat the previous two steps for each distribution set you wish to install. Change to the set's directory, run "Set_tmp_dir", and then run "Extract " to extract the set. Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system. To install via FTP or NFS: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. Configure the appropriate ethernet interface (e.g. ed0, ep0, etc.) up, with a command like: ifconfig [netmask ] where "" is the interface name, like those listed above, and "" is the numeric IP address of the interface. If the interface has a special netmask, supply the word "netmask" at and that netmask at the end of the command line. (The brackets indicate that those arguments are optional.) For instance, to configure interface ed0 with IP address 129.133.10.10, use the command: ifconfig ed0 129.133.10.10 and to configure interface ep0 with IP address 128.32.240.167 and a special netmask, 0xffffff00, use the command: ifconfig ep0 128.32.240.167 netmask 0xffffff00 If your board selects software selection of the ethernet interface to use, you might have to add special flags to the "ifconfig" command you use. Consult the table below for the appropriate flags: Interface Type Connector Flags --------- ---- --------- ----- ed with WD/SMC* BNC [none necessary] ed with WD/SMC* UTP [none necessary] ed with WD/SMC* AUI link0 ed with 3c503 BNC [none necessary] ed with 3c503 AUI link0 ep BNC [none necessary] ep AUI link0 ep UTP link0 link1 * Older WD boards do not support software configuration, and must be configured via jumpers. These flags will have no effect on them. In other words, if, in the last example, the AUI port of the board were being used, you would use the command: ifconfig ep0 128.32.240.167 netmask 0xffffff00 link0 If the NFS server or FTP server is not on a directly- connected network, you need to set up a route to it using a command like: route add default where is your gateway's numeric IP address. If you are NFS-mounting the distribution sets, mount them on the temporary directory with a command like: mount -t nfs : where is the server's numeric IP address, is the path to the distribution files on the server, and is the name of the local temporary directory. Once this is done, proceed as if you had loaded the files from tape, changing to the appropriate directories, running "Set_tmp_dir", and running "Extract" as appropriate. If you are retrieving the distribution sets using ftp, change into the temporary directory, and execute the command: ftp where is once again the server's numeric IP address. Get the files with FTP, taking care to use binary mode when transferring the files. Once you have all of the files for the distribution sets that you wish to install, you can proceed using the instructions above, as if you had installed from a floppy. (Note that as with the floppy install, if you're short on disk space, you can transfer only one set at a time, extract it, then delete it, to save space.) Once you have finished extracting all of the distribution sets that you wish to install, and are back at the "#" prompt, you are ready to configure your system. The configuration utility expects that you have installed the "base10" and "etc10" distribution sets. If you have not, you will not be able to run it successfully (nor will you have a functional system, in any case). To configure your newly-installed NetBSD system, run the command "Configure". It will ask you for the system's host name, domain name, and other network configuration information. It will set up your configuration files and make the device nodes for the newly-installed system. Kernel Installation: Enter "halt" at the prompt to halt the system. When the system is halted, remove the "inst-10" floppy from the floppy drive, and replace it with the NetBSD 1.0 kernel-copy floppy that you previously booted from. Reboot with that floppy. with that floppy. Once again, you will be prompted to insert a file system floppy. DO NOT replace the kernel-copy floppy, just hit any key. Again, While booting, you may see several warnings. You may be warned that no swap space is present, that init(8) cannot find /etc/rc, and that one or more databases with names like "pwd.db" cannot be found. Do not be alarmed, as, again, these are completely normal. Hit return at the prompt asking you for a shell name. You will be presented with a shell prompt, at which you should enter the "copy_kernel" command. It will ask you what partition to copy the kernel to, and you should reply with the name of your root partition (e.g. sd0a or wd0a). You will be asked if you are sure that you want to copy the kernel. Reply affirmatively, and it will check the file system on your root partition, mount it, and copy the kernel. Once the kernel is copied, you should use "halt" to halt the system. Once the system is halted, remove the kernel-copy floppy from the floppy disk drive, and hit any key to reboot. Congratulations, you have successfully installed NetBSD 1.0. When you reboot into NetBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. Some of the files in the NetBSD 1.0 distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified, as well. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. @ 1.5.4.1 log @update the install notes for 1.1 @ text @d59 1 a59 1 disk (the "inst-11" floppy) is writable, insert it into the d226 2 a227 2 install the "base11" distribution set, followed by the "man11" distribution set, and finally the "etc11" d229 3 a231 3 Extract base11 Extract man11 Extract etc11 d286 1 a286 1 set. For instance, if you're extracting the "base11" d288 1 a288 1 Extract base11 d406 1 a406 1 expects that you have installed the "base11" and "etc11" d418 2 a419 2 system is halted, remove the "inst-11" floppy from the floppy drive, and replace it with the NetBSD 1.1 kernel-copy floppy d448 1 a448 1 Congratulations, you have successfully installed NetBSD 1.1. When you d454 1 a454 1 Some of the files in the NetBSD 1.1 distribution might need to be @ 1.4 log @doc update...needs wordsmithing @ text @d175 13 a187 12 It will also create an /etc/fstab for your system, and mount all of the file systems under /mnt. (In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, and so on.) There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. You will be placed at a shell prompt ("#"). The remaining tasks are to copy the kernel from the kernel copy floppy to the hard drive's root filesystem and install the distribution sets. The flow of installation differs depending on your hardware resources, and on what media the distribution sets reside. d191 7 a197 6 installation is different. Follow the directions in the "Kernel installation" section which will help you install a kernel on the hard drive and then boot off the hard drive. Then continue with the rest of the process described here to install the distribution sets from floppy: d202 2 a203 2 that if your disk is still mounted under /mnt; you should probably pick a directory under /mnt/usr.) d417 4 a420 4 Enter "halt" at the prompt to halt the system. When the system is halted, remove the "inst-10" floppy from the floppy drive, and replace it with the NetBSD 1.0 kernel-copy floppy that you previously booted from. Reboot @ 1.3 log @clarifications about lack of 1-floppy-drive install support. @ text @d173 14 a186 11 systems you specified. It will also create an /etc/fstab for your system, and mount all of the file systems under /mnt. (In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, and so on.) There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. You will be placed at a shell prompt ("#"), and from there you have to load and install the distribution sets. How you do this depends on which installation medium you've chosen; instructions for the various types are below. d189 7 a195 6 NOTE THAT THE NetBSD 1.0 DISTRIBUTION DOES _NOT_ SUPPORT INSTALLATION VIA FLOPPY ON MACHINES WITH ONE FLOPPY DRIVE. If you only have one floppy drive, you'll have to use a different method of installation. This will be fixed in the future. d200 2 a201 3 that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. d413 3 a415 2 Once your system is configured, you must install a kernel on your hard disk. Enter "halt" at the prompt to halt the @ 1.2 log @clarify and fix typo @ text @d186 6 d207 3 a209 1 you're using the second. @ 1.1 log @Initial revision @ text @d329 3 a331 3 ed with WD/SMC BNC [none necessary] ed with WD/SMC UTP [none necessary] ed with WD/SMC AUI link0 d338 5 a342 1 In other words, if, in the last example, the AUP port @ 1.1.1.1 log @install notes build goop @ text @@