<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffff66" text="#000000">
I have had this problem before and it turned out<br>
to be that even though FSTAB was on a R/W<br>
File System that VI was also attempting<br>
to write to the /TMP directory, which is<br>
not writable, instead of the /mnt/sysimage/tmp<br>
directory. I don't remember how I got around <br>
it.<br>
<br>
im<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:fedora-test-list-request@redhat.com">fedora-test-list-request@redhat.com</a> wrote:
<blockquote cite="mid:20080422153202.E59AF6194B5@hormel.redhat.com"
type="cite">
<pre wrap="">Send fedora-test-list mailing list submissions to
<a class="moz-txt-link-abbreviated" href="mailto:fedora-test-list@redhat.com">fedora-test-list@redhat.com</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/fedora-test-list">https://www.redhat.com/mailman/listinfo/fedora-test-list</a>
or, via email, send a message with subject or body 'help' to
<a class="moz-txt-link-abbreviated" href="mailto:fedora-test-list-request@redhat.com">fedora-test-list-request@redhat.com</a>
You can reach the person managing the list at
<a class="moz-txt-link-abbreviated" href="mailto:fedora-test-list-owner@redhat.com">fedora-test-list-owner@redhat.com</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of fedora-test-list digest..."
Today's Topics:
1. Re: F9: fsck gotcha on booting (Todd Denniston)
2. Re: small program that generates terms in OEIS sequence
A016278 (Michael Schwendt)
3. Re: F9: fsck gotcha on booting (Patrick O'Callaghan)
4. Re: X settings not saved under KDE 4 (Patrick O'Callaghan)
5. Re: small program that generates terms in OEIS sequence
A016278 (Antonio Olivares)
6. Re: X settings not saved under KDE 4 (Gianluca Cecchi)
7. Re: KDE 4 Pager doesn't show desktop names (Rex Dieter)
8. Digital Clock in KDE (Antonio Olivares)
9. Re: Thinkpad middle button scroll in F9/ rawhide (Derek Cramer)
10. Re: X settings not saved under KDE 4 (Patrick O'Callaghan)
11. Re: Atheros AR5006X Wireless Network Adapter (Bob Arendt)
12. Re: Digital Clock in KDE (Patrick O'Callaghan)
13. Re: Digital Clock in KDE (Antonio Olivares)
14. f9 prerelease crash (update sw raid) (Neal Becker)
----------------------------------------------------------------------
Message: 1
Date: Tue, 22 Apr 2008 09:12:13 -0400
From: Todd Denniston <a class="moz-txt-link-rfc2396E" href="mailto:Todd.Denniston@ssa.crane.navy.mil"><Todd.Denniston@ssa.crane.navy.mil></a>
Subject: Re: F9: fsck gotcha on booting
To: For testers of Fedora Core development releases
<a class="moz-txt-link-rfc2396E" href="mailto:fedora-test-list@redhat.com"><fedora-test-list@redhat.com></a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:480DE42D.6000507@ssa.crane.navy.mil"><480DE42D.6000507@ssa.crane.navy.mil></a>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Patrick O'Callaghan wrote, On 04/21/2008 11:35 PM:
</pre>
<blockquote type="cite">
<pre wrap="">On Mon, 2008-04-21 at 20:32 -0700, Andrew Farris wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Patrick O'Callaghan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">My fstab contains the line:
LABEL=/xtra /xtra ext3 defaults 1 2
which worked fine on F8. Now with F9-Preview the boot process halts with
the following error (I'm working form memory here):
Fsck: cannot resolve "LABEL=/xtra"
and drops me to a Shell to fix the problem. Two things:
1) From the Shell I can happily "mount /xtra" with no problems, so what
gives?
2) I can't edit /etc/fstab from this Shell. "mount" claims that the
system disk is mounted rw. but when I try to edit fstab "vi" tells me
it's read-only, and in fact "> foo" from the Shell gives the same error.
So I feel I have to ask why is the emergency Shell set up to not let me
edit anything?
</pre>
</blockquote>
<pre wrap="">Did you try editing then using w! to save it? That may have worked.
</pre>
</blockquote>
<pre wrap="">Of course. It didn't. w! is fine if it's just a write-protected file.
This was a read-only filesystem.
poc
</pre>
</blockquote>
<pre wrap=""><!---->
when in faulted file system mode, trust /proc/mounts instead of /etc/mtab
(which is what mount returns data from).
a trick for when you need to write to these file systems:
mount -oremount,rw /mountpoint
i.e., for the root file system
mount-oremount,rw /
</pre>
</blockquote>
</body>
</html>