Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!caen!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] System's not finding/using swap
Message-ID: <1992Oct15.195756.3388@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1992Oct15.045324.14859@news2.cis.umn.edu> <1992Oct15.162400.24424@fcom.cc.utah.edu> <JDOLTER.92Oct15140414@sawtooth.eecs.umich.edu>
Date: Thu, 15 Oct 92 19:57:56 GMT
Lines: 48
In article <JDOLTER.92Oct15140414@sawtooth.eecs.umich.edu> jdolter@eecs.umich.edu (James W. Dolter) writes:
>>>>>> Regarding Re: [386BSD] System's not finding/using swap; terry@cs.weber.edu (A Wizard of Earth C) adds:
>
> .....
>
> terry> The swap has to go at the end of the disk.
> .....
>
>That is not true.... I have both of my configured swap partitions in the
>middle of my disks.
>
>I suggest checking out your kernel config and swap386bsd.c to make sure
>that you have a entry in the swap device table (swdevt)...
The only error I see here is that the default dist.fs/fixit.fs don't have
swap devices configured. It may be possible to recompile a kernel to set
this up without first having it set up in the default location (the end
of the disk). Every time I have tried this, I have run out of memory
and crashed. I suppose that it's posible if you have a large amount
of memory (physical RAM) in your box; but then again, if you're using
ISA drivers, there is a possiblity that your DMA will fail without the
"bounce buffer" patch to insure all DMA I/O occurs below 16Meg.
In either case, you will probably have to have a working kernel build
environment before you tackle this, and if you don't put the swap at the
end of the disk, you may not be able to have a build succeed. This is like
trying to run a BusTek or AHA174x disk without Julian's drivers so you
can install them.
One potential workaroung of the memory problem is to make -n the kernel,
then enter in the compilation lines by hand. This is messy, but it
worked for me. It's much easier to accept the default configuration
from install, or make your own disktab entry and use the fixit.fs
procedure of Chris' in the FAQ.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------