From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: /var/tmp on tmpfs
Date: Thu, 8 Feb 2018 19:50:09 -0600 [thread overview]
Message-ID: <951006b1-40db-b049-6cf9-9425937e3c74@gmail.com> (raw)
In-Reply-To: <CA+t6X7e2au8vJWSaUDywxSG2+MoavZFnv2dcM0wOx8LnHdyHNw@mail.gmail.com>
gevisz wrote:
>
> You probably will be surprised, but the main reason I am trying to use
> tmpfs for /var/tmp/ is not because I want to make emerging chromium
> faster (I have no hope about that because read somewhere that it will
> make compilation only 10 percent faster) but because I have not too
> much free space on / (sometimes in the past chromium refused to build
> in the similar conditions) and because of that either have to move /var/tmp
> to the separate partition anyway or try to use tmpfs + swap and, if it fails,
> to move to the separate partition only /var/tmp/portage/notmpfs
>
I think you can tell emerge/portage to build that specific program on
another disk. You just have to tell it where, sort of the same way you
tell it to build on disk instead of tmpfs. I've never done it but it
should work the same way. Just make sure the permissions are right.
My thinking. Let's say you have chromium that won't fit on the usual
disk. Tell emerge/portage to build chromium in another directory that
is on another disk.
/etc/portage/env/largedisk.conf
PORTAGE_TMPDIR="/var/tmp/largedisk"
/etc/portage/package.env/package.env
www-client/chromium ../env/largedisk.conf
Once you have those files set up to work, then make sure you have your
large disk mounted at /var/tmp/largedisk and I would think it would
work. Anytime you emerge chromium, it should do that in
/var/tmp/largedisk. Only question is, do you have another disk to try
this on???
Anyone think that wouldn't work??? Basically, you are just telling
emerge/portage to build somewhere else and it shouldn't care where that
is, tmpfs or disk. Right?
Dale
:-) :-)
next prev parent reply other threads:[~2018-02-09 1:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 17:11 [gentoo-user] /var/tmp on tmpfs gevisz
2018-02-08 17:47 ` [gentoo-user] " Nikos Chantziaras
2018-02-08 18:13 ` Rich Freeman
2018-02-08 19:05 ` Nikos Chantziaras
2018-02-08 19:42 ` Rich Freeman
2018-02-08 21:52 ` gevisz
2018-02-08 21:57 ` Rich Freeman
2018-02-08 22:16 ` gevisz
2018-02-09 1:50 ` Dale [this message]
2018-02-09 11:52 ` gevisz
2018-02-08 22:32 ` Nikos Chantziaras
2018-02-08 21:31 ` gevisz
2018-02-08 22:19 ` Nikos Chantziaras
2018-02-08 22:32 ` gevisz
2018-02-08 22:38 ` Rich Freeman
2018-02-08 22:50 ` Tsukasa Mcp_Reznor
2018-02-09 10:07 ` gevisz
2018-02-09 11:00 ` Neil Bothwick
2018-02-08 23:42 ` Grant Taylor
2018-02-10 18:56 ` Kai Krakow
2018-02-10 19:38 ` Wols Lists
2018-02-10 19:52 ` Kai Krakow
2018-02-10 20:06 ` Rich Freeman
2018-02-10 21:13 ` Kai Krakow
2018-02-10 21:20 ` Wol's lists
2018-02-10 22:17 ` Kai Krakow
2018-02-08 19:17 ` [gentoo-user] " Dale
2018-02-08 19:41 ` [gentoo-user] " Nikos Chantziaras
2018-02-09 1:31 ` Dale
2018-02-08 19:50 ` [gentoo-user] " Rich Freeman
2018-02-09 1:24 ` Dale
2018-02-09 10:55 ` gevisz
2018-02-10 19:01 ` [gentoo-user] " Kai Krakow
2018-02-08 21:57 ` [gentoo-user] " gevisz
2018-02-09 1:35 ` Dale
2018-02-08 20:56 ` Grant Taylor
2018-02-08 23:18 ` Wol's lists
2018-02-08 23:28 ` Grant Taylor
2018-02-09 0:02 ` Rich Freeman
2018-02-09 1:15 ` Wol's lists
2018-02-09 2:15 ` [gentoo-user] " Ian Zimmerman
2018-02-09 11:57 ` gevisz
2018-02-10 19:11 ` Kai Krakow
2018-02-09 8:11 ` [gentoo-user] " Neil Bothwick
2018-02-09 10:12 ` Peter Humphrey
2018-02-09 10:58 ` Neil Bothwick
2018-02-10 19:06 ` [gentoo-user] " Kai Krakow
2018-02-09 10:30 ` [gentoo-user] " gevisz
2018-02-09 10:57 ` Neil Bothwick
2018-02-09 10:58 ` Gerrit Kühn
2018-02-09 22:03 ` Grant Taylor
2018-02-10 19:08 ` [gentoo-user] " Kai Krakow
2018-02-10 18:02 ` Kai Krakow
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=951006b1-40db-b049-6cf9-9425937e3c74@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.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