From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Dale <rdalek1967@gmail.com>
Subject: Re: [gentoo-dev] Re: Last rites: www-client/chromium-bin
Date: Sat, 5 Mar 2011 05:41:40 -0500 [thread overview]
Message-ID: <AANLkTimZk6NqGOFi4ky5HXJN1rMhuseWYRUEGDfs5u21@mail.gmail.com> (raw)
In-Reply-To: <4D720EB0.5060507@gmail.com>
On Sat, Mar 5, 2011 at 5:21 AM, Dale <rdalek1967@gmail.com> wrote:
> It seems you correct the first time.
>
> http://en.wikipedia.org/wiki/Tmpfs
>
> I found the same examples in other paces as well. One is in the mount man
> page.
While this is drifting off-topic this is not the case. You can limit
the size of a tmpfs, but you can't limit the amount of physical RAM
that it uses (other than its size limit). At least, not using
anything in either of those sources.
When building chromium limiting the tmpfs size isn't a very practical
solution... At least, not until that contrib directory doesn't have
half a gig of stuff already on my system BEFORE I compile it.
next prev parent reply other threads:[~2011-03-05 10:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 9:35 [gentoo-dev] Last rites: www-client/chromium-bin "Paweł Hajdan, Jr."
2011-03-04 23:32 ` Tomáš Chvátal
2011-03-04 23:46 ` Alex Alexander
2011-03-04 23:51 ` Tomáš Chvátal
2011-03-04 23:58 ` Alex Alexander
2011-03-05 9:23 ` "Paweł Hajdan, Jr."
2011-03-05 10:05 ` [gentoo-dev] " Duncan
2011-03-10 11:12 ` "Paweł Hajdan, Jr."
2011-03-10 20:04 ` James Cloos
2011-03-10 20:33 ` Mike Gilbert
2011-03-10 20:42 ` "Paweł Hajdan, Jr."
2011-03-11 22:17 ` James Cloos
2011-03-05 2:33 ` [gentoo-dev] " Antoni Grzymala
2011-03-05 2:41 ` Rich Freeman
2011-03-05 3:01 ` dev-random
2011-03-05 8:01 ` Jeroen Roovers
2011-03-05 10:00 ` [gentoo-dev] " Nikos Chantziaras
2011-03-05 10:05 ` Nikos Chantziaras
2011-03-05 10:21 ` Dale
2011-03-05 10:41 ` Rich Freeman [this message]
2011-03-05 10:29 ` Rich Freeman
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=AANLkTimZk6NqGOFi4ky5HXJN1rMhuseWYRUEGDfs5u21@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=rdalek1967@gmail.com \
/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