From: Christoph Rohland <cr@sap.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x-ac: No loop on tmpfs
Date: 29 Oct 2001 18:03:20 +0100 [thread overview]
Message-ID: <m3r8rmgyzr.fsf@linux.local> (raw)
In-Reply-To: <200110291629.f9TGTt6K010692@pincoya.inf.utfsm.cl>
Hi Horst,
On Mon, 29 Oct 2001, Horst von Brand wrote:
> Any fundamental reason for this behaviour, and should RH just use
> /var/tmp or something else? Or is this a simple oversight of some
> sort?
loop needs a feature that tmpfs - for fundamental design reasons -
does not support.
Greetings
Christoph
prev parent reply other threads:[~2001-10-29 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 16:29 2.4.x-ac: No loop on tmpfs Horst von Brand
2001-10-29 17:03 ` Christoph Rohland [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=m3r8rmgyzr.fsf@linux.local \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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