From: Tom Guilliams <tguilliams@san.rr.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: vda <vda@port.imtp.ilyichevsk.odessa.ua>,
DHollenbeck <dick@softplc.com>,
busybox@mail.codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: [BusyBox] [Fwd: Loopback device setup?]
Date: Tue, 17 Feb 2004 14:41:23 -0800 [thread overview]
Message-ID: <40329893.2080208@san.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402171649420.22275-100000@localhost.localdomain>
Thanks to all who responded. I have a 2.4.20 kernel so mounting on the
tmpfs is not supported. I have found an alternative by using the ram
device nodes for storage.
Thanks again,
Tom
Hugh Dickins wrote:
> On Tue, 17 Feb 2004, vda wrote:
>
>>On Tuesday 17 February 2004 02:20, Tom Guilliams wrote:
>>
>>>in /driver/block/loop.c -
>>>
>>>loop_set_fd()
>>>
>>> /*
>>> * If we can't read - sorry. If we only can't write -
>>> * well, it's going to be read-only.
>>> */
>>> if (!aops->readpage)
>>> goto out_putf;
>>>
>>>I confirmed the "if (!aops->readpage)" is true. I'm not sure what the
>>>readpage routine is trying to do (which dev or file) in my command below -
>>># mount -t ext2 -o loop ramdisk.image rootfs
>>>
>>>Anyone have any thoughts?? This is all being done in the /tmp
>>>dircectory which is mounted as "tmpfs". Not sure if that has anything
>>>to do with it.
>>
>>I recall that tmpfs cannot do readpage (by design?).
>>CCing LKML, maybe someone will pour in more info.
>
>
> readpage is not straightforward for tmpfs, so it took a long time
> to be added, but tmpfs has supported loop since 2.4.22 and 2.5.45.
>
> Hugh
>
>
prev parent reply other threads:[~2004-02-17 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40314A9F.3090801@softplc.com>
[not found] ` <40315E31.90201@san.rr.com>
2004-02-17 8:22 ` [BusyBox] [Fwd: Loopback device setup?] vda
2004-02-17 17:00 ` Hugh Dickins
2004-02-17 22:41 ` Tom Guilliams [this message]
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=40329893.2080208@san.rr.com \
--to=tguilliams@san.rr.com \
--cc=busybox@mail.codepoet.org \
--cc=dick@softplc.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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