head 1.18; access; symbols netbsd-11-0-RC4:1.18 netbsd-11-0-RC3:1.18 netbsd-11-0-RC2:1.18 netbsd-11-0-RC1:1.18 perseant-exfatfs-base-20250801:1.18 netbsd-11:1.18.0.60 netbsd-11-base:1.18 netbsd-10-1-RELEASE:1.18 perseant-exfatfs-base-20240630:1.18 perseant-exfatfs:1.18.0.58 perseant-exfatfs-base:1.18 netbsd-8-3-RELEASE:1.18 netbsd-9-4-RELEASE:1.18 netbsd-10-0-RELEASE:1.18 netbsd-10-0-RC6:1.18 netbsd-10-0-RC5:1.18 netbsd-10-0-RC4:1.18 netbsd-10-0-RC3:1.18 netbsd-10-0-RC2:1.18 netbsd-10-0-RC1:1.18 netbsd-10:1.18.0.56 netbsd-10-base:1.18 netbsd-9-3-RELEASE:1.18 cjep_sun2x-base1:1.18 cjep_sun2x:1.18.0.54 cjep_sun2x-base:1.18 cjep_staticlib_x-base1:1.18 netbsd-9-2-RELEASE:1.18 cjep_staticlib_x:1.18.0.52 cjep_staticlib_x-base:1.18 netbsd-9-1-RELEASE:1.18 phil-wifi-20200421:1.18 phil-wifi-20200411:1.18 is-mlppp:1.18.0.50 is-mlppp-base:1.18 phil-wifi-20200406:1.18 netbsd-8-2-RELEASE:1.18 netbsd-9-0-RELEASE:1.18 netbsd-9-0-RC2:1.18 netbsd-9-0-RC1:1.18 phil-wifi-20191119:1.18 netbsd-9:1.18.0.48 netbsd-9-base:1.18 phil-wifi-20190609:1.18 netbsd-8-1-RELEASE:1.18 netbsd-8-1-RC1:1.18 pgoyette-compat-merge-20190127:1.18 pgoyette-compat-20190127:1.18 pgoyette-compat-20190118:1.18 pgoyette-compat-1226:1.18 pgoyette-compat-1126:1.18 pgoyette-compat-1020:1.18 pgoyette-compat-0930:1.18 pgoyette-compat-0906:1.18 netbsd-7-2-RELEASE:1.18 pgoyette-compat-0728:1.18 netbsd-8-0-RELEASE:1.18 phil-wifi:1.18.0.46 phil-wifi-base:1.18 pgoyette-compat-0625:1.18 netbsd-8-0-RC2:1.18 pgoyette-compat-0521:1.18 pgoyette-compat-0502:1.18 pgoyette-compat-0422:1.18 netbsd-8-0-RC1:1.18 pgoyette-compat-0415:1.18 pgoyette-compat-0407:1.18 pgoyette-compat-0330:1.18 pgoyette-compat-0322:1.18 pgoyette-compat-0315:1.18 netbsd-7-1-2-RELEASE:1.18 pgoyette-compat:1.18.0.44 pgoyette-compat-base:1.18 netbsd-7-1-1-RELEASE:1.18 matt-nb8-mediatek:1.18.0.42 matt-nb8-mediatek-base:1.18 perseant-stdc-iso10646:1.18.0.40 perseant-stdc-iso10646-base:1.18 netbsd-8:1.18.0.38 netbsd-8-base:1.18 prg-localcount2-base3:1.18 prg-localcount2-base2:1.18 prg-localcount2-base1:1.18 prg-localcount2:1.18.0.36 prg-localcount2-base:1.18 pgoyette-localcount-20170426:1.18 bouyer-socketcan-base1:1.18 pgoyette-localcount-20170320:1.18 netbsd-7-1:1.18.0.34 netbsd-7-1-RELEASE:1.18 netbsd-7-1-RC2:1.18 netbsd-7-nhusb-base-20170116:1.18 bouyer-socketcan:1.18.0.32 bouyer-socketcan-base:1.18 pgoyette-localcount-20170107:1.18 netbsd-7-1-RC1:1.18 pgoyette-localcount-20161104:1.18 netbsd-7-0-2-RELEASE:1.18 localcount-20160914:1.18 netbsd-7-nhusb:1.18.0.30 netbsd-7-nhusb-base:1.18 pgoyette-localcount-20160806:1.18 pgoyette-localcount-20160726:1.18 pgoyette-localcount:1.18.0.28 pgoyette-localcount-base:1.18 netbsd-7-0-1-RELEASE:1.18 netbsd-7-0:1.18.0.26 netbsd-7-0-RELEASE:1.18 netbsd-7-0-RC3:1.18 netbsd-7-0-RC2:1.18 netbsd-7-0-RC1:1.18 netbsd-5-2-3-RELEASE:1.17 netbsd-5-1-5-RELEASE:1.17 netbsd-6-0-6-RELEASE:1.18 netbsd-6-1-5-RELEASE:1.18 netbsd-7:1.18.0.24 netbsd-7-base:1.18 yamt-pagecache-base9:1.18 yamt-pagecache-tag8:1.18 netbsd-6-1-4-RELEASE:1.18 netbsd-6-0-5-RELEASE:1.18 tls-earlyentropy:1.18.0.22 tls-earlyentropy-base:1.18 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.18 riastradh-drm2-base3:1.18 netbsd-6-1-3-RELEASE:1.18 netbsd-6-0-4-RELEASE:1.18 netbsd-5-2-2-RELEASE:1.17 netbsd-5-1-4-RELEASE:1.17 netbsd-6-1-2-RELEASE:1.18 netbsd-6-0-3-RELEASE:1.18 netbsd-5-2-1-RELEASE:1.17 netbsd-5-1-3-RELEASE:1.17 netbsd-6-1-1-RELEASE:1.18 riastradh-drm2-base2:1.18 riastradh-drm2-base1:1.18 riastradh-drm2:1.18.0.14 riastradh-drm2-base:1.18 netbsd-6-1:1.18.0.20 netbsd-6-0-2-RELEASE:1.18 netbsd-6-1-RELEASE:1.18 khorben-n900:1.18.0.18 netbsd-6-1-RC4:1.18 netbsd-6-1-RC3:1.18 agc-symver:1.18.0.16 agc-symver-base:1.18 netbsd-6-1-RC2:1.18 netbsd-6-1-RC1:1.18 yamt-pagecache-base8:1.18 netbsd-5-2:1.17.0.56 netbsd-6-0-1-RELEASE:1.18 yamt-pagecache-base7:1.18 netbsd-5-2-RELEASE:1.17 netbsd-5-2-RC1:1.17 matt-nb6-plus-nbase:1.18 yamt-pagecache-base6:1.18 netbsd-6-0:1.18.0.12 netbsd-6-0-RELEASE:1.18 netbsd-6-0-RC2:1.18 tls-maxphys:1.18.0.10 tls-maxphys-base:1.18 matt-nb6-plus:1.18.0.8 matt-nb6-plus-base:1.18 netbsd-6-0-RC1:1.18 yamt-pagecache-base5:1.18 yamt-pagecache-base4:1.18 netbsd-6:1.18.0.6 netbsd-6-base:1.18 netbsd-5-1-2-RELEASE:1.17 netbsd-5-1-1-RELEASE:1.17 yamt-pagecache-base3:1.18 yamt-pagecache-base2:1.18 yamt-pagecache:1.18.0.4 yamt-pagecache-base:1.18 cherry-xenmp:1.18.0.2 cherry-xenmp-base:1.18 bouyer-quota2-nbase:1.17 bouyer-quota2:1.17.0.54 bouyer-quota2-base:1.17 matt-mips64-premerge-20101231:1.17 matt-nb5-mips64-premerge-20101231:1.17 matt-nb5-pq3:1.17.0.52 matt-nb5-pq3-base:1.17 netbsd-5-1:1.17.0.50 netbsd-5-1-RELEASE:1.17 netbsd-5-1-RC4:1.17 matt-nb5-mips64-k15:1.17 netbsd-5-1-RC3:1.17 netbsd-5-1-RC2:1.17 netbsd-5-1-RC1:1.17 netbsd-5-0-2-RELEASE:1.17 matt-nb5-mips64-premerge-20091211:1.17 matt-premerge-20091211:1.17 matt-nb5-mips64-u2-k2-k4-k7-k8-k9:1.17 matt-nb4-mips64-k7-u2a-k9b:1.17 matt-nb5-mips64-u1-k1-k5:1.17 matt-nb5-mips64:1.17.0.48 netbsd-5-0-1-RELEASE:1.17 jym-xensuspend-nbase:1.17 netbsd-5-0:1.17.0.46 netbsd-5-0-RELEASE:1.17 netbsd-5-0-RC4:1.17 netbsd-5-0-RC3:1.17 netbsd-5-0-RC2:1.17 jym-xensuspend:1.17.0.44 jym-xensuspend-base:1.17 netbsd-5-0-RC1:1.17 netbsd-5:1.17.0.42 netbsd-5-base:1.17 matt-mips64-base2:1.17 matt-mips64:1.17.0.40 netbsd-4-0-1-RELEASE:1.17 wrstuden-revivesa-base-3:1.17 wrstuden-revivesa-base-2:1.17 wrstuden-fixsa-newbase:1.17 wrstuden-revivesa-base-1:1.17 yamt-pf42-base4:1.17 yamt-pf42-base3:1.17 hpcarm-cleanup-nbase:1.17 yamt-pf42-baseX:1.17 yamt-pf42-base2:1.17 wrstuden-revivesa:1.17.0.38 wrstuden-revivesa-base:1.17 yamt-pf42:1.17.0.36 yamt-pf42-base:1.17 mjf-devfs2:1.17.0.34 mjf-devfs2-base:1.17 keiichi-mipv6:1.17.0.32 keiichi-mipv6-base:1.17 mjf-devfs:1.17.0.30 mjf-devfs-base:1.17 matt-armv6-nbase:1.17 matt-armv6-prevmlocking:1.17 wrstuden-fixsa-base-1:1.17 netbsd-4-0:1.17.0.28 netbsd-4-0-RELEASE:1.17 cube-autoconf:1.17.0.26 cube-autoconf-base:1.17 netbsd-4-0-RC5:1.17 netbsd-4-0-RC4:1.17 netbsd-4-0-RC3:1.17 netbsd-4-0-RC2:1.17 netbsd-4-0-RC1:1.17 matt-armv6:1.17.0.24 matt-armv6-base:1.17 matt-mips64-base:1.17 hpcarm-cleanup:1.17.0.22 hpcarm-cleanup-base:1.17 netbsd-3-1-1-RELEASE:1.17 netbsd-3-0-3-RELEASE:1.17 wrstuden-fixsa:1.17.0.20 wrstuden-fixsa-base:1.17 abandoned-netbsd-4-base:1.17 abandoned-netbsd-4:1.17.0.14 netbsd-3-1:1.17.0.16 netbsd-3-1-RELEASE:1.17 netbsd-3-0-2-RELEASE:1.17 netbsd-3-1-RC4:1.17 netbsd-3-1-RC3:1.17 netbsd-3-1-RC2:1.17 netbsd-3-1-RC1:1.17 netbsd-4:1.17.0.18 netbsd-4-base:1.17 netbsd-3-0-1-RELEASE:1.17 netbsd-3-0:1.17.0.12 netbsd-3-0-RELEASE:1.17 netbsd-3-0-RC6:1.17 netbsd-3-0-RC5:1.17 netbsd-3-0-RC4:1.17 netbsd-3-0-RC3:1.17 netbsd-3-0-RC2:1.17 netbsd-3-0-RC1:1.17 netbsd-2-0-3-RELEASE:1.17 netbsd-2-1:1.17.0.10 netbsd-2-1-RELEASE:1.17 netbsd-2-1-RC6:1.17 netbsd-2-1-RC5:1.17 netbsd-2-1-RC4:1.17 netbsd-2-1-RC3:1.17 netbsd-2-1-RC2:1.17 netbsd-2-1-RC1:1.17 netbsd-2-0-2-RELEASE:1.17 netbsd-3:1.17.0.8 netbsd-3-base:1.17 netbsd-2-0-1-RELEASE:1.17 netbsd-2:1.17.0.6 netbsd-2-base:1.17 netbsd-2-0-RELEASE:1.17 netbsd-2-0-RC5:1.17 netbsd-2-0-RC4:1.17 netbsd-2-0-RC3:1.17 netbsd-2-0-RC2:1.17 netbsd-2-0-RC1:1.17 netbsd-2-0:1.17.0.4 netbsd-2-0-base:1.17 netbsd-1-6-PATCH002-RELEASE:1.17 netbsd-1-6-PATCH002:1.17 netbsd-1-6-PATCH002-RC4:1.17 netbsd-1-6-PATCH002-RC3:1.17 netbsd-1-6-PATCH002-RC2:1.17 netbsd-1-6-PATCH002-RC1:1.17 netbsd-1-6-PATCH001:1.17 netbsd-1-6-PATCH001-RELEASE:1.17 netbsd-1-6-PATCH001-RC3:1.17 netbsd-1-6-PATCH001-RC2:1.17 netbsd-1-6-PATCH001-RC1:1.17 fvdl_fs64_base:1.17 netbsd-1-6-RELEASE:1.17 netbsd-1-6-RC3:1.17 netbsd-1-6-RC2:1.17 netbsd-1-6-RC1:1.17 netbsd-1-6:1.17.0.2 netbsd-1-6-base:1.17 netbsd-1-5-PATCH003:1.16.4.1 netbsd-1-5-PATCH002:1.16.4.1 netbsd-1-5-PATCH001:1.16.4.1 netbsd-1-5-RELEASE:1.16.4.1 netbsd-1-5-BETA2:1.16.4.1 netbsd-1-5-BETA:1.16 netbsd-1-4-PATCH003:1.13.2.2 netbsd-1-5-ALPHA2:1.16 netbsd-1-5:1.16.0.4 netbsd-1-5-base:1.16 minoura-xpg4dl:1.16.0.2 minoura-xpg4dl-base:1.16 netbsd-1-4-PATCH002:1.13.2.2 wrstuden-devbsize-19991221:1.15 wrstuden-devbsize:1.15.0.4 wrstuden-devbsize-base:1.15 comdex-fall-1999:1.15.0.2 comdex-fall-1999-base:1.15 netbsd-1-4-PATCH001:1.13.2.2 netbsd-1-4-RELEASE:1.13.2.2 netbsd-1-4:1.13.0.2 netbsd-1-4-base:1.13 netbsd-1-3-PATCH003:1.6.2.4 netbsd-1-3-PATCH003-CANDIDATE2:1.6.2.4 netbsd-1-3-PATCH003-CANDIDATE1:1.6.2.4 netbsd-1-3-PATCH003-CANDIDATE0:1.6.2.4 netbsd-1-3-PATCH002:1.6.2.4 netbsd-1-3-PATCH001:1.6.2.3 netbsd-1-3-RELEASE:1.6.2.3 netbsd-1-3-BETA:1.6.2.1 netbsd-1-3:1.6.0.2 netbsd-1-3-base:1.6 netbsd-1-2-PATCH001:1.4 netbsd-1-2-RELEASE:1.4 netbsd-1-2-BETA:1.4 netbsd-1-2-base:1.4 netbsd-1-2:1.4.0.4 netbsd-1-1-PATCH001:1.3.2.1 netbsd-1-1-RELEASE:1.3.2.1 netbsd-1-1:1.3.0.2 netbsd-1-1-base:1.3 netbsd-1-0-PATCH06:1.1 netbsd-1-0-PATCH05:1.1 netbsd-1-0-PATCH04:1.1 netbsd-1-0-PATCH03:1.1 netbsd-1-0-PATCH02:1.1 netbsd-1-0-PATCH1:1.1 netbsd-1-0-PATCH0:1.1 netbsd-1-0-RELEASE:1.1 netbsd-1-0:1.1.0.2 netbsd-1-0-base:1.1; locks; strict; comment @# @; 1.18 date 2011.05.27.17.38.42; author tsutsui; state Exp; branches; next 1.17; 1.17 date 2000.10.10.12.55.16; author lukem; state Exp; branches 1.17.34.1; next 1.16; 1.16 date 2000.03.13.22.37.12; author soren; state Exp; branches 1.16.4.1; next 1.15; 1.15 date 99.05.05.18.47.40; author is; state Exp; branches; next 1.14; 1.14 date 99.04.11.15.12.49; author is; state Exp; branches; next 1.13; 1.13 date 99.01.13.07.30.02; author ross; state Exp; branches 1.13.2.1; next 1.12; 1.12 date 98.05.15.20.13.02; author is; state Exp; branches; next 1.11; 1.11 date 98.01.09.18.45.50; author perry; state Exp; branches; next 1.10; 1.10 date 97.12.26.02.57.30; author chopps; state Exp; branches; next 1.9; 1.9 date 97.12.14.18.22.52; author is; state Exp; branches; next 1.8; 1.8 date 97.11.30.13.12.05; author veego; state Exp; branches; next 1.7; 1.7 date 97.10.31.21.15.56; author mhitch; state Exp; branches; next 1.6; 1.6 date 97.04.07.17.47.51; author is; state Exp; branches 1.6.2.1; next 1.5; 1.5 date 96.09.29.03.13.43; author chopps; state Exp; branches; next 1.4; 1.4 date 95.11.28.23.57.56; author jtc; state Exp; branches; next 1.3; 1.3 date 95.10.09.02.44.21; author chopps; state Exp; branches 1.3.2.1; next 1.2; 1.2 date 94.10.21.08.27.03; author chopps; state Exp; branches; next 1.1; 1.1 date 94.09.19.17.45.49; author chopps; state Exp; branches 1.1.2.1; next ; 1.17.34.1 date 2008.10.05.20.10.26; author mjf; state dead; branches; next ; 1.16.4.1 date 2000.11.01.03.44.38; author tv; state Exp; branches; next ; 1.13.2.1 date 99.04.12.11.50.05; author is; state Exp; branches; next 1.13.2.2; 1.13.2.2 date 99.05.05.20.57.27; author perry; state Exp; branches; next ; 1.6.2.1 date 97.11.01.04.34.05; author mellon; state Exp; branches; next 1.6.2.2; 1.6.2.2 date 97.11.30.13.16.49; author veego; state Exp; branches; next 1.6.2.3; 1.6.2.3 date 97.12.15.06.24.36; author mellon; state Exp; branches; next 1.6.2.4; 1.6.2.4 date 98.05.29.04.10.00; author mycroft; state Exp; branches; next ; 1.3.2.1 date 95.10.20.10.52.44; author chopps; state Exp; branches; next ; 1.1.2.1 date 94.09.19.17.45.49; author chopps; state dead; branches; next 1.1.2.2; 1.1.2.2 date 94.09.19.17.45.50; author chopps; state Exp; branches; next ; desc @@ 1.18 log @- move "MD instructions on setting up boot media" from common/xfer with messy mdoc .if conditionals into MD xfer files so that developers can see what contents are missing or obsolete and should be written or updated - remove some useless MD description for maintainability XXX: still a bunch of unmaintained .if \n [${MACHINE}] in common files @ text @.\" $NetBSD: xfer,v 1.17 2000/10/10 12:55:16 lukem Exp $ .\" .\" Copyright (c) 1999-2004 The NetBSD Foundation, Inc. .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" . .\" ---------- MD instructions on setting up boot media . .\" XXX to be written . .\" ---------- MI instructions for getting distribution off installation medium . .so ../common/xfer @ 1.17 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 @d1 32 a32 1 .\" $NetBSD: xfer,v 1.16 2000/03/13 22:37:12 soren Exp $ @ 1.17.34.1 log @Sync with HEAD. @ text @d1 1 a1 1 .\" $NetBSD: xfer,v 1.17 2000/10/10 12:55:16 lukem Exp $ @ 1.16 log @Fix doubled 'the's. @ text @d1 3 a3 153 .\" $NetBSD: xfer,v 1.15 1999/05/05 18:47:40 is Exp $ .Pp Installation is supported from several media types, including: .Bl -bullet .It AmigaDOS HD partitions .It Tape .It NFS partitions .It FTP .It NetBSD partitions, if doing an upgrade. .It CD-ROM (SCSI or ATAPI) .El .Pp The miniroot file system needs to be transferred to the NetBSD swap partition. This can be done from AmigaDOS in the case of a new install or upgrade, or from NetBSD when doing an upgrade. See the "Preparing your System for NetBSD Installation" section for details. .Pp The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. .Bl -bullet .It To prepare for installing via an AmigaDOS partition: .Pp To install NetBSD from an AmigaDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an AmigaDOS partition. All of the set_name.xx pieces can be placed in a single directory instead of separate ones for each distribution set. This will also simplify the installation work later on. .Pp Note where you place the files you will need this later. .Pp Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. .It To prepare for installing from CD-ROM: .Pp To install NetBSD from a CD-ROM drive, make sure it is a SCSI CD-ROM on a SCSI bus currently supported by NetBSD (refer to the supported hardware list) or an ATAPI cd-rom connected to the A1200 or A4000 internal IDE connector. If it is a SCSI CD-ROM on a non-supported SCSI bus like Blizzard-3 SCSI, Apollo SCSI) you must first copy the distribution sets to an AmigaDOS partition like described above. .Pp If your SCSI CD-ROM is connected to a supported SCSI host adapter, or it is an ATAPI cd-rom connected to the A1200/A4000 internal IDE connector, simply put the CD into the drive before installation. .Pp Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. .It To prepare for installing via a tape: .Pp To install NetBSD from a tape, you need to somehow get the NetBSD file sets you wish to install on your system on to the appropriate kind of tape. .Pp If you're making the tape on a UN*X system, the easiest way to do so is: .Bd -literal -offset indent dd if=\* of=\* dd if=\*<2nd file\*> of=\* \&... .Ed .Pp where "\*" is the name of the non-rewinding tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). If you can't figure it out, ask your system administrator. "\*" are the names of the "set_name.tgz" files which you want to be placed on the tape. .Pp If you have a slow cpu (e.g. 68030 @@ 25 MHz) on the target machine, but big tapes, you might want to store the uncompressed installation sets instead. This will help tape streaming when doing the actual installation. E.g, do: .Bd -literal -offset indent gzip -d -c \* | dd of=\* gzip -d -c \*<2nd file\*> | dd of=\* \&... .Ed Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. .It To prepare for installing via an NFS partition: .(tag Em Note: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. .tag) .Pp Place the NetBSD software you wish to install into a directory on an NFS server, and make that directory mountable by the machine which you will be installing NetBSD on. This will probably require modifying the /etc/exports file of the NFS server and resetting mountd, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of the router closest to the new NetBSD machine, if the NFS server is not on a network which is directly attached to the NetBSD machine. .Pp Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. .It To prepare for installing via FTP: .(tag Em Note: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. .tag) .Pp The preparations for this method of installation are easy: all you have to do is make sure that there's some FTP site from which you can retrieve the NetBSD installation when it's time to do the install. You should know the numeric IP address of that site, the numeric IP address of your nearest router if one is necessary .Pp Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. .It If you are upgrading NetBSD, you also have the option of installing NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: .Pp Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base" set somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. .Pp Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. .El @ 1.16.4.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 153 a153 3 .\" $NetBSD: xfer,v 1.17 2000/10/10 12:55:16 lukem Exp $ . .so ../common/xfer @ 1.15 log @We support ATAPI CD-ROMs, nowadays @ text @d1 1 a1 1 .\" $NetBSD: xfer,v 1.14 1999/04/11 15:12:49 is Exp $ d110 1 a110 1 the router closest to the the new NetBSD machine, @ 1.14 log @We do support the CyberSCSI Mk3/PPC now @ text @d1 1 a1 1 .\" $NetBSD: xfer,v 1.13 1999/01/13 07:30:02 ross Exp $ d16 1 a16 1 CD-ROM (but only SCSI CD-ROM) d47 2 a48 1 supported hardware list). If it is an ATAPI CD-ROM, or a d54 1 @ 1.13 log @Markup for -mdoc and -mdoc2html. @ text @d1 1 a1 1 .\" $NetBSD: xfer,v 1.12 1998/05/15 20:13:02 is Exp $ d48 1 a48 1 SCSI CD-ROM on a non-supported SCSI bus like CyberSCSI Mk.3, @ 1.13.2.1 log @Pullup from -current: we support CS Mk.3 now @ text @d1 1 a1 1 .\" $NetBSD: xfer,v 1.14 1999/04/11 15:12:49 is Exp $ d48 1 a48 1 SCSI CD-ROM on a non-supported SCSI bus like @ 1.13.2.2 log @pullup 1.14->1.15 (is) @ text @d1 1 a1 1 .\" $NetBSD: xfer,v 1.15 1999/05/05 18:47:40 is Exp $ d16 1 a16 1 CD-ROM (SCSI or ATAPI) d47 1 a47 2 supported hardware list) or an ATAPI cd-rom connected to the A1200 or A4000 internal IDE connector. If it is a a52 1 or it is an ATAPI cd-rom connected to the A1200/A4000 internal IDE connector, @ 1.12 log @Add a section about installation from CD-ROM media. @ text @d1 2 a2 2 $NetBSD: xfer,v 1.11 1998/01/09 18:45:50 perry Exp $ d4 15 a18 7 AmigaDOS HD partitions Tape NFS partitions FTP NetBSD partitions, if doing an upgrade. CD-ROM (but only SCSI CD-ROM) d23 1 a23 1 d27 2 a28 1 d30 13 a42 13 To install NetBSD from an AmigaDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an AmigaDOS partition. All of the set_name.xx pieces can be placed in a single directory instead of separate ones for each distribution set. This will also simplify the installation work later on. Note where you place the files you will need this later. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. d44 14 a57 14 To install NetBSD from a CD-ROM drive, make sure it is a SCSI CD-ROM on a SCSI bus currently supported by NetBSD (refer to the supported hardware list). If it is an ATAPI CD-ROM, or a SCSI CD-ROM on a non-supported SCSI bus like CyberSCSI Mk.3, Blizzard-3 SCSI, Apollo SCSI) you must first copy the distribution sets to an AmigaDOS partition like described above. If your SCSI CD-ROM is connected to a supported SCSI host adapter, simply put the CD into the drive before installation. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. d59 32 a90 31 To install NetBSD from a tape, you need to somehow get the NetBSD file sets you wish to install on your system on to the appropriate kind of tape. If you're making the tape on a UN*X system, the easiest way to do so is: dd if= of= dd if=<2nd file> of= ... where "" is the name of the non-rewinding tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). If you can't figure it out, ask your system administrator. "" are the names of the "set_name.tgz" files which you want to be placed on the tape. If you have a slow cpu (e.g. 68030 @@ 25 MHz) on the target machine, but big tapes, you might want to store the uncompressed installation sets instead. This will help tape streaming when doing the actual installation. E.g, do: gzip -d -c | dd of= gzip -d -c <2nd file> | dd of= ... Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. d92 23 a114 22 NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the NetBSD software you wish to install into a directory on an NFS server, and make that directory mountable by the machine which you will be installing NetBSD on. This will probably require modifying the /etc/exports file of the NFS server and resetting mountd, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of the router closest to the the new NetBSD machine, if the NFS server is not on a network which is directly attached to the NetBSD machine. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. d116 20 a135 19 NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. The preparations for this method of installation are easy: all you have to do is make sure that there's some FTP site from which you can retrieve the NetBSD installation when it's time to do the install. You should know the numeric IP address of that site, the numeric IP address of your nearest router if one is necessary Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. d140 12 a151 11 Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base" set somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. @ 1.11 log @RCS Id Police. @ text @d1 1 a1 1 $NetBSD$ d9 1 d30 15 @ 1.10 log @add non-rewinding note from 1.3 branch @ text @d1 2 @ 1.9 log @Change to describe the tape format for the new miniroot. @ text @d44 2 a45 2 where "" is the name of the tape device that describes the tape drive you're using (possibly @ 1.8 log @Remove the 13 from sets13. @ text @d35 1 a35 2 your system on to the appropriate kind of tape, in tar format. d40 3 a42 1 tar cvf d48 1 a48 1 "" are the names of the "set_name.xx" files d50 9 @ 1.7 log @Initial updates to document install and upgrades using the MI miniroot. Update revision numbers for 1.3. @ text @d104 1 a104 1 "base13" set somewhere in your file system. If you wish, @ 1.6 log @Some corrections (mostly typos) by Thorsten Frueauf (PR 3315). @ text @d8 4 a11 5 The install or upgrade miniroot file system needs to be transferred to the NetBSD swap partition. This can be done from AmigaDOS in the case of a new install or upgrade, or from NetBSD when doing an upgrade. See the "Preparing your System for NetBSD Installation" section for details. d104 1 a104 1 "base11" set somewhere in your file system. If you wish, @ 1.6.2.1 log @Pull rev 1.7 up from trunk (mhitch) @ text @d8 5 a12 4 The miniroot file system needs to be transferred to the NetBSD swap partition. This can be done from AmigaDOS in the case of a new install or upgrade, or from NetBSD when doing an upgrade. See the "Preparing your System for NetBSD Installation" section for details. d105 1 a105 1 "base13" set somewhere in your file system. If you wish, @ 1.6.2.2 log @Sync with trunk. @ text @d104 1 a104 1 "base" set somewhere in your file system. If you wish, @ 1.6.2.3 log @Pull rev 1.9 up from trunk (with edits) (is) @ text @d35 2 a36 1 your system on to the appropriate kind of tape. d41 1 a41 3 dd if= of= dd if=<2nd file> of= ... d43 2 a44 2 where "" is the name of the non-rewinding tape device that describes the tape drive you're using (possibly d47 1 a47 1 "" are the names of the "set_name.tgz" files a48 9 If you have a slow cpu (e.g. 68030 @@ 25 MHz) on the target machine, but big tapes, you might want to store the uncompressed installation sets instead. This will help tape streaming when doing the actual installation. E.g, do: gzip -d -c | dd of= gzip -d -c <2nd file> | dd of= ... @ 1.6.2.4 log @Pull up 1.12, per request of is. @ text @a6 1 CD-ROM (but only SCSI CD-ROM) a26 15 Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing from CD-ROM: To install NetBSD from a CD-ROM drive, make sure it is a SCSI CD-ROM on a SCSI bus currently supported by NetBSD (refer to the supported hardware list). If it is an ATAPI CD-ROM, or a SCSI CD-ROM on a non-supported SCSI bus like CyberSCSI Mk.3, Blizzard-3 SCSI, Apollo SCSI) you must first copy the distribution sets to an AmigaDOS partition like described above. If your SCSI CD-ROM is connected to a supported SCSI host adapter, simply put the CD into the drive before installation. @ 1.5 log @update notes from release branch and clean up a little @ text @d48 1 a48 1 "" are the names of the "set_name.nnn" files @ 1.4 log @merge in changes from 1.1 release branch @ text @d8 1 a8 1 The install or upgrade miniroot filesystem needs to be transferred d35 1 a35 1 get the NetBSD filesets you wish to install on @ 1.3 log @update from osymh@@gemini.oscs.montana.edu (Michael L. Hitch) @ text @d8 5 a12 22 >>> Transfering install/upgrade file system image to swap partition No matter what you do, however, you'll need to have one disk handy, on which you will put the install floppy image. All the images are available from the directory "amiga/floppies", >>> ^^^^^^^^ under the root of the NetBSD tree at your favorite archive site. If you are using NetBSD/amiga to make the floppies, you should use the command dd(1) to write the raw floppy images (.fs files) to the disk. To write onto fd0 use: dd if=inst-11.fs of=/dev/rfd0a bs=11b If you are using AmigaDOS to make the floppies, you should use the rawwrite utility, provided in the directory "amiga/utilities" in the distribution. To write the image to the floppy in df0 use (from cli): rawwrite 0 inst-11.fs >>> fix above to document file system transfer to swap paritition >>> using xstreamtodev @ 1.3.2.1 log @update notes from osymh@@gemini.oscs.montana.edu (Michael L. Hitch) @ text @d8 22 a29 5 The install or upgrade miniroot filesystem needs to be transferred to the NetBSD swap partition. This can be done from AmigaDOS in the case of a new install or upgrade, or from NetBSD when doing an upgrade. See the "Preparing your System for NetBSD Installation" section for details. @ 1.2 log @various small fixes. @ text @d6 1 d8 1 d13 1 d20 1 a20 1 dd if=inst-10.fs of=/dev/rfd0a bs=11b d27 3 a29 1 rawwrite 0 inst-10.fs d113 16 @ 1.1 log @install document parts for amiga arch. @ text @d34 4 a37 1 on your system on to an AmigaDOS partition. d46 2 a47 2 To install NetBSD from a tape, you need to be somehow to get the NetBSD filesets you wish to install on @ 1.1.2.1 log @file xfer was added on branch netbsd-1-0 on 1994-09-19 17:45:50 +0000 @ text @d1 104 @ 1.1.2.2 log @install document parts for amiga arch. @ text @a0 104 Installation is supported from several media types, including: AmigaDOS HD partitions Tape NFS partitions FTP No matter what you do, however, you'll need to have one disk handy, on which you will put the install floppy image. All the images are available from the directory "amiga/floppies", under the root of the NetBSD tree at your favorite archive site. If you are using NetBSD/amiga to make the floppies, you should use the command dd(1) to write the raw floppy images (.fs files) to the disk. To write onto fd0 use: dd if=inst-10.fs of=/dev/rfd0a bs=11b If you are using AmigaDOS to make the floppies, you should use the rawwrite utility, provided in the directory "amiga/utilities" in the distribution. To write the image to the floppy in df0 use (from cli): rawwrite 0 inst-10.fs The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. To prepare for installing via an AmigaDOS partition: To install NetBSD from an AmigaDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an AmigaDOS partition. Note where you place the files you will need this later. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via a tape: To install NetBSD from a tape, you need to be somehow to get the NetBSD filesets you wish to install on your system on to the appropriate kind of tape, in tar format. If you're making the tape on a UN*X system, the easiest way to do so is: tar cvf where "" is the name of the tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). If you can't figure it out, ask your system administrator. "" are the names of the "set_name.nnn" files which you want to be placed on the tape. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via an NFS partition: NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the NetBSD software you wish to install into a directory on an NFS server, and make that directory mountable by the machine which you will be installing NetBSD on. This will probably require modifying the /etc/exports file of the NFS server and resetting mountd, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of the router closest to the the new NetBSD machine, if the NFS server is not on a network which is directly attached to the NetBSD machine. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via FTP: NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. The preparations for this method of installation are easy: all you have to do is make sure that there's some FTP site from which you can retrieve the NetBSD installation when it's time to do the install. You should know the numeric IP address of that site, the numeric IP address of your nearest router if one is necessary Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. @