Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Friday February 17 2017, @08:07AM   Printer-friendly
from the they-didn't-want-to-interrupt-our-anniversary-party dept.

Following an initial report that Microsoft's Patch/Update Tuesday would be delayed comes the notice that it will actually be postponed. Oh, and there is a zero-day SMB exploit currently in the wild for which Microsoft intended to release a patch last Tuesday. That fix, and all the others scheduled for February, have been postponed to be released on March's Patch Tuesday.

Here are some stories that lay things out:

Many businesses have regular processes in place to test and roll out patches on their systems; how has this postponement affected you?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Friday February 17 2017, @08:37PM

    by Anonymous Coward on Friday February 17 2017, @08:37PM (#468331)

    Linux would never even take an hour to determine what it needs, even on a rusty Pentium III with a dying hard disk

    I just don't understand people who tolerate the MICROS~1 update paradigm.
    Having M$ take over your box, leaving it unusable for long periods (hours?; days??) is just insane.
    We previously discussed an actual example of that paradigm of unwanted, invasive, clumsy updating.
    German Basketball Team Relegated to Lower Division Due to Untimely Windows Updates [soylentnews.org]

    It never was a proper way to do things.
    ...and the Windoze Registry was a horrible idea from the very start.
    Needing to restart the OS for a minor tweak or an added app??
    How could anyone ever think that was a proper design choice?
    It makes me cringe whenever I see Windoze on a box in a medical environment.
    It's frightening to think what might happen in the middle of a procedure.

    With Linux, the download for an update is a background process and the installation is a separate process and, again, a -background- process.
    Not only does it not grab total control of your system, you can wait so that the update doesn't even take away that tiny bit of resources from what you are doing; you can execute the update when you are away from the box, giving it maximum resources (in the PIII example).
    ...and, as you note, Linux updates don't take an eternity to finish.

    It must be awful having a jones for a Windoze-only game that simply must be satiated and having to deal with the associated MICROS~1 nonsense.

    -- OriginalOwner_ [soylentnews.org]