head 1.31; access; symbols perseant-exfatfs-base-20261102:1.31 netbsd-11-1-RELEASE:1.31 netbsd-10-2-RELEASE:1.31 netbsd-9-5-RELEASE:1.27.18.1 netbsd-11-0-RELEASE:1.31 netbsd-11-0-RC7:1.31 netbsd-11-0-RC6:1.31 netbsd-11-0-RC5:1.31 netbsd-11-0-RC4:1.31 netbsd-11-0-RC3:1.31 netbsd-11-0-RC2:1.31 netbsd-11-0-RC1:1.31 perseant-exfatfs-base-20250801:1.31 netbsd-11:1.31.0.6 netbsd-11-base:1.31 netbsd-10-1-RELEASE:1.31 perseant-exfatfs-base-20240630:1.31 perseant-exfatfs:1.31.0.4 perseant-exfatfs-base:1.31 netbsd-8-3-RELEASE:1.27 netbsd-9-4-RELEASE:1.27.18.1 netbsd-10-0-RELEASE:1.31 netbsd-10-0-RC6:1.31 netbsd-10-0-RC5:1.31 netbsd-10-0-RC4:1.31 netbsd-10-0-RC3:1.31 netbsd-10-0-RC2:1.31 netbsd-10-0-RC1:1.31 netbsd-10:1.31.0.2 netbsd-10-base:1.31 netbsd-9-3-RELEASE:1.27.18.1 cjep_sun2x-base1:1.30 cjep_sun2x:1.30.0.6 cjep_sun2x-base:1.30 cjep_staticlib_x-base1:1.30 netbsd-9-2-RELEASE:1.27.18.1 cjep_staticlib_x:1.30.0.4 cjep_staticlib_x-base:1.30 netbsd-9-1-RELEASE:1.27.18.1 phil-wifi-20200421:1.30 phil-wifi-20200411:1.30 is-mlppp:1.30.0.2 is-mlppp-base:1.30 phil-wifi-20200406:1.30 netbsd-8-2-RELEASE:1.27 netbsd-9-0-RELEASE:1.27.18.1 netbsd-9-0-RC2:1.27.18.1 netbsd-9-0-RC1:1.27.18.1 phil-wifi-20191119:1.27 netbsd-9:1.27.0.18 netbsd-9-base:1.27 phil-wifi-20190609:1.27 netbsd-8-1-RELEASE:1.27 netbsd-8-1-RC1:1.27 pgoyette-compat-merge-20190127:1.27 pgoyette-compat-20190127:1.27 pgoyette-compat-20190118:1.27 pgoyette-compat-1226:1.27 pgoyette-compat-1126:1.27 pgoyette-compat-1020:1.27 pgoyette-compat-0930:1.27 pgoyette-compat-0906:1.27 netbsd-7-2-RELEASE:1.26.26.1 pgoyette-compat-0728:1.27 netbsd-8-0-RELEASE:1.27 phil-wifi:1.27.0.16 phil-wifi-base:1.27 pgoyette-compat-0625:1.27 netbsd-8-0-RC2:1.27 pgoyette-compat-0521:1.27 pgoyette-compat-0502:1.27 pgoyette-compat-0422:1.27 netbsd-8-0-RC1:1.27 pgoyette-compat-0415:1.27 pgoyette-compat-0407:1.27 pgoyette-compat-0330:1.27 pgoyette-compat-0322:1.27 pgoyette-compat-0315:1.27 netbsd-7-1-2-RELEASE:1.26.26.1 pgoyette-compat:1.27.0.14 pgoyette-compat-base:1.27 netbsd-7-1-1-RELEASE:1.26.26.1 matt-nb8-mediatek:1.27.0.12 matt-nb8-mediatek-base:1.27 perseant-stdc-iso10646:1.27.0.10 perseant-stdc-iso10646-base:1.27 netbsd-8:1.27.0.8 netbsd-8-base:1.27 prg-localcount2-base3:1.27 prg-localcount2-base2:1.27 prg-localcount2-base1:1.27 prg-localcount2:1.27.0.6 prg-localcount2-base:1.27 pgoyette-localcount-20170426:1.27 bouyer-socketcan-base1:1.27 pgoyette-localcount-20170320:1.27 netbsd-7-1:1.26.26.1.0.6 netbsd-7-1-RELEASE:1.26.26.1 netbsd-7-1-RC2:1.26.26.1 netbsd-7-nhusb-base-20170116:1.26.26.1 bouyer-socketcan:1.27.0.4 bouyer-socketcan-base:1.27 pgoyette-localcount-20170107:1.27 netbsd-7-1-RC1:1.26.26.1 pgoyette-localcount-20161104:1.27 netbsd-7-0-2-RELEASE:1.26.26.1 localcount-20160914:1.27 netbsd-7-nhusb:1.26.26.1.0.4 netbsd-7-nhusb-base:1.26.26.1 pgoyette-localcount-20160806:1.27 pgoyette-localcount-20160726:1.27 pgoyette-localcount:1.27.0.2 pgoyette-localcount-base:1.27 netbsd-7-0-1-RELEASE:1.26.26.1 netbsd-7-0:1.26.26.1.0.2 netbsd-7-0-RELEASE:1.26.26.1 netbsd-7-0-RC3:1.26.26.1 netbsd-7-0-RC2:1.26.26.1 netbsd-7-0-RC1:1.26.26.1 netbsd-5-2-3-RELEASE:1.24.2.2 netbsd-5-1-5-RELEASE:1.24.2.2 netbsd-6-0-6-RELEASE:1.26 netbsd-6-1-5-RELEASE:1.26 netbsd-7:1.26.0.26 netbsd-7-base:1.26 yamt-pagecache-base9:1.26 yamt-pagecache-tag8:1.26 netbsd-6-1-4-RELEASE:1.26 netbsd-6-0-5-RELEASE:1.26 tls-earlyentropy:1.26.0.24 tls-earlyentropy-base:1.26 riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.26 riastradh-drm2-base3:1.26 netbsd-6-1-3-RELEASE:1.26 netbsd-6-0-4-RELEASE:1.26 netbsd-5-2-2-RELEASE:1.24.2.2 netbsd-5-1-4-RELEASE:1.24.2.2 netbsd-6-1-2-RELEASE:1.26 netbsd-6-0-3-RELEASE:1.26 netbsd-5-2-1-RELEASE:1.24.2.2 netbsd-5-1-3-RELEASE:1.24.2.2 netbsd-6-1-1-RELEASE:1.26 riastradh-drm2-base2:1.26 riastradh-drm2-base1:1.26 riastradh-drm2:1.26.0.16 riastradh-drm2-base:1.26 netbsd-6-1:1.26.0.22 netbsd-6-0-2-RELEASE:1.26 netbsd-6-1-RELEASE:1.26 khorben-n900:1.26.0.20 netbsd-6-1-RC4:1.26 netbsd-6-1-RC3:1.26 agc-symver:1.26.0.18 agc-symver-base:1.26 netbsd-6-1-RC2:1.26 netbsd-6-1-RC1:1.26 yamt-pagecache-base8:1.26 netbsd-5-2:1.24.2.2.0.10 netbsd-6-0-1-RELEASE:1.26 yamt-pagecache-base7:1.26 netbsd-5-2-RELEASE:1.24.2.2 netbsd-5-2-RC1:1.24.2.2 matt-nb6-plus-nbase:1.26 yamt-pagecache-base6:1.26 netbsd-6-0:1.26.0.14 netbsd-6-0-RELEASE:1.26 netbsd-6-0-RC2:1.26 tls-maxphys:1.26.0.12 tls-maxphys-base:1.26 matt-nb6-plus:1.26.0.10 matt-nb6-plus-base:1.26 netbsd-6-0-RC1:1.26 yamt-pagecache-base5:1.26 yamt-pagecache-base4:1.26 netbsd-6:1.26.0.8 netbsd-6-base:1.26 netbsd-5-1-2-RELEASE:1.24.2.2 netbsd-5-1-1-RELEASE:1.24.2.2 yamt-pagecache-base3:1.26 yamt-pagecache-base2:1.26 yamt-pagecache:1.26.0.6 yamt-pagecache-base:1.26 cherry-xenmp:1.26.0.4 cherry-xenmp-base:1.26 bouyer-quota2-nbase:1.26 bouyer-quota2:1.26.0.2 bouyer-quota2-base:1.26 matt-mips64-premerge-20101231:1.26 matt-nb5-mips64-premerge-20101231:1.24.2.2 matt-nb5-pq3:1.24.2.2.0.8 matt-nb5-pq3-base:1.24.2.2 netbsd-5-1:1.24.2.2.0.6 netbsd-5-1-RELEASE:1.24.2.2 netbsd-5-1-RC4:1.24.2.2 matt-nb5-mips64-k15:1.24.2.2 netbsd-5-1-RC3:1.24.2.2 netbsd-5-1-RC2:1.24.2.2 netbsd-5-1-RC1:1.24.2.2 netbsd-5-0-2-RELEASE:1.24.2.2 matt-nb5-mips64-premerge-20091211:1.24.2.2 matt-premerge-20091211:1.26 matt-nb5-mips64-u2-k2-k4-k7-k8-k9:1.24.2.2 matt-nb4-mips64-k7-u2a-k9b:1.24.2.2 matt-nb5-mips64-u1-k1-k5:1.24.2.2 matt-nb5-mips64:1.24.2.2.0.4 netbsd-5-0-1-RELEASE:1.24.2.2 jym-xensuspend-nbase:1.26 netbsd-5-0:1.24.2.2.0.2 netbsd-5-0-RELEASE:1.24.2.2 netbsd-5-0-RC4:1.24.2.1 netbsd-5-0-RC3:1.24.2.1 netbsd-5-0-RC2:1.24.2.1 jym-xensuspend:1.25.0.2 jym-xensuspend-base:1.26 netbsd-5-0-RC1:1.24.2.1 netbsd-5:1.24.0.2 netbsd-5-base:1.24 matt-mips64-base2:1.24 matt-mips64:1.22.0.32 netbsd-4-0-1-RELEASE:1.22.20.1 wrstuden-revivesa-base-3:1.24 wrstuden-revivesa-base-2:1.24 wrstuden-fixsa-newbase:1.22.10.1 wrstuden-revivesa-base-1:1.22 yamt-pf42-base4:1.22 yamt-pf42-base3:1.22 hpcarm-cleanup-nbase:1.22 yamt-pf42-baseX:1.22 yamt-pf42-base2:1.22 wrstuden-revivesa:1.22.0.30 wrstuden-revivesa-base:1.22 yamt-pf42:1.22.0.28 yamt-pf42-base:1.22 mjf-devfs2:1.22.0.26 mjf-devfs2-base:1.24 keiichi-mipv6:1.22.0.24 keiichi-mipv6-base:1.22 mjf-devfs:1.22.0.22 mjf-devfs-base:1.22 matt-armv6-nbase:1.22 matt-armv6-prevmlocking:1.22 wrstuden-fixsa-base-1:1.22 netbsd-4-0:1.22.0.20 netbsd-4-0-RELEASE:1.22 cube-autoconf:1.22.0.18 cube-autoconf-base:1.22 netbsd-4-0-RC5:1.22 netbsd-4-0-RC4:1.22 netbsd-4-0-RC3:1.22 netbsd-4-0-RC2:1.22 netbsd-4-0-RC1:1.22 matt-armv6:1.22.0.16 matt-armv6-base:1.22 matt-mips64-base:1.22 hpcarm-cleanup:1.22.0.14 hpcarm-cleanup-base:1.22 netbsd-3-1-1-RELEASE:1.22 netbsd-3-0-3-RELEASE:1.22 wrstuden-fixsa:1.22.0.12 wrstuden-fixsa-base:1.22.10.1 abandoned-netbsd-4-base:1.22 abandoned-netbsd-4:1.22.0.6 netbsd-3-1:1.22.0.8 netbsd-3-1-RELEASE:1.22 netbsd-3-0-2-RELEASE:1.22 netbsd-3-1-RC4:1.22 netbsd-3-1-RC3:1.22 netbsd-3-1-RC2:1.22 netbsd-3-1-RC1:1.22 netbsd-4:1.22.0.10 netbsd-4-base:1.22 netbsd-3-0-1-RELEASE:1.22 netbsd-3-0:1.22.0.4 netbsd-3-0-RELEASE:1.22 netbsd-3-0-RC6:1.22 netbsd-3-0-RC5:1.22 netbsd-3-0-RC4:1.22 netbsd-3-0-RC3:1.22 netbsd-3-0-RC2:1.22 netbsd-3-0-RC1:1.22 netbsd-2-0-3-RELEASE:1.21.2.1 netbsd-2-1:1.21.2.1.0.4 netbsd-2-1-RELEASE:1.21.2.1 netbsd-2-1-RC6:1.21.2.1 netbsd-2-1-RC5:1.21.2.1 netbsd-2-1-RC4:1.21.2.1 netbsd-2-1-RC3:1.21.2.1 netbsd-2-1-RC2:1.21.2.1 netbsd-2-1-RC1:1.21.2.1 netbsd-2-0-2-RELEASE:1.21.2.1 netbsd-3:1.22.0.2 netbsd-3-base:1.22 netbsd-2-0-1-RELEASE:1.21.2.1 netbsd-2:1.21.2.1.0.2 netbsd-2-base:1.21.2.1 netbsd-2-0-RELEASE:1.21.2.1 netbsd-2-0-RC5:1.21.2.1 netbsd-2-0-RC4:1.21.2.1 netbsd-2-0-RC3:1.21.2.1 netbsd-2-0-RC2:1.21.2.1 netbsd-2-0-RC1:1.21.2.1 netbsd-2-0:1.21.0.2 netbsd-2-0-base:1.21 netbsd-1-6-PATCH002-RELEASE:1.18.2.2 netbsd-1-6-PATCH002:1.18.2.2 netbsd-1-6-PATCH002-RC4:1.18.2.2 netbsd-1-6-PATCH002-RC3:1.18.2.2 netbsd-1-6-PATCH002-RC2:1.18.2.2 netbsd-1-6-PATCH002-RC1:1.18.2.2 netbsd-1-6-PATCH001:1.18.2.2 netbsd-1-6-PATCH001-RELEASE:1.18.2.2 netbsd-1-6-PATCH001-RC3:1.18.2.2 netbsd-1-6-PATCH001-RC2:1.18.2.2 netbsd-1-6-PATCH001-RC1:1.18.2.2 fvdl_fs64_base:1.20 netbsd-1-6-RELEASE:1.18.2.2 netbsd-1-6-RC3:1.18.2.2 netbsd-1-6-RC2:1.18.2.2 netbsd-1-6-RC1:1.18.2.2 netbsd-1-6:1.18.0.2 netbsd-1-6-base:1.18 netbsd-1-5-PATCH003:1.8.8.3 netbsd-1-5-PATCH002:1.8.8.3 netbsd-1-5-PATCH001:1.8.8.3 netbsd-1-5-RELEASE:1.8.8.3 netbsd-1-5-BETA2:1.8.8.2 netbsd-1-5-BETA:1.8 netbsd-1-4-PATCH003:1.7 netbsd-1-5-ALPHA2:1.8 netbsd-1-5:1.8.0.8 netbsd-1-5-base:1.8 minoura-xpg4dl:1.8.0.6 minoura-xpg4dl-base:1.8 netbsd-1-4-PATCH002:1.7 wrstuden-devbsize-19991221:1.8 wrstuden-devbsize:1.8.0.4 wrstuden-devbsize-base:1.8 comdex-fall-1999:1.8.0.2 comdex-fall-1999-base:1.8 netbsd-1-4-PATCH001:1.7 netbsd-1-4-RELEASE:1.7 netbsd-1-4:1.7.0.2 netbsd-1-4-base:1.7 netbsd-1-3-PATCH003:1.5 netbsd-1-3-PATCH003-CANDIDATE2:1.5 netbsd-1-3-PATCH003-CANDIDATE1:1.5 netbsd-1-3-PATCH003-CANDIDATE0:1.5 netbsd-1-3-PATCH002:1.5 netbsd-1-3-PATCH001:1.5 netbsd-1-3-RELEASE:1.5 netbsd-1-3-BETA:1.5 netbsd-1-3:1.5.0.2 netbsd-1-3-base:1.5 netbsd-1-2-PATCH001:1.2.6.2 netbsd-1-2-RELEASE:1.2.6.2 netbsd-1-2-BETA:1.2 netbsd-1-2-base:1.2 netbsd-1-2:1.2.0.6 netbsd-1-1-PATCH001:1.2 netbsd-1-1-RELEASE:1.2 netbsd-1-1:1.2.0.2 netbsd-1-1-base:1.2; locks; strict; comment @# @; 1.31 date 2022.09.28.06.09.14; author charlotte; state Exp; branches; next 1.30; commitid iV5NANKAaXaiRAVD; 1.30 date 2019.11.27.18.34.56; author uwe; state Exp; branches; next 1.29; commitid oYg8FLjJTC6UhwMB; 1.29 date 2019.11.27.09.29.25; author martin; state Exp; branches; next 1.28; commitid rQanOfNSclucgtMB; 1.28 date 2019.11.24.23.26.43; author uwe; state Exp; branches; next 1.27; commitid H9yRnjscz7MYZ9MB; 1.27 date 2015.05.19.19.30.29; author snj; state Exp; branches 1.27.16.1 1.27.18.1; next 1.26; commitid QNF6BPxp3DF3J5my; 1.26 date 2009.04.23.01.56.50; author snj; state Exp; branches 1.26.26.1; next 1.25; 1.25 date 2008.11.20.20.52.17; author jdc; state Exp; branches 1.25.2.1; next 1.24; 1.24 date 2008.09.07.05.11.55; author tsutsui; state Exp; branches 1.24.2.1; next 1.23; 1.23 date 2008.09.06.19.53.44; author tsutsui; state Exp; branches; next 1.22; 1.22 date 2004.06.12.16.41.14; author mbw; state Exp; branches 1.22.10.1 1.22.12.1 1.22.20.1 1.22.26.1 1.22.30.1; next 1.21; 1.21 date 2003.10.21.02.16.34; author mbw; state Exp; branches 1.21.2.1; next 1.20; 1.20 date 2002.07.11.04.52.51; author scottr; state Exp; branches; next 1.19; 1.19 date 2002.06.30.12.43.05; author lukem; state Exp; branches; next 1.18; 1.18 date 2002.05.03.03.58.45; author mbw; state Exp; branches 1.18.2.1; next 1.17; 1.17 date 2002.04.29.23.33.41; author mbw; state Exp; branches; next 1.16; 1.16 date 2001.07.24.18.14.34; author nra; state Exp; branches; next 1.15; 1.15 date 2000.11.05.21.30.22; author pk; state Exp; branches; next 1.14; 1.14 date 2000.11.03.02.18.50; author mbw; state Exp; branches; next 1.13; 1.13 date 2000.11.01.20.56.06; author mbw; state Exp; branches; next 1.12; 1.12 date 2000.10.29.14.08.10; author lukem; state Exp; branches; next 1.11; 1.11 date 2000.10.22.00.44.04; author mbw; state Exp; branches; next 1.10; 1.10 date 2000.10.21.04.49.26; author mbw; state Exp; branches; next 1.9; 1.9 date 2000.10.10.12.55.22; author lukem; state Exp; branches; next 1.8; 1.8 date 99.06.12.11.24.35; author pk; state Exp; branches 1.8.8.1; next 1.7; 1.7 date 99.01.13.07.30.08; author ross; state Exp; branches; next 1.6; 1.6 date 98.01.09.18.47.26; author perry; state Exp; branches; next 1.5; 1.5 date 97.07.14.14.59.23; author pk; state Exp; branches; next 1.4; 1.4 date 96.11.23.21.39.23; author pk; state Exp; branches; next 1.3; 1.3 date 96.10.09.00.13.36; author jtc; state Exp; branches; next 1.2; 1.2 date 95.10.08.02.05.48; author pk; state Exp; branches 1.2.6.1; next 1.1; 1.1 date 94.10.25.06.48.19; author deraadt; state Exp; branches; next ; 1.27.16.1 date 2020.04.08.14.03.51; author martin; state Exp; branches; next ; commitid Qli2aW9E74UFuA3C; 1.27.18.1 date 2019.11.27.13.36.55; author msaitoh; state Exp; branches; next ; commitid WlY3MxbqBImDDuMB; 1.26.26.1 date 2015.05.24.11.14.45; author martin; state Exp; branches; next ; commitid w9Ap5nNIPTG0PGmy; 1.25.2.1 date 2009.05.13.19.17.48; author jym; state Exp; branches; next ; 1.24.2.1 date 2008.12.02.01.32.56; author snj; state Exp; branches; next 1.24.2.2; 1.24.2.2 date 2009.04.25.23.16.35; author snj; state Exp; branches; next ; 1.22.10.1 date 2008.09.14.21.09.57; author bouyer; state Exp; branches; next ; 1.22.12.1 date 2008.09.15.08.09.57; author skrll; state Exp; branches; next ; 1.22.20.1 date 2008.09.14.21.10.44; author bouyer; state Exp; branches; next ; 1.22.26.1 date 2008.09.28.11.09.18; author mjf; state Exp; branches; next 1.22.26.2; 1.22.26.2 date 2008.10.05.20.10.29; author mjf; state dead; branches; next ; 1.22.30.1 date 2008.09.18.04.41.11; author wrstuden; state Exp; branches; next ; 1.21.2.1 date 2004.06.15.23.11.48; author he; state Exp; branches; next ; 1.18.2.1 date 2002.07.02.04.20.17; author lukem; state Exp; branches; next 1.18.2.2; 1.18.2.2 date 2002.07.11.18.41.51; author thorpej; state Exp; branches; next ; 1.8.8.1 date 2000.11.01.03.48.33; author tv; state Exp; branches; next 1.8.8.2; 1.8.8.2 date 2000.11.03.20.38.40; author tv; state Exp; branches; next 1.8.8.3; 1.8.8.3 date 2000.11.09.22.44.57; author tv; state Exp; branches; next ; 1.2.6.1 date 96.06.28.00.00.09; author pk; state Exp; branches; next 1.2.6.2; 1.2.6.2 date 96.09.02.23.37.39; author pk; state Exp; branches; next ; desc @@ 1.31 log @Avoid dead link to the NVRAM FAQ in docs for sparc, too @ text @.\" $NetBSD: prep,v 1.30 2019/11/27 18:34:56 uwe Exp $ . .Ss2 Configuring your PROM . Before you start, you should configure your PROM. There are three categories of PROM: .Dq sunmon (sometimes called Restricted Prompt, sun monitor, or old command mode), OpenBoot PROM 1, and OpenBoot PROM 2. The sun4 machines only have sunmon. Some of the early sun4c models default to sunmon but have OpenBoot PROM 1. The later sun4c models and all sun4m models have OpenBoot PROM 2. .Pp First, you need to stop your system from automatically booting when powered on. Pressing the .Key STOP key (sometimes called the .Key L1 key, found on the left side of your keyboard) and the .Key a key will halt your system and give you a PROM prompt. If you are using a Tadpole SPARCbook, you press the .Key Pause and .Key a keys. If you are using a serial console, send a .Dq BREAK signal from your terminal (the method of sending .Dq BREAK varies from terminal to terminal). .Pp If the ethernet address of your \*M system is .Li ff:ff:ff:ff:ff:ff , then your NVRAM battery is dead and you will have trouble using ethernet (among other problems). Read the .Lk https://web.archive.org/web/20150611091616/https://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html "Sun NVRAM/Hostid FAQ" . .Pp If you have a valid ethernet address and you plan to netboot, write down your system's ethernet address. .Pp Next, you should set your system to always use the OpenBoot PROM (sometimes called .Dq "new command mode" ) if it defaults to sunmon. The .Nx kernel relies on some of the functionality provided by the OpenBoot PROM. If your machine gives you a `\*[Gt]' prompt instead of an `ok' prompt, type: .Pp .(disp .No \*[Gt] Ic n .No ok Ic "setenv sunmon-compat? false" .No ok .disp) .Pp Next, if you are using any security features of OpenBoot PROM, you should turn them off \(em .Nx can't deal well with this. .Pp .(disp .No ok Ic "setenv security-mode none" .disp) .Pp If you are using a serial console, the .Nx*M installer defaults to using 9600 bps, 8N1 settings. You may want to configure your system and serial terminal like this prior to booting the installer. Additionally, a new installation of .Nx*M will default to these settings as well. .Pp The OpenBoot PROM 1 machines (SPARCstation/server 1, SPARCstation/server 1+, IPC, and SLC) have an odd SCSI quirk you should be aware of. There are three SCSI addressing schemes used by your system: SCSI target ID (set by physical jumpers on the device), PROM .Sq unit number (set by OpenBoot PROM 1, based on its SCSI target ID), and the name you reference within an operating system (set by the kernel, based on the PROM .Sq unit number). .Pp Sun shipped these systems with the internal drives set to SCSI target IDs 3 and 1. The default value of the OpenBoot PROM variable .Sq Li sd-targets is .Sq Li 31204567. This variable maps how the OpenBoot PROM 1 assigns .Sq unit numbers based on the SCSI target ID. Thus the device at SCSI target ID 3 is considered .Sq unit 0, and the SCSI device at target ID 0 is .Sq unit 3. When you type .Dq Ic boot scsi(0,0,0) , the OpenBoot PROM will boot from .Sq unit 0 (which is SCSI target ID 3, the internal hard drive). The .Tn SunOS kernel is hard-wired to map .Li sd0 to SCSI target 3, and .Li sd3 to SCSI target 0. .Bl -column -offset indent PROM\ Unit# SCSI\ Target SunOS\ name .It Em PROM\ Unit# Ta Em SCSI\ Target Ta Em SunOS\ name .It \~\~\~0 Ta \~\~\~3 Ta \~\~\~sd0 .It \~\~\~1 Ta \~\~\~1 Ta \~\~\~sd1 .It \~\~\~2 Ta \~\~\~2 Ta \~\~\~sd2 .It \~\~\~3 Ta \~\~\~0 Ta \~\~\~sd3 .It \~\~\~4 Ta \~\~\~4 Ta \~\~\~st0 .It \~\~\~5 Ta \~\~\~5 Ta \~\~\~st1 .It \~\~\~6 Ta \~\~\~6 Ta \~\~\~cdrom .El .Pp The .Nx*M .Li GENERIC kernel does not wire things down as does .Tn SunOS . It names the disks in the order that the SCSI targets are probed (01234567). If you only have one disk, it is always .Li sd0 regardless of its SCSI target ID or its PROM .Sq unit number, and there are no problems. If you have two disks, one at SCSI ID 2 .Pf ( Sq unit 2) and SCSI ID 3 .Pf ( Sq unit 0), then they are recognized as .Li sd0 and .Li sd1 respectively. This can be a problem if you are not aware of it, particularly when creating an fstab. .Pp There are two approaches to fixing this problem: changing the mapping that OpenBoot PROM 1 does, and changing the .Nx kernel configuration. To get OpenBoot PROM 1 to number the SCSI .Sq unit numbers the same as the SCSI target IDs, you need to run this command: .Pp .(disp .No ok Ic "setenv sd-targets 01234567" .disp) .Pp This may, however, cause problems if you were to later attempt to use .Tn SunOS on this machine or if you reset the OpenBoot PROM variables. .Pp The other approach is to use a .Nx kernel that matches the PROM's odd target mapping by treating .Sq unit 0 (i.e. SCSI target ID 3) as .Li sd0 and .Sq unit 3 (i.e. SCSI target ID 0) as .Li sd3 . The .Li GENERIC_SCSI3 kernel performs this target mapping, but the .Li GENERIC and .Li INSTALL kernels do not. .Pp .(Note This is also a concern when you start building your own customised kernels. .Note) .Pp The machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) have a similar SCSI target mapping in the form of a .Ic devalias entry. That is, the device alias .Ic disk is shorthand for the disk at SCSI ID 3 on the internal SCSI controller. Normally, the .Ic disk device alias is what the PROM uses as the default boot device, i.e. in the absence of a .Ar device argument to the .Ic boot command. Note that there are also pre-configured device alias entries for .Ic disk0, .Ic disk1, .Ic disk2 and .Ic disk3 , which are in fact a one-to-one mapping to the SCSI targets .Ic 0 to .Ic 3 .Pq all on the internal SCSI controller . .Pp Again, it may be advantageous to use a fixed .Dq SCSI target to .Dq Nx "" disk unit mapping in your kernel configuration file (such as is done in the .Li GENERIC_SCSI3 kernel) to ensure that your disks remain showing up at the same .Nx device unit numbers even if you add disks to your system at a later time. . .Ss2 Determining how to access your SCSI disk from the PROM . sunmon and OpenBoot PROM 1 use an archaic .Li sd( Ns Ar c,u,p Ns Ic \&) syntax to address SCSI devices. OpenBoot PROM 2 uses a more intuitive syntax using device aliases. .Pp To calculate the parameters for sunmon and OpenBoot PROM 1: .(tag xcc -offset indent .It Ar c specifies the SCSI controller number (first is 0, second is 1, ...) .It Ar u the hexadecimal number obtained from evaluating the expression .Em (8 * TARGET) + LUN .It Ar p the partition number from which to boot .Pf ( Sq Li 0 = .Sq Li a , .Sq Li 1 = .Sq Li b , etc.) .tag) .Pp Therefore, to boot from the swap partition on the internal hard drive (first SCSI bus, target 0, lun 0, partition 1), one would use: .Pp .(disp .No ok Ic "boot sd(0,0,1)" .disp) .Pp To boot from a CD-ROM (first SCSI bus, target 6, lun 0, partition dynamically determined), one would use: .Pp .(disp .No ok Ic "boot sd(0,30,)" .disp) .Pp And, to boot from a kernel named .Li netbsd-GENERIC on the fourth partition .Pf ( Sq Li d , often the .Pa /usr partition) on an external hard drive (first SCSI bus, target 2, lun 0, partition 3), one would use: .Pp .(disp .No ok Ic "boot sd(0,10,3)netbsd-GENERIC" .disp) .Pp Now, for OpenBoot PROM 2, SCSI devices are specified by an OpenBOOT .Ic devalias which provides simple mnemonics for the full path to the device. Type .Ic devalias in OpenBoot PROM 2 to get a list of all of the available aliases. Just the alias and partition are necessary when booting. .Pp Therefore, to boot from the swap partition on the internal hard drive (OpenBoot PROM 2 assumes the internal hard drive is at target 3), one would use: .Pp .(disp .No ok Ic "boot disk:b" .disp) .Pp To boot from a CD-ROM (OpenBoot PROM 2 assumes the CD-ROM is at target 6), one would use: .Pp .(disp .No ok Ic "boot cdrom" .disp) .Pp And, to boot from a kernel named .Li netbsd-GENERIC on the fourth partition .Pf ( Sq Li d , often the .Pa /usr partition) on an external hard drive (target 2, partition 3), one would use: .Pp .(disp .No ok Ic "boot disk2:d netbsd-GENERIC" .disp) .Pp The full device path specifier for OpenBoot PROM 2 depends on how OpenBoot PROM 2 recognizes your SCSI controller. Typically, one would use something like: .Pa /sbus/esp/sd@@ Ns Ar t,p where t is the SCSI target and p is the partition number. . .Ss2 Determining how to boot from an SBUS card . Some SBUS cards have firmware that lets you use them as a boot device. These cards do not automatically create a .Ic devalias entry, so you must traverse the device tree to figure out what the OpenBoot PROM calls your card. You will be using OpenBoot PROM commands at the `ok' prompt. First `cd' to the top of the device tree and list the nodes there. The following is the procedure to boot from an HME card in a SPARC Classic. .(disp .No ok Ic "cd /" .No ok Ic "ls" ffd3b790 TI,TMS390S10@@0,f8fffffc ffd2d254 virtual-memory@@0,0 ffd2d198 memory@@0,0 ffd2b65c obio ffd2b310 iommu@@0,10000000 ffd2b2a0 openprom ffd24af0 aliases ffd24abc options ffd24a88 packages .disp) Usually, you can simply type in the name before the at (@@) sign and the OpenBoot PROM will fill in the rest. .(disp .No ok Ic "cd iommu" .No ok Ic "ls" ffd2b454 sbus@@0,10001000 .No ok Ic "cd sbus" .No ok Ic "ls" ffd467e8 cgthree@@3,0 ffd42a1c SUNW,hme@@1,8c00000 ffd4297c le@@0,c00000 ffd40d28 ledma@@4,8400010 ffd40c9c SUNW,bpp@@4,c800000 ffd40c00 audio@@4,1300000 ffd3dc68 espdma@@4,8400000 .No ok Ic "cd SUNW,hme" .No ok Ic "ls" .No ok Ic "pwd" /iommu@@0,10000000/sbus@@0,10001000/SUNW,hme@@1,8c00000 .disp) OK, now we know the path to the HME device in this example. Now, we need to determine if it's capable of booting. If it is, it will have the .Ic word `open'. .(disp .No ok Ic "words" reset seek load open close watch-net selftest obp-selftest write read preamble-32 enable-link-pulse disable-link-pulse force-speeds reset-transceiver use-bit-bang-mode use-frame-mode dump-phys transfer-speed=10 transfer-speed=100 mii-write mii-read create-rev-id .disp) Great! Also, in case you're interested in further details about your hardware, you can use the `.attributes' command. .(disp .No ok Ic ".attributes" hm-rev 00000022 version 1.18 model SUNW,501-2919 device_type network intr 00000037 00000000 interrupts 00000004 address-bits 00000030 max-frame-size 00004000 reg 00000001 08c00000 00000108 00000001 08c02000 00002000 00000001 08c04000 00002000 00000001 08c06000 00002000 00000001 08c07000 00000020 name SUNW,hme ok .disp) So, when it's time to type in a boot command, use the shortened version of the .Ic pwd command. In this example, you'd type: .(disp .No ok Ic "boot /iommu/sbus/SUNW,hme" .disp) And when the kernel is done booting, it may not automatically use your card as the root device -- you may need to type in the .Nx*M name for that device: .(disp root on sd0a dumps on sd0b no file system for sd0 (dev 0x700) cannot mount root, error = 79 .No "root device (default sd0a):" Ic "?" use one of: fd0[a-h] le0 le1 hme0 sd0[a-h] halt .No "root device (default sd0a):" Ic "hme0" .No "dump device:" Ic "hme0" .No "file system (default generic):" Ic "nfs" root on hme0 .disp) . .Ss2 Deciding on partition sizes . If you're installing .Nx*M for the first time it's a good idea to look at the partition sizes of disk you intend installing .Nx*M on. .Pp A minimal installation of .Nx requires about 140 MB. A full installation requires considerably more. A good initial size for the swap partition is twice the amount of physical memory in your machine (unlike .Tn SunOS 4.x , there are no restrictions on the size of the swap partition that would render part of your memory unusable). .Pp Note that there are limitations on the size of the root partition for various models. .Pp On sun4 machines, the .Nx sparc boot loader can only boot from RAID partitions that start at the beginning of the disk. .Pp On sun4 and early PROM version sun4c machines, the PROM can only boot from the first 1Gb of the disk. .Pp On later PROM version sun4c and early PROM version sun4m machines, the PROM can only boot from the first 2Gb of the disk. .Pp On later PROM version sun4m machines, the PROM can only boot from the first 4Gb of the disk. . .Ss2 Configuration of network interfaces . Some network devices (i.e. the built-in .Em le interface on sun4m machines) allow a choice between operating on a UTP or a AUI port once the .Nx kernel is running. The .Em le driver supports automatic detection of the port which is actually connected to the wire. Additionally, some of the Fast ethernet devices (such as .Em be , .Em hme , .Em qec , and .Em qfe ) support selection of various speeds and options. The default is to attempt to automatically detect the speed. .Pp If automatic detection is not available or not working properly in your environment, you may have to specify the type connection using the .Ic media parameter of .Xr ifconfig 8 . During installation, you'll get the opportunity to specify the appropriate medium. Use .Li 10base5 or .Li AUI to select the AUI connector, or .Li 10baseT or .Li UTP to select the UTP connector. Fast ethernet interfaces default to .Li auto , which usually does not detect properly and runs at .Sq 10BaseT speed. The options are .Li 10baseT , .Li 10baseTX , and .Li auto . The .Em hme and .Em qfe interfaces also allow .Li 10baseT-FDX and .Li 100baseT-FDX . @ 1.30 log @Undo the .Ss2 quoting hack, the macros can now handle it. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.29 2019/11/27 09:29:25 martin Exp $ d36 1 a36 1 .Lk http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html "Sun NVRAM/Hostid FAQ" . @ 1.29 log @More cleanup: - simplify TOC handling and remove arg limit (from uwe) - use Lk with explicit anchor text in some places - do not allow official release builds when we can not derive the proper date from the buildid @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.28 2019/11/24 23:26:43 uwe Exp $ d215 1 a215 1 .Ss2 "Determining how to access your SCSI disk from the PROM" @ 1.28 log @Quote long .Ss2 title to avoid troff's limitation. Troff is limited to 9 macro parameters and this title is 10 words, so we lose the last word here when we pass arguments around. We have more titles like that but for now I wanted to commit only one just to flag the problem. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.27 2015/05/19 19:30:29 snj Exp $ d35 2 a36 2 ethernet (among other problems). Read the Sun NVRAM/Hostid FAQ. .Lk http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html @ 1.27 log @- update upgrade issues: + ARM ABI change + new users + new groups - add modules set where missing - formatting improvements - note that rtsol{,d} will be gone in the future - fix raw partition info - update sparc64 hardware support - remove note about sparc SMP support being broken - update some size requirements (still lots of ancient bogus RAM minimums lingering -- HI PORTMASTERS!) - various other minor content modernization - whitespace fixes @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.26 2009/04/23 01:56:50 snj Exp $ d215 1 a215 1 .Ss2 Determining how to access your SCSI disk from the PROM @ 1.27.16.1 log @Merge changes from current as of 20200406 @ text @d1 1 a1 1 .\" $NetBSD$ d35 2 a36 2 ethernet (among other problems). Read the .Lk http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html "Sun NVRAM/Hostid FAQ" . @ 1.27.18.1 log @Pull up following revision(s) (requested by martin in ticket #489): distrib/notes/Makefile.inc: revision 1.46 distrib/notes/common/postinstall: revision 1.86 distrib/notes/sparc64/prep: revision 1.16 distrib/notes/common/netboot: revision 1.38 distrib/notes/common/main: revision 1.555 distrib/notes/common/main: revision 1.556 distrib/notes/common/main: revision 1.557 distrib/notes/common/macros: revision 1.44 distrib/notes/common/sysinst: revision 1.110 distrib/notes/sparc/prep: revision 1.28 distrib/notes/sparc/prep: revision 1.29 distrib/notes/common/list-portmasters.pl: file removal Remove list-portmasters.pl script. We dropped that list from "main" some time ago. Quote long .Ss2 title to avoid troff's limitation. Troff is limited to 9 macro parameters and this title is 10 words, so we lose the last word here when we pass arguments around. We have more titles like that but for now I wanted to commit only one just to flag the problem. More cleanup: - simplify TOC handling and remove arg limit (from uwe) - use Lk with explicit anchor text in some places - do not allow official release builds when we can not derive the proper date from the buildid Add "Oxford comma" Improve heading a bit. While here, use quotes to group some of the words to avoid the 9-arg limitation of .Ss @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.27 2015/05/19 19:30:29 snj Exp $ d35 2 a36 2 ethernet (among other problems). Read the .Lk http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html "Sun NVRAM/Hostid FAQ" . d215 1 a215 1 .Ss2 "Determining how to access your SCSI disk from the PROM" @ 1.26 log @Various updates to the INSTALL notes in preparation for 5.0. Changes are still to come. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.25 2008/11/20 20:52:17 jdc Exp $ d420 1 a420 1 requires about 100 MB. @ 1.26.26.1 log @Pull up following revision(s) (requested by snj in ticket #799): distrib/notes/Makefile.inc: revision 1.43 distrib/notes/acorn26/contents: revision 1.2 distrib/notes/acorn26/legal: delete distrib/notes/acorn32/contents: revision 1.2 distrib/notes/acorn32/hardware: revision 1.3 distrib/notes/acorn32/legal: delete distrib/notes/acorn32/prep: revision 1.15 distrib/notes/acorn32/prep.RISCOS: revision 1.23 distrib/notes/alpha/contents: revision 1.16 distrib/notes/alpha/hardware: revision 1.18 distrib/notes/alpha/legal: delete distrib/notes/amd64/contents: revisions 1.4, 1.5 distrib/notes/amd64/legal: delete distrib/notes/amiga/contents: revision 1.20 distrib/notes/amiga/legal: delete distrib/notes/arc/contents: revision 1.2 distrib/notes/arc/legal: delete distrib/notes/atari/contents: revision 1.20 distrib/notes/atari/legal: delete distrib/notes/bebox/contents: revision 1.2 distrib/notes/bebox/hardware: revision 1.2 distrib/notes/bebox/legal: delete distrib/notes/cats/contents: revision 1.2 distrib/notes/cats/legal: delete distrib/notes/common/legal.common: revisions 1.93-1.96 distrib/notes/common/list-setsizes.sh: delete distrib/notes/common/macros: revisions 1.41, 1.42 distrib/notes/common/main: revisions 1.519-1.521 distrib/notes/common/netboot: revision 1.36 distrib/notes/common/postinstall: revision 1.80, 1.81 distrib/notes/common/sysinst: revisions 1.105, 1.106 distrib/notes/common/upgrade: revisions 1.29, 1.30 distrib/notes/common/xfer: revision 1.74 distrib/notes/emips/contents: revision 1.2 distrib/notes/emips/hardware: revision 1.2 distrib/notes/emips/install: revision 1.2 distrib/notes/emips/legal: delete distrib/notes/evbarm/contents: revision 1.2 distrib/notes/evbarm/legal: delete distrib/notes/evbppc/contents: revision 1.3 distrib/notes/evbppc/legal: delete distrib/notes/ews4800mips/contents: revision 1.2 distrib/notes/ews4800mips/legal: delete distrib/notes/hp300/contents: revision 1.17 distrib/notes/hp300/legal: delete distrib/notes/hpcarm/contents: revision 1.3 distrib/notes/hpcarm/legal: delete distrib/notes/hpcmips/contents: revision 1.10 distrib/notes/hpcmips/legal: delete distrib/notes/hpcsh/contents: revision 1.3 distrib/notes/hpcsh/legal: delete distrib/notes/hppa/contents: revision 1.2 distrib/notes/hppa/legal: delete distrib/notes/i386/contents: revision 1.29 distrib/notes/i386/legal: delete distrib/notes/landisk/contents: revision 1.3 distrib/notes/landisk/legal: delete distrib/notes/mac68k/contents: revision 1.20 distrib/notes/mac68k/hardware: revision 1.25 distrib/notes/mac68k/legal: delete distrib/notes/mac68k/prep: revision 1.17 distrib/notes/macppc/contents: revision 1.11 distrib/notes/macppc/hardware: revision 1.48 distrib/notes/macppc/legal: delete distrib/notes/macppc/prep.OPENFIRMWARE: revision 1.18 distrib/notes/mmeye/contents: revision 1.3 distrib/notes/mmeye/legal: delete distrib/notes/mvme68k/contents: revision 1.13 distrib/notes/mvme68k/legal: delete distrib/notes/mvme68k/xfer: revision 1.18 distrib/notes/news68k/contents: revision 1.6 distrib/notes/news68k/legal: delete distrib/notes/newsmips/contents: revision 1.2 distrib/notes/newsmips/legal: delete distrib/notes/next68k/contents: revision 1.7 distrib/notes/next68k/legal: delete distrib/notes/ofppc/contents: revision 1.3 distrib/notes/ofppc/legal: delete distrib/notes/pmax/contents: revision 1.17 distrib/notes/pmax/hardware: revision 1.18 distrib/notes/pmax/legal: delete distrib/notes/prep/contents: revision 1.2 distrib/notes/prep/hardware: revision 1.5 distrib/notes/prep/legal: delete distrib/notes/prep/upgrade: revision 1.2 distrib/notes/rs6000/contents: revision 1.2 distrib/notes/rs6000/legal: delete distrib/notes/sandpoint/contents: revision 1.2 distrib/notes/sandpoint/legal: delete distrib/notes/sgimips/contents: revision 1.2 distrib/notes/sgimips/legal: delete distrib/notes/shark/contents: revision 1.2 distrib/notes/shark/legal: delete distrib/notes/sparc/contents: revision 1.21 distrib/notes/sparc/hardware: revision 1.37 distrib/notes/sparc/legal: delete distrib/notes/sparc/prep: revision 1.27 distrib/notes/sparc64/Makefile: revision 1.4 distrib/notes/sparc64/contents: revision 1.5 distrib/notes/sparc64/hardware: revision 1.28 distrib/notes/sparc64/legal: delete distrib/notes/sun2/contents: revision 1.2 distrib/notes/sun2/legal: delete distrib/notes/sun3/contents: revision 1.16 distrib/notes/sun3/legal: delete distrib/notes/vax/contents: revision 1.11 distrib/notes/vax/hardware: revision 1.11 distrib/notes/vax/legal: delete distrib/notes/x68k/contents: revision 1.17 distrib/notes/x68k/hardware: revision 1.18 distrib/notes/x68k/legal: delete distrib/notes/xen/legal: delete Remove reference to a 14 year old IP address for ftp.NetBSD.org. This is not a joke. -- mention etcupdate and reorder a bit -- first pass de-suckification for 2015. modernize content a bit, fix dirty rotten lies, improve wording, sync legalese with reality, yada yada yada. -- This product includes software developed by Yasushi Yamasaki. -- - update upgrade issues: + ARM ABI change + new users + new groups - add modules set where missing - formatting improvements - note that rtsol{,d} will be gone in the future - fix raw partition info - update sparc64 hardware support - remove note about sparc SMP support being broken - update some size requirements (still lots of ancient bogus RAM minimums lingering -- HI PORTMASTERS!) - various other minor content modernization - whitespace fixes -- finish removing the set size stuff, which was thrown out four years ago. -- merge port-specific legal sections into the common file. most of these entries were already in the common file, and it's a pain to maintain them separately. -- don't look for now-gone sparc/legal -- restore rcsid accidentally deleted in previous -- bah. this time without a typo. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.26 2009/04/23 01:56:50 snj Exp $ d420 1 a420 1 requires about 140 MB. @ 1.25 log @Note root partition size limitations on certain sparc and sparc64 models (taken from the boot(8) manual pages). @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.24 2008/09/07 05:11:55 tsutsui Exp $ d418 1 a418 5 Assuming a classic partition scheme with .Pa / (root) and .Pa /usr file systems, a comfortable size for the d420 4 a423 3 root file system partition is about 20 MB; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike d426 1 a426 3 part of your memory unusable). A full binary installation takes about 275 MB in .Pa /usr . @ 1.25.2.1 log @Sync with HEAD. Third (and last) commit. See http://mail-index.netbsd.org/source-changes/2009/05/13/msg221222.html @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.26 2009/04/23 01:56:50 snj Exp $ d418 5 a422 1 A minimal installation of d424 3 a426 4 requires about 100 MB. A full installation requires considerably more. A good initial size for the swap partition is twice the amount of physical memory in your machine (unlike d429 3 a431 1 part of your memory unusable). @ 1.24 log @Suppress the whitespace after parenthesis. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.23 2008/09/06 19:53:44 tsutsui Exp $ d433 16 a448 2 Most sparc systems have trouble booting if the root partition extends beyond the first 2 GB of your disk. @ 1.24.2.1 log @Pull up following revision(s) (requested by jdc in ticket #159): distrib/notes/sparc/prep: revision 1.25 distrib/notes/sparc64/prep: revision 1.13 Note root partition size limitations on certain sparc and sparc64 models (taken from the boot(8) manual pages). @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.24 2008/09/07 05:11:55 tsutsui Exp $ d433 2 a434 16 Note that there are limitations on the size of the root partition for various models. .Pp On sun4 machines, the .Nx sparc boot loader can only boot from RAID partitions that start at the beginning of the disk. .Pp On sun4 and early PROM version sun4c machines, the PROM can only boot from the first 1Gb of the disk. .Pp On later PROM version sun4c and early PROM version sun4m machines, the PROM can only boot from the first 2Gb of the disk. .Pp On later PROM version sun4m machines, the PROM can only boot from the first 4Gb of the disk. @ 1.24.2.2 log @Pull up following revision(s) (requested by rmind in ticket #728): distrib/alpha/README.files: revision 1.14 distrib/notes/acorn26/upgrade: revision 1.2 distrib/notes/acorn32/hardware: revision 1.2 distrib/notes/acorn32/prep: revision 1.14 distrib/notes/acorn32/prep.RISCOS: revision 1.20 distrib/notes/alpha/hardware: revisions 1.16-1.17 distrib/notes/alpha/install: revisions 1.35-1.37 distrib/notes/amd64/prep: revision 1.2 distrib/notes/amiga/hardware: revision 1.46 distrib/notes/amiga/install: revision 1.35 distrib/notes/amiga/prep: revision 1.28 distrib/notes/amiga/upgrade: revision 1.28 distrib/notes/arc/prep: revision 1.2 distrib/notes/atari/hardware: revision 1.22 distrib/notes/atari/prep: revision 1.13 distrib/notes/cats/hardware: revision 1.7 distrib/notes/cats/prep: revision 1.11 distrib/notes/cats/upgrade: revision 1.4 distrib/notes/common/contents: revisions 1.150-1.155 distrib/notes/common/legal.common: revision 1.52 distrib/notes/common/main: revisions 1.444-1.446 distrib/notes/common/postinstall: revisions 1.73, 1.74 distrib/notes/common/sysinst: revisions 1.97, 1.98 distrib/notes/common/upgrade: revisions 1.27, 1.28 distrib/notes/common/xfer: revisions 1.64-1.66 distrib/notes/evbarm/prep: revision 1.10 distrib/notes/evbarm/upgrade: revision 1.2 distrib/notes/evbppc/hardware: revision 1.5 distrib/notes/evbppc/upgrade: revision 1.2 distrib/notes/hp300/prep: revision 1.24 distrib/notes/i386/upgrade: revision 1.23 distrib/notes/i386/prep: revision 1.14 distrib/notes/mac68k/hardware: revision 1.24 distrib/notes/mac68k/prep: revision 1.16 distrib/notes/mac68k/upgrade: revision 1.21 distrib/notes/mac68k/xfer: revision 1.20 distrib/notes/macppc/prep: revisions 1.43, 1.44 distrib/notes/macppc/prep.OPENFIRMWARE: revision 1.13 distrib/notes/macppc/hardware: revision 1.47 distrib/notes/macppc/prep.OPENFIRMWARE: revision 1.12 distrib/notes/mvme68k/hardware: revision 1.11 distrib/notes/mvme68k/install: revision 1.21 distrib/notes/next68k/prep: revision 1.8 distrib/notes/pmax/hardware: revision 1.17 distrib/notes/pmax/install: revision 1.41 distrib/notes/sgimips/hardware: revision 1.14 distrib/notes/sgimips/prep: revision 1.10 distrib/notes/shark/install: revision 1.5 distrib/notes/sparc/hardware: revisions 1.35, 1.36 distrib/notes/sparc/prep: revision 1.26 distrib/notes/sparc/upgrade: revision 1.16 distrib/notes/sparc64/prep: revision 1.15 distrib/notes/sun2/hardware: revision 1.4 distrib/notes/sun3/hardware: revision 1.10 distrib/notes/vax/hardware: revision 1.10 distrib/notes/vax/install: revision 1.18 distrib/notes/vax/prep: revision 1.7 distrib/notes/xen/xfer: revision 1.4 distrib/notes/x68k/hardware: revision 1.17 distrib/notes/x68k/prep: revision 1.9 Update release notes. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.24.2.1 2008/12/02 01:32:56 snj Exp $ d418 5 a422 1 A minimal installation of d424 3 a426 4 requires about 100 MB. A full installation requires considerably more. A good initial size for the swap partition is twice the amount of physical memory in your machine (unlike d429 3 a431 1 part of your memory unusable). @ 1.23 log @Fix warnings. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.22 2004/06/12 16:41:14 mbw Exp $ d129 4 a132 4 SCSI ID 2 ( .Sq unit 2) and SCSI ID 3 ( .Sq unit d231 2 a232 2 the partition number from which to boot ( .Sq Li 0 d257 2 a258 2 on the fourth partition ( .Sq Li d , d292 2 a293 2 on the fourth partition ( .Sq Li d , @ 1.22 log @Mention that installer defaults to serial speed of 9600 8N1 and user might want to pre-configure their system around that. Closes PR 11946 @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.21 2003/10/21 02:16:34 mbw Exp $ d47 1 a47 1 If your machine gives you a `\*>' prompt instead of an `ok' prompt, d51 1 a51 1 .No \*> Ic n d208 1 a208 4 .Do .Nx disk unit .Dc d231 1 a231 2 the partition number from which to boot .Po d238 1 a238 2 etc. .Pc @ 1.22.26.1 log @Sync with HEAD. @ text @d1 1 a1 1 .\" $NetBSD$ d47 1 a47 1 If your machine gives you a `\*[Gt]' prompt instead of an `ok' prompt, d51 1 a51 1 .No \*[Gt] Ic n d129 4 a132 4 SCSI ID 2 .Pf ( Sq unit 2) and SCSI ID 3 .Pf ( Sq unit d208 4 a211 1 .Dq Nx "" disk unit d235 2 a236 1 .Pf ( Sq Li 0 d242 2 a243 1 etc.) d262 2 a263 2 on the fourth partition .Pf ( Sq Li d , d297 2 a298 2 on the fourth partition .Pf ( Sq Li d , @ 1.22.26.2 log @Sync with HEAD. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.22.26.1 2008/09/28 11:09:18 mjf Exp $ @ 1.22.30.1 log @Sync with wrstuden-revivesa-base-2. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.22 2004/06/12 16:41:14 mbw Exp $ d47 1 a47 1 If your machine gives you a `\*[Gt]' prompt instead of an `ok' prompt, d51 1 a51 1 .No \*[Gt] Ic n d129 4 a132 4 SCSI ID 2 .Pf ( Sq unit 2) and SCSI ID 3 .Pf ( Sq unit d208 4 a211 1 .Dq Nx "" disk unit d235 2 a236 1 .Pf ( Sq Li 0 d242 2 a243 1 etc.) d262 2 a263 2 on the fourth partition .Pf ( Sq Li d , d297 2 a298 2 on the fourth partition .Pf ( Sq Li d , @ 1.22.12.1 log @Sync with netbsd-4. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.22.10.1 2008/09/14 21:09:57 bouyer Exp $ d47 1 a47 1 If your machine gives you a `\*[Gt]' prompt instead of an `ok' prompt, d51 1 a51 1 .No \*[Gt] Ic n d129 4 a132 4 SCSI ID 2 .Pf ( Sq unit 2) and SCSI ID 3 .Pf ( Sq unit d208 4 a211 1 .Dq Nx "" disk unit d235 2 a236 1 .Pf ( Sq Li 0 d242 2 a243 1 etc.) d262 2 a263 2 on the fourth partition .Pf ( Sq Li d , d297 2 a298 2 on the fourth partition .Pf ( Sq Li d , @ 1.22.20.1 log @Pull up following revision(s) (requested by tsutsui in ticket #1198): distrib/notes/sandpoint/install: revision 1.4 distrib/notes/macppc/hardware: revision 1.45, 1.46 distrib/notes/next68k/prep: revision 1.7 distrib/notes/sun3/install: revision 1.16 distrib/notes/macppc/prep.OPENFIRMWARE: revision 1.10, 1.11 distrib/notes/mvme68k/xfer: revision 1.17 distrib/notes/vax/install: revision 1.17 distrib/notes/common/contents: revision 1.142 distrib/notes/next68k/xfer: revision 1.7 distrib/notes/common/sysinst: revision 1.91 distrib/notes/alpha/install: revision 1.34 distrib/notes/mvme68k/install: revision 1.20 distrib/notes/hp300/prep: revision 1.23 distrib/notes/common/sysinst: revision 1.92 distrib/notes/alpha/hardware: revision 1.15 distrib/notes/sparc64/install: revision 1.30 distrib/notes/cats/prep: revision 1.10 distrib/notes/sparc/hardware: revision 1.34 distrib/notes/sparc/prep: revision 1.23, 1.24 distrib/notes/sparc/install: revision 1.55 distrib/notes/hpcmips/install: revision 1.11 distrib/notes/common/main: revision 1.416 distrib/notes/amiga/prep: revision 1.27 distrib/notes/i386/hardware: revision 1.123 distrib/notes/evbppc/hardware: revision 1.4 distrib/notes/evbarm/prep: revision 1.9 distrib/notes/amiga/install: revision 1.34 distrib/notes/macppc/install: revision 1.37 distrib/notes/evbarm/install: revision 1.9 distrib/notes/sun2/install: revision 1.7 distrib/notes/sun2/install: revision 1.8 distrib/notes/mvme68k/prep: revision 1.14 distrib/notes/hp700/prep: revision 1.2 distrib/notes/mvme68k/hardware: revision 1.10 distrib/notes/atari/xfer: revision 1.16 distrib/notes/amiga/upgrade: revision 1.27 Cosmetics or mdoc warning fixes @ text @d1 1 a1 1 .\" $NetBSD$ d47 1 a47 1 If your machine gives you a `\*[Gt]' prompt instead of an `ok' prompt, d51 1 a51 1 .No \*[Gt] Ic n d129 4 a132 4 SCSI ID 2 .Pf ( Sq unit 2) and SCSI ID 3 .Pf ( Sq unit d208 4 a211 1 .Dq Nx "" disk unit d235 2 a236 1 .Pf ( Sq Li 0 d242 2 a243 1 etc.) d262 2 a263 2 on the fourth partition .Pf ( Sq Li d , d297 2 a298 2 on the fourth partition .Pf ( Sq Li d , @ 1.22.10.1 log @Pull up following revision(s) (requested by tsutsui in ticket #1198): distrib/notes/sandpoint/install: revision 1.4 distrib/notes/macppc/hardware: revision 1.45, 1.46 distrib/notes/next68k/prep: revision 1.7 distrib/notes/sun3/install: revision 1.16 distrib/notes/macppc/prep.OPENFIRMWARE: revision 1.10, 1.11 distrib/notes/mvme68k/xfer: revision 1.17 distrib/notes/vax/install: revision 1.17 distrib/notes/common/contents: revision 1.142 distrib/notes/next68k/xfer: revision 1.7 distrib/notes/common/sysinst: revision 1.91 distrib/notes/alpha/install: revision 1.34 distrib/notes/mvme68k/install: revision 1.20 distrib/notes/hp300/prep: revision 1.23 distrib/notes/common/sysinst: revision 1.92 distrib/notes/alpha/hardware: revision 1.15 distrib/notes/sparc64/install: revision 1.30 distrib/notes/cats/prep: revision 1.10 distrib/notes/sparc/hardware: revision 1.34 distrib/notes/sparc/prep: revision 1.23, 1.24 distrib/notes/sparc/install: revision 1.55 distrib/notes/hpcmips/install: revision 1.11 distrib/notes/common/main: revision 1.416 distrib/notes/amiga/prep: revision 1.27 distrib/notes/i386/hardware: revision 1.123 distrib/notes/evbppc/hardware: revision 1.4 distrib/notes/evbarm/prep: revision 1.9 distrib/notes/amiga/install: revision 1.34 distrib/notes/macppc/install: revision 1.37 distrib/notes/evbarm/install: revision 1.9 distrib/notes/sun2/install: revision 1.7 distrib/notes/sun2/install: revision 1.8 distrib/notes/mvme68k/prep: revision 1.14 distrib/notes/hp700/prep: revision 1.2 distrib/notes/mvme68k/hardware: revision 1.10 distrib/notes/atari/xfer: revision 1.16 distrib/notes/amiga/upgrade: revision 1.27 Cosmetics or mdoc warning fixes @ text @d1 1 a1 1 .\" $NetBSD$ d47 1 a47 1 If your machine gives you a `\*[Gt]' prompt instead of an `ok' prompt, d51 1 a51 1 .No \*[Gt] Ic n d129 4 a132 4 SCSI ID 2 .Pf ( Sq unit 2) and SCSI ID 3 .Pf ( Sq unit d208 4 a211 1 .Dq Nx "" disk unit d235 2 a236 1 .Pf ( Sq Li 0 d242 2 a243 1 etc.) d262 2 a263 2 on the fourth partition .Pf ( Sq Li d , d297 2 a298 2 on the fourth partition .Pf ( Sq Li d , @ 1.21 log @update minimum disk requirements @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.20 2002/07/11 04:52:51 scottr Exp $ d65 8 @ 1.21.2.1 log @Pull up revision 1.22 (requested by mbw in ticket #487) Mention that the installer defaults to serial setting of 9600 8N1, the user might want to prepare for that. Fixes PR#11946. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.21 2003/10/21 02:16:34 mbw Exp $ a64 8 If you are using a serial console, the .Nx*M installer defaults to using 9600 bps, 8N1 settings. You may want to configure your system and serial terminal like this prior to booting the installer. Additionally, a new installation of .Nx*M will default to these settings as well. .Pp @ 1.20 log @Replace "filesystem" with the correct phrase, "file system." @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.19 2002/06/30 12:43:05 lukem Exp $ d426 1 a426 1 part of your memory unusable). A full binary installation takes about 60 MB @ 1.19 log @clean up whitespace and formatting @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.18 2002/05/03 03:58:45 mbw Exp $ d419 1 a419 1 filesystems, a comfortable size for the d421 1 a421 1 root filesystem partition is @ 1.18 log @add note about dead NVRAM (ethernet address is all F's) and link to FAQ @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.17 2002/04/29 23:33:41 mbw Exp $ d57 1 a57 1 turn them off - d85 1 a85 1 0, and the SCSI device at target ID 0 is d111 1 a111 1 .Li GENERIC d136 1 a136 1 To get OpenBoot PROM 1 to number the SCSI d154 1 a154 1 and d308 1 a308 1 These cards do not automatically create a d310 1 a310 1 entry, so you must traverse the device tree to figure out what the d349 1 a349 1 to determine if it's capable of booting. If it is, it will have the d362 2 a363 1 Great! Also, in case you're interested in further details about your d390 1 a390 1 card as the root device -- you may need to type in the d411 1 a411 1 to look at the partition sizes of disk you intend installing d419 1 a419 1 filesystems, a comfortable size for the d438 1 a438 1 allow a choice between operating on a UTP or a AUI port once the @ 1.18.2.1 log @manually sync distrib/notes/** to -current, excluding pmppc (which isn't in 1.6) @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.19 2002/06/30 12:43:05 lukem Exp $ d57 1 a57 1 turn them off \(em d85 1 a85 1 0, and the SCSI device at target ID 0 is d111 1 a111 1 .Li GENERIC d136 1 a136 1 To get OpenBoot PROM 1 to number the SCSI d154 1 a154 1 and d308 1 a308 1 These cards do not automatically create a d310 1 a310 1 entry, so you must traverse the device tree to figure out what the d349 1 a349 1 to determine if it's capable of booting. If it is, it will have the d362 1 a362 2 Great! Also, in case you're interested in further details about your d389 1 a389 1 card as the root device -- you may need to type in the d410 1 a410 1 to look at the partition sizes of disk you intend installing d418 1 a418 1 filesystems, a comfortable size for the d437 1 a437 1 allow a choice between operating on a UTP or a AUI port once the @ 1.18.2.2 log @pullup-1-6 ticket #469 (scottr). Original log message: Replace "filesystem" with the correct phrase, "file system." @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.18.2.1 2002/07/02 04:20:17 lukem Exp $ d419 1 a419 1 file systems, a comfortable size for the d421 1 a421 1 root file system partition is @ 1.17 log @add section describing how to boot from an SBUS card change ".Dl ok Ic commands" into ".(disp/.disp) and ".No ok Ic commands" since it actually uses a monospaced font in HTML @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.16 2001/07/24 18:14:34 nra Exp $ d31 9 @ 1.16 log @s/Asumming/Assuming/ @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.15 2000/11/05 21:30:22 pk Exp $ d41 5 a45 3 .Dl \*> Ic n .Dl ok Ic setenv sunmon-compat? false .Dl ok d48 3 a50 1 turn them off - NetBSD can't deal well with this. d52 3 a54 1 .Dl ok Ic setenv security-mode none d131 3 a133 1 .Dl ok Ic "setenv sd-targets 01234567" d162 1 a162 1 ELC, IPX, and all sun4m models) have s similar SCSI target mapping in the d232 3 a234 1 .Dl ok Ic "boot sd(0,0,1)" d239 3 a241 1 .Dl ok Ic "boot sd(0,30,)" d252 3 a254 1 .Dl ok Ic "boot sd(0,10,3)netbsd-GENERIC" d267 3 a269 1 .Dl ok Ic "boot disk:b" d274 3 a276 1 .Dl ok Ic "boot cdrom" d286 3 a288 1 .Dl ok Ic "boot disk2:d netbsd-GENERIC" d296 100 d401 3 a403 1 to look at the partition sizes of disk you intend installing NetBSD on. d409 3 a411 1 filesystems, a comfortable size for the NetBSD root filesystem partition is d428 3 a430 1 allow a choice between operating on a UTP or a AUI port. The @ 1.15 log @Some factual & typographical corrections on the SCSI target mapping topic. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.14 2000/11/03 02:18:50 mbw Exp $ d283 1 a283 1 Asumming a classic partition scheme with @ 1.14 log @fix some typos. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.13 2000/11/01 20:56:06 mbw Exp $ d94 1 a94 5 Unfortunately, the .Nx kernel believes the .Sq unit values returned by the OpenBoot PROM really are the SCSI target IDs. The d97 1 a97 1 kernel does not by default wire things down as does d100 2 a101 3 that the targets (actually the PROM .Sq unit numbers) are probed (01234567). If you only have one disk, it is always d111 2 a113 2 and .Li sd0 d120 1 a120 1 kernel. d133 1 a133 1 kernel that reverses this odd target mapping by treating d136 1 a136 1 .Li sd3 d140 1 a140 1 .Li sd0 . d143 1 a143 1 kernel performs this target remapping, but the d154 2 a155 2 ELC, IPX, and all sun4m models) do not have this mapping problem. You should be aware, however, that the OpenBoot PROM d157 27 a183 6 entries are similarly reversed. That is, .Li disk0 is the hard drive at SCSI ID 3, and .Li disk3 is the hard drive at SCSI ID 3. But don't worry, since it is only a device alias the d185 3 a187 3 kernel finds your SCSI device at the correct target ID. Some models have their internal hard drives fixed at SCSI ID 3, so it may still be advantageous to use the d189 3 a191 2 kernel to ensure that your internal drive shows up as .Li sd0 . @ 1.13 log @hardware: fix a couple of typos add ross sparc 20 clone a little more info on sw device prep: mention that can't boot if root partition is past first 2 GB of disk refine wording of section on scsi id mappings install: add a little more info to the tape booting section @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.12 2000/10/29 14:08:10 lukem Exp $ d278 1 a278 1 Pp @ 1.12 log @more work: - use .Tn, .Bx, .Ul, .Key, .Sq, .Dq, .Li, .Dl, (etc) ... as appropriate - be more consistent between various ports' install notes - other cleanups @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.11 2000/10/22 00:44:04 mbw Exp $ d53 6 a58 4 system: SCSI ID (set by physical jumpers on the device), SCSI target (set by OpenBoot PROM 1, based on its SCSI ID), and the name you reference within an operating system (set by the kernel, based on the SCSI target). d60 2 a61 2 Sun shipped these systems with the internal drive at SCSI ID 0. The default value of the OpenBoot PROM variable d65 8 a72 3 The means that the device at SCSI ID 3 is at SCSI target 0, and the SCSI device at ID 0 is at target 3. When you type d74 3 a76 2 the OpenBoot PROM will boot from target 0 (that is, SCSI ID 3). The d83 2 a84 10 This means that SCSI ID 0 (target 3) is .Li sd0 , SCSI ID 1 (target 1) is .Li sd1 , and so on. Essentially, .Tn SunOS reverses the OpenBoot PROM target remapping. .Bl -column -offset indent SCSI\ ID SCSI\ Target SunOS\ name .It Em SCSI\ ID Ta Em SCSI\ Target Ta Em SunOS\ name d94 1 a94 1 The d96 11 a106 3 kernel is not hard-wired in this manner and names the disks in the order that the targets are probed (01234567). If you only have one disk, it is always d108 8 a115 4 irregardless of its SCSI ID or target, and there are no problems. If you have two disks, one at SCSI ID 2 (target 2) and SCSI ID 3 (target 0), then they are recognized as d122 2 a123 2 There are two approaches to fixing this problem: changing OpenBoot PROM 1, and changing the d126 3 a128 2 To get OpenBoot PROM 1 to number the SCSI targets the same as the SCSI IDs, you need to run this command: d138 3 a140 2 kernel that reverses this odd target mapping by treating target 0 (i.e. SCSI ID 3) as d142 3 a144 1 and target 3 (i.e. SCSI ID 0) as d158 13 a170 3 The sun4 models and the machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) do not have this target mapping problem. You should be aware, however, that some models have their internal hard d214 3 a216 1 And, to boot from the fourth partition ( d223 1 a223 1 .Dl ok Ic "boot sd(0,10,3)" d243 3 a245 1 And, to boot from the fourth partition ( d251 1 a251 1 .Dl ok Ic "boot disk2:d" d278 3 @ 1.11 log @minor fixes, added info on how sun4 models deal with scsi targets some typos caught add info on how to break from automatically booting (i.e. enter ROM prompt) @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.10 2000/10/21 04:49:26 mbw Exp $ d3 1 a3 1 .Ss2 Configuring your ROM d5 8 a12 6 Before you start, you should configure your ROM. There are three categories of ROM: ``sunmon'' (sometimes called Restricted Prompt, sun monitor, or old command mode), OpenBoot PROM 1, and OpenBoot PROM 2. The sun4 machines only have sunmon. Some of the early sun4c models default to sunmon but have OpenBoot PROM 1 (OBP1). The later sun4c models and all sun4m models have OBP2. d15 2 a16 2 powered on. Pressing the .Pa `STOP' d18 4 a21 4 .Pa `L1' key, found on the left side of your keyboard) and the .Pa `a' key will halt your system and give you a ROM prompt. If you are using a d23 1 a23 1 .Pa `Pause' d25 3 a27 3 .Pa `a' keys. If you are using a serial console, send a .Pa `BREAK' d29 1 a29 1 .Pa `BREAK' d33 3 a35 1 (sometimes called ``new command mode'') if it defaults to sunmon. The d37 1 a37 1 kernel relies on some of the functionality provided by the OBP. d45 3 a47 2 Next, if you are using any security features of OBP, you should turn them off -- NetBSD can't deal well with this. d50 2 a51 2 The OBP1 machines (SPARCstation/server 1, SPARCstation/server 1+, IPC, and SLC) have an odd SCSI quirk you should be aware of. d54 1 a54 1 SCSI target (set by OBP1, based on its SCSI ID), and the name you d59 24 a82 12 The default value of the OBP variable .Pa `sd-targets' is .Pa 31204567. The means that the device at SCSI ID 3 is at SCSI target 0, and the SCSI device at ID 0 is at target 3. When you type ``boot scsi(0,0,0)'', OBP will boot from target 0 (that is, SCSI ID 3). The SunOS kernel is hard-wired to map sd0 to SCSI target 3, and sd3 to SCSI target 0. This means that SCSI ID 0 (target 3) is sd0, SCSI ID 1 (target 1) is sd1, and so on. Essentially, SunOS reverses the OBP target remapping. d94 1 a94 1 The d97 5 a101 3 that the targets are probed (01234567). If you only have one disk, it is always sd0 irregardless of its SCSI ID or target, and there are no problems. If you have two disks, one at d103 5 a107 1 as sd1 and sd0 respectively. This can be a problem if you are not d110 2 a111 2 There are two approaches to fixing this problem: changing OBP1, and changing the d113 2 a114 1 kernel. To get OBP1 to number the SCSI targets the same as the SCSI d116 3 a118 1 .Dl ok Ic setenv sd-targets 01234567 d120 2 a121 1 SunOS on this machine or if you reset the OBP variables. d123 1 a123 1 The other approach is to use a d126 11 a136 3 (i.e. SCSI ID 3) as sd3 and target 3 (i.e. SCSI ID 0) as sd0. The GENERIC_SCSI3 kernel performs this target remapping, but the GENERIC and INSTALL kernels do not. d142 13 a154 12 The sun4 models and the machines with OBP2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) do not have this target mapping problem. You should be aware, however, that some models have their internal hard drives fixed at SCSI ID 3, so it may still be advantageous to use the GENERIC_SCSI3 kernel to ensure that your internal drive shows up as sd0. . .Ss2 Determining how to access your SCSI disk from the ROM . sunmon and OBP1 use an archaic .Ic sd( Ns Ar c,u,p Ns Ic \&) syntax to address SCSI devices. OBP2 uses a more intuitive d157 2 a158 2 To calculate the parameters for sunmon and OBP1: .(tag xcc d163 2 a164 1 the expression `(8 * TARGET) + LUN' d166 10 a175 1 the partition number from which to boot (0=`a', 1=`b', etc). d177 1 d180 1 d182 1 d185 1 d187 4 a190 1 And, to boot from the fourth partition (`d', often the d194 1 d197 5 a201 5 Now, for OBP2, SCSI devices are specified by an OpenBOOT .Pa `devalias' which provides simple mnemonics for the full path to the device. Type .Pa `devalias' in OBP2 to get a list of all of the available aliases. d205 3 a207 1 (OBP2 assumes the internal hard drive is at target 3), one would use: d209 4 a212 1 To boot from a CD-ROM (OBP2 assumes the CD-ROM is at target 6), one would use: d214 7 a220 4 And, to boot from the fourth partition (`d', often the .Pa /usr partition) on an external hard drive (target 2, partition 3), one would use: d223 3 a225 2 The full device path specifier for OBP2 depends on how OBP2 recognizes your SCSI controller. Typically, one would use something like: d236 12 a247 6 Asumming a classic partition scheme with root (`/') and /usr filesystems, a comfortable size for the NetBSD root filesystem partition is about 20 MB; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike SunOS 4.x, there are no restrictions on the size of the swap partition that would render part of your memory unusable). A full binary installation takes about 60 MB in `/usr'. d251 13 a263 5 Some network devices (i.e. the built-in `le' interface on sun4m machines) allow a choice between operating on a UTP or a AUI port. The `le' driver supports automatic detection of the port which is actually connected to the wire. Additionally, some of the Fast ethernet devices (such as `be', `hme', `qec', and `qfe') support selection of various speeds and options. d268 31 a298 7 `media' parameter of ifconfig(8). During installation, you'll get the opportunity to specify the appropriate medium. Use ``10base5'' or ``AUI'' to select the AUI connector, or ``10baseT'' or ``UTP'' to select the UTP connector. Fast ethernet interfaces default to ``auto'', which usually does not detect properly and runs at ``10BaseT'' speed. The options are ``10baseT'', ``100baseTX'', and ``auto''. The hme and qfe interfaces also allow ``10baseT-FDX'' and ``100baseTX-FDX''. @ 1.10 log @Major overhaul. Cleaned up a lot of explanations, clarified instructions, provided more detail when necessary and removed extraneous instructions. hardware: totally revamped to be more readable and include all known supported hardware, now matches htdocs/Ports/sparc/hardware.html install: new section on CD-ROM, netboot has instructions on setting up a NetBSD server, removed disklabel instructions (miniroot/sysboot's instructions are clear enough and have error-checking anyways) prep: reorganized, put in cleaner explanation of SCSI target remapping on OpenBOOT PROM 1 machines, put in instructions on how to figure out names ROM uses for SCSI device, put in info about 100BaseTX network cards upgrade: now points to ../common/upgrade @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.9 2000/10/10 12:55:22 lukem Exp $ d12 19 a30 1 First, you should set your system to always use the OpenBoot PROM d55 1 a55 1 .Pa sd-targets d66 2 a67 2 .Bl -column -offset indent SCSI\ ID SCSI\ Target SunOS\ SD-Unit .It Em SCSI-ID Ta Em SCSI\ Target Ta Em SunOS\ SD-Unit d107 2 a108 1 The machines with OBP2 (SPARCstation/server 2, ELC, IPX, and all sun4m d116 1 a116 1 sunmon and OBP1 use a strange d137 3 a139 3 And, to boot from the fourth (`d', typically .Pa usr ) partition on an external hard drive (first SCSI bus, target 2, lun 0, d144 1 a144 1 .Pa devalias d146 1 a146 1 .Pa devalias d155 4 a158 3 And, to boot from the fourth (`d', typically .Pa usr Ns ) partition on an external hard drive (target 2, partition 3), one would use: @ 1.9 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 1 a1 1 .\" $NetBSD: prep,v 1.8 1999/06/12 11:24:35 pk Exp $ d3 54 a56 15 Before you start you might need to consider your disk configuration to sort out a quirk in SCSI-ID to SD-UNIT mapping that exists on Sun Sparcstations. .Pp Upon leaving the factory, SunOS and the OpenBOOT ROM map according to this table: .Bl -column -offset indent SCSI-ID SunOS\ SD-Unit .It Tn Em SCSI-ID Ta Tn Em SunOS\ SD-Unit .It \~\~\~0 Ta \~\~\~sd3 .It \~\~\~1 Ta \~\~\~sd1 .It \~\~\~2 Ta \~\~\~sd2 .It \~\~\~3 Ta \~\~\~sd0 .It \~\~\~4 Ta \~\~\~sd4 .It \~\~\~5 Ta \~\~\~sd5 .It \~\~\~6 Ta \~\~\~sd6 d59 25 a83 13 Unlike SunOS and the OpenBOOT ROM, a generic NetBSD kernel numbers scsi drives sequentially as it finds them. The drive with the lowest scsi-id will be called sd0, the next one sd1, etc. .Pp To ease the installation process, the default NetBSD kernel in the distribution is setup to match the Sun mapping above by hard-wiring scsi-id#3 to sd0 and scsi-id#0 to sd3. The remaining drives will be dynamically mapped to other sd* numbers. .Pp A truly generic NetBSD kernel is also provided as `/netbsd.GENERIC', which will do the standard NetBSD probe ordering. If your configuration differs from the default Sun setup, you can try to use this kernel to complete the installation. d89 59 a147 14 Your OpenBOOT ROM may need some setup. make sure you boot from `new command mode'. If your machine comes up and gives you a `\*>' prompt instead of `ok', type: .Dl \*> Ic n .Dl ok Ic setenv sunmon-compat? false .Dl ok This is needed because the NetBSD kernel relies on functionality provided by OpenBOOT ROMs -- the ability to pass down Forth commands and have them executed in the ROM -- that appears to go away when the OpenBOOT ROM operates in `old monitor compatibility' mode. .Pp Also, you cannot use the security modes of the sparc OpenBOOT ROM. .Dl ok Ic setenv security-mode none .Pp d159 3 a161 1 .Pp d165 3 a167 1 the wire. d172 6 a177 2 opportunity to specify the appropriate medium. Use ``10base5/AUI'' to select the AUI connector, or ``10baseT/UTP'' to select the UTP connector. @ 1.8 log @truely -> truly; PR 7762 @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.7 1999/01/13 07:30:08 ross Exp $ d52 3 a54 1 If you're installing NetBSD/sparc for the first time it's a good idea d58 1 a58 1 a comfortable size for the NetBSD root filesystem partition is about 20MB; d62 1 a62 1 unusable). A full binary installation takes about 60MB in `/usr'. @ 1.8.8.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 1 .\" $NetBSD: prep,v 1.12 2000/10/29 14:08:10 lukem Exp $ d3 34 a36 37 .Ss2 Configuring your PROM . Before you start, you should configure your PROM. There are three categories of PROM: .Dq sunmon (sometimes called Restricted Prompt, sun monitor, or old command mode), OpenBoot PROM 1, and OpenBoot PROM 2. The sun4 machines only have sunmon. Some of the early sun4c models default to sunmon but have OpenBoot PROM 1. The later sun4c models and all sun4m models have OpenBoot PROM 2. .Pp First, you need to stop your system from automatically booting when powered on. Pressing the .Key STOP key (sometimes called the .Key L1 key, found on the left side of your keyboard) and the .Key a key will halt your system and give you a PROM prompt. If you are using a Tadpole SPARCbook, you press the .Key Pause and .Key a keys. If you are using a serial console, send a .Dq BREAK signal from your terminal (the method of sending .Dq BREAK varies from terminal to terminal). .Pp Next, you should set your system to always use the OpenBoot PROM (sometimes called .Dq "new command mode" ) if it defaults to sunmon. The .Nx kernel relies on some of the functionality provided by the OpenBoot PROM. If your machine gives you a `\*>' prompt instead of an `ok' prompt, type: d38 3 d44 4 d49 1 a49 3 Next, if you are using any security features of OpenBoot PROM, you should turn them off - NetBSD can't deal well with this. .Pp d52 1 a52 184 The OpenBoot PROM 1 machines (SPARCstation/server 1, SPARCstation/server 1+, IPC, and SLC) have an odd SCSI quirk you should be aware of. There are three SCSI addressing schemes used by your system: SCSI ID (set by physical jumpers on the device), SCSI target (set by OpenBoot PROM 1, based on its SCSI ID), and the name you reference within an operating system (set by the kernel, based on the SCSI target). .Pp Sun shipped these systems with the internal drive at SCSI ID 0. The default value of the OpenBoot PROM variable .Sq Li sd-targets is .Sq Li 31204567. The means that the device at SCSI ID 3 is at SCSI target 0, and the SCSI device at ID 0 is at target 3. When you type .Dq Ic boot scsi(0,0,0) , the OpenBoot PROM will boot from target 0 (that is, SCSI ID 3). The .Tn SunOS kernel is hard-wired to map .Li sd0 to SCSI target 3, and .Li sd3 to SCSI target 0. This means that SCSI ID 0 (target 3) is .Li sd0 , SCSI ID 1 (target 1) is .Li sd1 , and so on. Essentially, .Tn SunOS reverses the OpenBoot PROM target remapping. .Bl -column -offset indent SCSI\ ID SCSI\ Target SunOS\ name .It Em SCSI\ ID Ta Em SCSI\ Target Ta Em SunOS\ name .It \~\~\~0 Ta \~\~\~3 Ta \~\~\~sd0 .It \~\~\~1 Ta \~\~\~1 Ta \~\~\~sd1 .It \~\~\~2 Ta \~\~\~2 Ta \~\~\~sd2 .It \~\~\~3 Ta \~\~\~0 Ta \~\~\~sd3 .It \~\~\~4 Ta \~\~\~4 Ta \~\~\~st0 .It \~\~\~5 Ta \~\~\~5 Ta \~\~\~st1 .It \~\~\~6 Ta \~\~\~6 Ta \~\~\~cdrom .El .Pp The .Nx kernel is not hard-wired in this manner and names the disks in the order that the targets are probed (01234567). If you only have one disk, it is always .Li sd0 irregardless of its SCSI ID or target, and there are no problems. If you have two disks, one at SCSI ID 2 (target 2) and SCSI ID 3 (target 0), then they are recognized as .Li sd1 and .Li sd0 respectively. This can be a problem if you are not aware of it, particularly when creating an fstab. .Pp There are two approaches to fixing this problem: changing OpenBoot PROM 1, and changing the .Nx kernel. To get OpenBoot PROM 1 to number the SCSI targets the same as the SCSI IDs, you need to run this command: .Pp .Dl ok Ic "setenv sd-targets 01234567" .Pp This may, however, cause problems if you were to later attempt to use .Tn SunOS on this machine or if you reset the OpenBoot PROM variables. .Pp The other approach is to use a .Nx kernel that reverses this odd target mapping by treating target 0 (i.e. SCSI ID 3) as .Li sd3 and target 3 (i.e. SCSI ID 0) as .Li sd0 . The .Li GENERIC_SCSI3 kernel performs this target remapping, but the .Li GENERIC and .Li INSTALL kernels do not. .Pp .(Note This is also a concern when you start building your own customised kernels. .Note) .Pp The sun4 models and the machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) do not have this target mapping problem. You should be aware, however, that some models have their internal hard drives fixed at SCSI ID 3, so it may still be advantageous to use the .Li GENERIC_SCSI3 kernel to ensure that your internal drive shows up as .Li sd0 . . .Ss2 Determining how to access your SCSI disk from the PROM . sunmon and OpenBoot PROM 1 use an archaic .Li sd( Ns Ar c,u,p Ns Ic \&) syntax to address SCSI devices. OpenBoot PROM 2 uses a more intuitive syntax using device aliases. .Pp To calculate the parameters for sunmon and OpenBoot PROM 1: .(tag xcc -offset indent .It Ar c specifies the SCSI controller number (first is 0, second is 1, ...) .It Ar u the hexadecimal number obtained from evaluating the expression .Em (8 * TARGET) + LUN .It Ar p the partition number from which to boot .Po .Sq Li 0 = .Sq Li a , .Sq Li 1 = .Sq Li b , etc. .Pc .tag) .Pp Therefore, to boot from the swap partition on the internal hard drive (first SCSI bus, target 0, lun 0, partition 1), one would use: .Pp .Dl ok Ic "boot sd(0,0,1)" .Pp To boot from a CD-ROM (first SCSI bus, target 6, lun 0, partition dynamically determined), one would use: .Pp .Dl ok Ic "boot sd(0,30,)" .Pp And, to boot from the fourth partition ( .Sq Li d , often the .Pa /usr partition) on an external hard drive (first SCSI bus, target 2, lun 0, partition 3), one would use: .Pp .Dl ok Ic "boot sd(0,10,3)" .Pp Now, for OpenBoot PROM 2, SCSI devices are specified by an OpenBOOT .Ic devalias which provides simple mnemonics for the full path to the device. Type .Ic devalias in OpenBoot PROM 2 to get a list of all of the available aliases. Just the alias and partition are necessary when booting. .Pp Therefore, to boot from the swap partition on the internal hard drive (OpenBoot PROM 2 assumes the internal hard drive is at target 3), one would use: .Pp .Dl ok Ic "boot disk:b" .Pp To boot from a CD-ROM (OpenBoot PROM 2 assumes the CD-ROM is at target 6), one would use: .Pp .Dl ok Ic "boot cdrom" .Pp And, to boot from the fourth partition ( .Sq Li d , often the .Pa /usr partition) on an external hard drive (target 2, partition 3), one would use: .Pp .Dl ok Ic "boot disk2:d" .Pp The full device path specifier for OpenBoot PROM 2 depends on how OpenBoot PROM 2 recognizes your SCSI controller. Typically, one would use something like: .Pa /sbus/esp/sd@@ Ns Ar t,p where t is the SCSI target and p is the partition number. . .Ss2 Deciding on partition sizes . If you're installing .Nx*M for the first time it's a good idea d55 11 a65 29 Asumming a classic partition scheme with .Pa / (root) and .Pa /usr filesystems, a comfortable size for the NetBSD root filesystem partition is about 20 MB; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike .Tn SunOS 4.x , there are no restrictions on the size of the swap partition that would render part of your memory unusable). A full binary installation takes about 60 MB in .Pa /usr . . .Ss2 Configuration of network interfaces . Some network devices (i.e. the built-in .Em le interface on sun4m machines) allow a choice between operating on a UTP or a AUI port. The .Em le driver supports automatic detection of the port which is actually connected to the wire. Additionally, some of the Fast ethernet devices (such as .Em be , .Em hme , .Em qec , and .Em qfe ) support selection of various speeds and options. The default is to attempt to automatically detect the speed. d69 3 a71 31 .Ic media parameter of .Xr ifconfig 8 . During installation, you'll get the opportunity to specify the appropriate medium. Use .Li 10base5 or .Li AUI to select the AUI connector, or .Li 10baseT or .Li UTP to select the UTP connector. Fast ethernet interfaces default to .Li auto , which usually does not detect properly and runs at .Sq 10BaseT speed. The options are .Li 10baseT , .Li 10baseTX , and .Li auto . The .Em hme and .Em qfe interfaces also allow .Li 10baseT-FDX and .Li 100baseT-FDX . @ 1.8.8.2 log @Pullup 1.13 and 1.14 [mbw]: mention that can't boot if root partition is past first 2 GB of disk refine wording of section on scsi id mappings @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.8.8.1 2000/11/01 03:48:33 tv Exp $ d53 4 a56 6 system: SCSI target ID (set by physical jumpers on the device), PROM .Sq unit number (set by OpenBoot PROM 1, based on its SCSI target ID), and the name you reference within an operating system (set by the kernel, based on the PROM .Sq unit number). d58 2 a59 2 Sun shipped these systems with the internal drives set to SCSI target IDs 3 and 1. The default value of the OpenBoot PROM variable d63 3 a65 8 This variable maps how the OpenBoot PROM 1 assigns .Sq unit numbers based on the SCSI target ID. Thus the device at SCSI target ID 3 is considered .Sq unit 0, and the SCSI device at target ID 0 is .Sq unit 3. When you type d67 2 a68 3 the OpenBoot PROM will boot from .Sq unit 0 (which is SCSI target ID 3, the internal hard drive). The d75 10 a84 2 .Bl -column -offset indent PROM\ Unit# SCSI\ Target SunOS\ name .It Em PROM\ Unit# Ta Em SCSI\ Target Ta Em SunOS\ name d94 1 a94 1 Unfortunately, the d96 3 a98 11 kernel believes the .Sq unit values returned by the OpenBoot PROM really are the SCSI target IDs. The .Nx*M .Li GENERIC kernel does not by default wire things down as does .Tn SunOS . It names the disks in the order that the targets (actually the PROM .Sq unit numbers) are probed (01234567). If you only have one disk, it is always d100 4 a103 8 regardless of its SCSI target ID or its PROM .Sq unit number, and there are no problems. If you have two disks, one at SCSI ID 2 ( .Sq unit 2) and SCSI ID 3 ( .Sq unit 0), then they are recognized as d110 2 a111 2 There are two approaches to fixing this problem: changing the mapping that OpenBoot PROM 1 does, and changing the d114 2 a115 3 To get OpenBoot PROM 1 to number the SCSI .Sq unit numbers the same as the SCSI target IDs, you need to run this command: d125 2 a126 3 kernel that reverses this odd target mapping by treating .Sq unit 0 (i.e. SCSI target ID 3) as d128 1 a128 3 and .Sq unit 3 (i.e. SCSI target ID 0) as d142 3 a144 13 The machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) do not have this mapping problem. You should be aware, however, that the OpenBoot PROM .Ic devalias entries are similarly reversed. That is, .Li disk0 is the hard drive at SCSI ID 3, and .Li disk3 is the hard drive at SCSI ID 3. But don't worry, since it is only a device alias the .Nx kernel finds your SCSI device at the correct target ID. Some models have their internal hard d188 1 a188 3 And, to boot from a kernel named .Li netbsd-GENERIC on the fourth partition ( d195 1 a195 1 .Dl ok Ic "boot sd(0,10,3)netbsd-GENERIC" d215 1 a215 3 And, to boot from a kernel named .Li netbsd-GENERIC on the fourth partition ( d221 1 a221 1 .Dl ok Ic "boot disk2:d netbsd-GENERIC" a247 3 .Pp Most sparc systems have trouble booting if the root partition extends beyond the first 2 GB of your disk. @ 1.8.8.3 log @Pullup 1.15 [pk]: Some factual & typographical corrections on the SCSI target mapping topic. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.8.8.2 2000/11/03 20:38:40 tv Exp $ d94 5 a98 1 The d101 1 a101 1 kernel does not wire things down as does d104 3 a106 2 that the SCSI targets are probed (01234567). If you only have one disk, it is always d116 2 a118 2 and .Li sd1 d125 1 a125 1 kernel configuration. d138 1 a138 1 kernel that matches the PROM's odd target mapping by treating d141 1 a141 1 .Li sd0 d145 1 a145 1 .Li sd3 . d148 1 a148 1 kernel performs this target mapping, but the d159 2 a160 2 ELC, IPX, and all sun4m models) have s similar SCSI target mapping in the form of a d162 6 a167 27 entry. That is, the device alias .Ic disk is shorthand for the disk at SCSI ID 3 on the internal SCSI controller. Normally, the .Ic disk device alias is what the PROM uses as the default boot device, i.e. in the absence of a .Ar device argument to the .Ic boot command. Note that there are also pre-configured device alias entries for .Ic disk0, .Ic disk1, .Ic disk2 and .Ic disk3 , which are in fact a one-to-one mapping to the SCSI targets .Ic 0 to .Ic 3 .Pq all on the internal SCSI controller . .Pp Again, it may be advantageous to use a fixed .Dq SCSI target to .Do d169 3 a171 3 disk unit .Dc mapping in your kernel configuration file (such as is done in the d173 2 a174 3 kernel) to ensure that your disks remain showing up at the same .Nx device unit numbers even if you add disks to your system at a later time. @ 1.7 log @Markup for -mdoc and -mdoc2html. @ text @d1 1 a1 1 .\" $NetBSD: prep,v 1.6 1998/01/09 18:47:26 perry Exp $ d29 1 a29 1 A truely generic NetBSD kernel is also provided as `/netbsd.GENERIC', @ 1.6 log @RCS Id Police. @ text @d1 2 a2 2 $NetBSD$ d6 1 a6 1 d9 11 a19 10 SCSI-ID -> SunOS SD-UNIT 0 sd3 1 sd1 2 sd2 3 sd0 4 sd4 5 sd5 6 sd6 d23 1 a23 1 d28 1 a28 1 d33 5 a37 5 NOTE: this is also a concern when you start building your own customised kernels. d39 1 a39 1 command mode'. If your machine comes up and gives you a `>' prompt d41 3 a43 5 >n ok setenv sunmon-compat? false ok d48 1 a48 1 d50 2 a51 5 ok setenv security-mode none d54 1 a54 1 d61 1 a61 1 d66 1 a66 1 a71 1 @ 1.5 log @Mention ifconfig(8)'s `media' parameter instead of `link[01]'. @ text @d1 2 @ 1.4 log @Update and clarifications (addresses PR#2933). @ text @d64 10 a73 6 Some network devices (`le') allow a choice between operating on a UTP or a AUI port. Automatic detection of which port is actually connected to the wire is not yet fully implemented in this release. This means that you may have to specify a `link-layer directive' during the installation process. The magic is `link0' to force the use of the UTP port, and `link1' to force the use of the AUI port. @ 1.3 log @merge in 1.2 branch @ text @d43 4 a46 2 This is needed because netbsd cannot handle the old-mode yet, and will firework on you. @ 1.2 log @Start documenting 1.1 installation. @ text @d50 19 @ 1.2.6.1 log @Update @ text @a49 12 If you're installing NetBSD/sparc for the first time it's a good idea to look at the partition sizes of disk you intend installing NetBSD on. Asumming a classic partition scheme with root (`/') and /usr filesystems, a comfortable size for the NetBSD root filesystem partition is about 20MB; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike SunOS 4.x, there are no restrictions on the size of the swap partition that would render part of your memory unusable). A full binary installation takes about 60MB in `/usr'. @ 1.2.6.2 log @Note possibility of using `link[01]' on le network interfaces. @ text @a61 7 Some network devices (`le') allow a choice between operating on a UTP or a AUI port. Automatic detection of which port is actually connected to the wire is not yet fully implemented in this release. This means that you may have to specify a `link-layer directive' during the installation process. The magic is `link0' to force the use of the UTP port, and `link1' to force the use of the AUI port. @ 1.1 log @first cut @ text @d1 49 a49 1 You will need SunOS to install NetBSD. @