From: Chiaki <ishikawa@yk.rim.or.jp>
To: linux-kernel@vger.kernel.org
Cc: Chiaki <ishikawa@yk.rim.or.jp>
Subject: Re: Configuration system bug? : tmpfs listing in /proc/filesystems when TMPFS was not configured!?
Date: Sun, 07 Nov 2004 10:31:32 +0900 [thread overview]
Message-ID: <418D7AF4.5090500@yk.rim.or.jp> (raw)
In-Reply-To: <418D0EFB.2040002@yk.rim.or.jp>
Chiaki wrote:
> (Please cc: me since I am not subscribed to linux-kernel list.)
>
> I think there is something fishy about kernel 2.6.9.
>
> I failed to enable TMPFS during configuration of
> my linux kernel 2.6.9.
>
> However, somehow /proc/filesystems lists "nodev tmpfs" line !?
>
> Is this to be expected?
>
Just in case, the compilation of the kernel used stale object files, or
something,
I recompiled the kernel after running make clean.
Still, "tmpfs" shows up in /proc/filesystems
listing although TMPFS was not configured.
I tried to figure out where "tmpfs" was
exported to /proc/filesystems, but could
not.
This bug may bite more users in subtle ways
in the future.
BTW, the kernel version is 2.6.9
(-test-tmscsim suffix to the version string below
is added to remind me that I was testing tmscsim SCSI driver module.)
ishikawa@duron$ uname -a
Linux duron 2.6.9-test-tmscsim #11 Sun Nov 7 03:28:42 JST 2004 i686
GNU/Linux
Is there a specific sub-system module to whose maintainer
I should submit a bug report?
next prev parent reply other threads:[~2004-11-07 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 17:50 Configuration system bug? : tmpfs listing in /proc/filesystems when TMPFS was not configured!? Chiaki
2004-11-06 19:04 ` [PATCH] " Måns Rullgård
2004-11-06 21:09 ` Hugh Dickins
2004-11-07 1:31 ` Chiaki [this message]
2004-11-07 2:05 ` Chiaki
2004-11-07 2:12 ` Chiaki
2004-11-07 4:49 ` Hugh Dickins
2004-11-07 6:00 ` Chiaki
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=418D7AF4.5090500@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--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