From owner-freebsd-questions Mon Jul 17 10:29:05 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA12067 for questions-outgoing; Mon, 17 Jul 1995 10:29:05 -0700 Received: from condor.physics.montana.edu (condor.physics.montana.edu [153.90.240.211]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA12061 for ; Mon, 17 Jul 1995 10:29:03 -0700 Received: (from handy@localhost) by condor.physics.montana.edu (8.6.11/8.6.9) id LAA00581; Mon, 17 Jul 1995 11:28:58 -0600 Date: Mon, 17 Jul 1995 11:28:57 -0600 (MDT) From: Brian Handy To: freebsd-questions@freebsd.org Subject: Increase swap Q Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@freebsd.org Precedence: bulk Well...I'm still paying for my ignorance when I installed 2.0.5. My swap space is way WAY too small. I have 24 MB of ram, and the disk partitions look like this (240 MB hard drive): Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 22823 12488 8509 59% / /dev/wd0s4e 179342 121801 43193 74% /usr procfs 4 4 0 100% /proc Yep...that's a big 4K for swap. So...after noting that little problem, I then note I'm short on disk space by about 40 MB. It appears I've configured away a large chunk of my disk. The whole disk is (supposed to be) FreeBSD. SO....my question was about to be 'how do I make a larger swapfile', but I have a feeling it's deeper than that. How can I figure out where the rest of my disk went, and any suggestions for how to reclaim it short of rebuilding the system? Furthermore...I'm a little vague on adding swapfiles. Specifically, I have an old e-mail that says to generate the swapfile do something like: dd if=/dev/zero of=/tmp/swapfile ...what's /dev/zero? This is new to me. Anyway, this starts building a file that increases without bound until the disk is full. How can I generate a swapfile of some specific size? I haven't found anything in the mail archives that explained this in the Fisher-Price tone of voice I need to hear. Thanks! Brian Handy