From owner-freebsd-questions Mon Jul 21 18:06:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24342 for questions-outgoing; Mon, 21 Jul 1997 18:06:47 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA24336 for ; Mon, 21 Jul 1997 18:06:42 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id VAA06432; Mon, 21 Jul 1997 21:08:57 -0400 (EDT) Date: Mon, 21 Jul 1997 21:08:57 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Doug White cc: Jan.Vedeler@student.unisg.ch, freebsd-questions@FreeBSD.ORG Subject: Re: Problem with 2.2.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think he's speaking of "Midnight Commander" which is a ripoff of the old DOS tool, Norton Commander; it's an interesting little file manipulation/manager tool... I'd guess that F9 tries to do something funny to get "info". Normally that probably wouldn't be bad, but I'm guessing in this case, the tool was running as root and had free reign to do bad things (tm). The rule here should be, before you try some neat new utility ported over from Dos->Linux->FBSD try it thoroughly as a regular user first. It's really not a good idea to run big unfamiliar programs as root... Charles On Mon, 21 Jul 1997, Doug White wrote: > On Sat, 19 Jul 1997 Jan.Vedeler@student.unisg.ch wrote: > > > I cant locate the problem, but if I f.ex. run MC and try to get info from > > the disk (F9 - I) I get the message "pid 507(mc), uid 0: exited on signal > > 11 - segmentation fault". Then the system start to act cracy. > > Where is this? There isn't a system utility called 'mc' as far as I can > find, at least in versions < 2.2.2. If it crashes and thus causes the > system to crash, perhaps you shouldn't be using it? :) > > > What I can find in this situation is that the rc.conf-file starts to be > > corrupted. It looks like as if all comments in the rc.conf duplicates - > > "the file starts to grow" - more or less every time I do something. And at > > the end it is finally corrupt - and some strange behavior comes up during > > booting. There is also a backup of the rc.conf - rc.conf.previous, but this > > will of course also go nuts if this "duplication" has been done 2 times. > > This sounds like some filesystem corruption. Run fsck -y on all your > filesystems to make sure they're clear. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > Spam routed to /dev/null by Procmail | Death to Cyberpromo >