mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob <rpc@cafe4111.org>
To: linux-kernel@vger.kernel.org
Subject: Re: seperate environments for different kernels
Date: Sun, 30 May 2004 01:12:44 -0500	[thread overview]
Message-ID: <200405300112.44866.rpc@cafe4111.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0405292206320.2487@tokyo.cc.gatech.edu>

On Saturday 29 May 2004 09:13 pm, Younggyun Koh wrote:
> Hi,
>
> i want to run linux 2.6.6 kernel, which needs upgrade of some system tools
> such as module-init-tools and nfs-utils. but other guys using the same
> machine with 2.4 kernel don't want me to upgrade them.
>

sorry, typo bug: that statement is actually 
[ `uname -r` == "2.x.x-this-script's-desired-version" ] || exit

and since mod-init-tools are in /, you may need to actually replace them all 
with wrapper scripts which call up the right one, passing all command-line 
arguments to the real one... you install the 2.4 utils, move them all (i.e., 
to *-2.4) then the same for 2.6, and make a script with the original name 
that calls the 2.6 binary when uname -r returns a 2.6 kernel, likewise with 
2.4, etc.

even easier: you may be able to get away with this hack:

mount --bind /some-dir/2.6-bin /bin
mount --bind /some-dir/2.6-lib /lib
mount --bind /some-dir/2.6-sbin /sbin
mount --bind /some-dir/2.6-etc /etc
and so on.

do this in a script that starts with that statement above, so that only when 
*your* kernel runs, it maps over the 2.4 kit without touching it.

-- 
Rob Couto [rpc@cafe4111.org]
computer safety tip: use only a non-conducting, static-free hammer.
--

  parent reply	other threads:[~2004-05-30  5:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30  2:13 Younggyun Koh
2004-05-30  5:58 ` Rob
2004-05-30  6:12 ` Rob [this message]
2004-05-30  7:19 ` Andre Tomt

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=200405300112.44866.rpc@cafe4111.org \
    --to=rpc@cafe4111.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

all inboxes | Powered by JetHome®