Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!sdd.hp.com!usc!isi.edu!gremlin!lazarus.nrtc.northrop.com!dec From: dec@lazarus.nrtc.northrop.com (Dwight E. Cass) Newsgroups: comp.unix.bsd Subject: Success with installation of 386BSD 0.1 ... Message-ID: <39669@gremlin.nrtc.northrop.com> Date: 19 Jul 92 16:05:03 GMT Article-I.D.: gremlin.39669 Sender: news@gremlin.nrtc.northrop.com Followup-To: dec@nrtc.northrop.com Organization: Northrop Research & Technology Center, Palos Verdes, CA Lines: 72 Well, its been a long night ... but my little 386 is now quite happyily running 386BSD 0.1, and is it great! Wow! My configuration: 25MHZ 386/DX Clone (Tangent Computers, Inc. - Uses C&T CS8230 Chipset, AMI Bios (1988) and 8Mb memory. Memory at .7 wait states, BIOS and Display shadowing enabled, IO Bus at 12.5 MHZ, No 387 [at least yet], Floppy/Hard driver controller on motherboard.) 1 1.2Mb 5 1/4" floppy 1 1.44Mb 3 1/2" floppy Generic VGA Card (VGA 208e from Headland Technology, Inc.) Generic Multipurpose I/O Card (1 Parallel, 4 Serial, 1 Gameport) Microsoft Bus Mouse Adaptec AHA-1542B with 1 667Mb Micropolis SCSI Drive Running DR DOS 6.0 (If I have to run DOS, at least I don't have to suffer with MS DOS!) Of course, the 5 1/4" floppy is drive 0 - so I transfered all of the 386BSD distribution to 3 1/2" floppies (via my Sun at work), then took them home and made a 5 1/4" Tiny 386BSD floppy. No problem - initially booted fine! Ran the install program - created the 386BSD partition and starting loading. I had seen the warning about the missing ']' on the net during the extract of bin01 - so that was no problem ... when extract complained, I just looked at the script and made sure that the hostname was properly set. (Since I did not find the second file [/etc/install.bin ??] in the MANIFEST - I assumed that it did not need to be run..) However, I next loaded the etc01 distribution (don't ask why - I like to get pain over quickly), and of course, it failed with too many files opened. So - I believed the release notes and started over again -- getting out my Tiny 386BSD disk and rerunning install. This time, install told me that a 386BSD system was already on the disk and asked if I wanted to overwrite it ... other than accepting n for an answer, it was determined to ignore me. So, I had to break out Norton, and manually blow away the partition. Why manually - well, I already have two DOS partitions on the disk ... a primary and an extended. The 386BSD partition looks like an extended partition, as such, DR DOS's fdisk wants all logical drives in the extended partitions deleted before it will delete this partition - ouch. So - back to installation. This time, when I get to the etc01 partition, I am a bit more awake, so I run it from csh (with the open file limit at 256). Works pretty well - but complains at the end that it could not do the final configuration because it could not find the configuration file - I checked the MANIFEST and the file is not there, so I finally decided to ignore the message (but it was bothersome!) Once etc01 was done - source was easy ... and I am now up and running, and quite impressed!!! shutdown -todos still does not work - I wonder if its confused about the partition type that DR DOS uses (or maybe it just needs more work, I am off to look at that first). Next, its X and TeX for me (ouch, I need more disk already! and maybe that EXAbyte is not such a bad investment.) Thanks, Thanks, and more thanks to everyone who put their time, energy, and care into this work - its wonderful. And thanks to Bill and Lynne Jolitz for everything!!! You've done a wonderful job. Well, its time for a few hours of sleep then back to hacking for me. Goodnight all! /dec Dwight E. Cass dec@nrtc.northrop.com | You are in a Automation Sciences Laboratory, Northrop Corporation | twisty maze of One Research Park, Palos Verdes Peninsula, CA 90274 | Sendmail rules, (310) 544-5393 | all obscure...