From: Daniel T. Poirot (poirot@aio.jsc.nasa.gov) Subject: Re: 386BSD -- new version soon... Newsgroups: comp.unix.bsd View: Complete Thread (4 articles) | Original Format Date: 1992-03-16 09:07:37 PST In article cgd@agate.berkeley.edu (Chris Demetriou) writes: >This post has had a few sources of input... > >Second: from John Sokol: > >There should be a new version out soon... >Apparently this version wasn't supposed to make it to >this wide an audience -- IF AT ALL POSSIBLE, WAIT >UNTIL EARLY NEXT WEEK TO GET IT -- To whom it may concern: I HATE SPLIT, COMPRESSED TAR FILES! First the whining... I got all the way home Friday with eight 3.5" disks, six from the bin set and two copies of the boot disk. I was only able to read the first disk of the bin set and then I got a disk read error. If we had seperate compressed tar files, I could have tried the rest of the disks and then fixed disk 1 when I got back to work today. I am going to try that later on my own. And now some observations... I was able to boot up on my 16MHz, 8Mb 386/387 with a 1988 Phoenix 1.10.00 BIOS. I made a disktab entry for a 32Mb Seagate ST238R RLL drive. The comments in the disktab file mention saving 5 cylinders at the end of the disk for bad blocks and overhead. Does this mean set 'nc' to the total number of cylinders and then not use them OR set 'nc' to (total number of cylinders - 5) ? I did the disklabel and newfs and tarred the boot disk to the 'a' partition. When I boot, I get a console error message about a read error in the bad block area. -- Daniel Poirot poirot@aio.jsc.nasa.gov NASA JSC "The mind is a terrible thing." ER3 tel: (713)483-8793 Houston, TX 77058 fax: (713)483-3204 From: Chris Demetriou (cgd@agate.berkeley.edu) Subject: 386BSD -- new version soon... Newsgroups: comp.unix.bsd View this article only Date: 1992-03-13 16:51:49 PST This post has had a few sources of input... From the admin at agate: PLEASE TRY TO WAIT UNTIL AFTER HOURS, OR SOMETHING, to ftp 386bsd from there... Agate really took a pounding this morning -- > 60 load ave, and it's xferred over 1/2 a gig of stuff so far... (and considering that it's a news server, it's already io-bound.) Second: from John Sokol: There should be a new version out soon... Apparently this version wasn't supposed to make it to this wide an audience -- IF AT ALL POSSIBLE, WAIT UNTIL EARLY NEXT WEEK TO GET IT -- an announcement will undoubtedly be posted here when the new version arrives... Thanks much, Chris cgd@agate.berkeley.edu person-who's-dealing-with-this-on-agate Message 2 in thread From: Daniel T. Poirot (poirot@aio.jsc.nasa.gov) Subject: Re: 386BSD -- new version soon... Newsgroups: comp.unix.bsd View this article only Date: 1992-03-16 09:07:37 PST In article cgd@agate.berkeley.edu (Chris Demetriou) writes: >This post has had a few sources of input... > >Second: from John Sokol: > >There should be a new version out soon... >Apparently this version wasn't supposed to make it to >this wide an audience -- IF AT ALL POSSIBLE, WAIT >UNTIL EARLY NEXT WEEK TO GET IT -- To whom it may concern: I HATE SPLIT, COMPRESSED TAR FILES! First the whining... I got all the way home Friday with eight 3.5" disks, six from the bin set and two copies of the boot disk. I was only able to read the first disk of the bin set and then I got a disk read error. If we had seperate compressed tar files, I could have tried the rest of the disks and then fixed disk 1 when I got back to work today. I am going to try that later on my own. And now some observations... I was able to boot up on my 16MHz, 8Mb 386/387 with a 1988 Phoenix 1.10.00 BIOS. I made a disktab entry for a 32Mb Seagate ST238R RLL drive. The comments in the disktab file mention saving 5 cylinders at the end of the disk for bad blocks and overhead. Does this mean set 'nc' to the total number of cylinders and then not use them OR set 'nc' to (total number of cylinders - 5) ? I did the disklabel and newfs and tarred the boot disk to the 'a' partition. When I boot, I get a console error message about a read error in the bad block area. -- Daniel Poirot poirot@aio.jsc.nasa.gov NASA JSC "The mind is a terrible thing." ER3 tel: (713)483-8793 Houston, TX 77058 fax: (713)483-3204 Message 3 in thread From: Chris Demetriou (cgd@agate.berkeley.edu) Subject: Re: 386BSD -- new version soon... Newsgroups: comp.unix.bsd View this article only Date: 1992-03-16 22:43:27 PST In article <1992Mar16.160203.2068@aio.jsc.nasa.gov> poirot@aio.jsc.nasa.gov (Daniel T. Poirot) writes: > >I HATE SPLIT, COMPRESSED TAR FILES! I agree... unfortunately, that's a *VERY* easy way to distribute things... >First the whining... > >I got all the way home Friday with eight 3.5" disks, six from the bin >set and two copies of the boot disk. I was only able to read the first >disk of the bin set and then I got a disk read error. If we had >seperate compressed tar files, I could have tried the rest of the disks >and then fixed disk 1 when I got back to work today. I am going to try >that later on my own. If you'd read my install notes, you would have know that the "mr" program is borken in some ways... the solution is to do: mr $FTRK $RFD > disk.1  and so on for 2-6, then cat them together, and uncompress and untarr the resulting monolith... >I did the disklabel and newfs and tarred the boot disk to the 'a' >partition. When I boot, I get a console error message about a read >error in the bad block area. The same thing happens for me... the exact message is: "wd0: error in bad-sector file" I believe that this happens because when the UN*X formatter is used, it creates the bad block list in some format, and we didn't use the UN*X formatter on the hard drives (because there isn't one for 386BSD yet...), and so the bad block list is "bad" 8-) Chris cgd@agate.berkeley.edu Message 4 in thread From: Martin Rausche (mnrausch@immd4.informatik.uni-erlangen.de) Subject: Re: 386BSD -- new version soon... Newsgroups: comp.unix.bsd View this article only Date: 1992-03-23 04:59:46 PST cgd@agate.berkeley.edu (Chris Demetriou) writes: >>I did the disklabel and newfs and tarred the boot disk to the 'a' >>partition. When I boot, I get a console error message about a read >>error in the bad block area. >The same thing happens for me... the exact message is: >"wd0: error in bad-sector file" >I believe that this happens because when the UN*X formatter is used, >it creates the bad block list in some format, and we didn't use the UN*X >formatter on the hard drives (because there isn't one for 386BSD >yet...), and so the bad block list is "bad" 8-) Hmmmm, I've got rid of this message by fiddling with the fstab entry. First I had an entry, which didn't fill all tracks -> I got the bad .... message Now my fstab entry fills all tracks perfectly -> Now I don't get any "wd0: ..." messages Don't ask me why :-) Hardware: ETEQ 486/33-256 AMI BIOS 5/5/91 4MB floppy 0 1.44MB floppy 1 1.2MB hd 0 Quantum LPS 240 IDE hd 1 none Soundblaster 1.0 (hey, where is Soundblaster support :-) Martin. --- ------------------------------------------------------------------------------ | Martin Rausche | | EMail: mnrausch@immd4.informatik.uni-erlangen.de | | Trust me, I know what I'm doing -- Sledge Hammer | ------------------------------------------------------------------------------