From: Andrew Gaffney <agaffney@gentoo.org>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Challenging Update Question
Date: Tue, 12 Feb 2008 06:17:13 -0600 [thread overview]
Message-ID: <47B18E49.6070201@gentoo.org> (raw)
In-Reply-To: <20080212050049.t5rxg319w8ws4ccs@webmail.collinstarkweather.com>
Collin Starkweather wrote:
> This may seem a novice question, but can you build a 2.6 kernel and use
> it to boot a system built against 2.4? That is, to divide the move into
> two testable components, kernel and everything else,
This will probably bite you in the ass. Most notably, support for devfs was
dropped around 2.6.13, so unless you are managing a static /dev, you're going to
need udev. However, I'm not sure if the baselayout from that long ago had any
notion of udev or if you can even build udev while running a 2.4 kernel (this is
probably less of an issue).
Really, the "best" way to do this is to just do a new install on the second
drive. However, you might have some of the problems noted above, since you're
still running a 2.4 kernel while building a system intended for 2.6.
I guess that your only remaining "sane" option is to build a new install on a
"local" machine, and then rsync the entire thing over to the 2nd drive in your
existing machine. Then setup grub to boot from the install on the 2nd drive by
default.
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
--
gentoo-server@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-12 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 6:30 [gentoo-server] Challenging Update Question Collin Starkweather
2008-02-12 6:38 ` RijilV
2008-02-12 7:13 ` W.Kenworthy
2008-02-12 12:00 ` Collin Starkweather
2008-02-12 12:17 ` Andrew Gaffney [this message]
2008-02-12 12:18 ` William Kenworthy
2008-02-12 13:13 ` Benjamen R. Meyer
2008-02-12 19:44 ` Randy Barlow
2008-02-12 20:34 ` RijilV
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=47B18E49.6070201@gentoo.org \
--to=agaffney@gentoo.org \
--cc=gentoo-server@lists.gentoo.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