Heat exists outside of transfer. Heat is "thermal density."
Temperature has differing, barely-related meanings as you go up and down the scale of temperatures (e.g., the temperature at the Sun's core isn't really about kinetic energy). The unifying theme is entropy, but the temperature-entropy relationship is somewhat of an emergent property, rather than being fundamental (except for "negative" temperatures, which are only about entropy).
Sure. It's nice if you can use github, since that's your offsite backup, but lot of people can't. The main thing is, your local site is the "backup" of the production server, at least if you can launch a new prod server quickly with a script.
It's a weird dichotomy for MS. Half the time they're either fighting or getting clever to protect customer privacy, yet the other half they're spying on customers to an absurd degree. WTF MS?
MS could have been a real alternative to the Google panopticon had they gone a different way with Win10, but now all trust is gone.
I have to disagree here a bit. Not with the idea of doing backups -- everyone should -- but that's looking at the half problem the wrong way. It's the right solution for customer data, but not for all the code and other materials that make your web site happen.
I've seen this problem a lot: all the work product that makes a web presence happen gets done on the hosted server. That's beyond stupid - that's failing to even understand your job.
All the work that goes into your hosted web site -- your store, your code that aggregates or helps the customer in whatever way makes you valuable, all that stuff -- needs to live in a version control system you control locally. Ideally github, so backups are free, but not everyone can do that. Your entire web presence other than customer data should be pushed from where the real work is done, and of course there should bee a way to revert as well.
When you look at it that way, it's obvious that a key place to replicate your customer data to is close to the machines you do your build/push work from (not the same machines, unless you have strong read-only protection, but close). That way, if your hosting provider takes your site down on a whim, a couple of scripts you already have give you the same web site with the same data at a new hosting provider. That also makes you safe against physical server failure, rm -rf, and anything else that happens in the cloud.
This isn't rocket science, it the minimum standard that separates amateur from professional.
You don't always have internet access, especially in rural areas and at customer sites. Also, non-IT reference books tend to be good for many years, as the laws of physics don't change so fast.
I have enough physical books, thanks. I've spent well north of $10k on books over the years (and still a great deal for the hours of entertainment provided), so $300 is just noise.
The question is: is the reading experience better? The portability of a library on an e-reader does a lot to make up for the problems you mention. The only reasonable cause for avoiding e-readers is that one finds the reading experience less pleasant than physical books. I did for years, until I started wanting a larger font, and then suddenly e-readers were awesome.
I don't care much about the epub, since I'm just reading stuff I bought through Kindle anyhow (if every one is deleted or lost I still have >1000 physical books, more than I know what to do with really). I think this sucks because the screen is tiny. A 6" screen*? Really?
Maybe I'm not their target market. I'm old enough to like a large font (otherwise I'd stick with physical books), and a 7" tablet is too small to have a proper column width with a larger font. Sure, the 6" screen has a better aspect ratio, but it's still not as wide as the text in a hardback book.
Maybe they'll make a bigger one next, but at ~$300 for the small one... eesh.
* Why are we still measuring screens in inches, and not proper standard units, like millifurlongs?
I did mention the constitution there, which everyone is so in the habit of ignoring. But even with a "reasonable" bar, this still wasn't a reasonable search: if the traffic could be tied to a TOR exit node, it's fanciful to imagine some non-TOR cause for the traffic.
Some variants of ransomware erase backup drives and cloud backups/network shares.
If it can be overwritten or erased by the live system it's not a backup. RAID is not a backup strategy. Copying files to a share is not a backup strategy.
A duplicate drive sitting on a shelf is a backup strategy. A tape in a box in is a backup strategy. A cloud-based solution that requires some special admin task to delete old backups is a backup strategy.
real way to solve the problem isn't just having more data for ransomware to encrypt or destroy. Work on pull based backups
No, you must have cause to believe that the specific person probably committed a specific crime for a constitutional search. Everyone might have done every crime, and "possible cause" is no bar at all to clear.
A reward is different. Also, violent crime actually matters, while this theft is only a curiosity (a point well made by the Thomas Crown remake, I thought).
I really hope the money for the reward was funded by the insurance company, not the taxpayer. Otherwise that's taking corporate welfare to a whole new place.
That is what people like Anita often call "disagreement", yes. Though it would be more traditional to call them "blasphemers", since the offense is "disagreeing with what I've arbitrarily decided is the inarguable truth".
That doesn't sound like it could ever be abused...
There have been some eye-opening kernel exploits found using the USB bus, but if that's limited to direct physical access it sound less scary. With this change? Eesh.
This is like a remote control for a chainsaw: it sounds handy, but you know it will end in tears.
There is no evidence of a lack of probable cause though.
Do you understand the difference between "probable" and "might possibly be"? It seems like you don't, but "probable" means "more than 50%". If you know it's a TOR exit node, what are the odds? Ultimately, it's the judge's call, but being a TOR exit node dramatically changes those odds.
I don't expect much from the submitters and editors here, but it's kind of pathetic to see jabs like the "And on the other side of the isle, everyone surely already knows how likely Republican nominee Donald Trump feels about illegal aliens." one in the summary.
What's pathetic is the joke itself. Here, try this one:
Everyone surely already knows how Republican and Reform party governors such as Schwarzenegger and Ventura feel about illegal aliens.
Truck drives jobs will be secure for many years to come. Trucks are expensive - if the AI were ready today it would take 10-20 years. The lawn care business is pretty saturated, but there aren't enough plumbers or electricians or welders or handimen. And it's not like construction-related truck driving is going away in my lifetime.
I've never really understood this admin/developer dichotomy. If you're a developer, don't you need to know how to do admin tasks like install operating systems, manage user accounts, compile software from source and build packages?
Even in devops, I never install an OS or manage a user account - we're too large scale and each of those things is a well-staffed specialty. We do software deployments to quite a large number of machines. If we do it wrong, and take the whole fleet down due to a bug, it costs us hundreds of dollars per minute (so we're sort of medium-scale). There's a whole career around managing deployments and patching responsibly, ensuring you don't break anything, and if anything breaks on it's own, you're paged within a few minutes. (DBA? What is this, the 20th century?)
We have elaborate automated toolchains for each of those things, as every big enough company does. But nothing is idiot-proof, especially when it comes to "OK, it's broke and it's 4AM - what do you do next?"
Allowing inexperienced people to touch a production environment is a recipe for outages
You'd think that would be obvious, wouldn't you?
DevOps should be staffed with people who are experienced admins _and_ developers.
What, not staff up mostly with new college hires on H1-Bs? Who's going to pay for that? Not an MBA, that's for sure.
Slashdot Mirror
Heat exists outside of transfer. Heat is "thermal density."
Temperature has differing, barely-related meanings as you go up and down the scale of temperatures (e.g., the temperature at the Sun's core isn't really about kinetic energy). The unifying theme is entropy, but the temperature-entropy relationship is somewhat of an emergent property, rather than being fundamental (except for "negative" temperatures, which are only about entropy).
Sure. It's nice if you can use github, since that's your offsite backup, but lot of people can't. The main thing is, your local site is the "backup" of the production server, at least if you can launch a new prod server quickly with a script.
It's a weird dichotomy for MS. Half the time they're either fighting or getting clever to protect customer privacy, yet the other half they're spying on customers to an absurd degree. WTF MS?
MS could have been a real alternative to the Google panopticon had they gone a different way with Win10, but now all trust is gone.
I have to disagree here a bit. Not with the idea of doing backups -- everyone should -- but that's looking at the half problem the wrong way. It's the right solution for customer data, but not for all the code and other materials that make your web site happen.
I've seen this problem a lot: all the work product that makes a web presence happen gets done on the hosted server. That's beyond stupid - that's failing to even understand your job.
All the work that goes into your hosted web site -- your store, your code that aggregates or helps the customer in whatever way makes you valuable, all that stuff -- needs to live in a version control system you control locally. Ideally github, so backups are free, but not everyone can do that. Your entire web presence other than customer data should be pushed from where the real work is done, and of course there should bee a way to revert as well.
When you look at it that way, it's obvious that a key place to replicate your customer data to is close to the machines you do your build/push work from (not the same machines, unless you have strong read-only protection, but close). That way, if your hosting provider takes your site down on a whim, a couple of scripts you already have give you the same web site with the same data at a new hosting provider. That also makes you safe against physical server failure, rm -rf, and anything else that happens in the cloud.
This isn't rocket science, it the minimum standard that separates amateur from professional.
You don't always have internet access, especially in rural areas and at customer sites. Also, non-IT reference books tend to be good for many years, as the laws of physics don't change so fast.
I have enough physical books, thanks. I've spent well north of $10k on books over the years (and still a great deal for the hours of entertainment provided), so $300 is just noise.
The question is: is the reading experience better? The portability of a library on an e-reader does a lot to make up for the problems you mention. The only reasonable cause for avoiding e-readers is that one finds the reading experience less pleasant than physical books. I did for years, until I started wanting a larger font, and then suddenly e-readers were awesome.
I don't care much about the epub, since I'm just reading stuff I bought through Kindle anyhow (if every one is deleted or lost I still have >1000 physical books, more than I know what to do with really). I think this sucks because the screen is tiny. A 6" screen*? Really?
Maybe I'm not their target market. I'm old enough to like a large font (otherwise I'd stick with physical books), and a 7" tablet is too small to have a proper column width with a larger font. Sure, the 6" screen has a better aspect ratio, but it's still not as wide as the text in a hardback book.
Maybe they'll make a bigger one next, but at ~$300 for the small one ... eesh.
* Why are we still measuring screens in inches, and not proper standard units, like millifurlongs?
I did mention the constitution there, which everyone is so in the habit of ignoring. But even with a "reasonable" bar, this still wasn't a reasonable search: if the traffic could be tied to a TOR exit node, it's fanciful to imagine some non-TOR cause for the traffic.
Some variants of ransomware erase backup drives and cloud backups/network shares.
If it can be overwritten or erased by the live system it's not a backup. RAID is not a backup strategy. Copying files to a share is not a backup strategy.
A duplicate drive sitting on a shelf is a backup strategy. A tape in a box in is a backup strategy. A cloud-based solution that requires some special admin task to delete old backups is a backup strategy.
real way to solve the problem isn't just having more data for ransomware to encrypt or destroy. Work on pull based backups
Indeed.
No, you must have cause to believe that the specific person probably committed a specific crime for a constitutional search. Everyone might have done every crime, and "possible cause" is no bar at all to clear.
A reward is different. Also, violent crime actually matters, while this theft is only a curiosity (a point well made by the Thomas Crown remake, I thought).
Thomas Crown was not available for comment.
I really hope the money for the reward was funded by the insurance company, not the taxpayer. Otherwise that's taking corporate welfare to a whole new place.
That is what people like Anita often call "disagreement", yes. Though it would be more traditional to call them "blasphemers", since the offense is "disagreeing with what I've arbitrarily decided is the inarguable truth".
Possible, possible, possible, but not probable, which is the question.
Your penerdantry is interfering with your daily life.
"USB" by itself is ambiguous - there are USB devices, USB controllers, USB hubs, and, yes, the USB bus itself.
Are you seriously proposing that someone operating a TOR exit node would then go on to do something sketchy without using TOR?
That doesn't sound like it could ever be abused...
There have been some eye-opening kernel exploits found using the USB bus, but if that's limited to direct physical access it sound less scary. With this change? Eesh.
This is like a remote control for a chainsaw: it sounds handy, but you know it will end in tears.
There is no evidence of a lack of probable cause though.
Do you understand the difference between "probable" and "might possibly be"? It seems like you don't, but "probable" means "more than 50%". If you know it's a TOR exit node, what are the odds? Ultimately, it's the judge's call, but being a TOR exit node dramatically changes those odds.
Nice! Really hoping the Model 3 works out well - just because everything Tesla is overhyped doesn't prevent it from actually being good.
I don't expect much from the submitters and editors here, but it's kind of pathetic to see jabs like the "And on the other side of the isle, everyone surely already knows how likely Republican nominee Donald Trump feels about illegal aliens." one in the summary.
What's pathetic is the joke itself. Here, try this one:
Everyone surely already knows how Republican and Reform party governors such as Schwarzenegger and Ventura feel about illegal aliens.
There, was that so hard?
Truck drives jobs will be secure for many years to come. Trucks are expensive - if the AI were ready today it would take 10-20 years. The lawn care business is pretty saturated, but there aren't enough plumbers or electricians or welders or handimen. And it's not like construction-related truck driving is going away in my lifetime.
That's pretty crazy even by /. conspiracy theory standards.
I've never really understood this admin/developer dichotomy. If you're a developer, don't you need to know how to do admin tasks like install operating systems, manage user accounts, compile software from source and build packages?
Even in devops, I never install an OS or manage a user account - we're too large scale and each of those things is a well-staffed specialty. We do software deployments to quite a large number of machines. If we do it wrong, and take the whole fleet down due to a bug, it costs us hundreds of dollars per minute (so we're sort of medium-scale). There's a whole career around managing deployments and patching responsibly, ensuring you don't break anything, and if anything breaks on it's own, you're paged within a few minutes. (DBA? What is this, the 20th century?)
We have elaborate automated toolchains for each of those things, as every big enough company does. But nothing is idiot-proof, especially when it comes to "OK, it's broke and it's 4AM - what do you do next?"
Allowing inexperienced people to touch a production environment is a recipe for outages
You'd think that would be obvious, wouldn't you?
DevOps should be staffed with people who are experienced admins _and_ developers.
What, not staff up mostly with new college hires on H1-Bs? Who's going to pay for that? Not an MBA, that's for sure.