public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <sofar@foo-projects.org>
To: Steve Brueggeman <xioborg@mchsi.com>
Cc: Akula2 <akula2.shark@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Multi kernel tree support on the same distro?
Date: Thu, 04 Jan 2007 23:30:39 -0800	[thread overview]
Message-ID: <459DFE9F.9050904@foo-projects.org> (raw)
In-Reply-To: <tekrp2tqo78uh6g2pjmrhe0vpup8aalpmg@4ax.com>

Steve Brueggeman wrote:
> There are some difficulties with gcc versions between linux-2.4 and linux-2.6,
> but I do not recall all of the details off of the top of my head.  If I recall
> correctly, one of the issues is, linux-2.4 ?prefers? gcc-2.96, while newer
> linux-2.6 support/prefer gcc-3.? or greater.

gcc 3.4.x works great on both 2.6 and 2.4, no issues whatsoever.

> At any rate, what I've done is create a chroot environment.  I created this
> chroot directory by installing an older distribution that was created with
> linux-2.4 in mind (example, RedHat v8.2) into that at chroot directory.  The
> easiest way to do this that I'm aware of is to install the older distribution
> (minimal development, no server junk, no X junk) on another computer, then copy
> from that computer to a directory on your development computer.

it's even easier to not do that and install and compile everything in one rootfs, which 
is perfectly possible and I have done so many times. You can leave away the chroot and 
any possible security issues that you fear, allthough those are pretty much nonexistant.

The only real bottom line issue is that module-init-tools cannot load modules on a 2.4 
kernel, and modutils doesn't do that on 2.6, so you will have to switch or wrap them to 
detect the running kernel. The same goes for udev vs. devfs.

of course, setting up a qemu image or separate partition is easier, but that was not the 
question I think.

Most binary distro's won't support this, but I think all of the source distro's and more 
specific ones support it and a few handle it out of the box.


Cheers,

Auke

  reply	other threads:[~2007-01-05  7:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 19:46 Multi kernel tree support on the same distro? Akula2
2007-01-04 20:23 ` Kristof Provost
2007-01-05 11:50   ` Akula2
2007-01-05  0:14 ` Auke Kok
2007-01-05  4:28   ` Steve Brueggeman
2007-01-05  7:30     ` Auke Kok [this message]
2007-01-05 12:04       ` Akula2
2007-01-05 12:28         ` Renato S. Yamane
2007-01-05 16:10           ` Auke Kok
     [not found]       ` <8355959a0701050402g673f446em1c263dea826f3bcb@mail.gmail.com>
     [not found]         ` <459E77D9.8080209@foo-projects.org>
2007-01-07  9:13           ` Akula2
2007-01-07  9:30     ` Willy Tarreau
2007-01-07 13:11       ` Akula2
2007-01-07 13:20         ` Willy Tarreau
2007-01-07 14:19           ` Akula2
2007-01-07 14:32             ` Willy Tarreau
2007-01-07 17:52               ` Akula2

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=459DFE9F.9050904@foo-projects.org \
    --to=sofar@foo-projects.org \
    --cc=akula2.shark@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xioborg@mchsi.com \
    /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