From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] another openoffice build failure
Date: Sat, 2 Sep 2006 16:26:16 -0700 [thread overview]
Message-ID: <7573e9640609021626m4ebbb138q13fdfc064e4da93e@mail.gmail.com> (raw)
In-Reply-To: <200609021423.55605.lordsauronthegreat@gmail.com>
On 9/2/06, Lord Sauron <lordsauronthegreat@gmail.com> wrote:
> A cheap way to get more memory:
>
> o wipe a USB key clean (back it up though!)
> o mkspwap /dev/sda1 or whereever your usb memory stick is
> o swapon all
It had better be a disposable key, as flash memory is only good for so
many writes before it fails....better (and faster) would be to add a
swap file.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-02 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 18:07 [gentoo-user] another openoffice build failure Allan Gottlieb
2006-09-02 18:22 ` Rafael Fernández López
2006-09-02 20:19 ` Allan Gottlieb
2006-09-02 21:10 ` Richard Fish
2006-09-02 21:23 ` Lord Sauron
2006-09-02 23:26 ` Richard Fish [this message]
2006-09-02 23:14 ` Allan Gottlieb
2006-09-03 1:36 ` Allan Gottlieb
2006-09-03 2:16 ` Richard Fish
2006-09-04 21:59 ` Allan Gottlieb
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=7573e9640609021626m4ebbb138q13fdfc064e4da93e@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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