SoylentNews is people
SoylentNews
SoylentNews first reported the vulnerabilities on January 3. Since then, we have had a few stories addressing different reports about these vulnerabilities. Now that it is over two weeks later and we are *still* dealing with reboots, I am curious as to what our community's experience has been.
What steps have you taken, if any, to deal with these reports? Be utterly proactive and install every next thing that comes along? Do a constrained roll out to test a system or two before pushing out to other systems? Wait for the dust to settle before taking any steps?
What providers (system/os/motherboard/chip) have been especially helpful... or non-helpful? How has their response affected your view of that company?
What resources have you been using to check on the status of fixes for your systems? Have you found a site that stands above the others in timeliness and accuracy?
How has this affected your purchasing plans... and your expectations on what you could get for selling your old system? Are you now holding off on purchasing something new?
(Score: 2) by inertnet on Friday January 19 2018, @05:10PM (1 child)
After some Linux updates I thought all my VM's were bricked because of these issues, but a more recent Virtualbox version fixed everything again. I don't know if this was related to a Meltdown/Spectre security fix, but because of the timing I have to assume so. Ubuntu 16.10 repositories still have the old bricking Virtualbox version as far as I can tell.
(Score: 0) by Anonymous Coward on Friday January 19 2018, @06:42PM
This was my hairloss experience most of last week. After the kernel patch arrived, every time I started up any VM it would freeze the entire machine (host), leave no logs and no other way out than the power button. Then I found a thread that was auto-dismissed by the moderators on a tech site which I won't name, but below their terse silliness lay a reply with the answer. I had even removed Vbox and re-installed from the repos, something like 5.0.24 .. but the solution was to get Oracle's 5.2 release directly.