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: Mon, 6 Nov 2006 11:44:01 +0000	[thread overview]
Message-ID: <200611061144.01773.prh@gotadsl.co.uk> (raw)
In-Reply-To: <eimsge$q3t$6@sea.gmane.org>

On Monday 06 November 2006 08:41, Duncan wrote:

> Peter Humphrey <prh@gotadsl.co.uk> posted
> > Perhaps I ought to look into putting /tmp and /var/tmp onto tmpfs.
>
> Do so.  It makes a /big/ difference!

My reading so far suggests that I include these two lines in /etc/fstab:

tmpfs	/tmp		tmpfs	nodev,nosuid,noexec	0 0
tmpfs	/var/tmp	tmpfs	nodev,nosuid,noexec	0 0

Is that all I have to do? I assume I don't need to specify tmpfs sizes; I 
have 4 GB RAM of which 0.5 GB is unavailable (owing to a motherboard 
problem that prompted the system builder to refund some of my money - small 
consolation). Probably I should put a script into /etc/conf.d/start.local 
to create a symlink from /var/tmp/ccache back to a real cache directory on 
disk, as it seems daft to install a compiler cache and then flush it at 
every reboot - at present mine has 1.5 GB of data. /tmp has 750 MB of stuff 
and is a separate disk partition at present, mounted on whichever system I 
boot.

>  I don't have all of KDE merged here

Nor I; I just have 9 meta-packages because I didn't want the education or 
games stuff, among others. I might have preferred to go to finer grain 
still, but it looked like too much work.

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



  parent reply	other threads:[~2006-11-06 11:46 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 [this message]
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
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=200611061144.01773.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