Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!hermes.chpc.utexas.edu!xenon.brooks.af.mil!bsdns.brooks.af.mil!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.questions Subject: Re: 386bsd 0.1 Patchkit 0.2.4 - Problems, Questions Date: 11 Aug 1993 09:27:08 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 62 Message-ID: <24avka$9ne@hrd769.brooks.af.mil> References: <CBIpzw.6BM@csi.compuserve.com> <2497k2$qq2@pdq.coe.montana.edu> NNTP-Posting-Host: hrd769.brooks.af.mil In article <2497k2$qq2@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: }In article <CBIpzw.6BM@csi.compuserve.com>, }M Foley <mfoley@csi.compuserve.com> wrote: } }> How can I get it to finish? Is there a way to restart without having }> to do the whole thing over? } }Make will pick up where it's left off, so you can continue (leave it for }a week or so. :-) ) and it will keep going. } Come on Nate, it shouldn't take a week. Heck, I got through mine in only 5 days. Of course, it was on a 486/33 with a 40Meg swap space, but still. }> I am running a 80386-25 w/8087, 8MB of }> memory and whatever default swap space tiny bsd put on my drive - I }> believe 10000 blocks. I am using a 240MB partition on my 431MB Seagate }> (15530 ?) hard drive. I am not running out of disk space. I did not get }> an error in my afterinstall.OUT. } }the 5 MB swap partition is not adequate for any machine with any version of }386BSD available publically. And the steps on correcting are in the FAQ (which is available by anonymous FTP from hrd769.brooks.af.mil:~/pub/FAQ). } }>4. With the patchkit, I can now access my 2nd hard drive. BUT, I have a }> problem. I create a disklabel using "disklabel -R /dev/rwd1a 41mb" where }> '41mb' is a disklabel format file describing my 43MB Seagate 157A IDE }> drive. I then do "newfs -m 0 wd1" to create a file system - which works }> fine. I mount it, use it, etc. However, when I reboot and try to mount it }> again, I get a "BOGUS BOOT BLOCK" message and have to redo the label and }> recreate the file system all over. Why isn't the label/file system }> information 'sticking'? Any ideas? } }Check to make sure that the d partition has an offset of 0. } There are actually several possibilities here. The FAQ covers these as well (FAQ_02, as I recall). }>5. When I boot, I now get many "strayintr ff" messages on the console. }> Fairly quickly, it says there are too may of these type of error and it }> will stop logging them (I forget the exact wording). What are these? }> should I be worried? } }These are from the lp driver, it may be a bug or bad hardware. (I'm }not sure which one it is) } I have to report that I only get about one now, since I have installed the lpa driver. If gets reported before the system is really 'going', and I never get another after that. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX