public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: Unexpected side effect of GCC 4
Date: Fri, 10 Nov 2006 10:14:36 +0000	[thread overview]
Message-ID: <200611101014.37059.prh@gotadsl.co.uk> (raw)
In-Reply-To: <eissei$dvt$1@sea.gmane.org>

On Wednesday 08 November 2006 15:17, Duncan wrote:
> Peter Humphrey <prh@gotadsl.co.uk> posted
> > I decided on an even simpler approach. As I don't really want all the
> > other stuff in /var/tmp to evaporate every time I shut down, I put /tmp
> > on tmpfs, with this entry in /etc/fstab:
> >
> > 	tmpfs	/tmp		tmpfs	nodev,nosuid,size=85%		0 0
>
> Does the 85% actually work as implied?  If so, I just learned something
> new. =8^)

Can't say yet. I got the info 
from /usr/src/linux/Documentation/filesystems/tmpfs.txt.

> > Then I added these entries to /etc/make.conf:
> > 	BUILD_PREFIX="/tmp/portage/build"	# not sure I need this
>
> I don't think you do.  I don't have that var set here.

I was being cautious, having seen hints that setting a directory name 
doesn't necessarily also set any others below it.

> PORTAGE_TMPFS is a fairly new setting that may not have made it to stable
> portage yet. It doesn't appear to have made it into the make.conf manpage
> yet, but from make.conf.example:

[...]

Thanks - there's always one more place to look :-(

> Interesting [that PKG_TMPDIR] doesn't seem to be documented, and
> PORTAGE_TMPFS is in make.conf.example, but not in the make.conf manpage. 
> I should file a bug.

Perhaps. I may also complain about the inconsistency that some directory 
specifications are literal while others point to a directory above where 
data will actually be used.

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-11-10 10:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05  8:45 [gentoo-amd64] Unexpected side effect of GCC 4 Peter Humphrey
2006-11-05 10:12 ` [gentoo-amd64] " Duncan
2006-11-05 11:50   ` Peter Humphrey
2006-11-05 12:10     ` Peter Humphrey
2006-11-06  8:17       ` Duncan
2006-11-06  8:29         ` Hemmann, Volker Armin
2006-11-06 15:57           ` Duncan
2006-11-06  7:50     ` Duncan
2006-11-06  8:48       ` Peter Humphrey
2006-11-06 16:01         ` Duncan
2006-11-06 16:06         ` Peter Humphrey
2006-11-06  8:41     ` Duncan
2006-11-06 10:47       ` Hemmann, Volker Armin
2006-11-06 11:48         ` Peter Humphrey
2006-11-06 12:05           ` Hemmann, Volker Armin
2006-11-06 12:49             ` Jack Lloyd
2006-11-06 12:59               ` Hemmann, Volker Armin
2006-11-06 13:06                 ` Jack Lloyd
2006-11-06 15:06                 ` Peter Humphrey
2006-11-06 11:44       ` Peter Humphrey
2006-11-06 15:51         ` Duncan
2006-11-08 11:19           ` Peter Humphrey
2006-11-08 15:17             ` Duncan
2006-11-10 10:14               ` Peter Humphrey [this message]
2006-11-05 13:24   ` Hemmann, Volker Armin
2006-11-05 23:26     ` Duncan
2006-11-08 10:14 ` [gentoo-amd64] " Peter Humphrey
2006-11-08 11:06   ` [gentoo-amd64] " Duncan

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=200611101014.37059.prh@gotadsl.co.uk \
    --to=prh@gotadsl.co.uk \
    --cc=gentoo-amd64@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