From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: tmpfs sparse file failure in glibc "make check"
Date: Fri, 30 Jan 2004 10:07:52 -0700 [thread overview]
Message-ID: <401A8F68.60904@backtobasicsmgmt.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401301552470.1441-100000@localhost.localdomain>
Hugh Dickins wrote:
> I ought to fix this, but I'm averse to complexity. I'll mull over
> the options before fixing it: please don't hold your breath.
No problem, as I said I have a workaround that causes me no pain. It
seems that the use of tmpfs for both a traditional filesystem _and_
shmem is what's the root of this problem, what is the real advantage of
both functions being performed by the same code?
next prev parent reply other threads:[~2004-01-30 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 3:35 tmpfs sparse file failure in glibc "make check" Kevin P. Fleming
2004-01-30 16:53 ` Hugh Dickins
2004-01-30 17:07 ` Kevin P. Fleming [this message]
2004-01-30 17:47 ` Hugh Dickins
[not found] <1jKa4-1TZ-17@gated-at.bofh.it>
[not found] ` <1jKjY-27v-35@gated-at.bofh.it>
2004-02-09 9:12 ` Christoph Rohland
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=401A8F68.60904@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
/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