On 12/11/09 11:00, Dale wrote:
> Alan McKinnon wrote:
>> On Friday 11 December 2009 17:07:17 Dale wrote:
>>
>>> Alan McKinnon wrote:
>>>
>>>> On Friday 11 December 2009 15:16:01 Dale wrote:
>>>>
>>>>> Rebooting will also do all of this but it is not needed. From a
>>>>> technical stand point, the only time you must reboot is to load a new
>>>>> kernel.
>>>>>
>>>> And these days, not even then :-)
>>>>
>>>> [it requires some voodoo but is certainly possible]
>>>>
>>>> [[and I don't mean build and install a new kernel, I really do mean
>>>> loa
>>>> ti into memory and run it, dispensing with the old one]]
>>>>
>>> I have read about that but never read something from someone who has
>>> actually done it. I have always been curious as to how that would
>>> work,
>>> in reality not just theory.
>>>
>>
>> kexec and CONFIG_RELOCATABLE
>>
>>
>>> I have also wondered why a person would go to all that trouble.
>>> Wouldn't all the services have to be restarted anyway?
>>>
>>
>> Nope. userspace ABI is stable so services just carry on as normal
>> once he new kernel comes up. You don't need to restart SeaMonkey if
>> you restart a local apache on your machine - same thing
>>
>>
>
> That would be cool of you had a system that just couldn't be
> rebooted. Is there such a thing tho? What would be the reason a
> machine just could not be rebooted? I guess one would be if the puter
> was on planet Mars maybe? Is that how NASA does it? lol Could you
> imagine getting a blue screen of death on a computer that is on Mars?
> O_O
>
> Dale
>
> :-) :-)
The closest thing that I have used to not rebooting my machine is kexec,
it completely unloads the current running kernel and then loading the
new kernel in it's place.
