Recipes for Booting SunOS on TME (or Sun-2 Hardware)

1. build and install tme-0.8 installed in /opt/tme
2. export LTDL_LIBRARY_PATH=/opt/tme/lib
3. run tme; you'll get a window which is the "screen". Click in the window and use it as the console.
4. use the tape boot to boot sd(0,0,1)vmunix -as mount sd0* as the root device.

SunOS-2.0

Format the disk:

/opt/tme/bin/tmesh ./SUN2-S2.0T1

b st(0,0,0)
st(0,0,1)
[select adaptec scsi controller]
80000
0
0
label

pick maxtor xxx micropolis

Restart and copy the root file system:

b st(0,0,0)
st(0,0,2)

copy st(0,0,3) -> sd(0,0,1)

b st()
sd(0,0,1)vmunix -as
sd0*

After SunOS-2.0 boots and you get to the boot prompt, do the following to "prep" the root file system:

cd /dev
./MAKEDEV sd0
./MAKEDEV st0
newfs /dev/rsd0a
newfs /dev/rsd0g

mount /dev/sd0a /a
cd /a
mt -f /dev/nrst0 rew
mt -f /dev/nrst0 fsf 5
tar xf /dev/nrst0

cd /a/dev
./MAKEDEV std
./MAKEDEV ttys
./MAKEDEV pty0
./MAKEDEV sd0
./MAKEDEV st0
sync

ed /a/etc/fstab
a
/dev/sd0a / 4.2 rw,noquota 1 1
/dev/sd0g /usr 4.2 rw,noquota 1 1
.
w
q

ed /etc/passwd
ed /etc/group
mv /etc/ypbind /etc/ypbind.orig

SunOS-3.2

Format the disk as above but select the "vertex" disk

b st()
st(0,0,3)
[select adaptec scsi controller]
80000
0
0
[select vertex disk]
label

boot: st(0,0,4)
copy from: st(0,0,5)
copy to: sd(0,0,1)

boot: sd(0,0,1)vmunix -as
sd0*

Once SunOS-3.2 boots and you get a command prompt, "prep" the root filesystem with the following:

newfs /dev/rsd0a
newfs /dev/rsd0g
cd /dev
./MAKEDEV st0
mount /dev/sd0a /a
cd /a
mt -f /dev/nrst0 rew
mt -f /dev/nrst0 fsf 6
tar xfv /dev/nrst0

mt -f /dev/nrst0 rew
mt -f /dev/nrst0 fsf 7
tar xfv /dev/nrst0

cd /a/dev
./MAKEDEV std
./MAKEDEV ttys
./MAKEDEV pty0
./MAKEDEV sd0
./MAKEDEV st0
sync

ed /a/etc/fstab
a
/dev/sd0a / 4.2 rw,noquota 1 1
/dev/sd0g /usr 4.2 rw,noquota 1 1
.
w
q

mv /etc/ypbind /etc/ypbind.orig

SunOS-3.5

always mt -f /dev/nrst rew + fsf

Micropolis 1304 42mb Micropolis 1325 69mb Maxtor XT-1050 38mb Fujitsu M2243AS 68mb Vertex V185 71mb 1166/7/17

To get internal logs, which are helpful for debugging:

run with --log log
log scsibus0 1000
log cpu0 2000