No, most right-wing people *claim* they lean libertarian.
And they do. Except on drugs. And media regulation. And pornography. And abortion. And federal abstinance-only funding. And gay marriage. And government religious endorsement. And assisted suicide.
'Libertarian' in the US is essentially a codeword for 'conservative, but don't want to admit it.' The only true libertarian aspect they have left is their economic policy, which stems less from any form of idealism than it does from the influence of corporate pressure groups who regard any form of regulation as a direct attack on their profit-making ability.
Depends how many minions your terrorist cell has. Speed would be essential - you need to get down as many pylons as possible before the power company realises what just happened and sends in the local police, FBI and DHS after you. So it should be a coordinated strike in multiple places at once.
The EMP people tend to be a bit silly. They have no idea how an EMP would actually work or what it would do, and often end up doing silly things like making sure their torches are packed in metal boxes so the pulse won't somehow damage the electronics.
A little looking on google sat imagery lets you see where the big pylons go. Can't be that hard to identify the lines into a major city and have your acy-cutter team down a few pylons on each one.
Also, eventually a small child would catch something nasty and die after playing in the lawn sprinker (Though no definate proof of the origin of the infection will ever be possible). This would result in a media storm, national outrage, and a law mandating the grey water be purified and sterilised to the same standard as the drinking water.
Here, there's a fee to pay for the rain that lands on your property. It's a drainage fee - you have to pay the company that operates the storm drains to take it away.
Greedy, and there's an element of stabbing the competition in the back. Comcast is in the same business - they are a cable company, selling PPV movies and subscriptions to channels. The more successful netflix is, the more people will ditch their cable TV subscriptions.
It's just an awkward versioning scheme. If this was the unix world, they'd be talking about no longer updating 8.1.0 and requiring customers update to 8.1.1.
All good suggestions, but none of them quite how I'd imagined it:
Bloody 'Ell! How'd he go and miss an unchecked length field? Now I'm in all weekend workin' me bollocks off updating every server 'cos some fuckin' wanker couldn't be arsed to get his security-critical code reviewed.
And there lies the problem. Windows is very tolerant of badly-configured ACPI implimentations - it'll happily work even if half the configuration fields are wrong, as it simply ignores them and uses hard-coded suboptimal values. There's little incentive for OEMs to bother supporting any OS other than Windows, so typically once the firmware works for Windows it is considered good enough. All is well, until we stick linux on it - and linux then follows the ACPI specification correctly, and fails horribly.
I didn't say it would be easily updated. That's the kind of thing the firmware does. Just lock the hash value read-only immediately before loading the bootloader - the only way to change it would be to physically restart and do the 'press F1 to enter setup' thing. It would be a bit of a bother if you are trying to do an OS installation unattended over the network, but that's not a common situation and Secure Boot has its own problems with that. Try finding a signed image suitable for network booting.
They never stopped trying. What do you think Secure Boot is? Anyone can design an effective vendor-neutral protection system against boot-sector rootkits - it's a simple matter of storing the EFI bootloader hash in config flash and requiring a new one be re-hashed manually after OS installation. Trivial. But somehow Microsoft and Intel instead managed to come up with an over-complicated solution that just happens to only work for OS vendors which have the market share to get their own public keys added to the configuration by motherboard manufacturers? I'm not buying that as simply inept design: This has to be a deliberate attempt to inconvenience rivals while claiming to be about improving security.
Slashdot Mirror
No, most right-wing people *claim* they lean libertarian.
And they do. Except on drugs. And media regulation. And pornography. And abortion. And federal abstinance-only funding. And gay marriage. And government religious endorsement. And assisted suicide.
'Libertarian' in the US is essentially a codeword for 'conservative, but don't want to admit it.' The only true libertarian aspect they have left is their economic policy, which stems less from any form of idealism than it does from the influence of corporate pressure groups who regard any form of regulation as a direct attack on their profit-making ability.
Countries that describe themselves as democratic republics generally aren't very good at either.
No, it doesn't. The summary itsself contains a list to a definition.
It was a VM, allocated just enough RAM to do what it needs to do.
Some of us like to have money. These are not good economic times - most people can't be picky, they are lucky to get just one job offer.
Risky though. Some people prefer a guaranteed small-but-steady wage to gambling their income.
Depends how many minions your terrorist cell has. Speed would be essential - you need to get down as many pylons as possible before the power company realises what just happened and sends in the local police, FBI and DHS after you. So it should be a coordinated strike in multiple places at once.
UK.
The EMP people tend to be a bit silly. They have no idea how an EMP would actually work or what it would do, and often end up doing silly things like making sure their torches are packed in metal boxes so the pulse won't somehow damage the electronics.
A little looking on google sat imagery lets you see where the big pylons go. Can't be that hard to identify the lines into a major city and have your acy-cutter team down a few pylons on each one.
Just change your movie provider. Something of a more torrenty nature perhaps, legality optional.
Also, eventually a small child would catch something nasty and die after playing in the lawn sprinker (Though no definate proof of the origin of the infection will ever be possible). This would result in a media storm, national outrage, and a law mandating the grey water be purified and sterilised to the same standard as the drinking water.
Here, there's a fee to pay for the rain that lands on your property. It's a drainage fee - you have to pay the company that operates the storm drains to take it away.
Greedy, and there's an element of stabbing the competition in the back. Comcast is in the same business - they are a cable company, selling PPV movies and subscriptions to channels. The more successful netflix is, the more people will ditch their cable TV subscriptions.
And when you watch the show, they have annoying ad-banners pop up over the picture to promote other shows.
Winows 8.1 update 1.
It's just an awkward versioning scheme. If this was the unix world, they'd be talking about no longer updating 8.1.0 and requiring customers update to 8.1.1.
I recently mangled yum by running out of RAM mid-updates. That was ugly. Really ugly. Fixed it, but more through luck than skill.
Or linux.
Because another one blew up, and that replacement technology probably wouldn't be ready before the sun turns red giant.
All good suggestions, but none of them quite how I'd imagined it:
Bloody 'Ell! How'd he go and miss an unchecked length field? Now I'm in all weekend workin' me bollocks off updating every server 'cos some fuckin' wanker couldn't be arsed to get his security-critical code reviewed.
Fuck.
(Except here in the UK, we are more creative with our profanity.)
And there lies the problem. Windows is very tolerant of badly-configured ACPI implimentations - it'll happily work even if half the configuration fields are wrong, as it simply ignores them and uses hard-coded suboptimal values. There's little incentive for OEMs to bother supporting any OS other than Windows, so typically once the firmware works for Windows it is considered good enough. All is well, until we stick linux on it - and linux then follows the ACPI specification correctly, and fails horribly.
"Credit travels upwards, blame travels downwards. That's just the way it works." - The Pointy-Haired Boss.
I didn't say it would be easily updated. That's the kind of thing the firmware does. Just lock the hash value read-only immediately before loading the bootloader - the only way to change it would be to physically restart and do the 'press F1 to enter setup' thing. It would be a bit of a bother if you are trying to do an OS installation unattended over the network, but that's not a common situation and Secure Boot has its own problems with that. Try finding a signed image suitable for network booting.
They never stopped trying. What do you think Secure Boot is? Anyone can design an effective vendor-neutral protection system against boot-sector rootkits - it's a simple matter of storing the EFI bootloader hash in config flash and requiring a new one be re-hashed manually after OS installation. Trivial. But somehow Microsoft and Intel instead managed to come up with an over-complicated solution that just happens to only work for OS vendors which have the market share to get their own public keys added to the configuration by motherboard manufacturers? I'm not buying that as simply inept design: This has to be a deliberate attempt to inconvenience rivals while claiming to be about improving security.