linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: SMP module compilation on UP?
Date: Thu, 14 Jun 2001 19:27:43 +0200	[thread overview]
Message-ID: <20010614192743.E23383@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <3B277C2A.B2CC3FCF@sangate.com> <19041.992451035@ocs4.ocs-net>
In-Reply-To: <19041.992451035@ocs4.ocs-net>; from kaos@ocs.com.au on Thu, Jun 14, 2001 at 02:50:35AM +1000

[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]

On Thu, Jun 14, 2001 at 02:50:35AM +1000, Keith Owens wrote:
> On Wed, 13 Jun 2001 17:43:54 +0300, 
> Mark Mokryn <mark@sangate.com> wrote:
> >Is this the only way - to keep two separately configured kernel source
> >trees? No way to do it via some flag?
> 
> With 2.4, yes.  You need a complete set of kernel source for every set
> of config files you use because the object code is written to the
> source directory.  With 2.5 you can have a single source tree and
> multiple object trees, one for each config that you are working on.

Use cp -al to replicate your kernel source tree before configuring. It
creates a tree with hard links, so you don't waste disk space.
Just don't forget to unlink() the files, if you edit them manually. (*)

garloff@garloff:~/Physics/numerix $ type unlink
unlink is a function
unlink () 
{ 
    for name in $*;
    do
	test -f $name && { 
	    mv $name $name~$PPID;
	    cp -pd $name~$PPID $name;
	    rm $name~$PPID
	};
    done
}
								
(*) If you use emacs, you don't need to unlink before edit. The backup file
    will stay linked, but the edited is unique. patch does unlink, so
    patching is no problem. vi does NOT unlink.

Regards,
-- 
Kurt Garloff  <garloff@suse.de>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE GmbH, Nuernberg, FRG                               SCSI, Security

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-06-14 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 13:42 SMP module compilation on UP? Mark Mokryn
2001-06-13 15:25 ` Rafael Herrera
2001-06-13 14:43   ` Mark Mokryn
2001-06-13 16:50     ` Keith Owens
2001-06-14 17:27       ` Kurt Garloff [this message]
2001-06-13 16:42 ` Keith Owens
2001-06-13 21:14 ` Khalid Aziz

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=20010614192743.E23383@garloff.etpnet.phys.tue.nl \
    --to=garloff@suse.de \
    --cc=kaos@ocs.com.au \
    --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).