NetBSD

History

abs 2108b54359 34 different termcap subsets, plus a couple of ports still using the full termcap distfile. In an attempt to reduce the madness switch everyone (except the i386 cd install which does its own thing) to the same (under 8K) termcap subset: ansi ansi/pc-term compatible with color dumb\|unknown 80-column dumb tty hp300h HP Catseye console iris-ansi-ap IRIS ANSI in application-keypad mode iris-ansi\|iris-ansi-net IRIS emulating 40 line ANSI terminal (almost VT100) sun\|sun1\|sun2\|sun-il Sun Microsystems Inc. console with working insert-line vt100\|vt100-am DEC VT100 (w/advanced video) vt220-8 DEC VT220 8 bit terminal vt220\|vt200\|vt300 DEC VT220 in vt100 emulation mode wsvt25 NetBSD wscons in 25 line DEC VT220 mode wsvt25m NetBSD wscons in 25 line DEC VT220 mode with Meta x68k\|x68k-ite NetBSD/x68k ITE xterm\|vs100 xterm terminal emulator (X Window System) Trying to provide similar functionality across all ports? It'll never catch on...		2009-09-20 23:19:50 +00:00
..
cdroms
floppy-GENERIC	Consistently use gzip with the -n flag so dates are not embedded.	2009-04-03 22:36:34 +00:00
instkernel	34 different termcap subsets, plus a couple of ports still using	2009-09-20 23:19:50 +00:00
rz25dist	Consistently use gzip with the -n flag so dates are not embedded.	2009-04-03 22:36:34 +00:00
Makefile	Change remaining instances of ${RELEASEDIR}/${MACHINES} to	2008-06-23 02:16:53 +00:00
README.files	Various updates to the INSTALL notes in preparation for 5.0. Changes	2009-04-23 01:56:48 +00:00

README.files

$NetBSD: README.files,v 1.14 2009/04/23 01:56:48 snj Exp $

	   Tape, CD, Disk, and Netboot Images
	   ----- --- ----- --- ------- ------

This release or snapshot contains three installation image types.
The first, for floppies, is split into a multiple volume set.

	installation/floppy/disk1of3
	installation/floppy/disk2of3
	installation/floppy/disk3of3

	installation/diskimage/cdhdtape

	installation/instkernel/netbsd.gz

All three boot images load the same installation kernel into memory
and then make no further use of the source media. The general idea
is to load a kernel with a pre-initialized memory filesystem of
utilities and an installation program.

The floppy image set uses two floppies to load the install kernel.
The cdhdtape image can be written to a CD, hard drive, or tape and
then booted from the SRM console. The kernel image can be netbooted
or loaded off the root directory of an existing installation.

Note:	The netboot loader can load the netbsd.gz file directly; it
	is not necessary to ungzip this kernel first.

To copy the boot images to a magnetic disk under unix, the dd(1)
command can be used:

Floppy:
	dd if=disk1of3 of=/dev/rfd0a bs=18k
	(change floppies)
	dd if=disk2of3 of=/dev/rfd0a bs=18k
	(change floppies)
	dd if=disk3of3 of=/dev/rfd0a bs=18k


You can write the image to a hard drive too:

	dd bs=18k if=cdhdtape of=/dev/rsd1c
	dd bs=18k if=cdhdtape of=/dev/rsd1d (NetBSD/i386)

For a tape, it is important to use a block size of 512, so:

	dd bs=512 if=cdhdtape of=/dev/erst0	(NetBSD)
	dd bs=512 if=cdhdtape of=/dev/rmt0h	(Digital Unix)

Note that the bits on the installation media are only used when
initially loaded. They can be written to a hard drive, loaded, and
then overwritten during the installation with no conflict, or
alternatively, the boot CD or tape can be removed and replaced with
one containing the installation sets.

The install notes from this directory subtree are present on the
installation file system.