Browse Source

openbsd, not netbsd

OPENBSD_2_0
deraadt 28 years ago
parent
commit
a332c672cf
2 changed files with 25 additions and 30 deletions
  1. +22
    -27
      src/etc/etc.sparc/README
  2. +3
    -3
      src/etc/etc.sparc/install.sh

+ 22
- 27
src/etc/etc.sparc/README View File

@ -1,16 +1,11 @@
# $Id: README,v 1.1.1.1 1995/10/18 08:38:01 deraadt Exp $
# $Id: README,v 1.2 1995/11/08 07:12:52 deraadt Exp $
Initial test versions of a NetBSD/sparc binaries install are available
Initial test versions of a OpenBSD/sparc binaries install are available
at
ftp.iastate.edu:/pub/netbsd/NetBSD-current/binaries/sparc
sun-lamp.cs.berkeley.edu:pub/NetBSD/arch/sparc
ftp.wonderland.org:NetBSD/arch/sparc [UK]
ftp.informatik.tu-muenchen.de:\
/pub/comp/os/bsd/NetBSD/NetBSD-current/binaries/sparc
and many other NetBSD mirror sites. Some mirror sites may take a day
or two to catch up.
The NetBSD/sparc port runs on sun4c class machines, ie. the
ftp.openbsd.org:/pub/OpenBSD/snapshots/sparc
Some mirror sites may take a day or two to catch up.
The OpenBSD/sparc port runs on sun4c class machines, ie. the
SS 1, 1+, 2, IPC, IPX, SLC, and ELC. it does not run on the
server-series machines, or the SS10-series machines.
@ -21,7 +16,7 @@ NOTE: THESE INSTRUCTIONS MAY CHANGE WITH EACH SNAPSHOT.
Until there are better instructions written, here's a rough idea:
1. format and partition the disk using sunos. yup, NetBSD/sparc uses
1. format and partition the disk using sunos. yup, OpenBSD/sparc uses
sunos disk labels. i am running a quantum 105 with these partition
sizes:
a: 28140 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 133)
@ -39,9 +34,9 @@ Until there are better instructions written, here's a rough idea:
2. newfs it using sunos. yup, the filesystem format is identical.
UFS hasn't changed much over the years. (If you can, there is
a performance benefit from newfs'ing using NetBSD.)
a performance benefit from newfs'ing using OpenBSD.)
If you newfs using the NetBSD newfs command, be sure to use -O
If you newfs using the OpenBSD newfs command, be sure to use -O
to specify the `4.3BSD filesystem format' for your / partition,
otherwise you will not be able to boot. The SunOS boot blocks do
not understand the extended 4.4 filesystem format.
@ -49,7 +44,7 @@ Until there are better instructions written, here's a rough idea:
3. put a SunOS /boot program in the root partition, and use
"installboot" to cause it to work. the "installboot" man page
says to do something like this: say you are running SunOS, and
the drive you are installing NetBSD/sparc on is currently at
the drive you are installing OpenBSD/sparc on is currently at
/dev/sd1. You have made the filesystems on that drive already.
# mount /dev/sd1a /mnt
# cp /boot /mnt/boot
@ -66,22 +61,22 @@ Until there are better instructions written, here's a rough idea:
5. copy /mnt/etc/fstab.sd to /mnt/etc/fstab and edit to match your
disk layout.
6. the install script copies the kernel called "netbsd.scsi3" to
/mnt/netbsd. Two sample kernels are supplied: "netbsd" and
"netbsd.scsi3".
6. the install script copies the kernel called "bsd.scsi3" to
/mnt/bsd. Two sample kernels are supplied: "bsd" and
"bsd.scsi3".
Unlike SunOS and the ROM, NetBSD numbers scsi drives sequentially
Unlike SunOS and the ROM, OpenBSD numbers scsi drives sequentially
as it finds them. The drive with the lowest scsi-id will be called
sd0. SunOS and the ROM map normally map sd0 to scsi-id 3. Thus, if
you have two drives, it's quite likely that NetBSD will disagree with
you have two drives, it's quite likely that OpenBSD will disagree with
the ROM.
The "netbsd.scsi3" kernel gets around this problem, by hard-wiring
The "bsd.scsi3" kernel gets around this problem, by hard-wiring
scsi-id#3 to sd0. The remaining drives will be dynamically mapped
to other sd* numbers. If you have more than one drive you will
want to use this kernel.
the "netbsd" kernel expects your root drive to be at the standard
the "bsd" kernel expects your root drive to be at the standard
SunOS sd0==scsi-id#3 location. If you have a second drive at any
of scsi-id's 0, 1, or 2, this kernel will NOT work for you. If you
know what you are doing, you could use this kernel.
@ -91,7 +86,7 @@ Until there are better instructions written, here's a rough idea:
>n
ok setenv sunmon-compat? false
ok
this is needed because netbsd cannot handle the old-mode yet,
this is needed because bsd cannot handle the old-mode yet,
and will firework on you.
you cannot use the security modes of the sparc ROM. sorry, same
@ -100,14 +95,14 @@ Until there are better instructions written, here's a rough idea:
8. if needed, swap your scsi id's. now try a reboot. initially I'd
suggest you boot "-bs", then try multiuser after that. if you boot
single-user the netbsd incantation for making root read-write
single-user the bsd incantation for making root read-write
is "mount -u /dev/sd0a /". alternatively, the command reboot is
found in /sbin.
9. to boot from netbsd by default, tell something like this to your
9. to boot from bsd by default, tell something like this to your
ROM.
>n
ok setenv boot-from sd(0,0,0)netbsd
ok setenv boot-from sd(0,0,0)bsd
ok
please let me know of any errors in these instructions or in the
@ -115,4 +110,4 @@ archives. if so i'll correct them.
good luck.
<deraadt@fsa.ca>
<deraadt@openbsd.org>

+ 3
- 3
src/etc/etc.sparc/install.sh View File

@ -1,5 +1,5 @@
#!/bin/sh
# $Id: install.sh,v 1.1.1.1 1995/10/18 08:38:02 deraadt Exp $
# $Id: install.sh,v 1.2 1995/11/08 07:12:53 deraadt Exp $
umask 0
cat ./bin.tar.gz | gzip -d | (cd /mnt; tar xvpf -)
cat ./etc.tar.gz | gzip -d | (cd /mnt; tar xvpf -)
@ -14,7 +14,7 @@ cat ./usr.sbin.tar.gz | gzip -d | (cd /mnt; tar xvpf -)
cat ./usr.share.tar.gz | gzip -d | (cd /mnt; tar xvpf -)
cat ./var.tar.gz | gzip -d | (cd /mnt; tar xvpf -)
cat ./dev.tar.gz | gzip -d | (cd /mnt; tar xvpf -)
cp ./netbsd.scsi3 /mnt/netbsd
chmod 640 /mnt/netbsd; chown root.kmem /mnt/netbsd
cp ./bsd.scsi3 /mnt/bsd
chmod 640 /mnt/bsd; chown root.kmem /mnt/bsd
cd /mnt/dev; ./MAKEDEV all
mv /mnt/etc/fstab.sd /mnt/etc/fstab

Loading…
Cancel
Save