Re: HELP: Crash in 3.0 results in failure to boot

Article View: comp.sys.next.bugs

Article #45

Back to comp.sys.next.bugs Previous Next

#45

From: Greg Johnson
Date: Sun, 10 Jan 1993 22:55

8 lines
974 bytes

In article <1993Jan7.165156.9501@dolphin.com>
Zacharias J. Beckman <zac@dolphin.com> writes:
>When the system started to boot Mach, it declared that it couldn't write to
>mtab because the file system was read only!!!
I found a colleague with a read-only root not long after doing a 3.0
install.  We finally discovered that he copied from the CD-ROM /NeXTCD
or some such file where the extended version packages are.  If a file
with that name is on /, the new /etc/rc mounts the file-system read-only!

Technical Details

Message-ID: <16B52EE0A.CCGREG@mizzou1.missouri.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!mont!mizzou1.missouri.edu!CCGREG

References: <1993Jan7.165156.9501@dolphin.com>

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.bugs
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!mont!mizzou1.missouri.edu!CCGREG
From: CCGREG@mizzou1.missouri.edu (Greg Johnson)
Subject: Re: HELP: Crash in 3.0 results in failure to boot
Message-ID: <16B52EE0A.CCGREG@mizzou1.missouri.edu>
Sender: news@mont.cs.missouri.edu
Nntp-Posting-Host: mizzou1.missouri.edu
Organization: University of Missouri
References:  <1993Jan7.165156.9501@dolphin.com>
Date: Sun, 10 Jan 93 16:55:19 CST
Lines: 8

Reply to Parent Message