From owner-freebsd-questions Wed Feb 5 22:32:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA29605 for questions-outgoing; Wed, 5 Feb 1997 22:32:33 -0800 (PST) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29564 for ; Wed, 5 Feb 1997 22:32:29 -0800 (PST) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.4/8.8.4) with ESMTP id BAA01806; Thu, 6 Feb 1997 01:32:21 -0500 (EST) Received: from perry3 (vabla-max-135.dynamic.usit.net [206.29.54.136]) by sable.cc.vt.edu (8.8.4/8.8.4) with SMTP id BAA23259; Thu, 6 Feb 1997 01:32:19 -0500 (EST) Message-Id: <3.0.32.19970206013234.0090f980@mail.vt.edu> X-Sender: plucas@mail.vt.edu X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 06 Feb 1997 01:32:36 -0500 To: Softweyr LLC From: Perry Lucas Subject: Re: Pkg Add problems? Cc: questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 06:09 PM 2/5/97 -0700, you wrote: >> I am installing FreeBSD onto a 2.1 gig hard drive all its >> own. I am running into a PKG_Add error that is preventing >> the addition of packages to the system. I get a write >> error, possible corruption of package message. >Given the sizes of your filesystems above, I'd say you're probably >filling /var/tmp. The next time pkg_add pukes on you, try df and see >which filesystem is at or above 108%. Or try setting TMPDIR to >/usr/tmp, which appears to be less likely to run out of room. This is what I get for Debug: proc: table is full Debug: Caught SIGPIPE while trying to install package. Debug: Switching back to VTYI DF Produces: mfs_root 89% / dev/wd0a 44% /mnt /mnt/dev/wd0s1f 23% /mnt/user /mnt/dev/wd0s1e 0% /mnt/var /dev/wcd0c 100% /cdrom DU Produces: A very long list that I am not going to copy :) I don't know what it is, probably something very simple that I am failing to see. I tried increasing the VAR partition size, but the error still came through. Any further ideas? --Perry Lucas