I've assembled some notes from old manuals and other sources
on the formats used for on-disk file systems through the
Seventh Edition:
http://www.cita.utoronto.ca/~norman/old-unix/old-fs.html
Additional notes, comments on style, and whatnot are welcome.
(It may be sensible to send anything in the last two categories
directly to me, rather than to the whole list.)
Hi,
I successfully made SIMH VAX-11/780 emulator run 32V, 3BSD and 4.0BSD.
Details are on my web site (thogh rather tarse):
http://zazie.tom-yam.or.jp/starunix/
Enjoy!
Naoki Hamada
nao(a)tom-yam.or.jp
I was looking at several NetBSD manual pages and saw that some HISTORY
sections had wrong .Bx or BSD reference like:
HISTORY
The xstr command appeared in 3.0BSD.
I looked at a few and saw this was in 4.4BSD manual pages. By the way,
when were these history sections added? (They aren't in 4.2BSD manual
pages. I should look at 4.3 before asking ...)
I didn't see any that refered to original Berkeley UNIX Software Tape
nor 2BSD.
But from looking at the 1BSD and 2BSD, I see:
apropos was in 2bsd
colcrt was in 1bsd but not in 2bsd
even though 2BSD iul, soelim, and ssp manuals referenced it
(why missing from 2BSD?)
colrm was in 1bsd but not in 2bsd
csh was in 2bsd (even 1bsd referenced the upcoming "csh")
ctags was in 2bsd, but as a shell script using ed
expand was in 1bsd and 2bsd
finger was in 2bsd
fmt was in 2bsd
from was in 2bsd
head was in 1bsd and 2bsd
lock was in 2bsd
last was in 1bsd and 2bsd
mkstr was in 1bsd and 2bsd
msgs was in 2bsd
printenv was in 2bsd
soelim was in first BSD and 2BSD
tset was in 1bsd and 2bsd
w was in 2bsd as finger -sf
whatis was in 2bsd
whereis was in 2bsd
xstr was in 2bsd
lastlog file format was in 1bsd and 2bsd (?? maybe different format??)
Any comments on the above?
Or is this simply because "2BSD" is not a operating system release per
se, so "3.0BSD" is correct?
But this makes me wonder if my 2BSD versions are newer than first
2BSD, so really 3BSD is correct for some of this.
I was going to ask a NetBSD list about this to fix these histories, but
decided to consult TUHS instead. Okay to change history to fix history?
:)
I don't know if this is interesting to anyone, but I thought I'd share that
386BSD will install on Bochs (although slowly, and it's prone to crashing),
however once the first patchkit is installed, it'll then run on Qemu!
(0.11.0, it seems the new bios layout of 0.12 is incompatible)
If anyone is interested, here is a link to a hard disk image that I've
prepared for Qemu:
http://vpsland.superglobalmegacorp.com/install/386BSD/bsd386.qcow2.gz
I run it like this:
qemu.exe -L pc-bios -hda bsd386.qcow2 -M isapc -net nic -net user -no-reboot
-m 256
And I can run lynx/irc as a test of the TCP/IP.
At any rate, I figure this kind of brings 386BSD back out of it's grave.
