Computer History Wiki - User contributions [en]

Installing 4.3 BSD Quasijarus on SIMH

2020-06-27T21:23:17Z

Dugo: reinstate the hint aboute the TYPE command on windows boxen

This is the procedure that I have used to install [[4.3 BSD]] onto [[SIMH]]'s [[MicroVAX II]] emulator. Please note that this is the Quasijarus release of 4.3 BSD.

== Obtaining an install tape ==

You have two choices now, either you can create your own, or you can download a pre-made tape on [https://sourceforge.net/project/showfiles.php?group_id=204974&package_id=309407&release_id=659789 sourceforge]. If you want to build your own tape image, then follow the next section.

== Building your own tape image ==

I will describe what is needed, and how to create your own Quasijarus tape image, that is suitable for installing with SIMH.

=== Requirements ===

You will need the following materials to put together a 4.3 BSD Quasijarus installation:

*A working perl interpeter to make the tape images. 
*A copy of gzip. 
*A working C compiler. 
*A compiled binary of vax from [[SIMH]], along with the ka655x.bin again from [[SIMH]].

You will need the following files from any 4 BSD archive from the Quasijarus0c directory. I have used the files from [https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/ Sourceforge]. You you will have to use a web browser to download them, to deal with the sourceforge download system. But that's the price of free hosting. 

[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/stand.Z/download stand.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/miniroot.Z/download miniroot.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/rootdump.Z/download rootdump.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/usr.tar.Z/download usr.tar.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/srcsys.tar.Z/download srcsys.tar.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/src.tar.Z/download src.tar.Z] 

=== gzcompat ===

Next it's easier on a host machine to convert the downloaded Quasijarus files into gzip, then uncompress them using gzip. For this you will need the [[gzcompat]] program. The sourcecode and a patch for windows compatibility on the link, as it's getting hard to find. Simply compile gzcompat.c. It should be straightforward. The original location for gzcompat is [[http://ifctfvax.superglobalmegacorp.com/releases/UNIX/components/compress.tar here]] and a known good copy is [[http://www.tuhs.org/Archive/4BSD/Distributions/components/compress.tar here]].

On most instances with gcc simply run:

<pre>gcc gzcompat.c -o gzcompat</pre>

And that should be it.

=== Preparing for installation ===

With the files downloaded you will need to uncompress them all and then create the tape file. With the different compression this will be somewhat involved.

The following command will decompress the tape files, on a UNIX install.
<pre>
cat miniroot.Z | gzcompat | gzip -dc > miniroot
cat rootdump.Z | gzcompat | gzip -dc > rootdump
cat src.tar.Z | gzcompat | gzip -dc > src.tar
cat srcsys.tar.Z | gzcompat | gzip -dc > srcsys.tar
cat stand.Z | gzcompat | gzip -dc > stand
cat usr.tar.Z | gzcompat | gzip -dc > usr.tar
</pre>

The tape needs to be created with the [[mkdisttap.pl]] program. Simply run the program and redirect it into a file called quas.tap. You may need to make a few small edits and use TYPE instead of cat when running on Windows. Hints in the link.

<pre>
% ./mkdisttap.pl > quas.tap
% ls -l quas.tap
-rw-r--r-- 1 Neozeed None_ploc 84450876 Feb 6 17:10 quas.tap
%</pre>

An empty RA82 can be created with:

<pre>
% dd if=/dev/zero of=quas.dsk bs=512 count=1216665
</pre>

Now we have our tape and disk, so we are ready to proceed with the install. For those wondering, unlike the 11/780 emulator, the MicrovaxII can run it's microcode in a logical fashion and we are able to boot from tape in this release.

== Boot 1. ==

I disable as many of the devices as possible to get a 'clean' install. So this is the install.ini that I'm going to use.

=== install.ini ===
<pre>
set cr dis
set lpt dis
set rl dis
set ry dis
set ts dis
set xq dis
set rq0 ra82
att rq0 quas.dsk
set rq1 dis
set rq2 dis
set rq3 dis
att tq0 quas.tap
set tti 7b
set tto 7b
boot cpu
</pre>

=== Booting the emulator ===

You then simply run the emulator and pass it the config file.

<pre>
C:\Quasijarus0c\work>vax.exe install.ini

VAX simulator V3.8-0
RQ: creating new file
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot mua0:
(BOOT/R5:0 MUA0

2..
-MUA0
1..0..

=
</pre>

Once the BIOS has done it's POST, it will prompt what device to boot off of at the >>> prompt. The first tape device is mua0:. Once the tape has done the first boot you'll be greeted with the = prompt. From here we are going to load the copy program. Simply type in the following:

<pre>
copy
tms(0,1)
ra(0,1)
</pre>

This will copy the second file onto tape, onto the second file position on our hard disk. The output should be the following:

<pre>
=copy
cpu: uVAX 3000
From: tms(0,1)
To: ra(0,1)
ra0: unlabeled
Copy completed: 308 records copied
=
</pre>

Next we run the boot program. Simply type in the following:

<pre>
boot
ra(0,1)vmunix
</pre>

The resulting output should be the following. The kernel will then prompt for the root partition.

<pre>
=boot
cpu: uVAX 3000

Boot
: ra(0,1)vmunix
ra0: unlabeled
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: no disk label: ra81, size = 891072 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
root device?
</pre>

We will answer with the first ra disk, in a special format, because we have not put a disklabel onto the disk yet.

<pre>
ra0*
</pre>

Once the disk has been mounted we will be dumped to the root prompt. The next step will be creating the default disk label.

=== Creating the disk label ===

Using the disklabel command we will setup the slices automatically (it's done from a file disktab) then install the boot programs. This way we can boot from disk.

Simply type in:

<pre>
disklabel -rw ra0 ra82 “Quasijarus” /usr/mdec/rdboot /usr/mdec/bootra
</pre>

And the disk will now be labled, and bootable from the firmware.

=== Restoring the rootdump ===

From here we are now running from the miniroot. The next step is to run the xtr program to restore the root, and then shutdown the emulator. Enter in the command:

<pre>
disk=ra0 type=ra82 tape=tms xtr
</pre>

And the following will happen:

<pre>
# disk=ra0 type=ra82 tape=tms xtr
Build root file system
Warning: 361 sector(s) in last cylinder unallocated
/dev/rra0a: 15884 sectors in 19 cylinders of 15 tracks, 57 sectors
8.1MB in 2 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776,
Check the file system
** /dev/rra0a
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1 files, 1 used, 7092 free (20 frags, 884 blocks, 0.3% fragmentation)
Rewind tape
Restore the dump image of the root
** /dev/rra0a
** Last Mounted on /a
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
426 files, 5195 used, 1898 free (18 frags, 235 blocks, 0.3% fragmentation)
Root filesystem extracted

If this is an 8650 or 8600, update the console rl02
If this is a 780 or 785, update the floppy
If this is a 730, update the cassette
#
</pre>

After this stage, I just sync the disk a few times, then halt the emulator (CONTROL+E) and exit out. Now we are ready for stage two.

<pre>
If this is a 730, update the cassette
# sync
# sync
# sync

Simulation stopped, PC: 800029AF (BNEQ 800029C6)
sim> q
Goodbye

C:\Quasijarus0c\work>
</pre>

== Boot 2. ==

Now that the install disk is prepared, we need to use a different config file to reflect the emulator being able to autoboot to the disk. The new configuration is as follows:

=== boot.ini ===
<pre>
set cr dis
set lpt dis
set rl dis
set ry dis
set ts dis
set xq dis
set rq0 ra82
att rq0 quas.dsk
set rq1 dis
set rq2 dis
set rq3 dis
att tq0 quas.tap
set tti 7b
set tto 7b
att nvr nvram.dat
dep bdr 1
boot cpu
</pre>

=== Booting the emulator ===

Now boot up the emulator with the boot.ini The first time we boot up in this configuration the emulator will prompt for what device will be the default device. If you typo this, you will have to delete the nvram.dat file, and try again. The default device will be dua0: which is the primary rq disk.

<pre>
C:\Quasijarus0c\work>vax.exe boot.ini

VAX simulator V3.8-0
NVR: creating new file
NVR: buffering file in memory
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
No default boot device has been specified.

Available devices.
-DUA0 (RA 82)
-MUA0 (TK 50)
-MUA1 (TK 50)
-MUA2 (TK 50)
-MUA3 (TK 50)

Device? [XQA0]: dua0:

(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

loading boot

Boot
: /vmunix
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: ra82, size = 1216665 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
Changing root device to ra0a
Automatic reboot in progress...
Fri Feb 6 09:47:10 PST 2004
Can't open checklist file: /etc/fstab
Automatic reboot failed... help!
erase ^?, kill ^U, intr ^C
#
</pre>

=== Preparing the disk ===

Now we have to prep the machine for both the tape, and the type of disk. Type in the following commands.

<pre>
# newfs ra0g ra82
# newfs ra0h ra82
# mkdir /home
# mount /dev/ra0g /usr
# cd /dev
# MAKEDEV tmscp0
# MAKEDEV dz0
</pre>

The output will be like this:

<pre>
# newfs ra0g ra82
/dev/rra0g: 841320 sectors in 984 cylinders of 15 tracks, 57 sectors
430.8MB in 62 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984,
123728, 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656,
246400, 260144, 273888, 287632, 301376, 315120, 328864, 342608, 356352,
370096, 383840, 397584, 411328, 425072, 437792, 451536, 465280, 479024,
492768, 506512, 520256, 534000, 547744, 561488, 575232, 588976, 602720,
616464, 630208, 643952, 656672, 670416, 684160, 697904, 711648, 725392,
739136, 752880, 766624, 780368, 794112, 807856, 821600, 835344,
# newfs ra0h ra82
Warning: 209 sector(s) in last cylinder unallocated
/dev/rra0h: 291346 sectors in 341 cylinders of 15 tracks, 57 sectors
149.2MB in 22 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984,
123728, 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656,
246400, 260144, 273888, 287632,
# mkdir /home
# mount /dev/ra0g /usr
# cd /dev
# MAKEDEV tmscp0
# MAKEDEV dz0
</pre>

=== Restoring the usr slice ===

The disk's /usr slice will not have been formatted. We can not go ahead and mount it, and restore the /usr files.

<pre>
# cd /usr
# mt rew
# mt fsf 3
# tar xpbf 20 /dev/rmt12
# mkdir src
# cd src
# mkdir sys
# cd sys
# mt fsf
# tar xpbf 20 /dev/rmt12
# cd ..
# mt fsf
# tar xpbf 20 /dev/rmt12
</pre>

=== Configuring the fstab ===

Now we just need to create the fstab then we can reboot the emulator into multiuser mode. Enter in the following commands:

<pre>
# cd /etc
# cat > fstab
/dev/ra0a:/:rw:1:1
/dev/ra0h:/home:rw:1:3
/dev/ra0g:/usr:rw:1:2
</pre>

Now you need to press CONTROL+d which will end the stream. Finally you can tell the emulator to reboot.

<pre>
# reboot
syncing disks... done

HALT instruction, PC: 8002F4F8 (BRB 8002F4F7)
sim> q
Goodbye
NVR: writing buffer to file
</pre>

== First Multiuser Boot ==

Now we can just re-run the last command, and we should boot multiuser! By default there is no root password. Also the system will run fsck uppon boot, so depending on your host computer this could take a while.

<pre>
C:\Quasijarus0c\work>vax.exe boot.ini

VAX simulator V3.8-0
NVR: buffering file in memory
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

loading boot

Boot
: /vmunix
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: ra82, size = 1216665 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
Changing root device to ra0a
Automatic reboot in progress...
Fri Feb 6 09:59:45 PST 2004
/dev/ra0a: 448 files, 5199 used, 1894 free (22 frags, 234 blocks, 0.3% fragmentation)
/dev/rra0g: 12312 files, 71682 used, 323169 free (417 frags, 40344 blocks, 0.1% fragmentation)
/dev/rra0h: 1 files, 1 used, 136503 free (15 frags, 17061 blocks, 0.0% fragmentation)
Fri Feb 6 09:59:58 PST 2004
checking quotas: done.
starting system logger

preserving editor files
clearing /tmp
standard daemons: update cron accounting.
starting network daemons: routedFeb 6 10:00:00 myname named[79]: /etc/named.boo
t: No such file or directory
named inetd printer.
starting local daemons: sendmail.
Fri Feb 6 10:00:01 PST 2004

4.3 BSD UNIX (myname.my.domain) (console)

login:
</pre>

Now we can simply logon as root.

<pre>
Fri Feb 6 10:00:01 PST 2004

4.3 BSD UNIX (myname.my.domain) (console)

login: root
Feb 6 10:01:26 myname login: ROOT LOGIN console
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004

Welcome to UNIX!

erase ^?, kill ^U, intr ^C
#
</pre>

From here you can explore the system. All of the man pages are installed, and there is enough of a base system to get going. Right now the networking is outside of the scope of this guide.

=== Enabling remote users ===

Shutdown the OS, and add the following lines into the boot.ini (just make sure they are above the boot command or it'll not work correctly..). This will allow for 8 users to connect on tcp port 8888.

<pre>
set dz lines=8
att dz 8888
set dz 7b
</pre>

I would also recommend to windows users, either [[putty]], or [[syncterm]]. The default telnet client sucks.

[[Category:SIMH Tutorials]]

Installing 4.3 BSD Quasijarus on SIMH

2020-06-27T18:24:42Z

Dugo: add windows tips

This is the procedure that I have used to install [[4.3 BSD]] onto [[SIMH]]'s [[MicroVAX II]] emulator. Please note that this is the Quasijarus release of 4.3 BSD.

== Obtaining an install tape ==

You have two choices now, either you can create your own, or you can download a pre-made tape on [https://sourceforge.net/project/showfiles.php?group_id=204974&package_id=309407&release_id=659789 sourceforge]. If you want to build your own tape image, then follow the next section.

== Building your own tape image ==

I will describe what is needed, and how to create your own Quasijarus tape image, that is suitable for installing with SIMH.

=== Requirements ===

You will need the following materials to put together a 4.3 BSD Quasijarus installation:

*A working perl interpeter to make the tape images. 
*A copy of gzip. 
*A working C compiler. 
*A compiled binary of vax from [[SIMH]], along with the ka655x.bin again from [[SIMH]].

You will need the following files from any 4 BSD archive from the Quasijarus0c directory. I have used the files from [https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/ Sourceforge]. You you will have to use a web browser to download them, to deal with the sourceforge download system. But that's the price of free hosting. 

[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/stand.Z/download stand.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/miniroot.Z/download miniroot.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/rootdump.Z/download rootdump.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/usr.tar.Z/download usr.tar.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/srcsys.tar.Z/download srcsys.tar.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/src.tar.Z/download src.tar.Z] 

=== gzcompat ===

Next it's easier on a host machine to convert the downloaded Quasijarus files into gzip, then uncompress them using gzip. For this you will need the [[gzcompat]] program. The sourcecode and a patch for windows compatibility on the link, as it's getting hard to find. Simply compile gzcompat.c. It should be straightforward. The original location for gzcompat is [[http://ifctfvax.superglobalmegacorp.com/releases/UNIX/components/compress.tar here]] and a known good copy is [[http://www.tuhs.org/Archive/4BSD/Distributions/components/compress.tar here]].

On most instances with gcc simply run:

<pre>gcc gzcompat.c -o gzcompat</pre>

And that should be it.

=== Preparing for installation ===

With the files downloaded you will need to uncompress them all and then create the tape file. With the different compression this will be somewhat involved.

The following command will decompress the tape files, on a UNIX install.
<pre>
cat miniroot.Z | gzcompat | gzip -dc > miniroot
cat rootdump.Z | gzcompat | gzip -dc > rootdump
cat src.tar.Z | gzcompat | gzip -dc > src.tar
cat srcsys.tar.Z | gzcompat | gzip -dc > srcsys.tar
cat stand.Z | gzcompat | gzip -dc > stand
cat usr.tar.Z | gzcompat | gzip -dc > usr.tar
</pre>

The tape needs to be created with the [[mkdisttap.pl]] program. Simply run the program and redirect it into a file called quas.tap. You may need to make small edit when running on Windows. Instructions in the link.

<pre>
% ./mkdisttap.pl > quas.tap
% ls -l quas.tap
-rw-r--r-- 1 Neozeed None_ploc 84450876 Feb 6 17:10 quas.tap
%</pre>

An empty RA82 can be created with:

<pre>
% dd if=/dev/zero of=quas.dsk bs=512 count=1216665
</pre>

Now we have our tape and disk, so we are ready to proceed with the install. For those wondering, unlike the 11/780 emulator, the MicrovaxII can run it's microcode in a logical fashion and we are able to boot from tape in this release.

== Boot 1. ==

I disable as many of the devices as possible to get a 'clean' install. So this is the install.ini that I'm going to use.

=== install.ini ===
<pre>
set cr dis
set lpt dis
set rl dis
set ry dis
set ts dis
set xq dis
set rq0 ra82
att rq0 quas.dsk
set rq1 dis
set rq2 dis
set rq3 dis
att tq0 quas.tap
set tti 7b
set tto 7b
boot cpu
</pre>

=== Booting the emulator ===

You then simply run the emulator and pass it the config file.

<pre>
C:\Quasijarus0c\work>vax.exe install.ini

VAX simulator V3.8-0
RQ: creating new file
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot mua0:
(BOOT/R5:0 MUA0

2..
-MUA0
1..0..

=
</pre>

Once the BIOS has done it's POST, it will prompt what device to boot off of at the >>> prompt. The first tape device is mua0:. Once the tape has done the first boot you'll be greeted with the = prompt. From here we are going to load the copy program. Simply type in the following:

<pre>
copy
tms(0,1)
ra(0,1)
</pre>

This will copy the second file onto tape, onto the second file position on our hard disk. The output should be the following:

<pre>
=copy
cpu: uVAX 3000
From: tms(0,1)
To: ra(0,1)
ra0: unlabeled
Copy completed: 308 records copied
=
</pre>

Next we run the boot program. Simply type in the following:

<pre>
boot
ra(0,1)vmunix
</pre>

The resulting output should be the following. The kernel will then prompt for the root partition.

<pre>
=boot
cpu: uVAX 3000

Boot
: ra(0,1)vmunix
ra0: unlabeled
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: no disk label: ra81, size = 891072 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
root device?
</pre>

We will answer with the first ra disk, in a special format, because we have not put a disklabel onto the disk yet.

<pre>
ra0*
</pre>

Once the disk has been mounted we will be dumped to the root prompt. The next step will be creating the default disk label.

=== Creating the disk label ===

Using the disklabel command we will setup the slices automatically (it's done from a file disktab) then install the boot programs. This way we can boot from disk.

Simply type in:

<pre>
disklabel -rw ra0 ra82 “Quasijarus” /usr/mdec/rdboot /usr/mdec/bootra
</pre>

And the disk will now be labled, and bootable from the firmware.

=== Restoring the rootdump ===

From here we are now running from the miniroot. The next step is to run the xtr program to restore the root, and then shutdown the emulator. Enter in the command:

<pre>
disk=ra0 type=ra82 tape=tms xtr
</pre>

And the following will happen:

<pre>
# disk=ra0 type=ra82 tape=tms xtr
Build root file system
Warning: 361 sector(s) in last cylinder unallocated
/dev/rra0a: 15884 sectors in 19 cylinders of 15 tracks, 57 sectors
8.1MB in 2 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776,
Check the file system
** /dev/rra0a
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1 files, 1 used, 7092 free (20 frags, 884 blocks, 0.3% fragmentation)
Rewind tape
Restore the dump image of the root
** /dev/rra0a
** Last Mounted on /a
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
426 files, 5195 used, 1898 free (18 frags, 235 blocks, 0.3% fragmentation)
Root filesystem extracted

If this is an 8650 or 8600, update the console rl02
If this is a 780 or 785, update the floppy
If this is a 730, update the cassette
#
</pre>

After this stage, I just sync the disk a few times, then halt the emulator (CONTROL+E) and exit out. Now we are ready for stage two.

<pre>
If this is a 730, update the cassette
# sync
# sync
# sync

Simulation stopped, PC: 800029AF (BNEQ 800029C6)
sim> q
Goodbye

C:\Quasijarus0c\work>
</pre>

== Boot 2. ==

Now that the install disk is prepared, we need to use a different config file to reflect the emulator being able to autoboot to the disk. The new configuration is as follows:

=== boot.ini ===
<pre>
set cr dis
set lpt dis
set rl dis
set ry dis
set ts dis
set xq dis
set rq0 ra82
att rq0 quas.dsk
set rq1 dis
set rq2 dis
set rq3 dis
att tq0 quas.tap
set tti 7b
set tto 7b
att nvr nvram.dat
dep bdr 1
boot cpu
</pre>

=== Booting the emulator ===

Now boot up the emulator with the boot.ini The first time we boot up in this configuration the emulator will prompt for what device will be the default device. If you typo this, you will have to delete the nvram.dat file, and try again. The default device will be dua0: which is the primary rq disk.

<pre>
C:\Quasijarus0c\work>vax.exe boot.ini

VAX simulator V3.8-0
NVR: creating new file
NVR: buffering file in memory
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
No default boot device has been specified.

Available devices.
-DUA0 (RA 82)
-MUA0 (TK 50)
-MUA1 (TK 50)
-MUA2 (TK 50)
-MUA3 (TK 50)

Device? [XQA0]: dua0:

(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

loading boot

Boot
: /vmunix
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: ra82, size = 1216665 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
Changing root device to ra0a
Automatic reboot in progress...
Fri Feb 6 09:47:10 PST 2004
Can't open checklist file: /etc/fstab
Automatic reboot failed... help!
erase ^?, kill ^U, intr ^C
#
</pre>

=== Preparing the disk ===

Now we have to prep the machine for both the tape, and the type of disk. Type in the following commands.

<pre>
# newfs ra0g ra82
# newfs ra0h ra82
# mkdir /home
# mount /dev/ra0g /usr
# cd /dev
# MAKEDEV tmscp0
# MAKEDEV dz0
</pre>

The output will be like this:

<pre>
# newfs ra0g ra82
/dev/rra0g: 841320 sectors in 984 cylinders of 15 tracks, 57 sectors
430.8MB in 62 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984,
123728, 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656,
246400, 260144, 273888, 287632, 301376, 315120, 328864, 342608, 356352,
370096, 383840, 397584, 411328, 425072, 437792, 451536, 465280, 479024,
492768, 506512, 520256, 534000, 547744, 561488, 575232, 588976, 602720,
616464, 630208, 643952, 656672, 670416, 684160, 697904, 711648, 725392,
739136, 752880, 766624, 780368, 794112, 807856, 821600, 835344,
# newfs ra0h ra82
Warning: 209 sector(s) in last cylinder unallocated
/dev/rra0h: 291346 sectors in 341 cylinders of 15 tracks, 57 sectors
149.2MB in 22 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984,
123728, 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656,
246400, 260144, 273888, 287632,
# mkdir /home
# mount /dev/ra0g /usr
# cd /dev
# MAKEDEV tmscp0
# MAKEDEV dz0
</pre>

=== Restoring the usr slice ===

The disk's /usr slice will not have been formatted. We can not go ahead and mount it, and restore the /usr files.

<pre>
# cd /usr
# mt rew
# mt fsf 3
# tar xpbf 20 /dev/rmt12
# mkdir src
# cd src
# mkdir sys
# cd sys
# mt fsf
# tar xpbf 20 /dev/rmt12
# cd ..
# mt fsf
# tar xpbf 20 /dev/rmt12
</pre>

=== Configuring the fstab ===

Now we just need to create the fstab then we can reboot the emulator into multiuser mode. Enter in the following commands:

<pre>
# cd /etc
# cat > fstab
/dev/ra0a:/:rw:1:1
/dev/ra0h:/home:rw:1:3
/dev/ra0g:/usr:rw:1:2
</pre>

Now you need to press CONTROL+d which will end the stream. Finally you can tell the emulator to reboot.

<pre>
# reboot
syncing disks... done

HALT instruction, PC: 8002F4F8 (BRB 8002F4F7)
sim> q
Goodbye
NVR: writing buffer to file
</pre>

== First Multiuser Boot ==

Now we can just re-run the last command, and we should boot multiuser! By default there is no root password. Also the system will run fsck uppon boot, so depending on your host computer this could take a while.

<pre>
C:\Quasijarus0c\work>vax.exe boot.ini

VAX simulator V3.8-0
NVR: buffering file in memory
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

loading boot

Boot
: /vmunix
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: ra82, size = 1216665 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
Changing root device to ra0a
Automatic reboot in progress...
Fri Feb 6 09:59:45 PST 2004
/dev/ra0a: 448 files, 5199 used, 1894 free (22 frags, 234 blocks, 0.3% fragmentation)
/dev/rra0g: 12312 files, 71682 used, 323169 free (417 frags, 40344 blocks, 0.1% fragmentation)
/dev/rra0h: 1 files, 1 used, 136503 free (15 frags, 17061 blocks, 0.0% fragmentation)
Fri Feb 6 09:59:58 PST 2004
checking quotas: done.
starting system logger

preserving editor files
clearing /tmp
standard daemons: update cron accounting.
starting network daemons: routedFeb 6 10:00:00 myname named[79]: /etc/named.boo
t: No such file or directory
named inetd printer.
starting local daemons: sendmail.
Fri Feb 6 10:00:01 PST 2004

4.3 BSD UNIX (myname.my.domain) (console)

login:
</pre>

Now we can simply logon as root.

<pre>
Fri Feb 6 10:00:01 PST 2004

4.3 BSD UNIX (myname.my.domain) (console)

login: root
Feb 6 10:01:26 myname login: ROOT LOGIN console
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004

Welcome to UNIX!

erase ^?, kill ^U, intr ^C
#
</pre>

From here you can explore the system. All of the man pages are installed, and there is enough of a base system to get going. Right now the networking is outside of the scope of this guide.

=== Enabling remote users ===

Shutdown the OS, and add the following lines into the boot.ini (just make sure they are above the boot command or it'll not work correctly..). This will allow for 8 users to connect on tcp port 8888.

<pre>
set dz lines=8
att dz 8888
set dz 7b
</pre>

I would also recommend to windows users, either [[putty]], or [[syncterm]]. The default telnet client sucks.

[[Category:SIMH Tutorials]]

Mkdisttap.pl

2020-06-27T18:18:42Z

Dugo: add tip for running this on windows

This is a simple perl script to create a tape suitable for SIMH to use. Importantly, it places end of file markers so you can have multiple files on a 'tape' image, much like how a real tape operates.

== Quasijarus 0c & 4.3 BSD UWisc ==

The following is the script formatted for [[4.3 BSD]] Quasijarus 0c, however it can easily be adapted for the other BSD's.

<pre>
#!/usr/local/bin/perl -w
use strict;

# Based on mkdisttap.pl
# ftp://ftp.mrynet.com/pub/os/PUPS/PDP-11/Boot_Images/2.11_on_Simh/211bsd/mkdisttap.pl

#
# $Id: mkdisttap.pl,v 1.1 2006/09/16 23:33:46 kirk Exp kirk $
#

# Based on the example in the HOWTO using dd. Does not work!
# add_file("cat mtboot mtboot boot |", 512);

# Based on the maketape.c program and the maketape.data data file.
add_file("stand", 512);
end_file();
add_file("miniroot", 10240);
end_file();
add_file("rootdump", 10240);
end_file();
add_file("usr.tar", 10240);
end_file();
add_file("srcsys.tar", 10240);
end_file();
add_file("src.tar", 10240);
end_file();
end_file();

sub end_file {
print "\x00\x00\x00\x00";
}

sub add_file {
my($filename, $blocksize) = @_;
my($block, $bytes_read, $length);

open(FILE, $filename) || die("Can't open $filename: $!");
while($bytes_read = read(FILE, $block, $blocksize)) {
if($bytes_read < $blocksize) {
$block .= "\x00" x ($blocksize - $bytes_read);
$bytes_read = $blocksize;
}
$length = pack("V", $bytes_read);
print $length, $block, $length;
}
close(FILE);
}
</pre>

== 4.2 & 4.3 BSD ==

This is the format of the script to generate 42.tap for [[4.2 BSD]], and the 43.tap for [[4.3 BSD]].

<pre>
#!/usr/local/bin/perl -w
use strict;

# Based on mkdisttap.pl
# ftp://ftp.mrynet.com/pub/os/PUPS/PDP-11/Boot_Images/2.11_on_Simh/211bsd/mkdisttap.pl

#
# $Id: mkdisttap.pl,v 1.1 2006/09/16 23:33:46 kirk Exp kirk $
#

# Based on the example in the HOWTO using dd. Does not work!
# add_file("cat mtboot mtboot boot |", 512);

# Based on the maketape.c program and the maketape.data data file.
add_file("stand", 512);
end_file();
add_file("miniroot", 10240);
end_file();
add_file("rootdump", 10240);
end_file();
add_file("srcsys.tar", 10240);
end_file();
add_file("usr.tar", 10240);
end_file();
add_file("vfont.tar", 10240);
end_file();
add_file("src.tar", 10240);
end_file();
add_file("new.tar", 10240);
end_file();
add_file("ingres.tar", 10240);
end_file();
end_file();

sub end_file {
print "\x00\x00\x00\x00";
}

sub add_file {
my($filename, $blocksize) = @_;
my($block, $bytes_read, $length);

open(FILE, $filename) || die("Can't open $filename: $!");
while($bytes_read = read(FILE, $block, $blocksize)) {
if($bytes_read < $blocksize) {
$block .= "\x00" x ($blocksize - $bytes_read);
$bytes_read = $blocksize;
}
$length = pack("V", $bytes_read);
print $length, $block, $length;
}
close(FILE);
}
</pre>

== 4.3 RENO ==

This is the config file for RENO:

<pre>
#!/usr/local/bin/perl -w
use strict;

# Based on mkdisttap.pl
# ftp://ftp.mrynet.com/pub/os/PUPS/PDP-11/Boot_Images/2.11_on_Simh/211bsd/mkdisttap.pl

#
# $Id: mkdisttap.pl,v 1.1 2006/09/16 23:33:46 kirk Exp kirk $
#

# Based on the example in the HOWTO using dd. Does not work!
# add_file("cat mtboot mtboot boot |", 512);

# Based on the maketape.c program and the maketape.data data file.
add_file("stand", 512);
end_file();
add_file("miniroot", 10240);
end_file();
add_file("rootdump", 10240);
end_file();
add_file("usr.tar", 10240);
end_file();
add_file("src.tar", 10240);
end_file();
add_file("srcsys.tar", 10240);
end_file();
add_file("contrib.tar", 10240);
end_file();
end_file();

sub end_file {
print "\x00\x00\x00\x00";
}

sub add_file {
my($filename, $blocksize) = @_;
my($block, $bytes_read, $length);

open(FILE, $filename) || die("Can't open $filename: $!");
while($bytes_read = read(FILE, $block, $blocksize)) {
if($bytes_read < $blocksize) {
$block .= "\x00" x ($blocksize - $bytes_read);
$bytes_read = $blocksize;
}
$length = pack("V", $bytes_read);
print $length, $block, $length;
}
close(FILE);
}
</pre>

== Ultrix 4.0 ==

The following is the script formatted for [[Ultrix]] 4.0. I would imagine it could be used for other Ultrix releases..

<pre>
#!/usr/local/bin/perl -w
use strict;

# Based on mkdisttap.pl
# ftp://ftp.mrynet.com/pub/os/PUPS/PDP-11/Boot_Images/2.11_on_Simh/211bsd/mkdisttap.pl

#
# $Id: mkdisttap.pl,v 1.1 2006/09/16 23:33:46 kirk Exp kirk $
#

# Based on the example in the HOWTO using dd. Does not work!
# add_file("cat mtboot mtboot boot |", 512);

# Based on the maketape.c program and the maketape.data data file.
add_file("file.01", 512);
end_file();
add_file("file.02", 512);
end_file();
add_file("file.03", 10240);
end_file();
add_file("file.04", 10240);
end_file();
add_file("file.05", 10240);
end_file();
add_file("file.06", 10240);
end_file();
add_file("file.07", 10240);
end_file();
add_file("file.08", 10240);
end_file();
add_file("file.09", 10240);
end_file();
add_file("file.10", 10240);
end_file();
add_file("file.11", 10240);
end_file();
add_file("file.12", 10240);
end_file();
add_file("file.13", 10240);
end_file();
add_file("file.14", 10240);
end_file();
add_file("file.15", 10240);
end_file();
add_file("file.16", 10240);
end_file();
add_file("file.17", 10240);
end_file();
add_file("file.18", 10240);
end_file();
add_file("file.19", 10240);
end_file();
add_file("file.20", 10240);
end_file();
add_file("file.21", 10240);
end_file();
add_file("file.22", 10240);
end_file();
add_file("file.23", 10240);
end_file();
add_file("file.24", 10240);
end_file();
add_file("file.25", 10240);
end_file();
add_file("file.26", 10240);
end_file();
add_file("file.27", 10240);
end_file();
add_file("file.28", 10240);
end_file();
add_file("file.29", 10240);
end_file();
add_file("file.30", 10240);
end_file();
add_file("file.31", 10240);
end_file();
add_file("file.32", 10240);
end_file();
add_file("file.33", 10240);
end_file();
add_file("file.34", 10240);
end_file();
add_file("file.35", 10240);
end_file();
add_file("file.36", 10240);
end_file();
add_file("file.37", 10240);
end_file();
add_file("file.38", 10240);
end_file();
end_file();

sub end_file {
print "\x00\x00\x00\x00";
}

sub add_file {
my($filename, $blocksize) = @_;
my($block, $bytes_read, $length);

open(FILE, $filename) || die("Can't open $filename: $!");
while($bytes_read = read(FILE, $block, $blocksize)) {
if($bytes_read < $blocksize) {
$block .= "\x00" x ($blocksize - $bytes_read);
$bytes_read = $blocksize;
}
$length = pack("V", $bytes_read);
print $length, $block, $length;
}
close(FILE);
}
</pre>

== Research Unix v7 ==

The following is the script formatted for [[Seventh Edition Unix]].

<pre>
#!/usr/local/bin/perl -w
use strict;

# Based on mkdisttap.pl
# ftp://ftp.mrynet.com/pub/os/PUPS/PDP-11/Boot_Images/2.11_on_Simh/211bsd/mkdisttap.pl

#
# $Id: mkdisttap.pl,v 1.1 2006/09/16 23:33:46 kirk Exp kirk $
#

# Based on the example in the HOWTO using dd. Does not work!
# add_file("cat mtboot mtboot boot |", 512);

# Based on the maketape.c program and the maketape.data data file.
add_file("f0", 512);
end_file();
add_file("f1", 512);
end_file();
add_file("f2", 512);
end_file();
add_file("f3", 512);
end_file();
add_file("f4", 512);
end_file();
add_file("f5", 10240);
end_file();
add_file("f6", 10240);
end_file();
end_file();

sub end_file {
print "\x00\x00\x00\x00";
}

sub add_file {
my($filename, $blocksize) = @_;
my($block, $bytes_read, $length);

open(FILE, $filename) || die("Can't open $filename: $!");
while($bytes_read = read(FILE, $block, $blocksize)) {
if($bytes_read < $blocksize) {
$block .= "\x00" x ($blocksize - $bytes_read);
$bytes_read = $blocksize;
}
$length = pack("V", $bytes_read);
print $length, $block, $length;
}
close(FILE);
}
</pre>

== Running mkdisttap.pl on Windows ==

To avoid issues with the different line/file endings on Windows add
<pre>
binmode STDOUT;
</pre>
..after the `use strict;' line and
<pre>
binmode FILE;
</pre>
after the `open(FILE, $filename)....' line

[[Category: Emulators]]

Gzcompat

2020-06-27T18:09:17Z

Dugo: Add patch for windows

gzcompat is a utility to convert from Sokolov compression into gzip. The primary use is to convert the Quasijarus install files into gzip, so that they can easily be decompressed. This is for the [[4.3 BSD]] Quasijarus Operating System.

== source code ==

<pre>
#ifndef lint
static char sccsid[] = "@(#)gzcompat.c 5.2 (Berkeley) 12/21/00";
#endif

/* gzcompat converts between compress -s and gzip formats. */

#include <stdio.h>

char magic_strong[2] = {037, 0241};
char magic_gzip[2] = {037, 0213};

struct gzheader {
unsigned char cm;
unsigned char flg;
unsigned char mtime[4];
unsigned char xfl;
unsigned char os;
} gzheader;

#define CM_DEFLATE 0x08

#define FTEXT 0x01
#define FHCRC 0x02
#define FEXTRA 0x04
#define FNAME 0x08
#define FCOMMENT 0x10
#define FRSVD 0xE0

#define OS_UNIX 0x03

int main(argc, argv)
char **argv;
{
FILE *infile;
char *inname;
char buf[4096];
int len;
int mkgzip;

if (argc == 1) {
infile = stdin;
inname = "stdin";
} else if (argc == 2) {
inname = argv[1];
infile = fopen(inname, "r");
if (infile == NULL) {
perror(inname);
exit(1);
}
} else {
fprintf(stderr, "usage: %s [infile]\n", argv[0]);
exit(1);
}

/* First read the input magic number. */
len = fread(buf, 1, 2, infile);
if (len < 0) {
perror(inname);
exit(1);
}
if (len != 2) {
fprintf(stderr, "%s: not in compress -s or gzip format\n",
inname);
exit(1);
}
if (buf[0] == magic_strong[0] && buf[1] == magic_strong[1])
mkgzip = 1;
else if (buf[0] == magic_gzip[0] && buf[1] == magic_gzip[1])
mkgzip = 0;
else {
fprintf(stderr, "%s: not in compress -s or gzip format\n",
inname);
exit(1);
}

/* Now read and check the gzip header if necessary. */
if (!mkgzip) {
len = fread(&gzheader, sizeof(struct gzheader), 1, infile);
if (len < 0) {
perror(inname);
exit(1);
}
if (len != 1) {
fprintf(stderr, "%s: invalid gzip header\n", inname);
exit(1);
}
if (gzheader.cm != CM_DEFLATE || gzheader.flg & FRSVD) {
fprintf(stderr, "%s: invalid gzip header\n", inname);
exit(1);
}
if (gzheader.flg & FEXTRA) {
int count;

count = getc(infile);
if (ferror(infile)) {
perror(inname);
exit(1);
}
if (feof(infile)) {
fprintf(stderr, "%s: invalid gzip header\n",
inname);
exit(1);
}
while (count) {
getc(infile);
if (ferror(infile)) {
perror(inname);
exit(1);
}
if (feof(infile)) {
fprintf(stderr, "%s: invalid gzip header\n", inname);
exit(1);
}
count--;
}
}
if (gzheader.flg & FNAME) {
int ch;

do {
ch = getc(infile);
if (ferror(infile)) {
perror(inname);
exit(1);
}
if (feof(infile)) {
fprintf(stderr, "%s: invalid gzip header\n", inname);
exit(1);
}
}
while (ch);
}
if (gzheader.flg & FCOMMENT) {
int ch;

do {
ch = getc(infile);
if (ferror(infile)) {
perror(inname);
exit(1);
}
if (feof(infile)) {
fprintf(stderr, "%s: invalid gzip header\n", inname);
exit(1);
}
}
while (ch);
}
if (gzheader.flg & FHCRC) {
len = fread(buf, 1, 2, infile);
if (len < 0) {
perror(inname);
exit(1);
}
if (len != 2) {
fprintf(stderr, "%s: invalid gzip header\n",
inname);
exit(1);
}
}
}

/* Now write the output magic number. */
if (mkgzip) {
if (fwrite(magic_gzip, 1, 2, stdout) != 2) {
perror("stdout");
exit(1);
}
}
else {
if (fwrite(magic_strong, 1, 2, stdout) != 2) {
perror("stdout");
exit(1);
}
}

/* Now write the gzip header if necessary. */
if (mkgzip) {
gzheader.cm = CM_DEFLATE;
gzheader.flg = 0;
gzheader.mtime[0] = 0;
gzheader.mtime[1] = 0;
gzheader.mtime[2] = 0;
gzheader.mtime[3] = 0;
gzheader.xfl = 0;
gzheader.os = OS_UNIX;
if (fwrite(&gzheader, sizeof(struct gzheader), 1, stdout) != 1) {
perror("stdout");
exit(1);
}
}

/* Now actually copy the data! */
for (;;) {
len = fread(buf, 1, sizeof(buf), infile);
if (len < 0) {
perror(inname);
exit(1);
}
if (len == 0)
break;
if (fwrite(buf, 1, len, stdout) != len) {
perror("stdout");
exit(1);
}
}

/* I can't believe we're done! */
if (argc == 2)
fclose(infile);
return(0);
}
</pre>

== patch for building/running on windows ==

<pre>
7a8,12
> #include <stdlib.h>
> #ifdef _WIN32
> #include <io.h>
> #include <fcntl.h>
> #endif
31a37
> int argc;
39c45,48
<
---
> #ifdef _WIN32
> setmode(fileno(stdout),O_BINARY);
> setmode(fileno(stdin),O_BINARY);
> #endif
</pre>

[[Category:Compression Software]]

Installing 4.3 BSD Quasijarus on SIMH

2020-06-27T10:26:26Z

Dugo: The original gzcompat doesn't do well on windows unless you coerce fread/fwrite to binary

This is the procedure that I have used to install [[4.3 BSD]] onto [[SIMH]]'s [[MicroVAX II]] emulator. Please note that this is the Quasijarus release of 4.3 BSD.

== Obtaining an install tape ==

You have two choices now, either you can create your own, or you can download a pre-made tape on [https://sourceforge.net/project/showfiles.php?group_id=204974&package_id=309407&release_id=659789 sourceforge]. If you want to build your own tape image, then follow the next section.

== Building your own tape image ==

I will describe what is needed, and how to create your own Quasijarus tape image, that is suitable for installing with SIMH.

=== Requirements ===

You will need the following materials to put together a 4.3 BSD Quasijarus installation:

*A working perl interpeter to make the tape images. 
*A copy of gzip. 
*A working C compiler. 
*A compiled binary of vax from [[SIMH]], along with the ka655x.bin again from [[SIMH]].

You will need the following files from any 4 BSD archive from the Quasijarus0c directory. I have used the files from [https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/ Sourceforge]. You you will have to use a web browser to download them, to deal with the sourceforge download system. But that's the price of free hosting. 

[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/stand.Z/download stand.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/miniroot.Z/download miniroot.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/rootdump.Z/download rootdump.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/usr.tar.Z/download usr.tar.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/srcsys.tar.Z/download srcsys.tar.Z] 
[https://sourceforge.net/projects/bsd42/files/Install%20tapes/4.3%20BSD%20Quasijarus%200c/ifctfvax/4.3BSD-Quasijarus0c/src.tar.Z/download src.tar.Z] 

=== gzcompat ===

Next it's easier on a host machine to convert the downloaded Quasijarus files into gzip, then uncompress them using gzip. For this you will need the [[gzcompat]] program. I've included the sourcecode on the link, as it's getting harder to find.. Simply compile the gzcompat.c into an exe. It should be somewhat straightforward. The original location for gzcompat is [[http://ifctfvax.superglobalmegacorp.com/releases/UNIX/components/compress.tar here]] and a known good copy is [[http://www.tuhs.org/Archive/4BSD/Distributions/components/compress.tar here]].

On most instances with gcc simply run:

<pre>gcc gzcompat.c -o gzcompat</pre>

And that should be it.

=== Preparing for installation ===

With the files downloaded you will need to uncompress them all and then create the tape file. With the different compression this will be somewhat involved.

The following command will decompress the tape files, on a UNIX install.
<pre>
cat miniroot.Z | gzcompat | gzip -dc > miniroot
cat rootdump.Z | gzcompat | gzip -dc > rootdump
cat src.tar.Z | gzcompat | gzip -dc > src.tar
cat srcsys.tar.Z | gzcompat | gzip -dc > srcsys.tar
cat stand.Z | gzcompat | gzip -dc > stand
cat usr.tar.Z | gzcompat | gzip -dc > usr.tar
</pre>

The tape needs to be created with the [[mkdisttap.pl]] program. Simply run the program and redirect it into a file called quas.tap .

<pre>
% ./mkdisttap.pl > quas.tap
% ls -l quas.tap
-rw-r--r-- 1 Neozeed None_ploc 84450876 Feb 6 17:10 quas.tap
%</pre>

An empty RA82 can be created with:

<pre>
% dd if=/dev/zero of=quas.dsk bs=512 count=1216665
</pre>

Now we have our tape and disk, so we are ready to proceed with the install. For those wondering, unlike the 11/780 emulator, the MicrovaxII can run it's microcode in a logical fashion and we are able to boot from tape in this release.

== Boot 1. ==

I disable as many of the devices as possible to get a 'clean' install. So this is the install.ini that I'm going to use.

=== install.ini ===
<pre>
set cr dis
set lpt dis
set rl dis
set ry dis
set ts dis
set xq dis
set rq0 ra82
att rq0 quas.dsk
set rq1 dis
set rq2 dis
set rq3 dis
att tq0 quas.tap
set tti 7b
set tto 7b
boot cpu
</pre>

=== Booting the emulator ===

You then simply run the emulator and pass it the config file.

<pre>
C:\Quasijarus0c\work>vax.exe install.ini

VAX simulator V3.8-0
RQ: creating new file
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot mua0:
(BOOT/R5:0 MUA0

2..
-MUA0
1..0..

=
</pre>

Once the BIOS has done it's POST, it will prompt what device to boot off of at the >>> prompt. The first tape device is mua0:. Once the tape has done the first boot you'll be greeted with the = prompt. From here we are going to load the copy program. Simply type in the following:

<pre>
copy
tms(0,1)
ra(0,1)
</pre>

This will copy the second file onto tape, onto the second file position on our hard disk. The output should be the following:

<pre>
=copy
cpu: uVAX 3000
From: tms(0,1)
To: ra(0,1)
ra0: unlabeled
Copy completed: 308 records copied
=
</pre>

Next we run the boot program. Simply type in the following:

<pre>
boot
ra(0,1)vmunix
</pre>

The resulting output should be the following. The kernel will then prompt for the root partition.

<pre>
=boot
cpu: uVAX 3000

Boot
: ra(0,1)vmunix
ra0: unlabeled
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: no disk label: ra81, size = 891072 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
root device?
</pre>

We will answer with the first ra disk, in a special format, because we have not put a disklabel onto the disk yet.

<pre>
ra0*
</pre>

Once the disk has been mounted we will be dumped to the root prompt. The next step will be creating the default disk label.

=== Creating the disk label ===

Using the disklabel command we will setup the slices automatically (it's done from a file disktab) then install the boot programs. This way we can boot from disk.

Simply type in:

<pre>
disklabel -rw ra0 ra82 “Quasijarus” /usr/mdec/rdboot /usr/mdec/bootra
</pre>

And the disk will now be labled, and bootable from the firmware.

=== Restoring the rootdump ===

From here we are now running from the miniroot. The next step is to run the xtr program to restore the root, and then shutdown the emulator. Enter in the command:

<pre>
disk=ra0 type=ra82 tape=tms xtr
</pre>

And the following will happen:

<pre>
# disk=ra0 type=ra82 tape=tms xtr
Build root file system
Warning: 361 sector(s) in last cylinder unallocated
/dev/rra0a: 15884 sectors in 19 cylinders of 15 tracks, 57 sectors
8.1MB in 2 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776,
Check the file system
** /dev/rra0a
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
1 files, 1 used, 7092 free (20 frags, 884 blocks, 0.3% fragmentation)
Rewind tape
Restore the dump image of the root
** /dev/rra0a
** Last Mounted on /a
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
426 files, 5195 used, 1898 free (18 frags, 235 blocks, 0.3% fragmentation)
Root filesystem extracted

If this is an 8650 or 8600, update the console rl02
If this is a 780 or 785, update the floppy
If this is a 730, update the cassette
#
</pre>

After this stage, I just sync the disk a few times, then halt the emulator (CONTROL+E) and exit out. Now we are ready for stage two.

<pre>
If this is a 730, update the cassette
# sync
# sync
# sync

Simulation stopped, PC: 800029AF (BNEQ 800029C6)
sim> q
Goodbye

C:\Quasijarus0c\work>
</pre>

== Boot 2. ==

Now that the install disk is prepared, we need to use a different config file to reflect the emulator being able to autoboot to the disk. The new configuration is as follows:

=== boot.ini ===
<pre>
set cr dis
set lpt dis
set rl dis
set ry dis
set ts dis
set xq dis
set rq0 ra82
att rq0 quas.dsk
set rq1 dis
set rq2 dis
set rq3 dis
att tq0 quas.tap
set tti 7b
set tto 7b
att nvr nvram.dat
dep bdr 1
boot cpu
</pre>

=== Booting the emulator ===

Now boot up the emulator with the boot.ini The first time we boot up in this configuration the emulator will prompt for what device will be the default device. If you typo this, you will have to delete the nvram.dat file, and try again. The default device will be dua0: which is the primary rq disk.

<pre>
C:\Quasijarus0c\work>vax.exe boot.ini

VAX simulator V3.8-0
NVR: creating new file
NVR: buffering file in memory
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
No default boot device has been specified.

Available devices.
-DUA0 (RA 82)
-MUA0 (TK 50)
-MUA1 (TK 50)
-MUA2 (TK 50)
-MUA3 (TK 50)

Device? [XQA0]: dua0:

(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

loading boot

Boot
: /vmunix
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: ra82, size = 1216665 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
Changing root device to ra0a
Automatic reboot in progress...
Fri Feb 6 09:47:10 PST 2004
Can't open checklist file: /etc/fstab
Automatic reboot failed... help!
erase ^?, kill ^U, intr ^C
#
</pre>

=== Preparing the disk ===

Now we have to prep the machine for both the tape, and the type of disk. Type in the following commands.

<pre>
# newfs ra0g ra82
# newfs ra0h ra82
# mkdir /home
# mount /dev/ra0g /usr
# cd /dev
# MAKEDEV tmscp0
# MAKEDEV dz0
</pre>

The output will be like this:

<pre>
# newfs ra0g ra82
/dev/rra0g: 841320 sectors in 984 cylinders of 15 tracks, 57 sectors
430.8MB in 62 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984,
123728, 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656,
246400, 260144, 273888, 287632, 301376, 315120, 328864, 342608, 356352,
370096, 383840, 397584, 411328, 425072, 437792, 451536, 465280, 479024,
492768, 506512, 520256, 534000, 547744, 561488, 575232, 588976, 602720,
616464, 630208, 643952, 656672, 670416, 684160, 697904, 711648, 725392,
739136, 752880, 766624, 780368, 794112, 807856, 821600, 835344,
# newfs ra0h ra82
Warning: 209 sector(s) in last cylinder unallocated
/dev/rra0h: 291346 sectors in 341 cylinders of 15 tracks, 57 sectors
149.2MB in 22 cyl groups (16 c/g, 7.00MB/g, 3200 i/g)
super-block backups (for fsck -b #) at:
32, 13776, 27520, 41264, 55008, 68752, 82496, 96240, 109984,
123728, 137472, 151216, 164960, 178704, 192448, 206192, 218912, 232656,
246400, 260144, 273888, 287632,
# mkdir /home
# mount /dev/ra0g /usr
# cd /dev
# MAKEDEV tmscp0
# MAKEDEV dz0
</pre>

=== Restoring the usr slice ===

The disk's /usr slice will not have been formatted. We can not go ahead and mount it, and restore the /usr files.

<pre>
# cd /usr
# mt rew
# mt fsf 3
# tar xpbf 20 /dev/rmt12
# mkdir src
# cd src
# mkdir sys
# cd sys
# mt fsf
# tar xpbf 20 /dev/rmt12
# cd ..
# mt fsf
# tar xpbf 20 /dev/rmt12
</pre>

=== Configuring the fstab ===

Now we just need to create the fstab then we can reboot the emulator into multiuser mode. Enter in the following commands:

<pre>
# cd /etc
# cat > fstab
/dev/ra0a:/:rw:1:1
/dev/ra0h:/home:rw:1:3
/dev/ra0g:/usr:rw:1:2
</pre>

Now you need to press CONTROL+d which will end the stream. Finally you can tell the emulator to reboot.

<pre>
# reboot
syncing disks... done

HALT instruction, PC: 8002F4F8 (BRB 8002F4F7)
sim> q
Goodbye
NVR: writing buffer to file
</pre>

== First Multiuser Boot ==

Now we can just re-run the last command, and we should boot multiuser! By default there is no root password. Also the system will run fsck uppon boot, so depending on your host computer this could take a while.

<pre>
C:\Quasijarus0c\work>vax.exe boot.ini

VAX simulator V3.8-0
NVR: buffering file in memory
Loading boot code from ka655x.bin

←[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

loading boot

Boot
: /vmunix
326312+104440+130352 start 0x23b8
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004
root@luthien.Harhan.ORG:/nbsd/usr/src/sys/GENERIC
real mem = 16744448
SYSPTSIZE limits number of buffers to 112
avail mem = 14920704
using 112 buffers containing 917504 bytes of memory
MicroVAX 3000, ucode rev 6
tmscp0 at uba0 csr 174500 vec 774, ipl 15
tms0 at tmscp0 slave 0
tms1 at tmscp0 slave 1
uda0 at uba0 csr 172150 vec 770, ipl 15
uda0: version 3 model 3
uda0: DMA burst size set to 4
ra0 at uda0 slave 0: ra82, size = 1216665 sectors
dz0 at uba0 csr 160100 vec 300, ipl 15
dz1 at uba0 csr 160110 vec 310, ipl 15
dz2 at uba0 csr 160120 vec 320, ipl 15
dz3 at uba0 csr 160130 vec 330, ipl 15
Changing root device to ra0a
Automatic reboot in progress...
Fri Feb 6 09:59:45 PST 2004
/dev/ra0a: 448 files, 5199 used, 1894 free (22 frags, 234 blocks, 0.3% fragmentation)
/dev/rra0g: 12312 files, 71682 used, 323169 free (417 frags, 40344 blocks, 0.1% fragmentation)
/dev/rra0h: 1 files, 1 used, 136503 free (15 frags, 17061 blocks, 0.0% fragmentation)
Fri Feb 6 09:59:58 PST 2004
checking quotas: done.
starting system logger

preserving editor files
clearing /tmp
standard daemons: update cron accounting.
starting network daemons: routedFeb 6 10:00:00 myname named[79]: /etc/named.boo
t: No such file or directory
named inetd printer.
starting local daemons: sendmail.
Fri Feb 6 10:00:01 PST 2004

4.3 BSD UNIX (myname.my.domain) (console)

login:
</pre>

Now we can simply logon as root.

<pre>
Fri Feb 6 10:00:01 PST 2004

4.3 BSD UNIX (myname.my.domain) (console)

login: root
Feb 6 10:01:26 myname login: ROOT LOGIN console
4.3 BSD Quasijarus UNIX #3: Sat Feb 14 20:31:03 PST 2004

Welcome to UNIX!

erase ^?, kill ^U, intr ^C
#
</pre>

From here you can explore the system. All of the man pages are installed, and there is enough of a base system to get going. Right now the networking is outside of the scope of this guide.

=== Enabling remote users ===

Shutdown the OS, and add the following lines into the boot.ini (just make sure they are above the boot command or it'll not work correctly..). This will allow for 8 users to connect on tcp port 8888.

<pre>
set dz lines=8
att dz 8888
set dz 7b
</pre>

I would also recommend to windows users, either [[putty]], or [[syncterm]]. The default telnet client sucks.

[[Category:SIMH Tutorials]]

User talk:Dugo

2019-04-11T09:31:23Z

Dugo:

Interest: Running Net/2 on bochs.

==Template:My sandbox==

So someone noticed you're using [[Template:My sandbox]] to create your user page; this is a slightly dodgy thing to do, using a system-wide space for personal stuff.

If you're using just using a template as a way to 'transclude' (the term Wikimedia uses for including one page's contents in another), the <nowiki>{{}}</nowiki> syntax can transclude pages/sub-pages from namespaces other than Template:, all one has to do is specify the namespace. So <nowiki>{{User:Dugo/My sandbox}}</nowiki> would do the exact same thing, but insert that sub-page of your User: page.

So, if you're OK with it, we'd like move that Template page (including all its history) to be a sub-page of your User: page, and adjust the latter to transclude if from there - unless there's some good reason we haven't understood why it's in Template:.

If this is OK, I'll do it for you (as an admin I can get rid of the leftover redirects, etc); just let us know. Thanks! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:16, 9 April 2019 (CEST)

: Go ahead jnc. It has been years ago I took notes on the fuzzballs, but I'm sure it was just that and not my idea for a system-wide template. [[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 00:23, 11 April 2019 (CEST)

:: OK, will do. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 01:01, 11 April 2019 (CEST)

::: Thanks jnc! [[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 11:30, 11 April 2019 (CEST)

User talk:ForOldHack

2019-04-11T09:25:54Z

Dugo: RE: HELP

==Sigs on Talk: pages==

We generally try and follow the Wikipedia style of signing posts on Talk: pages (so that people reading them will know straight off, without having to look in the history, who made comments, and when). There's even special Wiki syntax to do this easily; just add <nowiki>~~~~</nowiki> to the end of your post, and it will be automagically transformed in this sig, with the user and time. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 13:21, 11 March 2019 (CET)

: Hmm, something else is going on. '[[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:41, 12 March 2019 (CET)' gives me date and time, and <nowiki>~~~~</nowiki> gives me 4 tildies.

: Oh, now I understand to escape the wiki process and get tildies, use <nowiki>~~~~</nowiki>, but to get the sig use [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:42, 12 March 2019 (CET)

:: I have not seen such a funny time stamp in 34 years, when we were using uwasa.fi as a mail relay. ( Time is Wasausa, Finland ) [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 01:45, 12 March 2019 (CET)

: Please don't forget; I can add the sig manually, but it's easier for you. Thanks! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:52, 22 March 2019 (CET)

== Note ==

I would like to print to npib78003.local [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 05:45, 27 March 2019 (CET)

== Infobox line captions ==

The captions in infoboxes are specified in the template, as are the argument names; trying to change either in the invocation has no effect.

If you want to change the 'Year introduced' caption, I'd be OK with that, but just to 'Introduced' I think might be potentially confusing without something to indicate that it's a temporal meaning - e.g. 'Date introduced', or something. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 12:04, 7 April 2019 (CEST)

== External link syntax ==

We generally like to give the title of our external links, using the syntax <nowiki>'[URL title]'</nowiki>, so instead of:

[http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html]

one sees this:

[http://ana-3.lcs.mit.edu/~jnc/tech/DECIndicatorPanels.html Digital Equipment Corporation Indicator Panels]

Much nicer for our readers! The title is formally given inside <title> tags in the HTML of the page, and displayed by the browser (often in the window title bar, but exactly how will depend on the browser and OS).

PS: You shouldn't stick a sig in additions to ''content'' pages (where it intrudes), you only need to do it on Talk: pages. The reasoning (it dates to a very early stage on Wikipedia, before even I started there) seems to be that if one wants to know where something in a content page comes from, one looks at the History of that page; on Talk: pages (especially if one is reading one later - see for example the discussion at [[Help talk:Introduction to Categories]]), one can easily see who posted a given item directly, without needing to grub around in the history. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:25, 7 April 2019 (CEST)

:Very sorry, I had forgot, and even forgot to look it up. I am so amazed by the tiny bits I have found, I only used some of those machines a few times, they were apprently very popular because they were so fantastic.
:Ill follow this convention on. [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 04:57, 8 April 2019 (CET)

Sure. BTW, [https://en.wikipedia.org/wiki/Wikipedia:SIG here] is the Wikipedia sig policy, which we follow (although we don't follow Wikipedia in most things, in this one we do). [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:12, 9 April 2019 (CEST)

== new user ==

I don't see a new user. You are the newest user since 8 March 2019.
[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 11:25, 11 April 2019 (CEST)

User talk:Dugo

2019-04-10T22:23:21Z

Dugo: /* Template:My sandbox */

Interest: Running Net/2 on bochs.

==Template:My sandbox==

So someone noticed you're using [[Template:My sandbox]] to create your user page; this is a slightly dodgy thing to do, using a system-wide space for personal stuff.

If you're using just using a template as a way to 'transclude' (the term Wikimedia uses for including one page's contents in another), the <nowiki>{{}}</nowiki> syntax can transclude pages/sub-pages from namespaces other than Template:, all one has to do is specify the namespace. So <nowiki>{{User:Dugo/My sandbox}}</nowiki> would do the exact same thing, but insert that sub-page of your User: page.

So, if you're OK with it, we'd like move that Template page (including all its history) to be a sub-page of your User: page, and adjust the latter to transclude if from there - unless there's some good reason we haven't understood why it's in Template:.

If this is OK, I'll do it for you (as an admin I can get rid of the leftover redirects, etc); just let us know. Thanks! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 14:16, 9 April 2019 (CEST)

Go ahead jnc. It has been years ago I took notes on the fuzzballs, but I'm sure it was just that and not my idea for a system-wide template.
[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 00:23, 11 April 2019 (CEST)

Installing 386BSD on BOCHS

2019-04-01T23:32:30Z

Dugo: elaborate on milestones

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

Note that newer iptables has a slightly different syntax. -d ! has become ! -d.

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

If that fails you probably have a very recent version of bximage, in that case:

<pre>
printf "1\nhd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."

A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. The CHANGES file reads “Changes from 386bsd 0.1 + patchkit 0.2.2” and “some alpha patchkit 0.2.3 stuff (piecemeal, and in some cases improved)”.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patch kits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. Rodney Grimes announced patchkit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993. The guided tour will bring 386BSD all up to the point where maintaining the patch kits became rather cumbersome. The shortest and most available route is installing the last two official unofficial patch kits and skipping 0.2.2.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

Disk images created by roughly automating the above steps with github and travis-ci is available via this trilogy https://github.com/dugoh/386bsd0.1-c
== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)
* Upgrade to 0.x https://github.com/386bsd/386bsd/tree/0.1
[[Category:Tutorials]]

Talk:FreeBSD

2019-04-01T20:49:29Z

Dugo: Created page with ""I think we need to literally find and link every archive we can find... but that is just me.." Check http://callfortesting.org/tests/ ~~~~"

"I think we need to literally find and link every archive we can find... but that is just me.."

Check http://callfortesting.org/tests/
[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 22:49, 1 April 2019 (CEST)

Installing 386BSD on BOCHS

2019-04-01T20:00:53Z

Dugo: add link to automated build

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

Note that newer iptables has a slightly different syntax. -d ! has become ! -d.

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

If that fails you probably have a very recent version of bximage, in that case:

<pre>
printf "1\nhd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."
A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patchkits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

Disk images created by roughly automating the above steps with github and travis-ci is available via this trilogy https://github.com/dugoh/386bsd0.1-c
== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)
* Upgrade to 0.x https://github.com/386bsd/386bsd/tree/0.1
[[Category:Tutorials]]

Installing 386BSD on BOCHS

2019-04-01T19:56:33Z

Dugo: add link to 0.x

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

Note that newer iptables has a slightly different syntax. -d ! has become ! -d.

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

If that fails you probably have a very recent version of bximage, in that case:

<pre>
printf "1\nhd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."
A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patchkits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)
* Upgrade to 0.x https://github.com/386bsd/386bsd/tree/0.1
[[Category:Tutorials]]

386BSD

2016-10-10T06:54:11Z

Dugo: Add 2.0 source

[[Image:386BSD logo.jpg|thumb|150px|left|386BSD logo]]
{{Infobox OS
| image = 386bsd.png
| caption = Logging into a 386 BSD system
| name = 386 BSD
| creator = CSRG, University of California, Berkeley
| current version = 1.0 (1993)
| year introduced = 1991
| type = Multitasking, multiuser
| architecture = [[i386]] theoretically portable
}}

386 BSD was the first time that the [[Net/2]] project was put into a functional release onto commodity hardware, and into the public under the BSD license. As the project eventually stalled, it became the starting point for both [[NetBSD]] & [[FreeBSD]], via the patchkits. While 386 BSD may be of historical significance, it's not up to the challenge of day to day usage, as it hasn't received any updates or patches in over 15 years.

== Releases ==
There seems to have been four releases of 386 BSD, starting with it being freely available on the internet, then only available to those who purchased CD-ROMs.

=== 0.0 ===
This is the first version of 386 BSD that was released. This version doesn't share it's disk with MS-DOS or any other OS's, and uses a VAX style disktab/disklabel, making it difficult to install.

*[[386BSD 0.0]]

=== 0.1 ===
The 0.1 release was the most popular, as 0.0 proved to be very difficult to install, I'd think because it was more "VAX" like in how it treated the disks, and most people are not familiar with disklabels. There were 2 revisions to 0.1, with the patchkits, that eventually gave birth to both [[NetBSD]] and [[FreeBSD]]. Once patchkit 023 is installed, 386BSD will then run under [[Qemu]] 0.11.x

*[[386 BSD 0.1]]
*[[386 BSD 0.1 pl23]]
*[[386 BSD 0.1 pl24]]

*X11 I've found a massive lead [http://cd.textfiles.com/ldr199410/DISC2/X11/XFREE861/ here]. Thanks to shovelware CD makers!

=== 0.2 ===
An update for ISO-9660 and Rock Ridge extensions. See DrDobbs July 1993.

=== 1.0 ===
This was the CD-ROM / DrDobbs release

=== 2.0 ===
In an email with Lynne Jolitz, she has confirmed that there was a 2.0 release. In 2016 it was re-released on [https://github.com/386bsd/386bsd github]

== Where can I get a copy ==

At the moment the only known places to get copies are:

* [http://www.oldlinux.org/Linux.old/distributions/386BSD/ oldlinux.org] 0.0, 0.1 and the two patchkits.
* [ftp://minnie.tuhs.org/BSD/ tuhs.org] 0.0, 0.1 and the two patchkits.
* [ftp://ftp1.am.freebsd.org/pub/ancientBSD/386BSD/cd1.iso freebsd.org] ISO with 0.0, 0.1, the patchkits in various states, a large number of other contributions to 0.0 and 0.1 and a USENET archive of comp.unix.bsd.

== How do I get this to run?! ==
Right now the only version fully running in emulation is 0.1
The quickest way is to use [https://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/386BSD-0.1.exe/download 386BSD-0.1exe] which is a ready to run package for Windows users that includes a preconfigured Qemu & disk image.

{{Nav Unix}}

Installing 386BSD on BOCHS

2016-07-18T10:59:50Z

Dugo: /* Create a disk image */ for use with new bximage

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

Note that newer iptables has a slightly different syntax. -d ! has become ! -d.

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

If that fails you probably have a very recent version of bximage, in that case:

<pre>
printf "1\nhd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."
A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patchkits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-18T10:57:22Z

Dugo: /* Configure Bochs */ fix the symlink tun/tun0 issue

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

Note that newer iptables has a slightly different syntax. -d ! has become ! -d.

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."
A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patchkits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-18T10:56:36Z

Dugo: /* Prepare the host for networking Bochs */ iptables update

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

Note that newer iptables has a slightly different syntax. -d ! has become ! -d.

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."
A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patchkits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T23:22:27Z

Dugo: /* Fourth boot, multiuser mode */ thinly veiled commercial for Reeds book

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. 386BSD 0.2 never came and in early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD."
A few months later Chris Demetriou wrote “So you say you want an interim release of 386bsd?” and officially announced the first version of NetBSD. These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There is a BSD history book in the making by Jeremy C. Reed. It is very detailed and has a full annotated chapter on the patchkits. It is not yet in print, but rumor has the chapter can be obtained together with a warezed copy of NetBSD 0.8 in a manilla folder from a coughing, chain smoking guy in a raincoat if you know the right parking garage. For now see:

*http://reedmedia.net/books/bsd-history/

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T22:08:08Z

Dugo: /* Start up Bochs */ Manage expectations about speed

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

After a while you should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T21:44:04Z

Dugo: /* Get, patch, configure and compile Bochs */ fix link

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [https://sourceforge.net/p/bochs/code/9959/ patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T21:29:55Z

Dugo: /* Restart Bochs */ fix looks

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T21:29:02Z

Dugo: /* First boot, Tiny 386BSD */ fix looks

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T21:27:33Z

Dugo: /* Restart Bochs */ fix looks

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:12px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Installing 386BSD on BOCHS

2016-07-11T21:20:26Z

Dugo: /* Get, patch, configure and compile Bochs */ compile tip

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

Pasting into Bochs is a drag. Playing with BX_KBD_ELEMENTS in iodev/keyboard.h here and keyboard_paste_delay later on in the Bochs configuration can help, but YMMV.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:3px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

Coherent

2015-01-19T09:20:37Z

Dugo: /* Getting it to run */ add tip for fsck speed

[[Image:Coherent 4 print ad.jpg|200px|thumb|right|A print Coherent ad]]

Coherent was a 'clean room' clone of [[Seventh Edition Unix|Unix v7]], originally written for the PDP-11 in 1980. It was ported to run on the IBM PC in 1983 and to the [[Zilog Z8000]]-based [[Commodore 900]] in 1985. Coherent was somewhat famous for being audited by Bell Labs and was vetted to be free of AT&T code. Despite its low price it failed to achieve any significant market share.

A review from 1991 can be found [http://aplawrence.com/Reviews/coherent_1991.html here]

Coherent has been recently opensourced, under a 3-clause BSD license.

More information about the source code to Coherent can be found at [http://www.nesssoftware.com/home/mwc/source.php www.nesssoftware.com].

== Getting it to run ==
Right now the easiest way is to use [[Qemu]]. I've found that a memory size of 8MB is the best, as I had several issues with 12MB. The fsck of a large disk during boot does take a long time, so you need to be patient or use a small disk.

{{stub}}
{{Nav Unix}}
[[Category:Operating Systems]]

Installing UNIX v6 (PDP-11) on SIMH

2015-01-19T09:18:17Z

Dugo: /* Tape boot */ add note on how to do it on simh beta

I'm going to try to describe the install procedure used by [http://mailman.trailing-edge.com/pipermail/simh/2010-October/006009.html Tim Newsham] for [[Unix_System_6|Unix v6]] on the [[PDP-11/40]].

NOTE: Comments at the end of a line of the form:
<pre>
[## Comment]
</pre>
are just to tell you what to do when there is ambiguity; please do not type them in literally!.

== Materials ==
I'm going to expect you to have the [[SIMH]] emulator, 3.8-1 or higher, and a Unix v6 tape [http://sourceforge.net/projects/bsd42/files/Install%20tapes/Research%20Unix/Unix-v6-Ken-Wellsch.tap.bz2/download Unix-v6-Ken-Wellsch.tap]

== Tape boot ==
Here we load the bootblock and load up the root partition onto the rk disk file...

First the tboot.ini file. On more recent simh builds, remove the semicolons and the comments behind them.
<pre>
set cpu 11/40
set tm0 locked
attach tm0 dist.tap
attach rk0 rk0
attach rk1 rk1
attach rk2 rk2
d cpu 100000 012700 ; mov #172526,R0
d cpu 100002 172526
d cpu 100004 010040 ; mov R0,-(R0)
d cpu 100006 012740 ; mov #60003,-(R0)
d cpu 100010 060003
d cpu 100012 000777 ; br 100012
g 100000
</pre>

Once this is run, the simulation will 'lock', hit CTRL+E to break the emulation, and then execute the stand alone program to prepare the hard disk. Type in:
<pre>
g 0
</pre>

And the stand alone program will be ready to respond. Here is my install session:
<pre>
PDP-11 simulator V3.8-1
sim> set cpu 11/40
Disabling XQ
sim> set tm0 locked
sim> attach tm0 dist.tap
sim> attach rk0 rk0
RK: creating new file
sim> attach rk1 rk1
RK: creating new file
sim> attach rk2 rk2
RK: creating new file
sim> d cpu 100000 012700
sim> d cpu 100002 172526
sim> d cpu 100004 010040
sim> d cpu 100006 012740
sim> d cpu 100010 060003
sim> d cpu 100012 000777
sim> g 100000

Simulation stopped, PC: 100012 (BR 100012)
sim> g 0
=tmrk
disk offset
0
tape offset
100
count
1
=tmrk
disk offset
1
tape offset
101
count
3999
= [## Hit CTRL-E here]
Simulation stopped, PC: 137300 (BGE 137274)
sim> q
Goodbye
</pre>

== disk install ==

Here is our dboot.ini for booting from the hard disk:
<pre>
set cpu 11/40
set tto 7b
set tm0 locked
attach tm0 dist.tap
attach rk0 rk0
attach rk1 rk1
attach rk2 rk2
dep system sr 173030
boot rk0
</pre>

=== Booting up to single user mode ===
And this will boot us up to the bootloader, to which we just tell it to load the 'unix' kernel.
<pre>
PDP-11 simulator V3.8-1
sim> set cpu 11/40
Disabling XQ
sim> set tto 7b
sim> set tm0 locked
sim> attach tm0 dist.tap
sim> attach rk0 rk0
sim> attach rk1 rk1
sim> attach rk2 rk2
sim> dep system sr 173030
sim> boot rk0
@rkunix
mem = 1030
RESTRICTED RIGHTS

Use, duplication or disclosure is subject to
restrictions stated in Contract with Western
Electric Company, Inc.
#
</pre>

=== Fixing the Terminal ===
The first thing we are going to do with UNIX loaded is set the terminal back to lowercase... Enter the following command in lower case, it'll echo back in upper case, but that's just the way it works.

<pre>
# STTY -LCASE
</pre>

=== Rebuilding the kernel ===
We are going to rebuild the kernel to support the appropriate hardware that SIMH provides. First we must build the mkconf program
<pre>
chdir /usr/sys/conf
cc mkconf.c
mv a.out mkconf
</pre>

With the mkconf program built, we then feed it a basic configuration file. To do this we just run mkconf, then type in the list of devices we want.
<pre>
rk
tm
tc
8dc
lp
done
</pre>

And you'll get this:
<pre>
# ./mkconf
rk
tm
tc
8dc
lp
done
#
</pre>

Now we can compile the config, and link in the rest of the kernel, and copy it to the root.

<pre>
as m40.s
mv a.out m40.o
cc -c c.c
as l.s
ld -x a.out m40.o c.o ../lib1 ../lib2
mv a.out /unix
</pre>

And to verify, our kernel should be 30kb
<pre>
# ls -l /unix
-rwxrwxrwx 1 root 30346 Oct 10 12:43 /unix
</pre>

=== building device files ===
Now we'll build the device files. Just copy & paste this in.
<pre>
/etc/mknod /dev/rk0 b 0 0
/etc/mknod /dev/rk1 b 0 1
/etc/mknod /dev/rk2 b 0 2
/etc/mknod /dev/mt0 b 3 0
/etc/mknod /dev/tap0 b 4 0
/etc/mknod /dev/rrk0 c 9 0
/etc/mknod /dev/rrk1 c 9 1
/etc/mknod /dev/rrk2 c 9 2
/etc/mknod /dev/rmt0 c 12 0
/etc/mknod /dev/lp0 c 2 0
/etc/mknod /dev/tty0 c 3 0
/etc/mknod /dev/tty1 c 3 1
/etc/mknod /dev/tty2 c 3 2
/etc/mknod /dev/tty3 c 3 3
/etc/mknod /dev/tty4 c 3 4
/etc/mknod /dev/tty5 c 3 5
/etc/mknod /dev/tty6 c 3 6
/etc/mknod /dev/tty7 c 3 7
chmod 640 /dev/*rk*
chmod 640 /dev/*mt*
chmod 640 /dev/*tap*
</pre>

=== Restoring the rest of the OS ===

<pre>
dd if=/dev/mt0 of=/dev/rk1 count=4000 skip=4100
/etc/mount /dev/rk1 /usr/source
dd if=/dev/mt0 of=/dev/rk2 count=4000 skip=8100
mkdir /usr/doc
</pre>
[[Category:SIMH Tutorials]]

=== configure boot ===

I just use cat to append the boot statements for the other disks.
<pre>
/etc/mount /dev/rk1 /usr/source
/etc/mount /dev/rk2 /usr/doc
</pre>

And I append them like this:
<pre>
# cat >> /etc/rc
/etc/mount /dev/rk1 /usr/source
/etc/mount /dev/rk2 /usr/doc

</pre>
then hit CTRL+D

=== rebuild the df command ===
To config the df:
<pre>
# chdir /usr/source/s1
# ed df.c
/rp0/d
.-2a
"/dev/rk0",
"/dev/rk1",
.
w
q
# cc -s -O df.c
# cp a.out /bin/df
# rm a.out
</pre>

=== check filesystems ===
fsck didn't exist back then... So we run icheck/dcheck.
<pre>
icheck /dev/rrk0
dcheck /dev/rrk0
icheck /dev/rrk1
dcheck /dev/rrk1
icheck /dev/rrk2
dcheck /dev/rrk2
</pre>

=== enable multiser ===
The default /etc/ttys file isn't listening on the serial ports, so we change that by simply editing the file....
<pre>
# ed /etc/ttys
1,8s/^0/1/p
w
q
#
</pre>

=== reboot ===
There is no reboot command so run sync a few times, then Control+E to interrupt and quit the simulator.
<pre>
# sync
# sync
# sync
# sync
# [## Hit CTRL-E here]
Simulation stopped, PC: 002502 (MOV (SP)+,177776)
sim> q
Goodbye

C:\temp\v6\myv6>
</pre>

== Running normally ==
With the install all done, let's use the following ini file for normal operations.
<pre>
set cpu 11/40
set cpu idle
set tto 7b
set tm0 locked
attach rk0 rk0
attach rk1 rk1
attach rk2 rk2
attach lpt printer.txt
set dci en
set dci lines=8
set dco 7b
att dci 5555
boot rk0
</pre>

When we fire up the emulator we can then attach on tcp port 5555 for additional users. To boot unix, just pass the name unix to the bootloader.

<pre>

PDP-11 simulator V3.8-1
Disabling XQ
Listening on port 5555 (socket 108)
@unix

login: root
#
</pre>

It's also worth noting that there is no root password.

Installing UNIX v6 (PDP-11) on SIMH

2015-01-19T09:12:13Z

Dugo: /* rebuild the df command */ do it like `run' would do it

I'm going to try to describe the install procedure used by [http://mailman.trailing-edge.com/pipermail/simh/2010-October/006009.html Tim Newsham] for [[Unix_System_6|Unix v6]] on the [[PDP-11/40]].

NOTE: Comments at the end of a line of the form:
<pre>
[## Comment]
</pre>
are just to tell you what to do when there is ambiguity; please do not type them in literally!.

== Materials ==
I'm going to expect you to have the [[SIMH]] emulator, 3.8-1 or higher, and a Unix v6 tape [http://sourceforge.net/projects/bsd42/files/Install%20tapes/Research%20Unix/Unix-v6-Ken-Wellsch.tap.bz2/download Unix-v6-Ken-Wellsch.tap]

== Tape boot ==
Here we load the bootblock and load up the root partition onto the rk disk file...

First the tboot.ini file:
<pre>
set cpu 11/40
set tm0 locked
attach tm0 dist.tap
attach rk0 rk0
attach rk1 rk1
attach rk2 rk2
d cpu 100000 012700 ; mov #172526,R0
d cpu 100002 172526
d cpu 100004 010040 ; mov R0,-(R0)
d cpu 100006 012740 ; mov #60003,-(R0)
d cpu 100010 060003
d cpu 100012 000777 ; br 100012
g 100000
</pre>

Once this is run, the simulation will 'lock', hit CTRL+E to break the emulation, and then execute the stand alone program to prepare the hard disk. Type in:
<pre>
g 0
</pre>

And the stand alone program will be ready to respond. Here is my install session:
<pre>
PDP-11 simulator V3.8-1
sim> set cpu 11/40
Disabling XQ
sim> set tm0 locked
sim> attach tm0 dist.tap
sim> attach rk0 rk0
RK: creating new file
sim> attach rk1 rk1
RK: creating new file
sim> attach rk2 rk2
RK: creating new file
sim> d cpu 100000 012700
sim> d cpu 100002 172526
sim> d cpu 100004 010040
sim> d cpu 100006 012740
sim> d cpu 100010 060003
sim> d cpu 100012 000777
sim> g 100000

Simulation stopped, PC: 100012 (BR 100012)
sim> g 0
=tmrk
disk offset
0
tape offset
100
count
1
=tmrk
disk offset
1
tape offset
101
count
3999
= [## Hit CTRL-E here]
Simulation stopped, PC: 137300 (BGE 137274)
sim> q
Goodbye
</pre>

== disk install ==

Here is our dboot.ini for booting from the hard disk:
<pre>
set cpu 11/40
set tto 7b
set tm0 locked
attach tm0 dist.tap
attach rk0 rk0
attach rk1 rk1
attach rk2 rk2
dep system sr 173030
boot rk0
</pre>

=== Booting up to single user mode ===
And this will boot us up to the bootloader, to which we just tell it to load the 'unix' kernel.
<pre>
PDP-11 simulator V3.8-1
sim> set cpu 11/40
Disabling XQ
sim> set tto 7b
sim> set tm0 locked
sim> attach tm0 dist.tap
sim> attach rk0 rk0
sim> attach rk1 rk1
sim> attach rk2 rk2
sim> dep system sr 173030
sim> boot rk0
@rkunix
mem = 1030
RESTRICTED RIGHTS

Use, duplication or disclosure is subject to
restrictions stated in Contract with Western
Electric Company, Inc.
#
</pre>

=== Fixing the Terminal ===
The first thing we are going to do with UNIX loaded is set the terminal back to lowercase... Enter the following command in lower case, it'll echo back in upper case, but that's just the way it works.

<pre>
# STTY -LCASE
</pre>

=== Rebuilding the kernel ===
We are going to rebuild the kernel to support the appropriate hardware that SIMH provides. First we must build the mkconf program
<pre>
chdir /usr/sys/conf
cc mkconf.c
mv a.out mkconf
</pre>

With the mkconf program built, we then feed it a basic configuration file. To do this we just run mkconf, then type in the list of devices we want.
<pre>
rk
tm
tc
8dc
lp
done
</pre>

And you'll get this:
<pre>
# ./mkconf
rk
tm
tc
8dc
lp
done
#
</pre>

Now we can compile the config, and link in the rest of the kernel, and copy it to the root.

<pre>
as m40.s
mv a.out m40.o
cc -c c.c
as l.s
ld -x a.out m40.o c.o ../lib1 ../lib2
mv a.out /unix
</pre>

And to verify, our kernel should be 30kb
<pre>
# ls -l /unix
-rwxrwxrwx 1 root 30346 Oct 10 12:43 /unix
</pre>

=== building device files ===
Now we'll build the device files. Just copy & paste this in.
<pre>
/etc/mknod /dev/rk0 b 0 0
/etc/mknod /dev/rk1 b 0 1
/etc/mknod /dev/rk2 b 0 2
/etc/mknod /dev/mt0 b 3 0
/etc/mknod /dev/tap0 b 4 0
/etc/mknod /dev/rrk0 c 9 0
/etc/mknod /dev/rrk1 c 9 1
/etc/mknod /dev/rrk2 c 9 2
/etc/mknod /dev/rmt0 c 12 0
/etc/mknod /dev/lp0 c 2 0
/etc/mknod /dev/tty0 c 3 0
/etc/mknod /dev/tty1 c 3 1
/etc/mknod /dev/tty2 c 3 2
/etc/mknod /dev/tty3 c 3 3
/etc/mknod /dev/tty4 c 3 4
/etc/mknod /dev/tty5 c 3 5
/etc/mknod /dev/tty6 c 3 6
/etc/mknod /dev/tty7 c 3 7
chmod 640 /dev/*rk*
chmod 640 /dev/*mt*
chmod 640 /dev/*tap*
</pre>

=== Restoring the rest of the OS ===

<pre>
dd if=/dev/mt0 of=/dev/rk1 count=4000 skip=4100
/etc/mount /dev/rk1 /usr/source
dd if=/dev/mt0 of=/dev/rk2 count=4000 skip=8100
mkdir /usr/doc
</pre>
[[Category:SIMH Tutorials]]

=== configure boot ===

I just use cat to append the boot statements for the other disks.
<pre>
/etc/mount /dev/rk1 /usr/source
/etc/mount /dev/rk2 /usr/doc
</pre>

And I append them like this:
<pre>
# cat >> /etc/rc
/etc/mount /dev/rk1 /usr/source
/etc/mount /dev/rk2 /usr/doc

</pre>
then hit CTRL+D

=== rebuild the df command ===
To config the df:
<pre>
# chdir /usr/source/s1
# ed df.c
/rp0/d
.-2a
"/dev/rk0",
"/dev/rk1",
.
w
q
# cc -s -O df.c
# cp a.out /bin/df
# rm a.out
</pre>

=== check filesystems ===
fsck didn't exist back then... So we run icheck/dcheck.
<pre>
icheck /dev/rrk0
dcheck /dev/rrk0
icheck /dev/rrk1
dcheck /dev/rrk1
icheck /dev/rrk2
dcheck /dev/rrk2
</pre>

=== enable multiser ===
The default /etc/ttys file isn't listening on the serial ports, so we change that by simply editing the file....
<pre>
# ed /etc/ttys
1,8s/^0/1/p
w
q
#
</pre>

=== reboot ===
There is no reboot command so run sync a few times, then Control+E to interrupt and quit the simulator.
<pre>
# sync
# sync
# sync
# sync
# [## Hit CTRL-E here]
Simulation stopped, PC: 002502 (MOV (SP)+,177776)
sim> q
Goodbye

C:\temp\v6\myv6>
</pre>

== Running normally ==
With the install all done, let's use the following ini file for normal operations.
<pre>
set cpu 11/40
set cpu idle
set tto 7b
set tm0 locked
attach rk0 rk0
attach rk1 rk1
attach rk2 rk2
attach lpt printer.txt
set dci en
set dci lines=8
set dco 7b
att dci 5555
boot rk0
</pre>

When we fire up the emulator we can then attach on tcp port 5555 for additional users. To boot unix, just pass the name unix to the bootloader.

<pre>

PDP-11 simulator V3.8-1
Disabling XQ
Listening on port 5555 (socket 108)
@unix

login: root
#
</pre>

It's also worth noting that there is no root password.

User:Dugo/My sandbox

2014-06-22T14:30:57Z

Dugo: /* Fuzzball dsd 880 notes */

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
svn co https://dosemu.svn.sourceforge.net/svnroot/dosemu/trunk dosemu
cd dosemu
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tg* dosemu-freedos-bin.tgz
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.
A ready made image can be fetched from http://www.xs4all.nl/~dugo/fuzzball.img.bz2

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

=== Fuzzball clock notes. ===

The STARTF.COM on Mills fuzzball archive runs this before booting BOS.

DATE 1-JAN-92
R SETCLK

It is used to set time and date from local reference. The clocks in vogue at the time often don't provide the year, so this is specified first with the RT-11 DATE command.

SETCLK can be conditionally assembled. Assuming the defaults were used (suspend disbelief here) there is a PST/Traconexattached to what simh console keyboard uses as console keyboard.

Code:
.IIF NDF,SLUREG SLUREG == 176560 ;default slu device address
.IIF NDF,CLKTYP CLKTYP == ^RPST ;default clock type

Simh:
sim> sh TTI
TTI address=17777560-17777563, vector=60

COM12: .ASCIZ 'Enter date (mm/dd/yy): '<200>
COM13: .ASCIZ 'Enter time (hh:mm:ss): '<200>

=== Fuzzball CPU / bus/ MMU / LTC / disk notes ===

<pre>
; SIMH config file to emulate DCN6 fuzzball hardware
;
; "Laugh it up, fuzzball."
; Han Solo to Chewbacca, "The Empire Strikes Back"
;
; disable a lot of stuff first
;
set ptr dis
set ptp dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis
set CR dis
set rl dis
set rq dis
;
; From SUP6.MAC, the system conditionals for dcn6
; CPU == 5 ;sup cpu/bus type (22-bit I/D space)
;
; The CPU and memory configuration can be:
;
; CPU PS Memory
; -----------------------------------------------------------------
; 0 no 16 LSI-11/2 (without PS), 16-bit bus
; 1 yes 16 PDP11, LSI-11/2/23/73 (with PS), 16-bit bus
; 2 yes 18 PDP11, LSI-11/23/73 18-bit bus (default)
; 3 yes 22 LSI-11/23/73 22-bit bus
; 4 yes 22 LSI-11/73 22-bit bus with coincident i/d space
; 5 yes 22 LSI-11/73 22-bit bus with separate i/d space
;
; The 11/73 has an MMU, so let's give this a shot w/ 5, else try 3 and 4
;
set cpu 11/73 2048K
;
; Print listings until we have TCT/IP up!
;
set lpt enabled
ATTACH LPT LPT.TXT
;
; not sure if this is right,
; maybe 7b works better w/
; KED and friends?
; Mills does a
; SET TT: WIDTH=80
; SET TT: TAB
; SET TT: SCOPE
; in STARTF.COM
;
set tti 8b
set tto 8b
;
; Hardware clocks
;
; For UNIBUS systems the interval timer and system clock functions
; can be provided by the KW11-L or KW11-P. For Q-BUS systems these
; functions can be provided by the integral LTC or KWV11-A/C. For the
; highest accuracy and lowest overhead, the combination of LTC as the
; interval timer plus KWV11-A/C as the system clock is recommended.
;
; HDWCLK Timer Clock
; --------------------------------------------------------------
; 0 KW11-L/LTC KW11-L/LTC UNIBUS and Q-BUS
; 1 KW11-P KW11-P UNIBUS only
; 2 KWV11-A/C KWV11-A/C Q-BUS only
; 3 LTC KWV11-A/C Q-BUS only
;
; DCN6 had:
; HDWCLK == 3 ;sup hardware clock (kwv11-a/c)
; but simh doesn't have that (yet).
; 1 is available in a simh qbus system, but that's a bit weird.
; I'll go for 0 for now.
;
SET CLK 60HZ
;
; Now for disks
; there is the DSK Disk driver process
; and...
; DSKDU MSCP disk driver
; DSKDY RX21/RX02 disk driver
; DSKDL RL11/RL01/RL02 disk driver
; DSKVM RAM disk driver
; DSKFD AED 6200 disk driver
;
; DCN6 had:
; CS.D22 == 2 ;dskdy rx02 controller (sigma rxv31 22-bit)
; well.. that's DSKDY
;
;; Pdp11/dcn rx21/rx02 disk driver
;;
;; This module is an extension of the disk driver process. it services
;; The dec rx21/rxv21 disk controller with up to two rx02 drives and ssdd
;; disks. It also supports 22-bit mode and dsdd disks using the dsd 880 or
;; sigma rxv31 controllers. This driver does not support sssd disks.
;;
;; Max blocks: 988/1976, rt-11 directory segments: 4 (8 blocks), rt-11 id: 6
;;
;; Note: standard csr/vector addresses are 777170/264.
;;
;; Conditional assembly switches
;;
;.IIF NDF,CS.D22 CS.D22 == 0 ;0: dec rxv21, 1: dsd 880, 2: sigma rxv31
;;
;
;
; no simh clue here
; The RX211 is disabled in a Qbus system with more than 256KB
; so much for dskdy
; with the below I can get a build system up at least..
;
set rq enabled
set rq0 RD54
att rq0 fuzzball.img
;
;
; That's simhese for the RQDX3/UDA50 MSCP Disk Controllers (RQ, RQB, RQC, RQD)
; with a RD54 drive.
;
; there might be some support for that in the fuzz..
;
; Pdp11/dcn mscp disk driver
;
; This module is an extension of the disk driver process. it services
; the dec uda50 mscp disk controller and drives. Note that this driver
; supports up to six partitions on mscp unit 0 (hard disk), together
; with one partition each on mscp units 1 and 2 (floppette disks). RT-11
; drives 0-5 are associated with the six partitions on unit 0, while
; drive 6 is associated with unit 1 and drive 7 with unit 2.
;
; Max blocks: 65535, rt-11 directory segments: 32 (64 blocks), rt-11 id:
; 50
;
; Note: standard csr/vector addresses are 172150/154.
;
;;
; The dsd 880 mentioned above is an interesting beast.
; brochure at https://archive.org/details/bitsavers_dsdDSD880B_7659665
; ..and, this lucky chap got the front panel of one of those disks from a fuzzie
; http://www.vintagecomputer.net/browse_thread.cfm?id=357
;
sh dev
; this should show smth like
; CLK 60Hz, address=17777546-17777547, vector=100
; TTI address=17777560-17777563, vector=60
; TTO address=17777564-17777567, vector=64
; LPT address=17777514-17777517, vector=200
; RQ address=17772150-17772153, no vector, RQDX3, 4 units
;
; far from done, but hey..
boot rq0
quit
</pre>

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

SIMH

2014-06-22T07:30:23Z

Dugo: /* Emulated Systems */

[http://sourceforge.net/projects/simh/ SIMH] ([http://simh.trailing-edge.com/ home page]) consists of simulators for about 20 different machines, and as such, is a very important emulator for anyone interested in computer history, in particular, that of [[DEC]] systems, as the PDPs and even the [[VAX]] are well emulated by it. It can even emulate network interfaces for the [[PDP-10]], [[PDP-11]] and VAX, so the emulated systems can network directly onto the Internet, if the emulated operating system supports it, like BSD or [[VMS]].

SIMH was primarily written by Bob Supnik of Zork porting fame, and is now widely contributed to by others as well.

The current version is 3.9-0, released on May 3rd, 2012. More up to date developments may be found on their [https://github.com/simh/simh source code repository].

== Emulated Systems ==
=== Altair 8800 ===
This is the Altair 8800 emulator which can run both AltairDOS and CP/M 2.2

=== Altair Z80 ===

SIMH emulates the [[Altair]] architecture with your choice of either a [[Z80]] or [[Intel 8080]] processor. It can run [[CP/M]].

=== Honeywell H316/H516 ===

Emulates the work horse behind the ARPANET IMPs. In 2013 the emulator was modified to bring up the original IMP code and connect them together (tunnelled over IP). Demo instructions are available in the latest source. The IMP side of the 1822 is there, but there is not much of a host side yet. I don't see anything in simh that would be able to plug in anyway. An associated computer consultants (acc) 1822 card for the pdp-11 would be a start.

=== HP2100 ===

I really don't know much about this machine, but I included a way to run the basic1 program I found online. It kind of reminds me of the ROMBASIC back 'in the day'... It's basic with line numbers so I know it's kind of old.. I really don't know much otherwise about this machine.

=== Interdata 8/32 ===

The interdata 8/32 micro was the first non [[PDP-11]] to run UNIX. SIMH can run both v6 & v7 research editions for the Interdata.

=== Nova ===

SIMH can run [[RDOS]] 7.5 for the [[Nova]].

SIMH also includes [[Data General Eclipse]] support, but there is no available OS.

=== DEC PDP-1 ===

The original [[PDP-1]] is emulated although most of the software is expected to be toggled from the console, or loaded from paper tape. SIMH does not emulate the display needed for [[spacewar]].

=== DEC PDP-8 ===

The [[PDP-8]] was the first 'affordable' microcomputer... [[OS/8]] runs under SIMH.

=== DEC PDP-10 ===

The [[PDP-10]] model KS processor is emulated and will run all but the latest versions of the [[TOPS-10]] and [[TOPS-20]] operating systems.

=== DEC PDP-11 ===

The [[PDP-11]] is emulated enough to run most PDP-11 operating systems including the early Unixes (v1,4,5,6,7 are known to run).

=== MicroVAX II ===

SIMH can run the [[MicroVAX II]] with as much as 256mb of emulated ram. Both VMS, NetBSD, OpenBSD and original BSD can run on this emulator. Additionally, the network adapter functions correctly under this emulator, unlike the [[VAX-11/780]].

=== VAX 11/780 ===

SIMH can also emulate the first model of the VAX, the [[VAX-11/780]]. This is appropriate for older operating systems like VMS release 1.x and the original 32v, 3BSD and all 4BSD releases.

== Usage ==

SIMH can either take in configuration parameters interactively, or you can store them in a file. If the file is the name of the emulator+.ini it will load them automatically (eg vax.exe loads vax.ini automatically). The CONTROL+E key will break the emulation and bring you back to the SIMH console where you can alter the running state.

Networking is covered in the [[Networking with SIMH]] guide.

== Support ==

While not immediately obvious, there is a mailing list here [http://mailman.trailing-edge.com/pipermail/simh/ http://mailman.trailing-edge.com/pipermail/simh/]. I would recommend searching the thing, and you'll be amazed how much good information there is in there. Likewise, I'd recommend joining the list if you are interested in running SIMH. You can join [http://mailman.trailing-edge.com/mailman/listinfo/simh here].

[[Category:Emulators]]

User:Dugo/My sandbox

2014-06-12T18:44:49Z

Dugo: /* Fuzzball CPU .. more notes */

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
svn co https://dosemu.svn.sourceforge.net/svnroot/dosemu/trunk dosemu
cd dosemu
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tg* dosemu-freedos-bin.tgz
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.
A ready made image can be fetched from http://www.xs4all.nl/~dugo/fuzzball.img.bz2

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

=== Fuzzball clock notes. ===

The STARTF.COM on Mills fuzzball archive runs this before booting BOS.

DATE 1-JAN-92
R SETCLK

It is used to set time and date from local reference. The clocks in vogue at the time often don't provide the year, so this is specified first with the RT-11 DATE command.

SETCLK can be conditionally assembled. Assuming the defaults were used (suspend disbelief here) there is a PST/Traconexattached to what simh console keyboard uses as console keyboard.

Code:
.IIF NDF,SLUREG SLUREG == 176560 ;default slu device address
.IIF NDF,CLKTYP CLKTYP == ^RPST ;default clock type

Simh:
sim> sh TTI
TTI address=17777560-17777563, vector=60

COM12: .ASCIZ 'Enter date (mm/dd/yy): '<200>
COM13: .ASCIZ 'Enter time (hh:mm:ss): '<200>

=== Fuzzball CPU / bus/ MMU / LTC / disk notes ===

<pre>
; SIMH config file to emulate DCN6 fuzzball hardware
;
; "Laugh it up, fuzzball."
; Han Solo to Chewbacca, "The Empire Strikes Back"
;
; disable a lot of stuff first
;
set ptr dis
set ptp dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis
set CR dis
set rl dis
set rq dis
;
; From SUP6.MAC, the system conditionals for dcn6
; CPU == 5 ;sup cpu/bus type (22-bit I/D space)
;
; The CPU and memory configuration can be:
;
; CPU PS Memory
; -----------------------------------------------------------------
; 0 no 16 LSI-11/2 (without PS), 16-bit bus
; 1 yes 16 PDP11, LSI-11/2/23/73 (with PS), 16-bit bus
; 2 yes 18 PDP11, LSI-11/23/73 18-bit bus (default)
; 3 yes 22 LSI-11/23/73 22-bit bus
; 4 yes 22 LSI-11/73 22-bit bus with coincident i/d space
; 5 yes 22 LSI-11/73 22-bit bus with separate i/d space
;
; The 11/73 has an MMU, so let's give this a shot w/ 5, else try 3 and 4
;
set cpu 11/73 2048K
;
; Print listings until we have TCT/IP up!
;
set lpt enabled
ATTACH LPT LPT.TXT
;
; not sure if this is right,
; maybe 7b works better w/
; KED and friends?
; Mills does a
; SET TT: WIDTH=80
; SET TT: TAB
; SET TT: SCOPE
; in STARTF.COM
;
set tti 8b
set tto 8b
;
; Hardware clocks
;
; For UNIBUS systems the interval timer and system clock functions
; can be provided by the KW11-L or KW11-P. For Q-BUS systems these
; functions can be provided by the integral LTC or KWV11-A/C. For the
; highest accuracy and lowest overhead, the combination of LTC as the
; interval timer plus KWV11-A/C as the system clock is recommended.
;
; HDWCLK Timer Clock
; --------------------------------------------------------------
; 0 KW11-L/LTC KW11-L/LTC UNIBUS and Q-BUS
; 1 KW11-P KW11-P UNIBUS only
; 2 KWV11-A/C KWV11-A/C Q-BUS only
; 3 LTC KWV11-A/C Q-BUS only
;
; DCN6 had:
; HDWCLK == 3 ;sup hardware clock (kwv11-a/c)
; but simh doesn't have that (yet).
; 1 is available in a simh qbus system, but that's a bit weird.
; I'll go for 0 for now.
;
SET CLK 60HZ
;
; Now for disks
; there is the DSK Disk driver process
; and...
; DSKDU MSCP disk driver
; DSKDY RX21/RX02 disk driver
; DSKDL RL11/RL01/RL02 disk driver
; DSKVM RAM disk driver
; DSKFD AED 6200 disk driver
;
; DCN6 had:
; CS.D22 == 2 ;dskdy rx02 controller (sigma rxv31 22-bit)
; well.. that's DSKDY
;
;; Pdp11/dcn rx21/rx02 disk driver
;;
;; This module is an extension of the disk driver process. it services
;; The dec rx21/rxv21 disk controller with up to two rx02 drives and ssdd
;; disks. It also supports 22-bit mode and dsdd disks using the dsd 880 or
;; sigma rxv31 controllers. This driver does not support sssd disks.
;;
;; Max blocks: 988/1976, rt-11 directory segments: 4 (8 blocks), rt-11 id: 6
;;
;; Note: standard csr/vector addresses are 777170/264.
;;
;; Conditional assembly switches
;;
;.IIF NDF,CS.D22 CS.D22 == 0 ;0: dec rxv21, 1: dsd 880, 2: sigma rxv31
;;
;
;
; no simh clue here
; The RX211 is disabled in a Qbus system with more than 256KB
; so much for dskdy
; with the below I can get a build system up at least..
;
set rq enabled
set rq0 RD54
att rq0 fuzzball.img
;
; That's simhese for the RQDX3/UDA50 MSCP Disk Controllers (RQ, RQB, RQC, RQD)
; with a RD54 drive.
;
; there might be some support for that in the fuzz..
;
; Pdp11/dcn mscp disk driver
;
; This module is an extension of the disk driver process. it services
; the dec uda50 mscp disk controller and drives. Note that this driver
; supports up to six partitions on mscp unit 0 (hard disk), together
; with one partition each on mscp units 1 and 2 (floppette disks). RT-11
; drives 0-5 are associated with the six partitions on unit 0, while
; drive 6 is associated with unit 1 and drive 7 with unit 2.
;
; Max blocks: 65535, rt-11 directory segments: 32 (64 blocks), rt-11 id:
; 50
;
; Note: standard csr/vector addresses are 172150/154.
;
sh dev
; this should show smth like
; CLK 60Hz, address=17777546-17777547, vector=100
; TTI address=17777560-17777563, vector=60
; TTO address=17777564-17777567, vector=64
; LPT address=17777514-17777517, vector=200
; RQ address=17772150-17772153, no vector, RQDX3, 4 units
;
; far from done, but hey..
boot rq0
quit
</pre>

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

User:Dugo/My sandbox

2014-02-23T22:58:01Z

Dugo:

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
svn co https://dosemu.svn.sourceforge.net/svnroot/dosemu/trunk dosemu
cd dosemu
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tg* dosemu-freedos-bin.tgz
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.
A ready made image can be fetched from http://www.xs4all.nl/~dugo/fuzzball.img.bz2

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

=== Fuzzball clock notes. ===

The STARTF.COM on Mills fuzzball archive runs this before booting BOS.

DATE 1-JAN-92
R SETCLK

It is used to set time and date from local reference. The clocks in vogue at the time often don't provide the year, so this is specified first with the RT-11 DATE command.

SETCLK can be conditionally assembled. Assuming the defaults were used (suspend disbelief here) there is a PST/Traconexattached to what simh console keyboard uses as console keyboard.

Code:
.IIF NDF,SLUREG SLUREG == 176560 ;default slu device address
.IIF NDF,CLKTYP CLKTYP == ^RPST ;default clock type

Simh:
sim> sh TTI
TTI address=17777560-17777563, vector=60

COM12: .ASCIZ 'Enter date (mm/dd/yy): '<200>
COM13: .ASCIZ 'Enter time (hh:mm:ss): '<200>

=== Fuzzball CPU / memory notes ===

The supervisor can be assembled for the following 5 configurations.

<pre>
; CPU PS Memory
; -----------------------------------------------------------------
; 0 no 16 LSI-11/2 (without PS), 16-bit bus
; 1 yes 16 PDP11, LSI-11/2/23/73 (with PS), 16-bit bus
; 2 yes 18 PDP11, LSI-11/23/73 18-bit bus (default)
; 3 yes 22 LSI-11/23/73 22-bit bus
; 4 yes 22 LSI-11/73 22-bit bus with coincident i/d space
; 5 yes 22 LSI-11/73 22-bit bus with separate i/d space
</pre>

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

User:Dugo/My sandbox

2014-02-02T13:18:39Z

Dugo: clock note

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
svn co https://dosemu.svn.sourceforge.net/svnroot/dosemu/trunk dosemu
cd dosemu
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tg* dosemu-freedos-bin.tgz
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.
A ready made image can be fetched from http://www.xs4all.nl/~dugo/fuzzball.img.bz2

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

=== Fuzzball clock notes. ===

The STARTF.COM on Mills fuzzball archive runs this before booting BOS.

DATE 1-JAN-92
R SETCLK

It is used to set time and date from local reference. The clocks in vogue at the time often don't provide the year, so this is specified first with the RT-11 DATE command.

SETCLK can be conditionally assembled. Assuming the defaults were used (suspend disbelief here) there is a PST/Traconexattached to what simh console keyboard uses as console keyboard.

Code:
.IIF NDF,SLUREG SLUREG == 176560 ;default slu device address
.IIF NDF,CLKTYP CLKTYP == ^RPST ;default clock type

Simh:
sim> sh TTI
TTI address=17777560-17777563, vector=60

COM12: .ASCIZ 'Enter date (mm/dd/yy): '<200>
COM13: .ASCIZ 'Enter time (hh:mm:ss): '<200>

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

386BSD

2014-01-06T19:06:39Z

Dugo: added 0.2

[[Image:386BSD logo.jpg|thumb|150px|left|386BSD logo]]
{{Infobox OS
| image = 386bsd.png
| caption = Logging into a 386 BSD system
| name = 386 BSD
| creator = CSRG, University of California, Berkeley
| current version = 1.0 (1993)
| year introduced = 1991
| type = Multitasking, multiuser
| architecture = [[i386]] theoretically portable
}}

386 BSD was the first time that the [[Net/2]] project was put into a functional release onto commodity hardware, and into the public under the BSD license. As the project eventually stalled, it became the starting point for both [[NetBSD]] & [[FreeBSD]], via the patchkits. While 386 BSD may be of historical significance, it's not up to the challenge of day to day usage, as it hasn't received any updates or patches in over 15 years.

== Releases ==
There seems to have been four releases of 386 BSD, starting with it being freely available on the internet, then only available to those who purchased CD-ROMs.

=== 0.0 ===
This is the first version of 386 BSD that was released. This version doesn't share it's disk with MS-DOS or any other OS's, and uses a VAX style disktab/disklabel, making it difficult to install.

*[[386BSD 0.0]]

=== 0.1 ===
The 0.1 release was the most popular, as 0.0 proved to be very difficult to install, I'd think because it was more "VAX" like in how it treated the disks, and most people are not familiar with disklabels. There were 2 revisions to 0.1, with the patchkits, that eventually gave birth to both [[NetBSD]] and [[FreeBSD]]. Once patchkit 023 is installed, 386BSD will then run under [[Qemu]] 0.11.x

*[[386 BSD 0.1]]
*[[386 BSD 0.1 pl23]]
*[[386 BSD 0.1 pl24]]

*X11 I've found a massive lead [http://cd.textfiles.com/ldr199410/DISC2/X11/XFREE861/ here]. Thanks to shovelware CD makers!

=== 0.2 ===
An update for ISO-9660 and Rock Ridge extensions. See DrDobbs July 1993.

=== 1.0 ===
This was the CD-ROM / DrDobbs release

=== 2.0 ===
In an email with Lynne Jolitz, she has confirmed that there was a 2.0 release.

== Where can I get a copy ==

At the moment the only known places to get copies are:

* [http://www.oldlinux.org/Linux.old/distributions/386BSD/ oldlinux.org] 0.0, 0.1 and the two patchkits.
* [ftp://minnie.tuhs.org/BSD/ tuhs.org] 0.0, 0.1 and the two patchkits.
* [ftp://ftp1.am.freebsd.org/pub/ancientBSD/386BSD/cd1.iso freebsd.org] ISO with 0.0, 0.1, the patchkits in various states, a large number of other contributions to 0.0 and 0.1 and a USENET archive of comp.unix.bsd.

== How do I get this to run?! ==
Right now the only version fully running in emulation is 0.1
The quickest way is to use [https://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/386BSD-0.1.exe/download 386BSD-0.1exe] which is a ready to run package for Windows users that includes a preconfigured Qemu & disk image.

{{Nav Unix}}

Talk:386BSD

2014-01-06T10:05:01Z

Dugo: /* 64 bit Jolix */ new section

You can get 386BSD to run in a patched bochs 2.4.2, full blown with all the patches, triple make world, the works. Ok, ok, try to compile perl-5.10.1 and the compiler segfaults, but what is in the distro works. Everything works. There exists a broken (in a mere two pieces) shell script that reproduces a bochs image and environment on an AWS default fedora server. The script is of such questionable and perverted command line art that it is deemed unredistributable in its current form. It can be done!
[[User:Dugo|Dugo]]

Can you give more details?
Suddenly this is interesting again... !

[[User:Neozeed|neozeed]] 17:57, 3 April 2010 (UTC)

Ok here goes. Take a eg. Basic Fedora Core 8 box and install required software.
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

The 386BSD bootflop does something odd. The workaround is to patch bochs to ignore it instead of panic when 386BSD tries to write 0x02 to port 20h.

<pre>
# get bochs
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz?use_mirror=kent
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

During installation the 386BSD distribution files can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. There is a catch 22. 386BSD comes without gzip, but the patches are gzipped, here your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

To make bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
printf 'date; echo ${1##/*/} >/tmp/x' >>tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=/root/bsd/tunconfig
com1: enabled=0
__EOF
</pre>

Prepare the 386BSD boot floppy for our box with a fancy 1.44MB floppy drive.

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

Make a hard drive for the installation.

<pre>
rm disk.img; printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

You should now be able to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

Bochs will come up booting a tiny 386BSD from floppy, this needs to go to disk, which can be done with a simple

<pre>
(echo y; echo y)|install
</pre>

Now try to reboot with..:
<pre>shutdown -r now</pre>

..this will go horribly wrong but don't panic. Boch will probably crash, just fire it up with..:

<pre>bochs -q -f bochsrc</pre>

386BSD comes up and shuts down immediately causing bochs to crash again. This is a reoccuring theme, don't worry about it and fire bochs up again anytime this happens. Next, the real work, installing the distro.

[[User:Dugo|Dugo]]

The tiny 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, so try to do as much as possible with shell scripts. In this case everything just goes into .netrc.

Extract will complain about something being missing, according to an ancient FAQ this is a joke from Jolitz. Extract also opens more files than tiny 386BSD sh can handle, hence the use csh.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
# .netrc is now ready to do the installaion
# fire up the network and go, go go
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
ftp 10.0.0.1
</pre>

When all goes well bochs crashes when 386BSD shuts down. Restart twice and 386BSD should greet you with a login prompt and scold you for loging in as root (no password) when you do. Next up, patch the system and do a buildworld.
[[User:Dugo|Dugo]]

Now run the first pile of patches.

<pre>
cd /
tar -xvf pk023.tar
mv patch /dist
cd /dist
cd bin
./mkpatchdirs
cd /patch
cd bin
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
cd /patch
cd bin
sh -x afterinstall.sh
</pre>

Recompile the GENERIC kernel.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync;
reboot
</pre>

When bochs goes down because of the reboot, up the amount of mem or the following will take ages.

<pre>
cd /dist/bin
buildworld.sh
sync; sync; sync;
reboot
</pre>

Now do it all again with the second patch set.

<pre>
cd /
tar -xvf pk023024.tar
cd patch/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
sh -x afterinstall.sh
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync;
reboot
</pre>

<pre>
cd /patch/bin
./buildworld.sh
sync; sync; sync;
reboot
</pre>

For good meassure and proof the box works do another buildworld. Then go do something fun with it. Hack a uname system call into the kernel, fix the ancient zoneinfo, fail at getting ssh to work on it, etc..

If something is broken in the commands/scripts above, sorry, I fsckd up, but they should contain enough hints to get a 386BSD box emulated.
[[User:Dugo|Dugo]]
[[User:Dugo|Dugo]]
:Very interesting. I was using the 0.1 release (actually it may have been the 0.0 release, around Jan. 1992) for a short while when it came out, the reason I switched over to Linux 0.95 (early 1992) was IIRC something about the disk usage - I seem to recall that 386BSD wanted the whole disk while it was easy enough to partition with Linux. Or something other that made it easier to let Linux co-exist. Fuzzy memory. -- [[User:Tor|Tor]] 13:43, 30 June 2010 (UTC)

Damn dude, that's like an install article... feel free to write one (use any tutorial as a template if you want) or I'll just do it...

Thanks that's some great work thought!!!!!!

[[User:Neozeed|neozeed]] 04:21, 5 April 2010 (UTC)

I'll try to iron out any misdirections in the above and fold it into a networking with bochs and a 386BSD on bochs tutorial.
[[User:Dugo|Dugo]] 10:23, 5 April 2010 (UTC)

----
Awesome job so far!
[[User:Neozeed|neozeed]] 20:40, 9 April 2010 (UTC)

Getting there. While I think it is important to have this piece of history (386BSD 0.1 + patchkits) preserved for future emulator use there is something missing. Anyone with a clue where I can get an ISO of the 386BSD 1.0 release William & Lynne Jolitz show off on their website http://www.386bsd.org/past ?
[[User:Dugo|Dugo]] 05:26, 13 April 2010 (UTC)

:Re: ''"The 386BSD bootflop does something odd. The workaround is to patch bochs to ignore it instead of panic when 386BSD tries to write 0x02 to port 20h."''
:I had a look at bochs-2.4.6, and it appears to have the 386BSD workaround patch included now. --[[User:Tor|Tor]] ([[User talk:Tor|talk]]) 01:40, 2 April 2013 (PDT)

::Thx, updated the install manual. [[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 03:43, 3 April 2013 (PDT)

== 2.0 ==

I browsed through a load of old DDJ in the late 90s but can't remember a full blown 2.0 CDROM release. A Net release would have left traces on <strike>Dejanews</strike> google news. The German wiki on 386BSD mentions something about an update disk.

"Ebenfalls von Dr. Dobb's Journal wurde schließlich 1995 noch ein Update auf die letzte öffentliche Version 386BSD 2.0 in Form einer Update-Diskette herausgegeben."

== 64 bit Jolix ==

Just musings I suppose..
http://blog.jolix.com/categorylist_html?cat_id=6

Installing 386BSD on BOCHS

2013-07-08T15:12:39Z

Dugo: Y2K info

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

As explained in http://www.os2museum.com/wp/?p=1907 the initial kernel suffers from a Y2K bug. This can result in timestamps with the year 1970. Unfortunately the boot floppy doesn't let you work around this because it is missing the date command. If it bothers you creating new files and directories with a timestamp predating the release date you can set the time to eg. the 16th of July 1992 using bochsrc until you have the date command.

<pre>
clock: time0=711244800
</pre>

Once you are running with patch 00077 installed, Y2K+ bios dates shouldn't be a problem anymore.

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:3px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2 never happened. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Upgrade to NetBSD 0.8 ;)

[[Category:Tutorials]]

NetBSD

2013-06-19T21:13:44Z

Dugo:

{{Infobox OS
| name = NetBSD
| year introduced = 1993
| current version = NetBSD 6.1 (May 18, 2013)
| image = NetBSD imps.jpg
| caption = Of course it runs NetBSD!
| architecture = multiplatform
}}

NetBSD is a bit of a blessing for many hobbyists, as it includes support for the [[VAX]], [[Amiga]], 68k [[Mac]]s, various [[Sun Microsystems|Sun]] systems like the [[Sun-3]] as well as a wide variety of toasters and the [[HP300]]. You might want to check the entire list at the [http://netbsd.org/Ports/ NetBSD list of ports]. There's even some discussion of a port to [[PDP-10]]s!

NetBSD started out as a derivative of [[386 BSD]], as at the time it was a collection of patches to 386BSD. People grew dissatisfied with the lack of updates with 386BSD, and how the patchkit kept getting larger and larger & unwieldy leading to the various authors of the patches to start their own fork of 386BSD, called NetBSD as it was created on the 'internet'. NetBSD focuses on portability and simplicity of the code.

It's worth noting that a political fight within NetBSD led to the formation of [[OpenBSD]].

== Version 0.8, 0.9, 0.9a ==
These early versions were heavily based on [[386 BSD]] + patchkits and contained Net/2 files subject to USL scrutiny. Due to an agreement with USL these distributions are no longer officially available.

According to [http://www.onlamp.com/pub/a/bsd/2006/09/14/netbsd_future.html?page=2 Charles M. Hannum], "..the agreement is very clear, and nobody cares about that early code history any more--so this is all water under the bridge.". Historians beg to differ.

As we locate the older versions I'll add information about each release here.

*[[NetBSD 0.8]]
*[[NetBSD 0.9]]
*[[NetBSD 0.9a]]

== Version 1.2 ==
*[[NetBSD 1.2]]

This version restored support for the [[VAX]] Platform. Additionally more platforms were added solidifying NetBSD as a portable OS.

== Version 5.0.2 ==
The exiting change (well to me) was the inclusion of unit tests in the OS so that users of less used ports (VAX) can certify that their OS is performing as it should be...

[[Installing NetBSD 5.0.2 on the SIMH MicroVAX II]]

== Version 5.1 ==
For what its worth I've installed it on SIMH
[[Installing NetBSD 5.1 on the SIMH MicroVAX II]]

== Version 6.0 ==
Released on October 21 2012.

== Version 6.1 ==
As of May 18, 2013, this is the current version.

I'll tackle this at a later time.

== other ==
[[Running NetBSD on a VAX]]

{{Nav Unix}}

NetBSD

2013-06-19T21:06:57Z

Dugo: /* Version 0.8, 0.9, 0.9a */ updated link

{{Infobox OS
| name = NetBSD
| year introduced = 1993
| current version = NetBSD 6.0 (October 15, 2012)
| image = NetBSD imps.jpg
| caption = Of course it runs NetBSD!
| architecture = multiplatform
}}

NetBSD is a bit of a blessing for many hobbyists, as it includes support for the [[VAX]], [[Amiga]], 68k [[Mac]]s, various [[Sun Microsystems|Sun]] systems like the [[Sun-3]] as well as a wide variety of toasters and the [[HP300]]. You might want to check the entire list at the [http://netbsd.org/Ports/ NetBSD list of ports]. There's even some discussion of a port to [[PDP-10]]s!

NetBSD started out as a derivative of [[386 BSD]], as at the time it was a collection of patches to 386BSD. People grew dissatisfied with the lack of updates with 386BSD, and how the patchkit kept getting larger and larger & unwieldy leading to the various authors of the patches to start their own fork of 386BSD, called NetBSD as it was created on the 'internet'. NetBSD focuses on portability and simplicity of the code.

It's worth noting that a political fight within NetBSD led to the formation of [[OpenBSD]].

== Version 0.8, 0.9, 0.9a ==
These early versions were heavily based on [[386 BSD]] + patchkits and contained Net/2 files subject to USL scrutiny. Due to an agreement with USL these distributions are no longer officially available.

According to [http://www.onlamp.com/pub/a/bsd/2006/09/14/netbsd_future.html?page=2 Charles M. Hannum], "..the agreement is very clear, and nobody cares about that early code history any more--so this is all water under the bridge.". Historians beg to differ.

As we locate the older versions I'll add information about each release here.

*[[NetBSD 0.8]]
*[[NetBSD 0.9]]
*[[NetBSD 0.9a]]

== Version 1.2 ==
*[[NetBSD 1.2]]

This version restored support for the [[VAX]] Platform. Additionally more platforms were added solidifying NetBSD as a portable OS.

== Version 5.0.2 ==
The exiting change (well to me) was the inclusion of unit tests in the OS so that users of less used ports (VAX) can certify that their OS is performing as it should be...

[[Installing NetBSD 5.0.2 on the SIMH MicroVAX II]]

== Version 5.1 ==
For what its worth I've installed it on SIMH
[[Installing NetBSD 5.1 on the SIMH MicroVAX II]]

== Version 6.0 ==
Released on October 21 2012.

== Version 6.1 ==
As of May 18, 2013, this is the current version.

I'll tackle this at a later time.

== other ==
[[Running NetBSD on a VAX]]

{{Nav Unix}}

Talk:NetBSD 0.8

2013-06-18T14:27:35Z

Dugo:

apparently a complete binary/source has been located, waiting on details.

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 18:46, 13 June 2013 (PDT)

Wow, nearly everything that is in the missing list below is there!
There is no file named subr_disk.c, but it looks prety complete.

[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 00:12, 17 June 2013 (PDT)

What is subr_disk.c in the CVS tree, is ufs_disksubr.c in this 0.8(a?) dump.

[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 07:27, 18 June 2013 (PDT)

tty.c needs to cantain a bit more than "revision 1.4 intentionally removed" to compile a 0.8 kernel

The originals for these are missing in the tarball:

<pre>
/netbsd-0.8/src/src/bin/df/df.c
/netbsd-0.8/src/src/include/ar.h
/netbsd-0.8/src/src/include/assert.h
/netbsd-0.8/src/src/include/ctype.h
/netbsd-0.8/src/src/include/grp.h
/netbsd-0.8/src/src/include/nlist.h
/netbsd-0.8/src/src/include/protocols/dumprestore.h
/netbsd-0.8/src/src/include/pwd.h
/netbsd-0.8/src/src/include/setjmp.h
/netbsd-0.8/src/src/include/time.h
/netbsd-0.8/src/src/include/utmp.h
/netbsd-0.8/src/src/lib/libc/gen/ctype_.c
/netbsd-0.8/src/src/lib/libc/gen/isctype.c
/netbsd-0.8/src/src/sbin/restore/dirs.c
/netbsd-0.8/src/src/sbin/restore/pathnames.h
/netbsd-0.8/src/src/sbin/restore/restore.h
/netbsd-0.8/src/src/sbin/restore/tape.c
/netbsd-0.8/src/src/sys/arch/i386/i386/conf.c
/netbsd-0.8/src/src/sys/conf/param.c
/netbsd-0.8/src/src/sys/kern/init_main.c
/netbsd-0.8/src/src/sys/kern/kern_acct.c
/netbsd-0.8/src/src/sys/kern/kern_clock.c
/netbsd-0.8/src/src/sys/kern/kern_descrip.c
/netbsd-0.8/src/src/sys/kern/kern_exit.c
/netbsd-0.8/src/src/sys/kern/kern_fork.c
/netbsd-0.8/src/src/sys/kern/kern_prot.c
/netbsd-0.8/src/src/sys/kern/kern_resource.c
/netbsd-0.8/src/src/sys/kern/kern_sig.c
/netbsd-0.8/src/src/sys/kern/kern_subr.c
/netbsd-0.8/src/src/sys/kern/kern_synch.c
/netbsd-0.8/src/src/sys/kern/subr_disk.c
/netbsd-0.8/src/src/sys/kern/subr_prf.c
/netbsd-0.8/src/src/sys/kern/sys_generic.c
/netbsd-0.8/src/src/sys/kern/sys_process.c
/netbsd-0.8/src/src/sys/kern/sysv_shm.c
/netbsd-0.8/src/src/sys/kern/tty.c
/netbsd-0.8/src/src/sys/kern/tty_conf.c
/netbsd-0.8/src/src/sys/kern/vfs_lookup.c
/netbsd-0.8/src/src/sys/kern/vfs_subr.c
/netbsd-0.8/src/src/sys/kern/vfs_syscalls.c
/netbsd-0.8/src/src/sys/kern/vfs_vnops.c
/netbsd-0.8/src/src/sys/sys/acct.h
/netbsd-0.8/src/src/sys/sys/buf.h
/netbsd-0.8/src/src/sys/sys/callout.h
/netbsd-0.8/src/src/sys/sys/conf.h
/netbsd-0.8/src/src/sys/sys/dkstat.h
/netbsd-0.8/src/src/sys/sys/errno.h
/netbsd-0.8/src/src/sys/sys/exec.h
/netbsd-0.8/src/src/sys/sys/fcntl.h
/netbsd-0.8/src/src/sys/sys/ioctl.h
/netbsd-0.8/src/src/sys/sys/ioctl_compat.h
/netbsd-0.8/src/src/sys/sys/ipc.h
/netbsd-0.8/src/src/sys/sys/kernel.h
/netbsd-0.8/src/src/sys/sys/param.h
/netbsd-0.8/src/src/sys/sys/proc.h
/netbsd-0.8/src/src/sys/sys/shm.h
/netbsd-0.8/src/src/sys/sys/signal.h
/netbsd-0.8/src/src/sys/sys/stat.h
/netbsd-0.8/src/src/sys/sys/systm.h
/netbsd-0.8/src/src/sys/sys/timeb.h
/netbsd-0.8/src/src/sys/sys/times.h
/netbsd-0.8/src/src/sys/sys/tty.h
/netbsd-0.8/src/src/sys/sys/ttydefaults.h
/netbsd-0.8/src/src/sys/sys/types.h
/netbsd-0.8/src/src/sys/ufs/dir.h
/netbsd-0.8/src/src/sys/ufs/ufs_lookup.c
/netbsd-0.8/src/src/sys/ufs/ufs_vfsops.c
/netbsd-0.8/src/src/usr.bin/m4/serv.c
/netbsd-0.8/src/src/usr.bin/mesg/mesg.c
/netbsd-0.8/src/src/usr.sbin/lpr/common_source/common.c
/netbsd-0.8/src/src/usr.sbin/lpr/lpr/lpr.c
</pre>

[[User:Dugo|Dugo]] 14:45, 2 December 2010 (UTC)

I've made way more progress.. now im making headway on re-making the install sets...

from my notes:
<pre>

export DESTDIR=/tmp

find ./ -name 'obj' -exec rm {} \;

make obj
make
make install

etc
---
make distribution

</pre>

I figure I'll leave the tgz's on a filesystem, boot with a floppy, rm -rf most of the file system, unpack, configure and go.

[[User:Neozeed|neozeed]] 18:34, 5 December 2010 (PST)

Installing 386BSD on BOCHS

2013-06-18T13:56:20Z

Dugo: /* TODO */

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:3px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2 never happened. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Add some date(1) commands to the tutorial to prevent files going epoch
* Upgrade to NetBSD

[[Category:Tutorials]]

Talk:NetBSD 0.8

2013-06-17T07:12:10Z

Dugo:

apparently a complete binary/source has been located, waiting on details.

[[User:Neozeed|neozeed]] ([[User talk:Neozeed|talk]]) 18:46, 13 June 2013 (PDT)

Wow, nearly everything that is in the missing list below is there!
There is no file named subr_disk.c, but it looks prety complete.

[[User:Dugo|Dugo]] ([[User talk:Dugo|talk]]) 00:12, 17 June 2013 (PDT)

tty.c needs to cantain a bit more than "revision 1.4 intentionally removed" to compile a 0.8 kernel

The originals for these are missing in the tarball:

<pre>
/netbsd-0.8/src/src/bin/df/df.c
/netbsd-0.8/src/src/include/ar.h
/netbsd-0.8/src/src/include/assert.h
/netbsd-0.8/src/src/include/ctype.h
/netbsd-0.8/src/src/include/grp.h
/netbsd-0.8/src/src/include/nlist.h
/netbsd-0.8/src/src/include/protocols/dumprestore.h
/netbsd-0.8/src/src/include/pwd.h
/netbsd-0.8/src/src/include/setjmp.h
/netbsd-0.8/src/src/include/time.h
/netbsd-0.8/src/src/include/utmp.h
/netbsd-0.8/src/src/lib/libc/gen/ctype_.c
/netbsd-0.8/src/src/lib/libc/gen/isctype.c
/netbsd-0.8/src/src/sbin/restore/dirs.c
/netbsd-0.8/src/src/sbin/restore/pathnames.h
/netbsd-0.8/src/src/sbin/restore/restore.h
/netbsd-0.8/src/src/sbin/restore/tape.c
/netbsd-0.8/src/src/sys/arch/i386/i386/conf.c
/netbsd-0.8/src/src/sys/conf/param.c
/netbsd-0.8/src/src/sys/kern/init_main.c
/netbsd-0.8/src/src/sys/kern/kern_acct.c
/netbsd-0.8/src/src/sys/kern/kern_clock.c
/netbsd-0.8/src/src/sys/kern/kern_descrip.c
/netbsd-0.8/src/src/sys/kern/kern_exit.c
/netbsd-0.8/src/src/sys/kern/kern_fork.c
/netbsd-0.8/src/src/sys/kern/kern_prot.c
/netbsd-0.8/src/src/sys/kern/kern_resource.c
/netbsd-0.8/src/src/sys/kern/kern_sig.c
/netbsd-0.8/src/src/sys/kern/kern_subr.c
/netbsd-0.8/src/src/sys/kern/kern_synch.c
/netbsd-0.8/src/src/sys/kern/subr_disk.c
/netbsd-0.8/src/src/sys/kern/subr_prf.c
/netbsd-0.8/src/src/sys/kern/sys_generic.c
/netbsd-0.8/src/src/sys/kern/sys_process.c
/netbsd-0.8/src/src/sys/kern/sysv_shm.c
/netbsd-0.8/src/src/sys/kern/tty.c
/netbsd-0.8/src/src/sys/kern/tty_conf.c
/netbsd-0.8/src/src/sys/kern/vfs_lookup.c
/netbsd-0.8/src/src/sys/kern/vfs_subr.c
/netbsd-0.8/src/src/sys/kern/vfs_syscalls.c
/netbsd-0.8/src/src/sys/kern/vfs_vnops.c
/netbsd-0.8/src/src/sys/sys/acct.h
/netbsd-0.8/src/src/sys/sys/buf.h
/netbsd-0.8/src/src/sys/sys/callout.h
/netbsd-0.8/src/src/sys/sys/conf.h
/netbsd-0.8/src/src/sys/sys/dkstat.h
/netbsd-0.8/src/src/sys/sys/errno.h
/netbsd-0.8/src/src/sys/sys/exec.h
/netbsd-0.8/src/src/sys/sys/fcntl.h
/netbsd-0.8/src/src/sys/sys/ioctl.h
/netbsd-0.8/src/src/sys/sys/ioctl_compat.h
/netbsd-0.8/src/src/sys/sys/ipc.h
/netbsd-0.8/src/src/sys/sys/kernel.h
/netbsd-0.8/src/src/sys/sys/param.h
/netbsd-0.8/src/src/sys/sys/proc.h
/netbsd-0.8/src/src/sys/sys/shm.h
/netbsd-0.8/src/src/sys/sys/signal.h
/netbsd-0.8/src/src/sys/sys/stat.h
/netbsd-0.8/src/src/sys/sys/systm.h
/netbsd-0.8/src/src/sys/sys/timeb.h
/netbsd-0.8/src/src/sys/sys/times.h
/netbsd-0.8/src/src/sys/sys/tty.h
/netbsd-0.8/src/src/sys/sys/ttydefaults.h
/netbsd-0.8/src/src/sys/sys/types.h
/netbsd-0.8/src/src/sys/ufs/dir.h
/netbsd-0.8/src/src/sys/ufs/ufs_lookup.c
/netbsd-0.8/src/src/sys/ufs/ufs_vfsops.c
/netbsd-0.8/src/src/usr.bin/m4/serv.c
/netbsd-0.8/src/src/usr.bin/mesg/mesg.c
/netbsd-0.8/src/src/usr.sbin/lpr/common_source/common.c
/netbsd-0.8/src/src/usr.sbin/lpr/lpr/lpr.c
</pre>

[[User:Dugo|Dugo]] 14:45, 2 December 2010 (UTC)

I've made way more progress.. now im making headway on re-making the install sets...

from my notes:
<pre>

export DESTDIR=/tmp

find ./ -name 'obj' -exec rm {} \;

make obj
make
make install

etc
---
make distribution

</pre>

I figure I'll leave the tgz's on a filesystem, boot with a floppy, rm -rf most of the file system, unpack, configure and go.

[[User:Neozeed|neozeed]] 18:34, 5 December 2010 (PST)

Talk:386BSD

2013-04-03T10:43:17Z

Dugo:

Installing 386BSD on BOCHS

2013-04-03T10:41:29Z

Dugo: /* Get, patch, configure and compile Bochs */ Note about newer bochs versions

This is the procedure that was used to install [[386 BSD]] onto a patched version of the Bochs IA-32 emulator. This is based on ancient FAQs and trial & error. It is assumed you use a modern Linux with a kernel that features the ip_tables packet filter and TUN/TAP as host OS. If you want to use a different platform you can still follow the tutorial as a guideline but you are on your own figuring out how to get the emulator networked. A good starting point is http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html#AEN1831

Special attention has been given to the ability to run the emulator in a terminal and in the background.

Watch out for leading spaces if you copy/paste anything from the boxes below, they tend to break here-documents.

== Requirements ==

You will need the following to get a 386BSD system patched and installed:

*A modern Linux system with iptables
*A working copy of gunzip
*An http/ftp client like wget
*An acceptable C compiler like gcc to compile Bochs
*The curses/ncurses library for Bochs to simulate a monitor in a terminal
*An ftp server for the distribution files

On a stock Basic Fedora Core 8 box you have these in no time with
<pre>
yum -y install wget
yum -y install gcc
yum -y install gcc-c++
yum -y install ncurses-devel
yum -y install vsftpd
</pre>

We will get to this later in the tutorial, but for those attempting to install on a different platform or those using this tutorial as a guide, you also need:

*The Bochs 2.4.2 sources
*A patched pic.cc
*The 386BSD distribution and patchkits

 You can download the Bochs sources from sourceforge
*http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz

 A patched pic.cc can be found at
*http://www.xs4all.nl/~dugo/pic.cc

 The 386BSD 0.1 distribution and patchkits can be found at
*ftp://minnie.tuhs.org/BSD/
*http://www.oldlinux.org/Linux.old/distributions/386BSD/

== Preparing for installation ==

=== Get, patch, configure and compile Bochs ===

The Tiny 386BSD boot floppy does something odd. It writes 0x02 to port 20h of the emulated PIC. This causes Bochs to panic. The patch enables Bochs to continue in CLI mode. The available windows binary for Bochs comes up with a msgbox. The [http://bochs.svn.sourceforge.net/viewvc/bochs/trunk/bochs/iodev/pic.cc?r1=9609&r2=9959 patch] is included in more recent versions of Bochs.

<pre>
cd /usr/local/src
wget http://downloads.sourceforge.net/project/bochs/bochs/2.4.2/bochs-2.4.2.tar.gz
gunzip -c bochs-2.4.2.tar.gz |tar -xvf -
wget http://www.xs4all.nl/~dugo/pic.cc
mv -f pic.cc ./bochs-2.4.2/iodev/pic.cc
cd bochs-2.4.2
./configure --enable-cpu-level=3 \
--enable-ne2000 \
--with-term \
--with-nogui \
--enable-all-optimizations \
--enable-docbook=no
make && make install
</pre>

=== Get and serve the 386BSD distribution and patches ===

During installation the 386BSD distribution files and patches can be fetched with ftp. To facilitate this set up an anon ftpd that serves up the files. It should be possible to obtain these directly from minnie during install, but there are two problems. From the looks of it Warren Toomey never intended minnie to be a 386BSD install server. There is also a catch 22 in using the famous patchkits. Stock 386BSD 0.1 comes without gzip, the patches are gzipped, so here's your chance to get around that.

<pre>
echo listen=YES >> /etc/vsftpd/vsftpd.conf
vsftpd
cd /var/ftp
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-0.1/
wget -r -np ftp://minnie.tuhs.org/BSD/386bsd-patchkits/
mv minnie.tuhs.org/BSD ./
rmdir ./minnie.tuhs.org
cd /var/ftp/BSD/386bsd-patchkits
gunzip *gz
</pre>

=== Prepare the host for networking Bochs ===

To make Bochs' ne2k work without a spare NIC in your host you need to set up tunneling.

<pre>
echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
depmod -a
ln -s /dev/net/tun /dev/net/tun0
</pre>

Make a tunconfig script for bochs to fire off when the ne2k comes up. In this example 192.168.1.1 becomes the gw and you can pick an ip in 192.168.1.0/24 for the guest later.

<pre>
# set up the bsd dir w/ tunconfig
cd; mkdir bsd; cd bsd
printf '#!/bin/bash\n/sbin/ifconfig ${1##/*/} 192.168.1.1\n' >tunconfig
cat >>tunconfig <<__EOF
# carnival, put your masks on and go
/sbin/iptables -D POSTROUTING -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -j MASQUERADE >& /dev/null
/sbin/iptables -t nat -s 192.168.1.0/24 -d ! 192.168.1.0/24 -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
__EOF
chmod +x tunconfig
</pre>

=== Configure Bochs ===

The 386BSD installation fails on a box with a lot of mem, hence the `megs: 8' stanza in the Bochs configuration.

<pre>
cat >bochsrc <<__EOF
config_interface: textconfig
display_library: term
romimage: file=/usr/local/share/bochs/BIOS-bochs-legacy
cpu: count=1, ips=80000000, reset_on_triple_fault=0
megs: 8
vgaromimage: file=/usr/local/share/bochs/VGABIOS-lgpl-latest
vga: extension=none
floppya: 1_44=boot.img, status=inserted
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1024, heads=16, spt=63, translation=none, model=generic
boot: disk, floppy
floppy_bootsig_check: disabled=0
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 400000
keyboard_serial_delay: 250
keyboard_paste_delay: 1000000
mouse: enabled=0
private_colormap: enabled=0
keyboard_mapping: enabled=0, map=
i440fxsupport: enabled=0
ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun0, script=./tunconfig
com1: enabled=0
__EOF
</pre>

=== Create Tiny 386BSD floppy ===

Prepare the 386BSD boot floppy to work on our emulated box that has a fancy 1.44MB floppy drive. The original floppy was intended for 1.2MB floppys, but who wants to be caught dead using these nowadays?

<pre>
(cat /var/ftp/BSD/386bsd-0.1/bootable/dist.fs;dd if=/dev/zero bs=1 count=245760)>boot.img
</pre>

=== Create a disk image ===

Make a disk that has the same geometry as in the configuration file, in this case 1024 cylinders, 16 heads and 63 sectors per track. This gets you about 500 megabytes, go larger and you get yourself in heaps of trouble.

<pre>
printf "hd\nflat\n504\ndisk.img\n" |bximage
</pre>

== First boot, Tiny 386BSD ==

=== Start up Bochs ===

You should now be ready to fire up bochs in your terminal and start your journey back in time.

<pre>
bochs -q -f bochsrc
</pre>

You should get the following output:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
Plex86/Bochs VGABios 0.6c 08 Apr 2009 
This VGA/VBE Bios is released under the GNU LGPL 
 
Please visit : <nowiki>
 . http://bochs.sourceforge.net
</nowiki>
 
<nowiki>
 . http://www.nongnu.org/vgabios
</nowiki>
 

NO Bochs VBE Support available! 
 
Bochs BIOS - build: 09/28/09 
$Revision: 1.235 $ $Date: 2009/09/28 16:36:02 $ 
Options: apmbios pcibios eltorito 
 
ata0 master: generic ATA-6 Hard-Disk ( 504 MBytes) 
 
Press F12 for boot menu. 
 
Booting from Hard Disk... 
Boot failed: not a bootable disk 
 
Booting from Floppy... 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
changing root device to fd0a 
 
warning: no swap space present (yet) 
386BSD Distribution Installation Floppy (Tiny 386BSD) Release 0.1 
 
Please read the installation notes (type 'zmore INSTALL.NOTES') 
and registration information (type 'more REGISTRATION') before use. 
To install on hard disk drive, type 'install'. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

=== Format drive and install the distribution utilities ===

At the prompt give:

<pre>
(echo y; echo y)|install
</pre>

This will cause the installer to format the entire drive as it sees fit and install the distribution utilities on it. When the installer is finished Tiny 386BSD and Bochs will go down gracelessly.

== Second boot, Base System ==

=== Finish the installation.

==== Restart Bochs ====

Give another:
<pre>
bochs -q -f bochsrc
</pre>
..to boot the base system. After it finds the devices it will greet you with the following:

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:9px"| 
386BSD Base System Release 0.1 
 
Congratulations, you've got 386BSD on the hard disk! 
Please read the file REGISTRATION (e.g. type 'more REGISTRATION') 
to discover how to become a part of the 386BSD user group. 
 
To finish the installation, load the remaining distribution files into /tmp 
and type 'extract' . To load the files from DOS floppies, type 'mread a:*.* /tmp. 
' 
 
If you should wish to uninstall 386BSD, delete the partition by using the 
 DOS 5 FDISK program. If installed on the entire drive, use the FDISK/MBR 
 to remove the 386BSD bootstrap from the drive. 
 
erase ^?, werase ^H, kill ^U, intr ^C 
<nowiki>
# </nowiki>|| style="background:#000000;"|  
|}

==== Write an installer ====

The installed 386BSD kernel keeps kprinting `startartstartart' to your screen once network is up and running. This can get on your nerves, to work around this you can write an installer in a .netrc macro.

Change the ips below, 10.0.0.1 to where your ftpd lives, 192.168.1.1 to your gw and 192.168.1.2 to the ip you want to give the guest. Change odin into the name you want to give the guest.

<pre>
echo "machine 10.0.0.1" >.netrc
echo "login ftp" >>.netrc
echo "password news@EU.net" >>.netrc
echo "macdef init" >>.netrc
echo "#" >>.netrc
echo "pasv" >>.netrc
echo "prompt" >>.netrc
echo "bin" >>.netrc
echo "lcd /tmp" >>.netrc
echo "cd BSD/386bsd-0.1/bindist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../etcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../srcdist/" >>.netrc
echo "mget *" >>.netrc
echo "cd ../../386bsd-patchkits" >>.netrc
echo "mget *tar" >>.netrc
echo "!echo odin |extract bin01" >>.netrc
echo "!csh -c \"limit openfiles 512; extract src01 ; extract etc01 ; tar -cf /dist.tar /tmp/ ; cp pk023.tar /pk023.tar ; cp pk023024.tar /pk023024.tar ; sync ; sync ; sync ; /sbin/shutdown -r now\"" >>.netrc
echo "quit" >>.netrc
echo "#newl" >>.netrc
echo "" >>.netrc
chmod 400 .netrc
</pre>

==== Configure the network ====

Watch out for the startarts.

<pre>
ifconfig ne0 192.168.1.2 netmask 255.255.255.0 up
route add default 192.168.1.1
</pre>

==== Start the installation ====

Extract will complain with:

<pre>
/tmp/install.src01: Can't open /tmp/install.src01
extract: Cannot execute installation script of distribution, failed
</pre>

according to an ancient FAQ this is a joke from Jolitz. I don't get it.

Extract (or cat) also opens more files than the base sh can handle in case you were wondering about the use of csh.

<pre>
ftp 10.0.0.1
</pre>

When the macro is finished Bochs will go down gracelessly.

== Third boot, fsck ==

When you restart Bochs again with:

<pre>
bochs -q -f bochsrc
</pre>

386BSD will boot, fsck the disk and shut down again. Don't panic.

== Fourth boot, multiuser mode ==

=== Restart Bochs ===

After another
<pre>
bochs -q -f bochsrc
</pre>
you boot into multisuser mode.

{|
|-
| style="border:1px solid #000000; padding:1em; margin:auto; background:#000000;line-height:3px"| 
386BSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] 
Copyright (c) 1989,1990,1991,1992 William F. Jolitz. All rights reserved. 
Based in part on work by the 386BSD User Community and the 
BSD Networking Software, Release 2 by UCB EECS Department. 
pc0<color> at 0x60 irq 1 on isa 
wd0 <generic> at 0x1f0 irq 14 on isa 
fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa 
ne0 ethernet address fe:fd:00:00:00:01 at 0x300 irq 9 on isa 
npx0 at 0xf0 irq 13 on isa 
Automatic reboot in progress... 
/dev/rwd0a: 13409 files, 240517 used, 253130 free (674 frags, 31557 blocks, 0.1% 
 fragmentation)                                                                 
starting network                                                                 
starting system logger.                                                         
checking for core dump...                                                       
preserving editor files                                                         
clearing /tmp                                                                   
standard daemons: update crond.                                                 
starting network daemons: routed printer sendmail inetd.                         
starting local daemons:.                                                         
Wed Apr  8 13:16:44 PST 1970                                                     
                                                                                 

   386BSD (odin) (console) 
 
login: 
|| style="background:#000000;"|  
|}
 
386BSD 0.1 is installed now. You are at the point where Bill and Lynne Jolitz said "Cut the Tape" on 14th of July 1992. 386BSD 0.2 never happened. Now that you have 386BSD installed you can take the opportunity to travel forward in time to the birth of modern BSD. In 1992 and 1993 people released patch kits for 386BSD. In early 1993 David Greenman proposed a new operating system based on the patchkits with a new name: "FreeBSD." These steps will bring 386BSD up to the point where maintaining the patchkits became rather cumbersome.

For more on this part of history read:

*http://www.freebsdworld.gr/freebsd/bsd-family-tree.html
*http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/history.html

There were quite some patches. The shortest and most available route is installing the official unofficial patch kits. Rodney Grimes announced patch kit 0.2.3 in April 1993 and the last one 0.2.4 was announced in June 1993.

=== Apply the first patchkit ===

Login as root, no password, and install the first of the two patchkits.

<pre>
exec sh
cd /
tar -xvf pk023.tar
mv patch dist
cd dist/bin
./mkpatchdirs
(echo y; echo; echo; echo IALL; echo y ; echo ; echo q)|./patches
./afterinstall.sh
</pre>

=== Recompile the kernel ===

As instructed by afterinstall, recompile the kernel. For Bochs the GENERICISA will do for now. There is something to be said for adjusting the kernel configuration, but this is left as an exercise better done later on.

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

== Fifth boot, GENERICISA ==

=== Upgrade the virtual machine and restart ===

Now that you have a proper kernel you can upgrade your machine to use some more than the 8 megs we gave it before.

<pre>
sed -e's/megs: 8/megs: 64/' bochsrc >bochsrc64
bochs -q -f bochsrc64
</pre>

=== Buildworld ===

The system is in a bit of an odd state, the sources are patched but most of the binaries are still the same. So put your new memory to good use, log in as root and execute a buildworld. Note that this can take a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Sixth boot, patched and recompiled system ==

=== Apply the second patchkit ===

Login as root, don't use su.

<pre>
exec sh
cd /
tar -xvf pk023024.tar
cd dist/bin
(echo y ; echo ; echo ; echo IALL ; echo y ; echo ; echo q )|./patches
./afterinstall.sh
</pre>

=== Recompile GENERICISA ===

<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
config GENERICISA
cd /sys/compile/GENERICISA
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

and fire up Bochs again

<pre>
bochs -q -f bochsrc64
</pre>

== Seventh boot, almost there ==

=== Buildworld ===

Login as root and perform another buildworld. Like before, this takes a while.

<pre>
exec sh
cd /patch/bin
./buildworld.sh
sync; sync; sync
</pre>

The system is now up to date with the last patch kits released for 386BSD 0.1. This is a good point to save a copy of your image. Except for the hostname it is now in a pristine unconfigured state. What follows are some things you can do with the system and this is a point to rely on in case of a screw up or trying different routes.

Reboot at least once without the f(astboot) option for a long overdue fsck. Put zeros to a file and remove it when the disk is full if you care about image compression.

A BOCHS disk image created by following all of the above steps is available at http://www.xs4all.nl/~dugo/patched_386bsd.gz

== Running 386BSD ==

=== Kernel configuration, rolling your own ===

In bringing up the system the GENERICISA kernel served well and is more than fine if you want to just explore the system. If you want to do some more crazy things, like trying to get modern software compiled or even something more mundane as moving swap space around you will end up rolling your own kernel. This serves as an example on how to do just that. More specific configurations later when they are on topic. For now make it fit the current hardware and software configuration. More in depth information about config(8) at http://docs.freebsd.org/44doc/smm/02.config/paper.pdf

As usual do
<pre>
rm -r /sys/compile/*
cd /sys/i386/conf
</pre>

Now copy the GENERICISA configuration, give it a fitting name, eg. BOCHS, and dive into it with your favorite editor.

<pre>
grep -v "^#" GENERICISA > BOCHS
vi BOCHS
</pre>

<pre>

machine "i386"
cpu "i386"
## Private ident, shows up in eg. motd.
#ident GENERICISA
ident BOCHS
## Zone info, leap seconds and all are ancient.
## Living in a 90s Berkeley time zone will do for now.
timezone 8 dst
## We can handle a lot more in our emulator, let's double up.
#maxusers 10
maxusers 20
options INET #InterNETworking

## No CD configured yet.
#options ISOFS #ISO File System
## No NFS configured yet.
#options NFS #Network File System
options "COMPAT_43" #Compatible with BSD 4.3
## No 4.2BSD boxen around at the moment.
#options "TCP_COMPAT_42" #TCP/IP compatible with 4.2
## No X installed yet.
#options XSERVER #Xserver
#options UCONSOLE #X Console support

## No SCSI configured in bochs yet.
#config "386bsd" root on wd0 swap on wd0 and sd0
config "386bsd" root on wd0 swap on wd0

controller isa0

controller fd0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fd0 drive 0
## One floppy is enough, second one is a bit broken anyway.
#disk fd1 at fd0 drive 1

controller wd0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wd0 drive 0
## About 180 megabyte left, keep the slot for upgrade.
disk wd1 at wd0 drive 1

## Lot of things not in Bochs, not turned on or rather useless.
#controller ahb0 at isa? bio irq 11 vector ahbintr
#controller aha0 at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller scbus0

#device sd0
#device sd1
#device sd2
#device sd3

#device st0
#device st1
#device st2
#device st3

#device cd0
#device cd1

## Not set up for headless operation yet, screen and keyboard yes, com no.
device pc0 at isa? port "IO_KBD" tty irq 1 vector pcrint
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr

#device com0 at isa? port "IO_COM1" tty irq 4 vector comintr
#device com1 at isa? port "IO_COM2" tty irq 3 vector comintr
#device com2 at isa? port "IO_COM3" tty irq 5 vector comintr
#device com3 at isa? port "IO_COM4" tty irq 9 vector comintr

#device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr
#device lpa0 at isa? port "IO_LPT1" tty
#device lpa1 at isa? port "IO_LPT2" tty

## Network cards, Bochs only knows ne2k and we only have one configured.
#device we0 at isa? port 0x280 net irq 9 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x300 net irq 9 vector neintr
#device ec0 at isa? port 0x250 net irq 9 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device loop
pseudo-device ether
pseudo-device log
## No Slip and PPP for now.
#pseudo-device sl 2
##You run out of these fast when running screen.
#pseudo-device pty 4
pseudo-device pty 16
## Just in case 386BSD wants to say something.
pseudo-device speaker

pseudo-device swappager
pseudo-device vnodepager
pseudo-device devpager
#EOF

</pre>

Now bump the version and give it a shot. MAKEDEV is probably not needed.

<pre>
config BOCHS
cd /sys/compile/BOCHS
make newvers
make depend
make
mv /386bsd /386bsd.old
cp 386bsd /386bsd
sync; sync; sync
shutdown -rf now
</pre>

You should see the bumped minor version number, new ident and compile time..

<pre>
[0.1.1 (BOCHS) 04/29/10 05:54]
</pre>

.. and some moaning about the missing second drive..

<pre>
wd0 0:<generic> 1:<wdgetctlr failed, assuming OK> at 0x1f0 irq 14 on isa
</pre>

If you look in / you notice your kernel got a lot smaller and dropped from around 500k to around 350k.

== TODO ==

* Guest network config
* Disklabeling and adding swap space
* Tweaks to get big things to compile (limits, DFLDSIZ & MAXDSIZ / bash as sh )
* Add some date(1) commands to the tutorial to prevent files going epoch

[[Category:Tutorials]]

User:Dugo/My sandbox

2013-01-12T15:49:33Z

Dugo: /* Reconstructing the last know fuzzball disk */

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
svn co https://dosemu.svn.sourceforge.net/svnroot/dosemu/trunk dosemu
cd dosemu
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tg* dosemu-freedos-bin.tgz
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.
A ready made image can be fetched from http://www.xs4all.nl/~dugo/fuzzball.img.bz2

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

User:Dugo/My sandbox

2013-01-12T15:34:33Z

Dugo: /* Get the tools and archive in place */

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
svn co https://dosemu.svn.sourceforge.net/svnroot/dosemu/trunk dosemu
cd dosemu
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tg* dosemu-freedos-bin.tgz
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

RT-11

2012-06-11T12:33:11Z

Dugo: link to install tutorial

RT-11 was an OS for the PDP-11. Overall it has a very [[OS/8]] feel to it.

== notes ==

The filesystem is like that of OS/8 in that files are stored contiguously on the disk. If a new file does not fit in a 'hole' left by an old deleted file, the files on the disk must be moved together to create a larger area of free space.
http://www.vaxdungeon.com/

INITIALIZE (format floppy)

=== Device names ===
(''n'' is the numerical designation of the drive unit)
*DL''n'': RL01 disk cartridge
*DM''n'': RK06 disk cartridge
*DP''n'': RP02 or RP03 disk
*DS''n'': RJS03/4 disk
*DT''n'': TC11 DECtape
*DX''n'': RX01 diskette
*MM''n'': TU16 magtape
*MT''n'': TU10 or TS03 magtape
*RF''n'': RF11 fixed head disk drive
*RK''n'': RK05 disk cartridge
*DD''n'': TU58 DECtape II

*DK''n'': Logical device, user drive
*SY''n'': Logical device, disk ''n'' on the boot controller

dungeon instructions & image.
http://www.geocities.com/capecanaveral/5517/pdp11.htm
console floppies http://www.headcrashers.org/comp/rx01/

== Commands ==
These are a few commands that I've managed to work out, in no particular order.

=== COPY command ===
The copy command is a little weird in how wildcards work.
<pre>
copy dx0:*.* *.*
</pre>
Is the best way to copy the disk files into the working disk.....

=== DIR command ===
Just like MS-DOS
<pre>
.DIR

SWAP .SYS 25 01-Feb-82 RT11BL.SYS 65 01-Feb-82
RT11SJ.SYS 67 01-Feb-82 RT11FB.SYS 80 01-Feb-82
TT .SYS 2 01-Feb-82 DT .SYS 3 01-Feb-82
DP .SYS 3 01-Feb-82 DX .SYS 3 01-Feb-82
DY .SYS 4 01-Feb-82 RF .SYS 3 01-Feb-82
RK .SYS 3 01-Feb-82 DL .SYS 4 01-Feb-82
DM .SYS 5 01-Feb-82 DS .SYS 3 01-Feb-82
DD .SYS 5 01-Feb-82 MT .SYS 9 01-Feb-82
MM .SYS 9 01-Feb-82 MS .SYS 10 01-Feb-82
LP .SYS 2 01-Feb-82 LS .SYS 2 01-Feb-82
CR .SYS 3 01-Feb-82 NL .SYS 2 01-Feb-82
PC .SYS 2 01-Feb-82 PD .SYS 3 01-Feb-82
CT .SYS 6 01-Feb-82 BA .SYS 7 01-Feb-82
PIP .SAV 23 01-Feb-82 DUP .SAV 41 01-Feb-82
DIR .SAV 17 01-Feb-82 FORMAT.SAV 19 01-Feb-82
SLP .SAV 9 01-Feb-82 SIPP .SAV 20 01-Feb-82
STARTS.COM 1 01-Feb-82 STARTF.COM 1 01-Feb-82
V4USER.TXT 1 01-Feb-82 CREF .SAV 6 01-Feb-82
DUMP .SAV 8 01-Feb-82 MBOT16.BOT 1 01-Feb-82
RESORC.SAV 15 01-Feb-82 SYSMAC.SML 42 01-Feb-82
EDIT .SAV 19 01-Feb-82 KED .SAV 60 01-Feb-82
K52 .SAV 55 01-Feb-82 TECO .SAV 50 01-Feb-82
MACRO .SAV 51 01-Feb-82 MAC8K .SAV 56 01-Feb-82
LINK .SAV 41 01-Feb-82 LIBR .SAV 22 01-Feb-82
FILEX .SAV 18 01-Feb-82 SRCCOM.SAV 13 01-Feb-82
BINCOM.SAV 10 01-Feb-82 MTHD .SYS 4 01-Feb-82
MMHD .SYS 4 01-Feb-82 MSHD .SYS 5 01-Feb-82
PATCH .SAV 10 01-Feb-82 PAT .SAV 8 01-Feb-82
HELP .SAV 107 01-Feb-82 HELP .EXE 7 01-Feb-82
HELP .MLB 98 01-Feb-82 ERROUT.SAV 17 01-Feb-82
SYSGEN.SAV 39 01-Feb-82 SYSGEN.CND 134 01-Feb-82
SYSTBL.CND 23 01-Feb-82 DSAVE .DAT 10 -BAD-
BATCH .SAV 26 01-Feb-82 QUEMAN.SAV 13 01-Feb-82
QUEUE .REL 14 01-Feb-82 SYSLIB.OBJ 47 01-Feb-82
MDUP .SAV 18 01-Feb-82 MDUP .MM 48 01-Feb-82
MDUP .MT 48 01-Feb-82 MDUP .MS 48 01-Feb-82
MBOOT .BOT 1 01-Feb-82 MSBOOT.BOT 3 01-Feb-82
DEMOF1.FOR 2 01-Feb-82 DEMOED.TXT 1 01-Feb-82
README.TXT 36 01-Feb-82 VT52 .TEC 5 01-Feb-82
VEG .TEC 4 01-Feb-82 EDIT .TEC 1 01-Feb-82
INSERT.TEC 2 01-Feb-82 LOCAL .TEC 3 01-Feb-82
SORT .TEC 3 01-Feb-82 VTEDIT.TEC 32 01-Feb-82
TECO .TC 23 01-Feb-82 SEARCH.TEC 3 01-Feb-82
SQU .TEC 13 01-Feb-82 TYPE .TEC 12 01-Feb-82
TECO .INI 15 01-Feb-82 ODT .OBJ 9 01-Feb-82
VDT .OBJ 9 01-Feb-82 VTHDLR.OBJ 9 01-Feb-82
PLOT55.OBJ 3 01-Feb-82 TEST55.FOR 5 01-Feb-82
GETSTR.FOR 2 01-Feb-82 PUTSTR.FOR 2 01-Feb-82
DINDX .DAT 20 -BAD- DUNGEO.SAV 216 -BAD-
SPEED .SAV 4 01-Feb-82 SYCND .BL 3 01-Feb-82
SYSTBL.BL 4 01-Feb-82 SYCND .DIS 5 01-Feb-82
SYCND .HD 5 01-Feb-82 SYSTBL.DIS 4 01-Feb-82
RTBL .MAP 16 01-Feb-82 RTSJ .MAP 16 01-Feb-82
RTFB .MAP 23 01-Feb-82 DISMT1.COM 9 01-Feb-82
DISMT2.COM 8 01-Feb-82 DTEXT .DAT 383 -BAD-
110 Files, 2571 Blocks
2191 Free blocks
</pre>

=== type command ===
The type command will show the contents of a file, just like MS-DOS.
<pre>
.TYPE STARTS.COM
D 56=5015
TYPE V4USER.TXT
D 56=0
</pre>

=== RUN command ===
Dungeon for example is executed with RUN. I think you have to run .sav files.
<pre>
.RUN DUNGEO
Welcome to Dungeon. This version created 10-AUG-78.
You are in an open field west of a big white house with a boarded
front door.
There is a small mailbox here.
>
</pre>

=== @ command ===
COM files are like batch scripts, and are executed with the @ infront of them.
<pre>
.@STARTS.COM

.D 56=5015

.TYPE V4USER.TXT
Welcome to RT-11 Version 4. RT-11 V04 provides new hardware support
and some major enhancements over Version 3B.

Please use the HELP command; it describes the new options in many
of the utilities.

If you are using a terminal that requires fill characters,
modify location 56 with a Deposit command before proceeding with
system installation. LA36 DECwriter II and VT52 DECscope terminals
do NOT require such modification.
</pre>

=== SQUEEZE command ===
Disks will need to be 'defraged' or compacted with this command. In some version it'll just be SQU.
<pre>
.SQU
Device? DK0:
RK0:/Squeeze; Are you sure? Y
</pre>

=== SHOW command ===
This is a very usefull command to show some info about the OS.
<pre>
.SHOW
TT
RK (Resident)
RK0 = SY , DK
BA
PC
NL
LP
MS
MT
DM
DL
DX
DP
4 free slots
</pre>

show configuration

== Tutorials ==
You may find the following of interest:
*[[Installing RT-11 5.3 on SIMH]]
*[[Installing FORTRAN v2 on RT-11]]
*[http://www.skrenta.com/pdpbook.txt THE PDP-11 HOW-TO BOOK]

[[Category:Operating Systems]]
{{stub}}

Installing RT-11 5.3 on SIMH

2012-06-10T22:21:29Z

Dugo: add category

The installation manuals for RT-11 on bitsavers can be a bit scary and longwinding, but installing RT-11 can be done quickly in emulation nowadays.

== Pre install ==

* Get simh working (out of scope)
* Get an empty RL02 disk image where your installation will live.
<pre>
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
</pre>
* Get the Mentec software kit distributed as RL02 image
<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
</pre>
* To get text out of your installation without having to set up KERMIT provide an entry point for simh to print to
<pre>
touch lpt.txt
</pre>
* Configure a small PDP-11 with 2 disks and a line printer
<pre>
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF
</pre>

In case something goes wrong beyond this point you should be able to restart quickly with
<pre>
cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk
</pre>

== Installation ==

With a `pdp11 run.ini' you boot the installation media. If you follow the installation log below you end up with a freshly installed RT-11 in rl0.dsk.
<pre>

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

You can play around if you want now. There is no sync or shutdown in RT-11, just drop out of the emulator w/ ctrl-e when you are done.

== Post install ==

Configure simh to run your installation..

<pre>
cat >run.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl0
quit
__EOF
</pre>

..and run it w/ `pdp11 run.ini'

[[Category:SIMH Tutorials]]

Installing RT-11 5.3 on SIMH

2012-06-10T22:05:05Z

Dugo: Basic install of rt-11

User:Dugo/My sandbox

2012-06-10T19:44:00Z

Dugo: rebuilding modules

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
wget http://prdownloads.sourceforge.net/dosemu/dosemu-1.4.0.tgz?download
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tgz dosemu-freedos-bin.tgz
gunzip -c dosemu-1.4.0.tgz |tar -xvf -
cd dosemu-1.4.0
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

<pre>
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
</pre>

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

=== Rebuilding the configuration independent modules ===

The configuration independent modules don't need to be rebuild, but it is always fun to compare a modern box running simh with the old LSI-11/73s.

From readme.txt..:
<pre>
You can now mumble @SYSGEN and go read a book. The procedure, which
takes the better part of an hour, will result in a new logical disk FUZZ3.DSK
containing all the goodies.
</pre>

With STARTF.COM left intact the below commands will do the trick.
<pre>
UNPROTECT ARC:FUZZ3.DSK
DEL ARC:FUZZ3.DSK
@SYSGEN
</pre>

On museum (a EUR 200,-- Packard-Hell netbook + 1TB USB drive stuffed in a shoebox) the sysgen takes a mere 85 seconds.

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

User:Dugo/My sandbox

2012-06-09T23:04:41Z

Dugo: /* booting the fuzzball */

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
wget http://prdownloads.sourceforge.net/dosemu/dosemu-1.4.0.tgz?download
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tgz dosemu-freedos-bin.tgz
gunzip -c dosemu-1.4.0.tgz |tar -xvf -
cd dosemu-1.4.0
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.

=== booting the fuzzball ===
First some words of encouragement the esteemed Mills himself..
http://mailman.postel.org/pipermail/internet-history/2009-January.txt

"
The last remaing fuzzball is in my basement. The original PDP11 code yet
spins on a disk here. Someday somebody migh enjoy lighing it up in
simulation.
"
You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

User:Dugo/My sandbox

2012-06-09T11:40:27Z

Dugo: putr stuff, reconstructed backroom fuzzball

= fuzzball notes =

<pre>
** Important Note ***

This fuzzware is distributed only with permission from the Defense Advanced
Research Projects Agency (DARPA) under the condition that it not be
redistributed outside of the receiving organization without prior DARPA
approval. It is provided on an as-is basis only. Users should be cautioned
that only very minimal help is available and that support and maintenance is
not a contractual responsibility of the distributor.
</pre>

I know nothing about RT-11, let alone fuzzball operation, this is going to be fun!

From what I gathered so far, you have to bring up a fuzzball fully configured.

You build the configuration dependent modules. This is not something I'm fast with (yet).
I'm so used to bringing up something quickly and then molding it until it does something cool,
I'm not sure how to attack this yet. Getting handy at EDIT/TECO and rebuilding the resident
system, then bring up something iteratively.. or.. spend some time designing a setup.

For now a bit of both vectors.

A cage with an isolated standalone fuzzball is cruel, the poor critter keeps shouting
`Hello!' and `what time is it' at all interfaces. Archeological findings suggest the critter
is very social and likes swamps. Zoo management is currently looking into acquiring
a dozen fuzzbals so they can keep each other company. The cost for housing these will
be astronomical, but the finance director thinks this can earned back if they can be
trained to do some cool tricks. The PdpWorld Fuzzball Show!

This will require some digging because nobody in their right mind currently runs any
of these beasts and all the trainers of yesteryear are probably in or near retirement.

Digging hard and deep in and around French ftp caves of academic nature yielded a tarball
with loads of goodies. It is still being catalogued, bagged, mirrored and taged, but by the
looks of it is a backup of Mills workstation (udel2.udel.edu?) complete with RT-11 V 5.5
backups and even fuzzball configs from the time the NFSNET backbone critters were converted
to NTP servers.

* NET : 129.140.0.0 : NSFNET-BB :
** San Diego CA -- General Atomics -- San Diego Supercomputer Center, SDSC
** Urbana-Champaign IL -- University of Illinois -- National Center for Supercomputing Applications, NCSA
** Pittsburgh PA -- Carnegie Mellon University -- Pittsburgh Supercomputer Center, PSC
** Ithaca NY -- Cornell University -- Cornell Theory Center, CTC
** Princeton NJ -- Princeton University -- John von Neumann National Supercomputer Center, JvNC
** Boulder CO -- National Center for Atmospheric Research, NCAR

There are 30ish FUZZ entries in a 1987 DoD Internet Host Table, not sure if the NSFNET-BB fuzzballs were listed though.

Here is Mills archive of his du0 system disk..
http://malarky.udel.edu/~dmills/data/du0/

..and the complete archive is here.
http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz

I think the complete archive are dumps of what were 5 partitions on something like an RD54 MSCP disk. I should be able to recreate such a disk w/ PUTR (http://www.dbit.com/pub/putr/), but I dread solutions that require running MS-DOS.

I got that idea by looking at the SET statements in STARTF.COM.

<pre>
SET TT: QUIET
SET USR NOSWAP
SET TT: FORM
SET TT: WIDTH=80
SET TT: TAB
SET TT: SCOPE
ASSIGN SY: DK:
ASSIGN SY: INP:
ASSIGN SY: OUT:
ASSIGN DU1: ARC:
ASSIGN TT: LP:
SET DU0: UNIT=0 PART=0
SET DU1: UNIT=0 PART=1
SET DU2: UNIT=0 PART=2
SET DU3: UNIT=0 PART=3
SET DU4: UNIT=0 PART=4
DATE 1-JAN-92
R SETCLK
SET TT: NOQUIET
R PGWAIT
R BOS6
</pre>

What to set cpu in simh?
what it looked like.. eg this LSI-11
http://www.eecis.udel.edu/~mills/pic/fuzzballb.jpg

1MB mem in a 85/86 era pdp-11

DEQNA UNIBUS, PROTEON Unibus ethernet cards??

from tcp-ip archive:

*BRL used 2 PDP-11/34's and 1 11/23

*the 256Kb of memory on the full up 18 bit version of the PDP-11's is entirely adequate for an IP gateway.

What disks .. 2 RL02s look cool to get RT-11 to boot..
http://hampage.hu/pdp-11/kepek/1123PLUS.JPG

11/23 had what .. 248k?

From:
http://lists.ntp.org/pipermail/hackers/2003-September/000321.html

<pre>
The stuff I have is the Fuzzware for the NSFnet backbone, including all
sources, binaries and scripts. It's on three RT-11 flopette images now
spining on mort. Fuzzballs used the LSI-11/73 with the PDP11/45 memory
segmentation hardware, a real-time clock board and any of several kinds
of disk drives. Getting that stuff to spin in a simulator would be an
interesting exercise.</pre>

and from other places

<pre>
A Backbone node consists of a Digital Equipment Corporation LSI-
11173 system wtth 512K bytes of memory, dual-diskette drive,
Ethernet interface and serial interfaces.
One or two low-speed
serial-asynchronous interfaces are provided, as well as one to three
high-speed serial-synchronous interfaces. All Backbone nodes
include crystal-stabilized clock interfaces,
</pre>

&

<pre>
At the time
the NSF phase-I backbone had six LSI-11 fuzzballs as routers, each
connected to a hardware interface that did retransmissions when
necessary. The backbone was connected at several points to the ARPAnet,
most of which at 56/64 kbps. The fuzzbals were located at the five NSF
supercomputer centers on various college campuses.
</pre>

&

<pre>
..while the NSFNET backfuzz are connected only to each other
via DDCMP serial lines and to Ethernets at each site.
</pre>

<pre>
The NSFNET Backbone fuzzies
use DDCMP links with CRC checking and they do find significant numbers of
errors sometimes on marginal trunks. I would be a little uneasy if the IP
and/or TCP checksums were the only protection. However, I am completely
comfortable without CRC protection on single-user PCs and workstations
and would be even more comfortable if the drat Backfuzz links did NOT use
retransmission (DDCMP interface retransmissions are done in hardware and
cannot be disabled).
</pre>

Also lines in BOS6.COM and DAT6.COM yield a few clues..:

<pre>
! lsi-11/73 (2048k), rx02, mscp, dlv11, dmv11, etc.
</pre>

<pre>
.PARAM DQ0,<DQI,DQO>,27,1600.,270,174440,10000 ;ethernet link
.PARAM DM0,<DMI,DMO>,27,,330,160020,40100 ;dmv11 link
.PARAM DY,DYD,200,1976.,264,177170,0 ;rx03 disk controller (sigma)
.PARAM DU,DUD,200,65535.,154,172150,0 ;mscp disk controller (fuji)
</pre>

== get/compile/strip simh pdp11 ==
check pcap path .. maybe add -lnl .. mkdir BIN
$ gmake USE_NETWORK=1 all

== install rt-11 5.3 ==

<pre>
wget http://simh.trailing-edge.com/kits/rtv53swre.tar.Z
uncompress rtv53swre.tar.Z
cat rtv53swre.tar |tar -xvf -
cp Disks/rtv53_rl.dsk rl1.dsk
wget http://www.dbit.com/pub/pdp11/empty/rl02.dsk.gz
gunzip rl02.dsk.gz
cp rl02.dsk rl0.dsk
touch lpt.txt
cat >inst.ini <<__EOF
set cpu 11/23+ 256K
attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rl0 badblock
boot rl1
quit
__EOF

###restart
###cp Disks/rtv53_rl.dsk rl1.dsk; cp rl02.dsk rl0.dsk

$ pdp11 inst.ini

PDP-11 simulator V3.8-1
Disabling CR
Overwrite last track? [N] y
ZA[c\
Welcome to RT-11 V5.3

You have bootstrapped the RT-11 Distribution Disk. Use this disk to
install your RT-11 system, then store it in a safe place.

RT-11 V5.3 provides an automatic installation procedure which will
back up your distribution disk and build a working system disk which
should be used for your work with RT-11.
This working system disk will only contain the RT-11 operating
system. After the RT-11 installation is complete, follow the
installation instructions packaged with any optional languages or
utility software which you will be using.

Press the "RETURN" key when ready to continue.

You can choose to install RT-11 manually. This procedure is
described in the RT-11 Installation Guide.

If you are a new user of RT-11, DIGITAL highly recommends that you
use the automatic installation procedure.

Do you want to use the automatic installation procedure?
(Type YES or NO and press the "RETURN" key): y

You will be guided through the installation process by a series of
instructions and questions; you have an interactive dialog with the
RT-11 installation program. All you need to do is follow the
instructions carefully. When the instructions ask you to mount a
disk in a specified drive, find the disk with the correct label and
mount it in the drive, as shown in your installation booklet.

Do not remove any disk until specifically instructed to do so.
Once a disk is mounted in a drive, it must remain in the drive
until a message appears asking you to remove the disk.

Press the "RETURN" key when ready to continue.

Please enter today's date in the following format:

DD-MMM-YY
where DD is the day of the month
MMM is the first 3 letters in the name of the month
YY is the last two numbers of the year

For example: September 19, 1984 is 19-SEP-84

Type in the date, then press the "RETURN" key.

16-oct-94

A backup copy of the distribution disk will now be built.
Mount a blank disk in DL0 (Drive 0).
See the Automatic Installation Booklet for mounting instructions.
(Remember that the disk is not mounted until you have pressed the LOAD
button and the READY indicator light is on).

Press the "RETURN" key when you have mounted the disk.

Before a blank disk can be used it must be prepared so that the
software can write data to it. This preparation is called initiali-
zation.

The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying the distribution disk from DL1 (Drive 1) to DL0 (Drive 0).

This may take up to five minutes. Please wait...

Your backup copy of the distribution disk is in DL0 (Drive 0).

Please remove this disk from DL0 and label it
"RT-11 V5.3 BIN RL02 BACKUP".
Refer to Appendix B of your installation booklet for instructions
for dismounting a disk.

Press the "RETURN" key when you have removed the disk.

Your working system disk will now be built automatically. This disk
will contain the RT-11 Operating System.
Select a blank disk and label it: "RT-11 V5.3 BIN RL02 WORKING"
and mount it in DL0 (Drive 0).

Press the "RETURN" key when you have mounted the disk.

The disk you mounted in DL0 (Drive 0) is an original distribution
or backup disk.

The next procedure initializes DL0. As a result, any files
that currently reside on DL0 will be permanently lost. If you
would like to retain any files, EXIT from Automatic Installation
Procedure and copy them to another volume.

Do you want to EXIT from Automatic Installation (Y)? n
The disk in DL0 is now being initialized.

The following procedure should produce informational messages
in the form ?FORMAT-I-Message, or ?DUP-I-Message. No action
is required as a result of these messages. If BAD blocks are
detected, the block number will be provided. This information
should be noted for future reference.

This can take approximately fifteen minutes. Please wait...

?DUP-I-No bad blocks detected DL0:

Now copying RT-11 from DL1 (Drive 1) to DL0 (Drive 0).

This can take approximately two minutes. Please wait...

Your working system disk will now be bootstrapped.

Press the "RETURN" key when ready to continue.

RT-11FB V05.03

.TYPE V5USER.TXT

RT-11 V5.3

Installation of RT-11 Version 5.3 is complete and you are now
executing from the working volume (provided you have used the
automatic installation procedure). DIGITAL recommends you verify
the correct operation of your system's software using the
verification procedure. To do this, enter the command:

IND VERIFY

Note that VERIFY should be performed only after the distri-
bution media have been backed up. This was accomplished as part
of automatic installation on all RL02, RX02, TK50, and RX50
based systems, including the MicroPDP-11 and the Professional
300. If you have not completed automatic installation, you must
perform a manual backup before using VERIFY. Note also, VERIFY
is NOT supported on RX01 diskettes, DECtape I or II, or the
Professional 325.

DIGITAL also recommends you read the file V5NOTE.TXT, which
contains information formalized too late to be included in the
Release Notes. V5NOTE.TXT can be TYPED or PRINTED.

.
</pre>

== get the fuzzware ==

This used to go by mail
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0022.JPG
http://hpwren.ucsd.edu/~hwb/NSFNET/NSFNET_lost+found/RIMG0023.JPG

now we:
<pre>
wget http://www.dbit.com/pub/pdp11/fuzzball/bos.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz1.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz2.dsk.gz
wget http://www.dbit.com/pub/pdp11/fuzzball/fuzz3.dsk.gz
gunzip *dsk.gz
</pre>

and we have DSDD images..

Gee, thanks wizz!

AFAICT DEC didn't make 8" DS floppy drives,
simh doesn't have one for the emulated PDP-11 and
RT-11 V5.3 doesn't like the idea very much either.

Maybe they are not 8" ;)

<pre>
FUZZ1.DSK, FUZZ2.DSK, FUZZ3.DSK, NSF.DSK 5.25" floppy disk disk images
for the Fuzzball operating system and Internet
applications for the PDP11 family of computers. These
are in RT-11 file system format suitable for copying
to double-density, double-side media. The Fuzzball
operating system was used in the NSFnet Phase-1
Backbone during the period 1986-1988 and is probably
of historic interest only.
</pre>

== have a look around ==

Dream up some pdp-11 w/ 4 floppy drives..:

<pre>
set ptr dis
set ptp dis
set lpt dis
set dz DISABLED
set RK dis
set HK dis
set rx dis
set rp dis
set tm dis
set tq dis
set xq dis

set console telnet=50000
set tti 8b
set tto 8b
set cpu 11/23+ 256K
;attach LPT lpt.txt
set rl1 writeenabled
set rl1 rl02
attach rl1 rl1.dsk
set rl0 writeenabled
set rl0 rl02
attach rl0 rl0.dsk
set rq enabled
set rq0 RX33
set rq1 RX33
set rq2 RX33
set rq3 RX33
att rq0 bos.dsk
att rq1 fuzz1.dsk
att rq2 fuzz2.dsk
att rq3 fuzz3.dsk
set rl0 badblock
set rl1 badblock
;set throttle 500K
boot rl0
;boot rl1
;quit
</pre>

I tried an almost textbook rebuild of the configuration-independent modules w/
<pre>
DATE 25-oct-94 ! don't go even near turn of the century
TIME 15:35:35 ! fuzzballs like to know what time it is
ASSIGN DL1: DK:
INITIALIZE/NOQUERY DK: ! trash the rt-11 install files
ASSIGN DK: INP: !input device
ASSIGN DK: OUT: !output device
ASSIGN DK: ARC: !archive device
COPY/DEVICE/NOQUERY DU1: ARC:FUZZ1.DSK/FILE
COPY/DEVICE/NOQUERY DU2: ARC:FUZZ2.DSK/FILE
COPY DU2:SYSGEN.COM DK:
@SYSGEN
</pre>

This breaks somewhere around the compilation of TNLSI and again at LOG.

Unless you change something on the FUZZ1 or FUZZ2 volumes, these
steps will not be necessary, or so the README.TXT on DU2: claims.

I take that to mean you can take the binaries from fuzz3.dsk available here at DU3:

Building the resident system with configuration dependent files is another ballgame.

I'm going to give up building a fuzzball on RT-11 V5.3. All is not lost as the above shows nicely how to bring up RT-11 5.3.

I tried setting up RT-11 V5.5 from the various .DSK files in the complete Mills archive, but that gave me headaches and no booting system.

I'm going to give the PUTR (or maybe KERMIT @ 9600 baud) route a shot now as I do want to have a stylised Phase-1 NSFNET running to tie my other emulation projects together.

== DOSEMU & PUTR route==
Sometimes you have to make a detour to get something running. Funny how often MS-DOS is sitting in a corner shouting... use me!, use me! Well, not this time.

=== Get the tools and archive in place ===

The below commands get you dosemu, freedos, putr and the final fuzzball release.

<pre>
mkdir dos
cd dos
wget http://prdownloads.sourceforge.net/dosemu/dosemu-1.4.0.tgz?download
wget http://prdownloads.sourceforge.net/dosemu/dosemu-freedos-1.0-bin.tgz?download
mv dosemu-freedos-1.0-bin.tgz dosemu-freedos-bin.tgz
gunzip -c dosemu-1.4.0.tgz |tar -xvf -
cd dosemu-1.4.0
./configure
make
make install
cd ..
wget http://www.dbit.com/pub/putr/putr.com
wget http://www.eecis.udel.edu/~mills/resource/fuzzball.tar.gz
gunzip -c fuzzball.tar.gz |tar -xvf -
</pre>

=== Reconstructing the last know fuzzball disk ===
Get in the mood for this desecration ritual.
http://www.eecis.udel.edu/~mills/backroom.html

Now create an indirect command file called PUTR.INI

<pre>
CLS
SET COPY BINARY
SET MORE OFF
FORMAT fuzzball.img /RD54 /RT11
Y
DU
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:0
DU0
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:1
DU1
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:2
DU2
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:3
DU3
Mills
INITIALIZE fuzzball.img /RD54 /RT11 /PARTITION:4
DU4
Mills
MOUNT DU0: fuzzball.img /RD54 /RT11 /PARTITION:0
MOUNT DU1: fuzzball.img /RD54 /RT11 /PARTITION:1
MOUNT DU2: fuzzball.img /RD54 /RT11 /PARTITION:2
MOUNT DU3: fuzzball.img /RD54 /RT11 /PARTITION:3
MOUNT DU4: fuzzball.img /RD54 /RT11 /PARTITION:4
COPY DU0\*.* DU0:
COPY DU1\*.* DU1:
COPY DU2\*.* DU2:
COPY DU3\*.* DU3:
COPY DU4\*.* DU4:
BOOT DU0:
RT11FB
DU
DISMOUNT DU0:
DISMOUNT DU1:
DISMOUNT DU2:
DISMOUNT DU3:
DISMOUNT DU4:
EXIT
</pre>

With the command:

<pre>
dosemu putr.com
</pre>

you fire up PUTR in dosemu. PUTR reads in PUTR.INI, executes the commands and exits.

=== booting the fuzzball ===

You now have a bootable disk image fuzzball.img suitable for simh. The emulator ini will need something like:

<pre>
set rq0 RD54
att rq0 fuzzball.img
boot rq0
</pre>

The BOS6 system is nothing like our emulated PDP-11, so the whole thing comes crashing down, but nothing stops you from hitting ctrl-c twice and start building your own fuzzies now.

<pre>
PDP-11 simulator V3.9-0
Disabling CR

RT-11FB V05.05

.SET TT: QUIET
<nothing received>
?SETCLK-W-Device error

.R PGWAIT
NOTE TO USER: HIT CTRL C TWICE WITHIN 10 SECONDS FOR RT11
.R BOS6

HALT instruction, PC: 010262 (MOV 105754,73246)
Goodbye
</pre>

== deadly quote ==
"Laugh it up, fuzzball." - Han Solo to Chewbacca, "The Empire Strikes Back"

User:Dugo/My sandbox

2012-06-07T14:49:32Z

Dugo: