From owner-freebsd-current Thu Mar 12 09:23:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19476 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:23:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19456 for ; Thu, 12 Mar 1998 09:23:34 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id LAA00459; Thu, 12 Mar 1998 11:23:04 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803121723.LAA00459@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Thu, 12 Mar 1998 09:14:37 PST." <199803121714.JAA08296@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Mar 1998 11:23:04 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In article <199803121709.LAA00367@friley585.res.iastate.edu>, >Chris Csanady wrote: > >> I would, although my system is unable to do a dump. I have been wondering >> for a while why this is, but it seems that dumpon is just plain broken. >> It will not work on anything other that the first disk. (no, this is not >> specific to cam..) >> >> This is what happens.. >> >> $ dumpon /dev/da1s1b >> dumpon: sysctl: kern.dumpdev: No space left on device > >Probably you've added RAM recently. Remember, the dump is the full >size of the system RAM, so the dump device has to be at least that >large. I wish. :) I still have only 64M of ram, and 80M of swap on that disk. Do I still need more than this? If this is the case, I would like to repartition sometime soon anyways.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message