From: safemode <safemode@speakeasy.net>
To: linux-kernel@vger.kernel.org
Subject: question about tmpfs
Date: Fri, 17 Aug 2001 02:48:20 -0400 [thread overview]
Message-ID: <20010817064809Z269735-760+2777@vger.kernel.org> (raw)
I looked in the documentation for something about tmpfs and looked around for
some obvious tmpfs source but couldn't find any to figure out how to know
when/if it's doing what it's supposed to. when i ls the dir it's mounted to
i get nothing and this is what df gives me.
Filesystem 1k-blocks Used Available Use% Mounted on
tmpfs 144108 0 144108 0% /dev/shm
There are some mounting options that i did not use, just let it go to
defaults, and i've got a fair amount of shared memory programs open and i'm
just unable to tell if this is working correctly and if not how to fix it.
If anyone can point me to the right place to look that would be great.
Hopefully this kernel, 2.4.9, will not cause mozilla to start getting
retarded after 5 days of uptime.
next reply other threads:[~2001-08-17 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 6:48 safemode [this message]
2001-08-17 8:18 ` question about tmpfs 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=20010817064809Z269735-760+2777@vger.kernel.org \
--to=safemode@speakeasy.net \
--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