There seem to be two types of such humans: security guards for the building, who are very underpaid and unlikely to take sick days, their companies can replace them quickly. And cheeful pretty women with curves, who are still effective first contacts for making people feel welcome.
[...]
My father taught me "make friends with these people", and I *always* make friends with them and the cleaning staff. They work there, they're often treated like furniture, and they know material that the board and HR keep behind very poorly managed masks of confidentiality.
These people also typically have unbelievable levels of security accesse. They can be powerful allies.
Apple, Monster, Beats, an ex hedge fund manager turned headphone designer... This reads like a Marvel comic with only supervillains in it.
Or the start of a joke: Apple, Monster, Beats, and an ex hedge fund manager turned headphone designer walk into a bar...
While poorly written, I think the author was suggesting that any model of SSD for which the Linux kernel has specific special handling logic should be avoided. In my opinion, it is not an unreasonable statement.
It probably is an unreasonable statement. If Linux has special logic to handle the drive, then someone else probably already had the problem and now there's a fix in so it probably won't happen to you.
Perhaps. But if the drive was broken and someone had to write special software to fix it, how can you be sure that it was fixed correctly and completely? Can you also be sure that the "fix" works for all versions of firmware on the drive? While you might be confident of these things, I would suggest that it would be better to use a drive that follows the standards and doesn't require special code to make it work right. Granted that as always, your mileage may vary -- and it could vary in either direction.
"we don't recommend anyone to use any SSD that is anyhow mentioned in a bad way by the Linux kernel"
???? SERIOUSLY???
While poorly written, I think the author was suggesting that any model of SSD for which the Linux kernel has specific special handling logic should be avoided. In my opinion, it is not an unreasonable statement.
Wouldn't a simple wheel odometer work just fine for this? All you're tracking is miles traveled.
No, because that's not all you're tracking. You're tracking the miles traveled *in Oregon*. Oregon can't tax anything outside Oregon, that violates the US Constitution. So they have to prove to a reasonable standard that all the mileage they're taxing was driven in Oregon.
To add, for those who haven't looked at a map, the Portland metropolitan area, which is where the bulk of population in Oregon lives, is right on the border with Washington state. A large number of people commute and and regularly travel between Oregon and Washington. Any state level taxing solution needs to account for this.
The vulnerable code is used in Xen, KVM, and VirtualBox, while VMware, Hyper-V, and Bochs are unaffected. "Dan Kaminsky, a veteran security expert and researcher, said in an email that the bug went unnoticed for more than a decade because almost nobody looked at the legacy disk drive system, which happens to be in almost every virtualization software."
I note that the two proprietary systems were not impacted. Of course all software has bugs and vulnerabilities without regard to open source or proprietary, but here on slashdot we like think that open source is always the better option. This is not always the case.
The phrase "almost every virtualization software" is used, but the list of items given has three pieces of software that are impacted and three that are not. In terms of virtualization systems that are in production use by business, I would think that VMware and Hyper-V would take the lion's share (as they are commercial and "supported"), thus being a candidate for "almost every". I think the phrase should have been "almost every open source virtualization software".
Great idea. My power supplier currently has rates based on TOU (Time Of Use - http://www.torontohydro.com/si...), and I'd love to be able to charge up the battery supply for my house overnight at cheap rates, then run off the battery the rest of the time.
Are your night rates less than half of your day rates? I ask because battery charging isn't 100% efficient. I don't know the charging efficiency of the Tesla packs, but many battery types are only around 50% efficient in charging. By 50% efficient, I mean when charging you put in about twice as much energy as you can take back out later.
He has a team that will be with him providing supplies as needed. So would guess he will have generators, toilet, cooking heat source,elsewhere when not using those will stay in his ball.
I didn't get that from the articles. I read the following:
This is a precarious idea. Bellini will be completely isolated, and his adopted dwelling is liable to roll or fall apart at any moment, thrusting him into the icy sea or crushing him under hundreds of tons of ice.
The article may, of course, be incorrect, but from what I have read it appears he will be alone. If he is not alone, and he has a support team, How would the support team keep safe in the event that the iceberg they are all on collapses or tips over? I ask because the article talks about how he has to spend practically all of his time in the ball because the iceberg could tip over at any moment.
Bellini will spend almost all of his time in the capsule with the hatch closed, which will pose major challenges. He’ll have to stay active without venturing out onto a slippery, unstable iceberg. If it flips, he’ll have no time to react.
I would buy that Bellini or he and his team plan to live on an iceberg as it melts and collapses and their plan to survive during the actual collapse is to take refuge in survival balls, but I have a hard time believing what the article implies to me -- that he would live for a year within and be sustained solely by a survival ball.
It is easier to change the specification to fit the program than vice versa.