Difference between revisions of "386BSD 0.0"

From Computer History Wiki
Jump to: navigation, search
Line 1: Line 1:
 
[[Image:386BSD 0.0.jpg|thumb|200px|right|386BSD 0.0 floppy]]
 
[[Image:386BSD 0.0.jpg|thumb|200px|right|386BSD 0.0 floppy]]
  
So far I just found out that [[386 BSD]] 0.0 runs on VMWare Fusion on [[OS X]] enough to run the floppyI'm running into issues with the hard disk, with constant errors of:
+
386BSD 0.0 ... bareIt is not what you would expect, being spoiled in multiuser systems!
  
<pre>wd0: Format error in bad sector file</pre>
+
As they state:
 +
<pre>
 +
    At  the  moment,  386BSD  comes up single user, and re-
 +
quires manual starting of the system  daemons,  as  well  as
 +
filesystem  checks. In use, one would minimally wish to type
 +
after booting:
 +
 
 +
fsck -p
 +
mount -a
 +
update
 +
/etc/netstart
 +
 
 +
    This will improve in forthcoming  versions  of  386BSD.
 +
Be  aware  that  the  user is running as the super-user, and
 +
care should be taken given the maximum privileges present.
 +
</pre>
  
Which I'm thinking ties back to geometry.
+
that is right, no login, you are just running as root!!!!
  
I'll have to find a way to nicely re-create a Connor disk that has a disktab for 386BSD to make a 'like like' install, which didn't work. I think the only way out will be to make some disks, and boot it on a real pc with a hard disk that I've used to image [[Xenix]] and see if any emulator will load the disk image.
+
== The 0.0 announcement ==
 +
[[386BSD 0.0 announcement]]
  
Another hint from [http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/730282ea5c509e45/52e9db40611b261f?hl=en&ie=UTF-8&q=%22386BSD+0.0%22+ide+label#52e9db40611b261f usenet]
+
== what runs ==
<pre>
+
Well there isn't even a 'ps' command!  Gcc is version 1.39! A 'full' install, binaries and source is 43mb!  this is a super bare bones port!  
h...@pegasus.com (Huy Dinh) writes:
 
>Has anybody gotten the 386BSD 0.0 to boot off a Maxtor LXT213A IDE
 
>harddrive? I've managed to boot off the floppy, create a disktab
 
>entry for the drive, label it, and newfs the a and h partition. I
 
>do get error messages saying that there's a format error in the
 
>bad track table and an occasional extra-interrupt error. However,
 
  
I dont know about the rest, but the bad format track error comes from
+
*Ethernet seems to be only WD 8003 cards, and NE2000 ...  
your disktab entry. If the drive is 1001 cylc (like mine) you have
 
to create a disk tab saying that is is 996 cylc. disktab/mkfs know that
 
they can go 5 cylcs beyond the value in the disktab entry.  So in your case
 
if your drive ONLY has 1001 then disktab/mkfs was trying to format cylcs 1002
 
to 1006 thus producing an error. </pre>
 
  
 +
building a kernel easily causes it to trap!..
  
== The 0.0 announcement ==
+
danger ahead!
[[386BSD 0.0 announcement]]
 

Revision as of 07:57, 7 December 2010

386BSD 0.0 floppy

386BSD 0.0 ... bare. It is not what you would expect, being spoiled in multiuser systems!

As they state:

     At  the  moment,  386BSD  comes up single user, and re-
quires manual starting of the system  daemons,  as  well  as
filesystem  checks. In use, one would minimally wish to type
after booting:

fsck -p
mount -a
update
/etc/netstart

     This will improve in forthcoming  versions  of  386BSD.
Be  aware  that  the  user is running as the super-user, and
care should be taken given the maximum privileges present.

that is right, no login, you are just running as root!!!!

The 0.0 announcement

386BSD 0.0 announcement

what runs

Well there isn't even a 'ps' command! Gcc is version 1.39! A 'full' install, binaries and source is 43mb! this is a super bare bones port!

  • Ethernet seems to be only WD 8003 cards, and NE2000 ...

building a kernel easily causes it to trap!..

danger ahead!