Only if we were deliberately choosing to buy oil from people we knew were operating in a way as to be dangerous.
I won't speak for you, but I'd suggest a month ago most people had no idea there was the potential for such a thing to happen and go so long without being fixed. BP Management, however, did. If they had have come out and told me then - fine - they didn't, so they get to carry the can by themselves.
A Jehovah's Witness is one who would claim you are not a Christian, as they would anyone not a member of theirs. (I'm just sayin' - I have no doubt of your good faith myself).
Mind you, they wouldn't be seen having anything to do with any government department in this manner either - at least not directly or overtly.
I like the idea of TrueCrypt but what I find horrifying is how my (hypothetical) Judge / Jury will understand it, how the media will portray it, and ultimately Joe Sixpack's understanding of it, which will probably wind up being something along the lines of "It's a devil's homo machine"
Oh, look, another person who thinks he just learned what 'Straw man' means.
You don't think the act of a government sending its soldiers to war (keep me out of the morality of this, I'm just pointing out your logical failing) is an implicit declaration of "We're okay with this"?
On the other hand you might confuse the customs officials, and make them wonder why you're transporting an ostensibly broken laptop computer. I wonder how that might work out for you?
Yes, of course. You're exceedingly intelligent - in the top 5% in fact - because you've learned an Object Oriented Programming Language, and applied parts of its lexicon to real life, thereby changing the definition of the law, at least in the minds of yourself and the lucky 5%. The lucky 5% who understand that computers conceive themselves, install suitable radios and take to the streets cataloguing data. 95% of use don't realise that it doesn't take a human with intent for this to happen.
listening == using ones auditory senses, it only applies metaphorically to computer operations. To most people, listening to something absolutely means accessing (or "having" access to) it.
Let me guess, you also interpret DHCPOFFER packets literally as a legal invitation as well. You're in for a nasty fright when you find out you use such words quite differently to 95% of the population.
I wish you'd somehow made your point more politely, because there is actually at least some substance to your otherwise caustic and arrogant remark.
I think what is needed the most in the way of Documentation is somehow getting rid of the old stuff, all those HOWTO's, and so on. Many of them still show up in searches for common problems, with incorrect or suboptimal solutions for today's kernels and baselayouts. The "Last modified" date is a clue to the wise, but the learner has no way of knowing that docs written 8 or so years ago are sometimes very counter-productive.
Spending a few minutes on my distros IRC channel I really is disenchanting seeing how many people immediately leap to IRC for help on the the stuff that actually is documented well and easy to find. You wonder, even if documentation were more complete, what difference would it make? Half the people who don't need the documentation end up arguing over how it's written and other stupid details, and the people who do need it don't read it.
Crap: Even with a two-disk JBOD (and either one failing), and any well known filesystem, you've got a very good chance of getting 45-50% of your data back (assuming the files are relatively small compared to the size of the disk). Sure, it's not a simple as mounting what you've got left and copying it, but it's certainly a job I'd take on for a couple of Benjamins.
If the data is there (on the unfailed disk) then the only thing separating it and you is your determination and patience. Or your resources, in the form of contracting a specialist.
I'm not advocating JBOD at all - I'm just saying contingency recovery prospects are relatively good. With Raid0, unless you've got lots of useful files that are smaller than the RAID stripe size (and aligned with it) even the "Best Case" scenario is utterly useless.
Of course, he would have to use WinRar or Master Splitter for all those 1080p movies - according to the Wikipedia link, your maximum filesize with a GDrive is 25 meg.
The splitting of files is not something peculiar to WinRar and Master Splitter, many applications natively support splitting, especially when they deal with large files, sometimes on filesystems that are limited to 2GB files. It'd be trivial to write an abstraction filesystem that takes care of the segmentation and reassembly, chances are this is already done since the splitting of files into smaller chunks is something that has been done since the beginning of time for all sorts of reasons from Floppy backup/sneakernetting to EPROM burning in the old days, and Thumbdrives and DVDs today. Using APIs such as Linux FUSE you can get kernel support for such things without even rebooting.
It would depend on the video codec used, some codecs like DV could handle an entire chunk being zeroed out, and the frames neighboring that chunk would still be accessible, because all compression is "intra-frame". Other codecs not so much, but a DVD MPEG-2 VOB file with a 'hole in the middle' should still be somewhat recoerable, as long as whatever you're using to play it back doesn't give up the instant it encounters the hole.
I find this very hard to believe. Disable the ABS system maybe, but the brake system is designed to work above all else - if a computer can disable the brakes that suggests a malfunction can too.
To be honest, I believe the the case you're discussing is far more serious.
I don't really know why there are so many accidents with loaded guns, but I know I'm not missing something here: It is so easy to disable a gun from firing by removing the ammunition, rendering it no more harmful than a brick, with no chance of accidentally re-enabling it. We can't reasonably operate cars in this manner, however if you don't know how to safety and unload your own firearm, it's unquestionably in the wrong hands.
Maybe I haven't got your story straight, maybe he accidentally fired while unloading and checking before cleaning - sorry if this is the case. And I do hear you clearly on the disparity in people's thoughts on the dangers of guns versus cars, there's been a lot of hype and BS. And while I don't consider either of them to be "killing machines", there's one thing for sure about a gun, they do nothing but harm to what they're used on (unlike cars) whether or not that is desirable, and are designed to be easily safetied in light of that fact.
For example, a buffer overrun in a desktop app (excel, photoshop, whatever) is not a security breach, it's just annoying.
Bad choice of examples. That's what we were saying and thinking in 1998: IT to PHB: "Don't open any EXE files mailed to you, however Excel spreadsheets, Word docs etc, are fine".
A exploitable buffer overrun in any application where malicious inputs exist is a security hole.
What utterly unhelpful pedantry, calm down. When you compare "Open source" and "proprietary software" in the same sentence, most reasonable people know what you mean.
Slashdot Mirror
Okay, seen that term three times in this thread - can't find it on Google. What the hell is a "Bumper Check"?
Or don't, and say you did.
I won't speak for you, but I'd suggest a month ago most people had no idea there was the potential for such a thing to happen and go so long without being fixed. BP Management, however, did. If they had have come out and told me then - fine - they didn't, so they get to carry the can by themselves.
Mind you, they wouldn't be seen having anything to do with any government department in this manner either - at least not directly or overtly.
I like the idea of TrueCrypt but what I find horrifying is how my (hypothetical) Judge / Jury will understand it, how the media will portray it, and ultimately Joe Sixpack's understanding of it, which will probably wind up being something along the lines of "It's a devil's homo machine"
You don't think the act of a government sending its soldiers to war (keep me out of the morality of this, I'm just pointing out your logical failing) is an implicit declaration of "We're okay with this"?
On the other hand you might confuse the customs officials, and make them wonder why you're transporting an ostensibly broken laptop computer. I wonder how that might work out for you?
You've been watching the news too much - and when someone else says "porn" you only hear "child porn"
Yes, of course. You're exceedingly intelligent - in the top 5% in fact - because you've learned an Object Oriented Programming Language, and applied parts of its lexicon to real life, thereby changing the definition of the law, at least in the minds of yourself and the lucky 5%. The lucky 5% who understand that computers conceive themselves, install suitable radios and take to the streets cataloguing data. 95% of use don't realise that it doesn't take a human with intent for this to happen.
Let me guess, you also interpret DHCPOFFER packets literally as a legal invitation as well. You're in for a nasty fright when you find out you use such words quite differently to 95% of the population.
I think what is needed the most in the way of Documentation is somehow getting rid of the old stuff, all those HOWTO's, and so on. Many of them still show up in searches for common problems, with incorrect or suboptimal solutions for today's kernels and baselayouts. The "Last modified" date is a clue to the wise, but the learner has no way of knowing that docs written 8 or so years ago are sometimes very counter-productive.
Spending a few minutes on my distros IRC channel I really is disenchanting seeing how many people immediately leap to IRC for help on the the stuff that actually is documented well and easy to find. You wonder, even if documentation were more complete, what difference would it make? Half the people who don't need the documentation end up arguing over how it's written and other stupid details, and the people who do need it don't read it.
Heh, not quite the same, but I used to turn the Air Conditioning on-then-off to create "Markers" in the data log.
If the data is there (on the unfailed disk) then the only thing separating it and you is your determination and patience. Or your resources, in the form of contracting a specialist.
I'm not advocating JBOD at all - I'm just saying contingency recovery prospects are relatively good. With Raid0, unless you've got lots of useful files that are smaller than the RAID stripe size (and aligned with it) even the "Best Case" scenario is utterly useless.
The splitting of files is not something peculiar to WinRar and Master Splitter, many applications natively support splitting, especially when they deal with large files, sometimes on filesystems that are limited to 2GB files. It'd be trivial to write an abstraction filesystem that takes care of the segmentation and reassembly, chances are this is already done since the splitting of files into smaller chunks is something that has been done since the beginning of time for all sorts of reasons from Floppy backup/sneakernetting to EPROM burning in the old days, and Thumbdrives and DVDs today. Using APIs such as Linux FUSE you can get kernel support for such things without even rebooting.
It would depend on the video codec used, some codecs like DV could handle an entire chunk being zeroed out, and the frames neighboring that chunk would still be accessible, because all compression is "intra-frame". Other codecs not so much, but a DVD MPEG-2 VOB file with a 'hole in the middle' should still be somewhat recoerable, as long as whatever you're using to play it back doesn't give up the instant it encounters the hole.
I find this very hard to believe. Disable the ABS system maybe, but the brake system is designed to work above all else - if a computer can disable the brakes that suggests a malfunction can too.
I don't really know why there are so many accidents with loaded guns, but I know I'm not missing something here: It is so easy to disable a gun from firing by removing the ammunition, rendering it no more harmful than a brick, with no chance of accidentally re-enabling it. We can't reasonably operate cars in this manner, however if you don't know how to safety and unload your own firearm, it's unquestionably in the wrong hands.
Maybe I haven't got your story straight, maybe he accidentally fired while unloading and checking before cleaning - sorry if this is the case. And I do hear you clearly on the disparity in people's thoughts on the dangers of guns versus cars, there's been a lot of hype and BS. And while I don't consider either of them to be "killing machines", there's one thing for sure about a gun, they do nothing but harm to what they're used on (unlike cars) whether or not that is desirable, and are designed to be easily safetied in light of that fact.
I think my ISP is trialling a similar technology. The connection keeps
Bad choice of examples. That's what we were saying and thinking in 1998: IT to PHB: "Don't open any EXE files mailed to you, however Excel spreadsheets, Word docs etc, are fine".
A exploitable buffer overrun in any application where malicious inputs exist is a security hole.
That's what I use 172.16-31.x.y for - some people don't even know about that range!
What a nightmare!
I would go one further and say every GTK app, including my own.
What utterly unhelpful pedantry, calm down. When you compare "Open source" and "proprietary software" in the same sentence, most reasonable people know what you mean.
Arguing with a cop over the finer points of the law also isn't illegal, but it might as well be.
They also opened it and gave it an inspection that would make a customs officer blush