| 1 |
The other way around - update the toolchain first. That is gcc, |
| 2 |
binutils, glibc, ... |
| 3 |
|
| 4 |
When this is all working do a emerge world -ep to make sure everything |
| 5 |
is up to date for 2.4 (Dont forget the expat upgrade gotchas - read the |
| 6 |
guide!) Use revdep-rebuild liberally! |
| 7 |
|
| 8 |
Then do the kernel and reboot |
| 9 |
|
| 10 |
Then bring up anything that was held back by 2.4. |
| 11 |
|
| 12 |
It will actually be the toolchain (and probably expat) that will cause |
| 13 |
the most grief! Stay with a 3.x series gcc until the end - there are |
| 14 |
upgrade guides if you want a 4 series, but wait. |
| 15 |
|
| 16 |
I did this some time back on a large system (~1000 packages) and it does |
| 17 |
work - and the system can stay online for almost all of it as well. If |
| 18 |
you have a relatively small system, it is much easier and quicker as |
| 19 |
there are far fewer complications. |
| 20 |
|
| 21 |
BillK |
| 22 |
|
| 23 |
On Tue, 2008-02-12 at 05:00 -0700, Collin Starkweather wrote: |
| 24 |
> Quoting "W.Kenworthy" <billk@×××××××××.au>: |
| 25 |
> |
| 26 |
> > Rebuild/upgrade on the redundant drive in a chroot |
| 27 |
> > Rebuild elsewhere (local to you) on similar hardware and copy OS over. |
| 28 |
> > I suspect though, that building a new system, getting it working and |
| 29 |
> > shipping it as a black box would be the most low risk/effective |
| 30 |
> > strategy. |
| 31 |
> > |
| 32 |
> > Hint: |
| 33 |
> > Setup grub to boot either os so local support only has to select which |
| 34 |
> > disk to boot from if there is a failure. |
| 35 |
> |
| 36 |
> Thanks for the advice. |
| 37 |
> |
| 38 |
> This may seem a novice question, but can you build a 2.6 kernel and |
| 39 |
> use it to boot a system built against 2.4? That is, to divide the |
| 40 |
> move into two testable components, kernel and everything else, |
| 41 |
> |
| 42 |
> 1) Build a full new system on the redundant drive with a 2.6 kernel |
| 43 |
> 2) Copy *just* the kernel over and test it (with a menu in grub as you |
| 44 |
> suggest in case it barfs) |
| 45 |
> 3) If the kernel works, then move the rest over |
| 46 |
> |
| 47 |
> Or does the kernel change enough between major iterations that you'd |
| 48 |
> have to, say, rebuild glibc or somesuch? |
| 49 |
> |
| 50 |
> Cheers, |
| 51 |
> |
| 52 |
> -Collin |
| 53 |
> |
| 54 |
> -- |
| 55 |
> Collin Starkweather, Ph.D. |
| 56 |
> http://www.linkedin.com/in/collinstarkweather |
| 57 |
> |
| 58 |
-- |
| 59 |
William Kenworthy <billk@×××××××××.au> |
| 60 |
Home in Perth! |
| 61 |
-- |
| 62 |
gentoo-server@l.g.o mailing list |
Archives