public inbox for linux-kernel@vger.kernel.org
 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 00:58:28 -0500	[thread overview]
Message-ID: <200405300058.28834.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.
>
> is there any way i can make different system tools installed when i boot
> with the different kernel images other than mounting root directory to the
> different partitions? (i can't create a new partition)
>
> thank you,
>
> 			-Younggyun Koh (young@cc.gatech.edu)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

i was thinking about this... my brute force idea:
make some very early init scripts manipulate a bunch of symlinks, based on the 
output of uname -r. you have a different kernel, it renames some dirs, and 
goes on as normal. in fact, you oughta be able to have a few separate init 
script kits that all run but immediately exit if their designated kernel 
isn't running, like  `uname -r`= "2.6.6-test1" || exit
 
-- 
Rob Couto [rpc@cafe4111.org]
computer safety tip: use only a non-conducting, static-free hammer.
--

  reply	other threads:[~2004-05-30  4:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30  2:13 seperate environments for different kernels Younggyun Koh
2004-05-30  5:58 ` Rob [this message]
2004-05-30  6:12 ` Rob
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=200405300058.28834.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