Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!snorkelwacker.mit.edu!bloom-picayune.mit.edu!boltzmann!ccount From: ccount@boltzmann.mit.edu (Dr. Craig A. Counterman) Newsgroups: comp.unix.bsd Subject: taunted by happy extract command Message-ID: <1992Jul20.213814.10944@athena.mit.edu> Date: 20 Jul 92 21:38:14 GMT Article-I.D.: athena.1992Jul20.213814.10944 Sender: news@athena.mit.edu (News system) Organization: Electronic Materials Research Group, Cambridge Mass. Lines: 59 Nntp-Posting-Host: boltzmann.mit.edu I'm having a problem or two with installation, and have some questions about how to do what I'm going to want to do once I get it working. I've been following 386BSD since March, but not too closely since I had a scsi-only system and 0.1 would be out in another week... First. the dist floppy boots fine, install recognizes my hd OK and takes the space I left on it for BSD, and starts up from the hd OK. But /dev/rwt0 doesnt seem to work (device not found or some such) I didn't try this too hard though. My qic drive is at interrupt 7, which is a bit unusual. It is getting polled on boot though, I think. But the show-stopper is this: During 'extract' of bin01, it crunches away for a while, then panics and reboots. The panic (glimpsed briefly on the third go-round) involved 'panic kmem_malloc kmem_map too small'. Of course, I didn't know what was going on the first two times. I started it going, left the room, and came back in a few minutes to find it giving me a login: prompt. But things weren't quite right, fsck wouldn't run (something about /etc/fstab or disktab being bad), and before long it'd crash complaining about a bad directory entry. So: any clues, offhand? My guess is that I have too much memory for the dist kernal. System: 486-50 clone AMI/OPTI with 20MB memory, 256K cache AHA-1542B scsi, with two 200 meg disks QIC-02 mountain 60meg tape drive Prodesigner IIs Logitech bus mouse (IRQ 5) Serial card with one 16550 1.2 and 1.44 floppies I'm planning on adding a scsi CD-ROM, a soundblaster, and more disk. What, if any, problems are there with this setup? Right now, msdos takes all but 105 meg on the first disk and 170meg on the second. I assume I can use that 170 on the second drive once I get things working in the 105 it currently tries to use. Another question: How can I easily switch from DOS to BSD? I've been using fdisk to change the active partion, but I gather there's a better way. Thanks for any clues, hints, or pointers. Craig ------------------------------------------------------------------------ Dr. Craig Allen Counterman N1LRW ccount@mit.edu 13-4057, MIT, 77 Mass Ave, Cambridge MA 02139 W:(617)-253-3295 Pager:(617)-597-0455