Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1827 ; Tue, 23 Feb 93 15:00:00 EST Newsgroups: comp.os.386bsd.questions Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!wupost!udel!rochester!rit!isc-newsserver!ritvax.isc.rit.edu!DSF5454 From: dsf5454@ritvax.isc.rit.edu Subject: Re: Folks... Message-ID: <1993Feb21.184512.18193@ultb.isc.rit.edu> Sender: news@ultb.isc.rit.edu (USENET News System) Nntp-Posting-Host: vaxa.isc.rit.edu Reply-To: dsf5454@ritvax.isc.rit.edu Organization: Rochester Institute of Technology References: <1993Feb21.093820.13835@ultb.isc.rit.edu> Date: Sun, 21 Feb 1993 18:45:12 GMT Lines: 58 In article <1993Feb21.093820.13835@ultb.isc.rit.edu>, tjg2946@ritvax.isc.rit.edu writes: > I just got 386bsd dist.fs and fixit.fs files and installed them on >a blank 1.2 (each), and got an error with fixit.fs. I will check it later >but for dist.fs, I got an done message (using rawrite.exe). I backed up >my dos hd to hell and set my 200 (actually 191) mb HD to have 145 for BSD >and the rest for DOS. C: drive is dos and D: drive is BSD. I ran the >program (dist.fs) and got into 386bsd. I then installed it to the empty >space. After a long while, it would finished formating but yet have a >problem transfering files. I think the info said 146.7 mb formatting >high level something then after a while it would show 32, 3034 (?), etc. >showing one line at a time. After that it said transfering BSD to HD (or >something to that effect). After a while after that it would say I/O error >with all files from /dev directory, and a couple of other files from >different directories. HELP!!! > Folks, I was with him last night. I used to work for a small company as an Unix/VMS sysadmin. It was a lot of fun installing the system on the RA90's, RA92's, et al, with a HSC90 and CI controller, etc... But looks like my VMS days are over. Now, I have quite forgotten a lot of the details on manually installing a simple BSD-based Unix system. I left my SysAdmin refs home (and apparently, my brain).. He _did_ do a complete backup of his 200 MB IDE drive,(looks like manufactured by Western Digital), then partitioned the drive into a 45 MB DOS (BOS - Bandaid Operating System. ;-) ), and a 146 MB 386BSD partition, then booted the system off the 1.2 MB high density floppy containing dist.fs, and it came up, recognized all the proper devices with right interrupt numbers and mem addresses, etc... Then, ran install and it looks like it set up the uhh...can't remember what it was called, but allocation info table?... the output from newfs -N /dev/rwd0a (the hard drive) was: (condensed slightly) 286776 sectors in 569 cylinders of 14 tracks, 36 sectors 146.8 MB in 36 cylinder groups (16 c/g, 4.13 MB/g, 960 i/g) Super-block backups (for fsck -b #) at: 32, 8144, 16256, 24368, ..., 64928 73040, ..., 137168, 145280, ..., 210176 218288, ..., 282416 Then looks like it tried to mknod files from the dist.fs to /dev directory, and one or two for /etc, but all failed, saying 'I/O error'. When tried to mount /dev/rwd0a /mnt, mount said: Block device required. I _know_ what this is supposed to mean, but I just can't for the life of me remember it!! Anybody can help me recover from my little 'kernel panic mode interrupt' in my head...? ;-) Please post or send email to either me or tjg2946@ritvax.isc.rit.edu. Many thanks! You know, when I heard that he was going to install BSD Unix on something less than a workstation or a minicomputer, I laughed!! But, seeing that this is a seemingly _real_ implementation of Unix for PC-class computers, I might be sold on this concept. ;-) --Dan (in case my .sig isn't appended, email me at: dsf5454@ritvax.isc.rit.edu)