| 1 |
Quoting "W.Kenworthy" <billk@×××××××××.au>: |
| 2 |
|
| 3 |
> Rebuild/upgrade on the redundant drive in a chroot |
| 4 |
> Rebuild elsewhere (local to you) on similar hardware and copy OS over. |
| 5 |
> I suspect though, that building a new system, getting it working and |
| 6 |
> shipping it as a black box would be the most low risk/effective |
| 7 |
> strategy. |
| 8 |
> |
| 9 |
> Hint: |
| 10 |
> Setup grub to boot either os so local support only has to select which |
| 11 |
> disk to boot from if there is a failure. |
| 12 |
|
| 13 |
Thanks for the advice. |
| 14 |
|
| 15 |
This may seem a novice question, but can you build a 2.6 kernel and |
| 16 |
use it to boot a system built against 2.4? That is, to divide the |
| 17 |
move into two testable components, kernel and everything else, |
| 18 |
|
| 19 |
1) Build a full new system on the redundant drive with a 2.6 kernel |
| 20 |
2) Copy *just* the kernel over and test it (with a menu in grub as you |
| 21 |
suggest in case it barfs) |
| 22 |
3) If the kernel works, then move the rest over |
| 23 |
|
| 24 |
Or does the kernel change enough between major iterations that you'd |
| 25 |
have to, say, rebuild glibc or somesuch? |
| 26 |
|
| 27 |
Cheers, |
| 28 |
|
| 29 |
-Collin |
| 30 |
|
| 31 |
-- |
| 32 |
Collin Starkweather, Ph.D. |
| 33 |
http://www.linkedin.com/in/collinstarkweather |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-server@l.g.o mailing list |
Archives