From: Christoph Rohland <cr@sap.com>
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: "J . A . Magallon" <jamagallon@able.es>,
"H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] tmpfs for 2.4.1
Date: 04 Feb 2001 10:18:47 +0100 [thread overview]
Message-ID: <m3hf2bo5rs.fsf@linux.local> (raw)
In-Reply-To: <20010123205315.A4662@werewolf.able.es> <m3lmrqrspv.fsf@linux.local> <95csna$vb6$1@cesium.transmeta.com> <m3puh1que4.fsf@linux.local> <20010202215254.C2498@werewolf.able.es> <3A7B1EDC.DA2588BA@transmeta.com> <m3d7d0pwnr.fsf@linux.local> <3A7C69AB.9C7603A8@transmeta.com>
In-Reply-To: <3A7C69AB.9C7603A8@transmeta.com>
"H. Peter Anvin" <hpa@transmeta.com> writes:
> Do you need it for POSIX shm or not... if so, I would say you do need it
> (even if it's going to take some time until POSIX shm becomes widely
> used.)
Yes, you need it. glibc 2.2 will search for a shm fs on shm_open. And
without it fails. And the recommendation in the Configure.help is to
mount it.
But you do not need to mount it for any pre 2.4 functionality.
Greetings
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 19:53 swapfs for 2.4.1-pre J . A . Magallon
2001-02-01 21:39 ` [patch] tmpfs for 2.4.1 Christoph Rohland
2001-02-01 23:50 ` H. Peter Anvin
2001-02-02 9:57 ` Christoph Rohland
2001-02-02 20:52 ` J . A . Magallon
2001-02-02 20:55 ` H. Peter Anvin
2001-02-03 0:06 ` J . A . Magallon
2001-02-03 15:02 ` Christoph Rohland
2001-02-03 14:28 ` Christoph Rohland
2001-02-03 20:27 ` H. Peter Anvin
2001-02-03 20:46 ` J . A . Magallon
2001-02-04 9:53 ` Christoph Rohland
2001-02-04 9:18 ` Christoph Rohland [this message]
[not found] ` <20010203234550.A507@squish>
[not found] ` <m3zog2n6ec.fsf@linux.local>
[not found] ` <20010205210540.A10316@squish>
2001-02-06 9:18 ` VM question (ramfs abuse) 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=m3hf2bo5rs.fsf@linux.local \
--to=cr@sap.com \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=jamagallon@able.es \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.