linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Isaacson <adi@hexapodia.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.61 (Yes, there are still Alpha users out there. :-) )
Date: Mon, 3 Mar 2003 16:10:33 -0600	[thread overview]
Message-ID: <20030303161033.A7473@hexapodia.org> (raw)
In-Reply-To: <20030220113624.GP351@lug-owl.de>; from jbglaw@lug-owl.de on Thu, Feb 20, 2003 at 12:36:24PM +0100

On Thu, Feb 20, 2003 at 12:36:24PM +0100, Jan-Benedict Glaw wrote:
> This reminds me that I wanted to have a look at an additional feature -
> building the kernel _not_ within its source tree. So I wouldn't need to
> place 10 copies of the kernel onto disk / into memory...
> 
> Haven't I seen patches flyin' around? Anyone?

You can save your buffercache memory by doing a
"cp -al linux-2.5.61 linux-2.5.61-buildfoo", for each value of buildfoo,
and do your builds in a cloned tree.  Hard links save the day!

-andy

  parent reply	other threads:[~2003-03-03 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 11:25 2.5.61 (Yes, there are still Alpha users out there. :-) ) Oliver Pitzeier
2003-02-17 12:14 ` Jan-Benedict Glaw
2003-02-17 15:39 ` Fred K Ollinger
2003-02-17 21:29   ` Jan-Benedict Glaw
2003-02-19 18:00     ` Bill Davidsen
2003-02-19 19:55       ` Jan-Benedict Glaw
2003-02-19 20:39         ` Bill Davidsen
2003-02-20  6:23           ` Jan-Benedict Glaw
2003-02-20 11:23             ` Bill Davidsen
2003-02-20 11:36               ` Jan-Benedict Glaw
2003-02-20 17:21                 ` Sam Ravnborg
2003-03-03 22:10                 ` Andy Isaacson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-17 18:07 Jim Lucas
2003-02-17 11:19 Oliver Pitzeier
     [not found] <3E4FEF47.8010207@i-55.com>
2003-02-17 10:16 ` Oliver Pitzeier

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=20030303161033.A7473@hexapodia.org \
    --to=adi@hexapodia.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).