Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: Restarting after a security update...?

  1. #11

    Default Re: Restarting after a security update...?

    So these people that are suspending/hibernating aren't really getting the security updates? Which is what I was getting at. I suspect a few laptop owners resort to them frequently.

    Still not really sure on the answer, with your answer.
    Man first, have a try at Info, have a look at Wiki, if all that fails Scroogle!!!!!
    If I've helped click on the Rep button I don't know what it does but it sounds cool.

  2. #12
    Join Date
    Jun 2008
    Location
    UTC+10
    Posts
    9,686
    Blog Entries
    4

    Default Re: Restarting after a security update...?

    They'll get them the next time they resume the machine, provided it's on long enough for the updater applet to run and online of course.

    Look at it this way, a suspended machine is no different from an off machine, only it has a fast way of getting back to the state it was in before the shutdown.

  3. #13

    Default Re: Restarting after a security update...?

    But my understanding is it is reinstating the libs and apps too, which you sort of pointed out about not reverting to an old edit.

    Surely this would mean my app wouldn't open the same if it had changed the libs/app. Surely it is the same as the above not wanting to reboot.

    My understanding is we're grabbing the ram with hibernating dropping that to swap. When reinstating we drop the swap back into ram am I wrong then?
    Man first, have a try at Info, have a look at Wiki, if all that fails Scroogle!!!!!
    If I've helped click on the Rep button I don't know what it does but it sounds cool.

  4. #14
    Join Date
    Jun 2008
    Location
    UTC+10
    Posts
    9,686
    Blog Entries
    4

    Default Re: Restarting after a security update...?

    It's resumed from the point of the suspend. It's not resumed at any old point. If the updates had already been applied, they would be there. If you had not applied any updates before suspending, then it's ready for updates. That's why I said it's no different from the case of turning off your machine, package-wise. As for what happens in RAM, it's like you resumed, as advertised. It's not a shutdown, so you could still be using the old deleted libraries, but only for running processes, not new ones yet to be started. The advice that came with glib said restart the machine, not suspend and resume the machine.

    If I pull the power cord from my machine and go on holiday for 3 months, obviously when I turn the machine back on it's going to be 3 months behind in updates. Perhaps the updater applet should yell "Waitaminute waitaminute, don't do anything, lemme update you first" .

    Looking further ahead, one could imagine a really smart updater that would say "Hang on, I see you are using SUSE 9.3. This is out of support. I will shut you down now." Then we don't have to advise people who try to use old distros not to do so. This will really be a hit with the users. Not!

    But your point about snapshots is valid in the case of virtual machines like VirtualBox where one can take snapshots. If you resume from an old snapshot, obviously it's not going to have updates since you're going back in time. And the irony is that this is promoted as a way to get back to a pre-virus state for Windows.

  5. #15

    Default Re: Restarting after a security update...?

    Thank you for the time and the explanation.

    I'm just terrible for wanting to know how it all works and been fighting the Suspend/Hibernate battle today so was a little fresh(I won't bring hal into it).
    Man first, have a try at Info, have a look at Wiki, if all that fails Scroogle!!!!!
    If I've helped click on the Rep button I don't know what it does but it sounds cool.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •