Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucla-cs!admin.cognet.ucla.edu!casey From: casey@admin.cognet.ucla.edu (Casey Leedom) Newsgroups: comp.bugs.2bsd Subject: Re: Trouble with generic 2.10BSD Keywords: 2.10BSD Message-ID: <16093@shemp.CS.UCLA.EDU> Date: 21 Sep 88 04:56:12 GMT References: <2675@usceast.UUCP> Sender: news@CS.UCLA.EDU Reply-To: casey@cs.ucla.edu (Casey Leedom) Distribution: na Organization: none Lines: 34 In article <2675@usceast.UUCP> wilhite@cs.scarolina.edu (Robert Wilhite) writes: > I'm having a bit of trouble getting 2.10 to work on our PDP. Our > system is: > > a PDP 11/44 with 1 meg of memory, > two CDC 9762 disk drives > a TS11 tape drive > two DH11 tty boards > > The story so far: The generic kernel we got from the distribution tape > will boot. (It doesn't recognize our DH11's, tho, so no multi-user.) > We've been thru the "Config & Recompile" loop a number of times, trying to > get the kernel tailored to our system. Some resulted in a non-bootable > system (base segment too large, I think); others resulted in a bootable > system that would "panic" for some reason or another. (All from mistakes > in our configuration file, I'm sure.) The most successful attempt > resulted in a system that would boot and hang. Sorry for the incredible delay in answering. Things have really been piling up here. The generic kernel won't recognize your DH11's because it wasn't compiler with DH11 support. The generic kernels are only intended to be used long enough for you to configure and compile your own kernel. The hanging that you describe sounds like you haven't defined the ROOTDEV, PIPEDEV, SWAPDEV, and/or NSWAP correctly. Check those definitions carefully in your configuration file. The generic kernel's values for these are edited in by the script /GENALLSYS. When you just compile the GENERIC kernel and try to run it you get some random set of values for these. Casey