1 |
On 25/02/12 16:04, Alan Mackenzie wrote: |
2 |
> Hello, Nikos. |
3 |
> |
4 |
> On Sat, Feb 25, 2012 at 04:10:10AM +0200, Nikos Chantziaras wrote: |
5 |
>> On 25/02/12 04:00, Grant wrote: |
6 |
>>> I need to test a kernel config change on a remote system. Is there a |
7 |
>>> safe way to do this? The fallback thing in grub has never worked for |
8 |
>>> me. When does that ever work? |
9 |
> |
10 |
>> Oh crap, you said "remote system". Somehow I missed that. Ignore my |
11 |
>> previous post since obviously accessing Grub on a remote machine would |
12 |
>> require a hardware VNC module (if you had that, then you wouldn't have |
13 |
>> posted about the issue in the first place, I assume.) |
14 |
> |
15 |
>> The way I dealt with it, is to use the "boot once" functionality of Grub: |
16 |
> |
17 |
>> http://weichong78.blogspot.com/2007/04/grub-test-kernel-once.html |
18 |
> |
19 |
>> I didn't bother with the panic handler, since I had remote hard-reset |
20 |
>> functionality (I recommend it; it can save your day.) |
21 |
> |
22 |
> What is this "remote hard-reset functionality", if you don't mind me |
23 |
> asking? Do you mean somebody on the far end of a telephone line? |
24 |
|
25 |
No, it was a web interface button. It was instant. I assume it either |
26 |
cut the power to the slice or a controller was hooked up to the reset |
27 |
connector. |