From owner-freebsd-questions@FreeBSD.ORG Mon Oct 1 10:21:01 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAC24106566C for ; Mon, 1 Oct 2012 10:21:01 +0000 (UTC) (envelope-from rodperson@rodperson.com) Received: from www6.pairlite.com (www6.pairlite.com [64.130.10.16]) by mx1.freebsd.org (Postfix) with ESMTP id A58A68FC15 for ; Mon, 1 Oct 2012 10:21:01 +0000 (UTC) Received: from atomizer64 (c-67-186-61-206.hsd1.pa.comcast.net [67.186.61.206]) by www6.pairlite.com (Postfix) with ESMTPSA id F18F467AED; Mon, 1 Oct 2012 06:21:00 -0400 (EDT) Date: Tue, 2 Oct 2012 06:20:45 -0400 From: Rod Person To: Polytropon Message-ID: <20121002062045.020b8237@atomizer64> In-Reply-To: <20121001080254.46572b2e.freebsd@edvax.de> References: <20121001200829.2c8afade@atomizer64> <20121001080254.46572b2e.freebsd@edvax.de> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" Subject: Re: Port update hosed entire system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2012 10:21:02 -0000 On Mon, 1 Oct 2012 08:02:54 +0200 Polytropon wrote: > On Mon, 1 Oct 2012 20:08:29 -0400, Rod Person wrote: > > Hi All, > > > > I was attempting to update ports that used libogg with the command > > > > portmaster -d -y -r libogg > > > > I went away and came back some hours later and some updates had > > failed. Now my shell segfaults on any command such as ls, clear or > > su I tried to login on another console as root and after giving the > > password it just goes back to login. I am at a loss as to what to > > do to fix this one. > > That sounds like a really weird problem. FreeBSD and the > ports (which portmaster deals with) are separated systems, > so even if you totally hose your ports, the OS should not > be affected. I'm well aware of this, and is also why I no clue what could have happened. It would never have occured to me that updating a port that has to do with audio and video containers would totally leave me unable to login into my system or issue and shell commands without getting a segmentation fault. I did discover that my / file system had run out of space -131MB. I'm still able to issue sudo, so using sudo rm -r I was able to free up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't work and switching consoles doesn't let me log in. I maybe be left with attempting a single user boot, but I'm still not that comfortable at attempting such as I don't want to have a totally useless box. -- Rod Person http://www.rodperson.com "First we got population. The world today has 6.8 billion people. That's headed up to about 9 billion. Now if we do a really great job on new vaccines, health care, reproductive health services, we lower that by perhaps 10 or 15 percent." - Bill Gates