summaryrefslogtreecommitdiff
path: root/distrib/notes/sun3/xfer
diff options
context:
space:
mode:
authorMiod Vallat <miod@cvs.openbsd.org>2000-10-18 21:54:44 +0000
committerMiod Vallat <miod@cvs.openbsd.org>2000-10-18 21:54:44 +0000
commitdb311172ee37349e40ee183952296757a1403f7c (patch)
tree7e31e1f34fe30d363c7212e0a55d2f7e3782ec74 /distrib/notes/sun3/xfer
parent2f9713a1ba962936303d9cabbdea1d550e5bc657 (diff)
Various updates. Grammar/spelling proofread by ericj.
Diffstat (limited to 'distrib/notes/sun3/xfer')
-rw-r--r--distrib/notes/sun3/xfer36
1 files changed, 33 insertions, 3 deletions
diff --git a/distrib/notes/sun3/xfer b/distrib/notes/sun3/xfer
index 296b2051b39..aaf79f0ebd7 100644
--- a/distrib/notes/sun3/xfer
+++ b/distrib/notes/sun3/xfer
@@ -3,10 +3,11 @@ Installation is supported from several media types, including:
FFS partitions
Tape
Remote NFS partition
+ CD-ROM (with PROM versions >= 3.0)
FTP
HTTP
-However, you can only boot the installation procedure from tape or
+However, you can only boot the installation procedure from disk, tape or
network. This requires some setup work to prepare a bootable image,
either a tape, or a compatible net boot server.
@@ -20,6 +21,35 @@ widely in terms of what peripherals and what sort of network arrangements
a user has, the intent is to provide some way that will be practical.
+Creating a bootable hard disk using SunOS or other Un*x-like system:
+
+ You can copy the miniroot image "miniroot{:--:}OSrev.fs" onto
+ the hard disk you intend to boot on. Traditionally, the
+ way to do this is to use dd(1) to place the bootable filesystem
+ image in the "swap" partition of the disk (while running in
+ single user mode), and then booting from that partition.
+
+ Using the "b" partition allows you to boot without overwriting
+ any useful parts of the disk, you can also use another partition,
+ but don't used the "a" or "c" partition without understanding
+ the disklabel issues described below under "incompatible systems".
+
+ This requires that you be running SunOS, Solaris, OpenBSD or NetBSD
+ which have a compatible view of SunOS disk labels and partitions.
+
+ Use the dd(1) utility to copy the file to the hard drive.
+ Under SunOS, the command would be:
+
+ dd if=floppy{:--:}OSrev.fs of=/dev/rsd0b bs=36b
+ - or -
+ dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=36b
+
+ The blocksize is arbitrary as long as it's a multiple of 512-bytes
+ and within the maximum supported by the driver, i.e. bs=126b may
+ not work for all cases. Again, device/partition names may vary,
+ depending on the OS involved.
+
+
Creating a network bootable setup using SunOS or other Un*x-like system:
The details of setting up a network bootable environment vary
@@ -93,8 +123,8 @@ To install or upgrade OpenBSD using a tape, you need to do the following:
sh -x /tmp/maketape noboot
-If you're using a system other than OpenBSD or SunOS, the tape name and
-other requirements may change.
+ If you're using a system other than OpenBSD or SunOS, the tape
+ name and other requirements may change.
To install OpenBSD using a remote partition, mounted via