From: Dan Kegel <dank@kegel.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: re: RAMFS turned read-only after upgrade to 2.4.19-pre3
Date: Wed, 15 May 2002 09:22:51 -0700 [thread overview]
Message-ID: <3CE28B5B.A9D44029@kegel.com> (raw)
Roy wrote:
> after upgrading from 2.4.19-pre3-ac1 tp 2.4.19-pre8-ac3,
> RAMFS is suddenly read-only. This is extremely inconvinient ...
> How can I mend it?
I ran into the same thing. I only use ramfs as my initial boot
disk; upon boot I pivot root to tmpfs. Thus in my application,
one workaround was to make the new root directory before creating
the ramdisk image. Since that was the only write I ever did to
the initial ramdisk, avoiding the write let me boot again.
I have no idea why ramfs went ro. It is annoying. I haven't
tracked it down, though, since I was able to work around it.
(I may have to track it down yet, though, since I was thinking
of using ramfs to hold files that I intend to use with sendfile,
since tmpfs and sendfile don't [yet] mix.)
- Dan
next reply other threads:[~2002-05-15 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 16:22 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 15:14 RAMFS turned read-only after upgrade to 2.4.19-pre3 Roy Sigurd Karlsbakk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CE28B5B.A9D44029@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox