From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Sean Neakums <sneakums@zork.net>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: how to configure/build a kernel in a separate directory?
Date: Mon, 7 Jun 2004 19:28:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0406071926540.22541@localhost.localdomain> (raw)
In-Reply-To: <6uy8mz3vff.fsf@zork.zork.net>
On Mon, 7 Jun 2004, Sean Neakums wrote:
> "Robert P. J. Day" <rpjday@mindspring.com> writes:
>
> > is there an easy way to configure/build one or both of a 2.4 and 2.6
> > kernel in a totally separate directory from the source directory itself?
> >
> > i'd like to have a totally pristine ("make mrproper"ed) source tree,
> > write-protected, readable by all, so that several developers can
> > independently configure and build their own kernels without stepping on
> > each other.
>
> This isn't really what you want, but you can use 'cp -rl' to build a
> hard-linked tree from the pristine read-only tree and build there.
> This will at least address the space issue.
i was reminded of the easy solution with the 2.6 kernel, so that's a
relief. sadly, it's the 2.4 case that's more important to me at the
moment, and it looks like it's major symlink time. oh well ... more
incentive to move on up to 2.6.
thanks.
rday
next prev parent reply other threads:[~2004-06-07 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 21:00 Robert P. J. Day
2004-06-07 21:31 ` Richard B. Johnson
2004-06-07 21:52 ` Bernd Petrovitsch
2004-06-07 21:33 ` Sean Neakums
2004-06-07 23:28 ` Robert P. J. Day [this message]
2004-06-07 21:36 ` Sam Ravnborg
2004-06-08 6:32 ` Michelle Konzack
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=Pine.LNX.4.58.0406071926540.22541@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sneakums@zork.net \
/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
all inboxes | Powered by JetHome®