Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!bloom-beacon!mit-eddie!uw-beaver!rice!sun-spots-request
From: dupuy@cs.columbia.edu
Newsgroups: comp.sys.sun
Subject: Late night system administration == trouble on SunOS 4.x
Keywords: SunOS
Message-ID: <1910@brazos.Rice.edu>
Date: 2 Oct 89 18:32:06 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 16
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 151, message 9 of 15

> From: thomas@shire.cs.psu.edu (Angela Marie Thomas)
> Date: 30 Sep 89 05:33:31 GMT
> X-Sun-Spots-Digest: Volume 8, Issue 148, message 5 of 10

> ...  It seems that /sbin has enough programs in it to get you into trouble,
> but not enough to get you out of it.  No dump, no restore, no umount.  I
> couldn't even sync;sync;halt the system.  Oh, mount is there.  I could mount
> more newly newfs'd filesystems onto /usr until my face turned blue.  I can't
> believe it.  It was as if I had just stumbled into a cul-de-sac.

No - not a cul-de-sac.  A blind alley, perhaps, especially late at night.
The right thing to do is to mount a valid /usr filesystem (from anywhere,
even nfs) onto any spare directory.  Now you have umount, and can umount
/usr and try again.

@alex