Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Oct 1995 08:59:01 -0700 (PDT)
From:      bmk@dtr.com
To:        pete@puffin.pelican.com (Pete Carah)
Subject:   Re: Help..  FreeBSD's killing all my processes
Message-ID:  <199510241559.IAA01369@dtr.com>
In-Reply-To: <m0t7lMO-0000ReC@puffin.pelican.com> from "Pete Carah" at Oct 24, 95 08:33:00 am

next in thread | previous in thread | raw e-mail | index | archive | help

> (this is different in various versions of unix now; IRIX 5.x backs all ram
> by swap so you need enough for all running processes.  At least it lets
> you add swap on the fly in ordinary files, which we aren't up to yet.)

That's not true if you have a kernel compiled with:

pseudo-device vn		#Vnode driver (turns a file into a device)

Once that's accomplished, it's a simple as:

root@everest (17) # dd if=/dev/zero of=/dumps/swapfile bs=1m count=8
root@everest (17) # vnconfig /dev/vn0b /dumps/swapfile swap

root@everest (18) # swapinfo
Device      1K-blocks     Used    Avail Capacity  Type
/dev/sd0s1b     98304     7136    91104     7%    Interleaved
/dev/sd1s1b     98304     7076    91164     7%    Interleaved
Total          196480    14212   182268     7%

root@everest (19) # swapon /dev/vn0b

root@everest (20) # swapinfo
Device      1K-blocks     Used    Avail Capacity  Type
/dev/sd0s1b     98304     7136    91104     7%    Interleaved
/dev/sd1s1b     98304     7076    91164     7%    Interleaved
/dev/??          8192        0     8128     0%    Interleaved
Total          204608    14212   190396     7%

Naturally, you'd want to add an entry to /etc/vntab if you wanted the
device to survive the next reboot.

I haven't played with this feature much, so I may be missing a thing or
three.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510241559.IAA01369>