From owner-freebsd-questions Sun Oct 5 10:28:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA00932 for questions-outgoing; Sun, 5 Oct 1997 10:28:23 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA00927 for ; Sun, 5 Oct 1997 10:28:21 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id RAA01143; Sun, 5 Oct 1997 17:28:11 GMT Date: Sun, 5 Oct 1997 10:28:11 -0700 (PDT) From: Dan Busarow To: Jon Saenz cc: freebsd-questions@FreeBSD.ORG Subject: Re: read-only root filesystem... = disaster? In-Reply-To: <19971005111731334.AAA201@jon> 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 On Sun, 5 Oct 1997, Jon Saenz wrote: > When typing RETURN, sh starts and when I type df, I get the following > answer: > > Filesystem 512-blocks Used Avail Capacity Mounted on > root_device 67742 25762 36562 41% / > > I am NOT allowed to: > 1. edit files > 2. sh MAKEDEV You need to re-mount root rw mount -u / then mount /usr You now have a rw / and /usr for vi. Based on the sequence of events I'll bet that the device file for your Zip disk is a regular file, not a device special file. When you tried writing to it you created a large file in /dev. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82