| 1 |
On Thu, 23 Feb 2012 13:16:41 +0200 |
| 2 |
Coert Waagmeester <lgroups@××××××××××××××.za> wrote: |
| 3 |
|
| 4 |
> > Not doing it this way means a very high likelyhood of the machine |
| 5 |
> > not booting with every single upgrade, plus the huge amount of work |
| 6 |
> > it takes to go through everything in menuconfig. |
| 7 |
> |
| 8 |
> indeed, especially when the server is stuck in a far away rack. |
| 9 |
|
| 10 |
Ooooooooooh, those are the scary ones. |
| 11 |
|
| 12 |
Two excellent things can help with that: |
| 13 |
|
| 14 |
A proper RAC setup, or |
| 15 |
Copy the debian boot scheme, where is a kernel won't boot, it panics |
| 16 |
and times out after 30 seconds. Grub then automagically boots the |
| 17 |
previous working kernel. |
| 18 |
|
| 19 |
Just don't do what I did earlier: sit in Joburg and configure the |
| 20 |
firewall on a Xen host in deepest darkest Africa where there's no |
| 21 |
tarred roads to get to it. Check the iptables config three times, |
| 22 |
plus get your colleagues to look it over as well. We all signed off on |
| 23 |
it. |
| 24 |
|
| 25 |
Guess what? Yup, you got it. We all missed something and now we are |
| 26 |
locked out. Remember, it's in deepest darkest Africa. |
| 27 |
|
| 28 |
<sigh> |
| 29 |
|
| 30 |
-- |
| 31 |
Alan McKinnnon |
| 32 |
alan.mckinnon@×××××.com |
Archives