| 1 |
On Feb 25, 2012 9:14 AM, "Grant" <emailgrant@×××××.com> wrote: |
| 2 |
> |
| 3 |
> >> I need to test a kernel config change on a remote system. Is there a |
| 4 |
> >> safe way to do this? The fallback thing in grub has never worked for |
| 5 |
> >> me. When does that ever work? |
| 6 |
> > |
| 7 |
> > |
| 8 |
> > You can press ESC in the Grub screen and it will take you to text-only |
| 9 |
mode. |
| 10 |
> > There, you select an entry, press "e" and edit it. Press ENTER when |
| 11 |
you're |
| 12 |
> > finished, and then press "b" to boot your modified entry. |
| 13 |
> > |
| 14 |
> > That way, you can boot whatever kernel you want if the current one |
| 15 |
doesn't |
| 16 |
> > work. |
| 17 |
> |
| 18 |
> I can't do that remotely though. I'm probably asking for something |
| 19 |
> that doesn't exist. |
| 20 |
> |
| 21 |
> - Grant |
| 22 |
> |
| 23 |
|
| 24 |
Situations like these that made me decide with great conviction to always |
| 25 |
deploy my servers virtualized, even if the box in question will only host a |
| 26 |
single VM. |
| 27 |
|
| 28 |
Now, if I lost my intelligence for a couple of seconds and somehow ended up |
| 29 |
with a VM that's no longer accessible remotely, I just connect to the |
| 30 |
virtual console. |
| 31 |
|
| 32 |
The flip side? Now I'm getting too daring/careless, and the uptime now |
| 33 |
drops below my (self-imposed) target of 99.99% :-P |
| 34 |
|
| 35 |
Rgds, |
Archives