Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!bigbang.astro.indiana.edu!pitts From: pitts@bigbang.astro.indiana.edu (Jim Pitts) Subject: Re: More *BSD installation grief. Message-ID: <CDx5xB.LMq@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Nntp-Posting-Host: bigbang.astro.indiana.edu Organization: Indiana University Astrophysics, Bloomington, IN References: <280eic$eu4@acsc.com> Date: Sat, 25 Sep 1993 17:00:46 GMT Lines: 53 In article <280eic$eu4@acsc.com> fmayhar@acsc.com (Frank Mayhar) writes: >Well, I decided to fall back to FreeBSD, after my unsuccessful bout with >NetBSD. I grabbed the distribution, built the kc, filesystem, and cpio >floppies, and went for it. Consider yourself lucky. I started out at BSD386, went to NetBSD and THEN wound up with FreeBSD ... I am really sick of moving tar files around. Note: I am happily running FreeBSD now. Serial IO was crucial to my use and none of the others do a very good job at high speeds. FreeBSD has the ppp and sio drivers built in that seem to be GEMS. > >_This_ time, I can't even get as far as I did with NetBSD. The kc floppy >boots and asks for the filesystem floppy, which I provide. It then proceeds >to go through its startup sequence. It finally prints a "ISA strayintr 7" >message, indicates that it's changing the root filesystem to fd0a, and then >hangs forever. This is really wierd. I got the ISA strayinter 7 errors (which I still see), but I think this has something to do with having a line printer in the kernel (at irq 7) with none on the machine. I DID hava a similar problem. I would up using a disk that must have had a bad set of clusters on it. I simply wrote a new set of floppies and it worked great. Note: When I installed FreeBSD I ran into the following problem. FreeBSD will not install itself over exsisting partitions by default. When forced to do so, it started the FreeBSD partition at cluster 1. The machine, once all was installed from the install floppies, would go into a cyclic reboot. The solution: When FreeBSD install asks you for the number of clusters to use, give it ALL and it will start at 0 (this is what I did). I do not know what to do if you want to keep DOS around ... Of course keeping DOS around means that you will NEVER get FreeBSD to work as the free *nix gods will never shine their good fortune on you with DOS on your hard disk. ;) > >Note that I can, and have, booted 386bsd 0.1.2.4 several times during this >process, with no problems whatsoever. Also note that I'm not trying to >use my SCSI devices, although they are found. > I never had any real problems with 386bsd with the exception of the *hitty serial drivers. I don't think you will have any trouble getting your SCSI devices, but you will more than likley have to rebuild your kernel. >I'm about ready to shoot my computer. Sigh. extreme :-( Nooooo ... don't do it. A little patience goes a long way in this business. E-Mail me if you want to maintain a dialogue on this topic. Jim