From: Christoph Rohland <cr@sap.com>
To: Sean Hunter <sean@dev.sportingbet.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Geoffrey Gallaway <geoffeg@sin.sloth.org>,
linux-kernel@vger.kernel.org
Subject: Re: Ramdisks and tmpfs problems
Date: Wed, 10 Apr 2002 13:52:37 +0200 [thread overview]
Message-ID: <m3662zzs6y.fsf@linux.wdf.sap-ag.de> (raw)
In-Reply-To: <20020409144639.A14678@sin.sloth.org> <20020410084505.A4493@dev.sportingbet.com> <200204101028.g3AAS2X05866@Port.imtp.ilyichevsk.odessa.ua> <20020410114521.C4493@dev.sportingbet.com>
Hi Sean,
On Wed, 10 Apr 2002, Sean Hunter wrote:
>> /dev is for devices, why do you use it for mounting filesystems?
>
> Normally yes, but the tmpfs provides posix shared memory semantics
> and thus /dev/shm is the "normal" place to mount it. Don't blame
> me.
Yes, and he does not want to use it for POSIX shared mem, but as a
local filesystem. So he should mount it where he needs it and
definitely not misunse the posix mount for different things.
Greetings
Christoph
next prev parent reply other threads:[~2002-04-10 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 18:46 Ramdisks and tmpfs problems Geoffrey Gallaway
2002-04-09 19:49 ` Andrew Morton
2002-04-09 21:18 ` Geoffrey Gallaway
2002-04-10 7:45 ` Sean Hunter
2002-04-10 15:31 ` Denis Vlasenko
2002-04-10 10:45 ` Sean Hunter
2002-04-10 11:52 ` Christoph Rohland [this message]
2002-04-10 14:49 ` Sean Hunter
2002-04-10 11:01 ` Denis Vlasenko
2002-04-10 14:23 ` Update - " Geoffrey Gallaway
2002-04-10 14:52 ` Sean Hunter
2002-04-10 15:01 ` Geoffrey Gallaway
2002-04-10 16:03 ` Sean Hunter
2002-04-11 11:03 ` Denis Vlasenko
2002-04-11 15:47 ` 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=m3662zzs6y.fsf@linux.wdf.sap-ag.de \
--to=cr@sap.com \
--cc=geoffeg@sin.sloth.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@dev.sportingbet.com \
--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