Installing 386BSD on BOCHS - Revision history

Jnc: Better cat

2023-03-26T21:38:25Z

Better cat

Dugo: elaborate on milestones

2019-04-01T23:32:30Z

elaborate on milestones

Dugo: add link to automated build

2019-04-01T20:00:53Z

add link to automated build

Dugo: add link to 0.x

2019-04-01T19:56:33Z

add link to 0.x

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

2016-07-18T10:59:50Z

‎Create a disk image: for use with new bximage

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

2016-07-18T10:57:22Z

‎Configure Bochs: fix the symlink tun/tun0 issue

Dugo: /* Prepare the host for networking Bochs */ iptables update

2016-07-18T10:56:36Z

‎Prepare the host for networking Bochs: iptables update

Dugo: /* Fourth boot, multiuser mode */ thinly veiled commercial for Reeds book

2016-07-11T23:22:27Z

‎Fourth boot, multiuser mode: thinly veiled commercial for Reeds book

Dugo: /* Start up Bochs */ Manage expectations about speed

2016-07-11T22:08:08Z

‎Start up Bochs: Manage expectations about speed

Dugo: /* Get, patch, configure and compile Bochs */ fix link

2016-07-11T21:44:04Z

‎Get, patch, configure and compile Bochs: fix link

@@ Line 677: / Line 677: @@
 *  Upgrade to NetBSD 0.8 ;)
 *  Upgrade to 0.x https://github.com/386bsd/386bsd/tree/0.1
-[[Category:Tutorials]]

@@ Line 395: / Line 395: @@
 <br>
 BSD 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:
@@ Line 402: / Line 403: @@
 *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:
+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. 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.
+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 ===

@@ Line 522: / Line 522: @@
 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
+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 ==

@@ Line 676: / Line 676: @@
 *  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]]

← Older revision		Revision as of 10:59, 18 July 2016
Line 166:		Line 166:
	</pre>		</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 ==		== First boot, Tiny 386BSD ==

@@ Line 137: / Line 137: @@
 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
+ne2k: ioaddr=0x300, irq=9, mac=fe:fd:00:00:00:01, ethmod=tuntap, ethdev=/dev/net/tun, script=./tunconfig
 com1: enabled=0
 __EOF

@@ Line 88: / Line 88: @@
 echo alias char-major-10-200 tun >>/etc/modprobe.d/modprobe.conf.dist
 depmod -a
 </pre>
@@ Line 96: / Line 95: @@
 # 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 '#!/bin/bash\n/sbin/ifconfig ${1##/*0/} 192.168.1.1\n' >tunconfig
 cat >>tunconfig <<__EOF
 # carnival, put your masks on and go
@@ Line 105: / Line 104: @@
 chmod +x tunconfig
 </pre>
 === Configure Bochs ===

← Older revision		Revision as of 22:08, 11 July 2016
Line 176:		Line 176:
	</pre>		</pre>

−	~~You~~ should get the following output:	+	After a while you should get the following output:

@@ Line 45: / Line 45: @@
 === 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.
+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.