From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Cc: kaboom@gatech.edu, chris.ricker@genetics.utah.edu
Subject: Re: 2.4.7 tmpfs strange behaviour
Date: Tue, 24 Jul 2001 20:22:56 -0700 (PDT) [thread overview]
Message-ID: <20010725032256.D3F0F785B8@mail.clouddancer.com> (raw)
In-Reply-To: <9jl7as$a2h$1@ns1.clouddancer.com>
In-Reply-To: <20010725005940.A5607@werewolf.able.es> <w53bsm9c06f.wl@megaela.fe.dis.titech.ac.jp> <20010725025014.A2431@werewolf.able.es> <20010725032634.A1175@werewolf.able.es> <20010725025014.A2431@werewolf.able.es>; from jamagallon@able.es on Wed, Jul 25, 2001 at 02:50:14 +0200 <9jl7as$a2h$1@ns1.clouddancer.com>
In clouddancer.list.kernel, you wrote:
>
>On 20010725 J . A . Magallon wrote:
>>
>>On 20010725 GOTO Masanori wrote:
>>>> /dev/sdb1 4232960 32840 4200120 1% /mnt/disk
>>>> /root/tmpfs 131072 0 131072 0% /dev/shm
>>>> /tmp/tmpfs 131072 0 131072 0% /dev/shm
>>>>
>>>> ???? Strange devices.... both mounted under /dev/shm.
>>>
>>>I don't have any problems... mount version is 2.11g on 2.4.7
>>>Uni-Processor and 2.4.7-pre3 SMP.
>>>
>>
>>Mmm, mine is mount-2.11e on 2.4.7 final, SMP box.
>>perhaps mount bug ?
>>Going to get the new one...
>>
>
>Right, mount bug. Version 2.11h works fine...
>
>--
>J.A. Magallon # Let the source be with you...
>mailto:jamagallon@able.es
>Mandrake Linux release 8.1 (Cooker) for i586
This means an update to the Changes documentation. It lists 2.10o as
the minimum.
prev parent reply other threads:[~2001-07-25 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 22:59 2.4.7 tmpfs strange behaviour J . A . Magallon
2001-07-25 0:38 ` GOTO Masanori
2001-07-25 0:50 ` J . A . Magallon
2001-07-25 1:26 ` J . A . Magallon
[not found] ` <9jl7as$a2h$1@ns1.clouddancer.com>
2001-07-25 3:22 ` Colonel [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=20010725032256.D3F0F785B8@mail.clouddancer.com \
--to=klink@clouddancer.com \
--cc=chris.ricker@genetics.utah.edu \
--cc=kaboom@gatech.edu \
--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.