Of course not. That's why the industry is heavily regulated and monitored.
By people from the nuclear industry who think that their job is to act as its PR wing rather than to actually hold them to account in any way, at least in most cases I've seen...
And lets not forget how reliable and predictable it is. A nuclear reactor is certain to output a set amount of energy in a certain configuration no matter what.
Until they have to unexpectedly shut it down for safety reasons. It's more common than you might think...
Chicken pox is fun because IIRC there's some evidence getting the actual disease once doesn't provide lifetime protection on its own - you need occasional low-level exposure to the virus in order to maintain your immunity, and vaccination removes that exposure.
(Of course, vaccines actually fairly unambigously benefit those that take them, unlike forced sterilization or eugenics. Not sure if the GP was trolling or if he seriously believes that eugenics are OK...)
Yeah. Here in the UK, the NHS has historically been rather reluctant to vaccinate against chicken pox - immunity isn't life-long, and there's some evidence to suggest that vaccinating actually increases the risk of adults getting it, which is generally quite nasty.
What they did was implementing a form of hyperthreading by throwing in an extra integer ALU into each core. They changed the name "core" to "module" and now falsely claim that each "module" now has two cores. If that were true then the old Sun UltraSPARC T1 would be 32 core, the Pentum D would actually be quad core (as it is also specified to have two ALUs per core), and all Intel processors that support hyperthreading can double their core count.
Actually, each of the two cores in a Bulldozer module has two ALUs all to itself just like a Pentium D core (plus two AGUs which IIRC can calculate some integer operations too). If they were actually counting cores in the ridiculous way you're claiming - which they're not, in case you didn't get the hint - they could claim four cores per module. In theory Bulldozer actually has the same amount of FPU power per core as the previous generation, too.
My application needs traditional text log files on disk, can I configure journald to generate those? No, you can’t. If you need this, just run the journal side-by-side with a traditional syslog implementation like rsyslog which can generate this file for you. Why doesn’t the journal generate traditional log files? Well, for starters, traditional log files are not indexed, and many key operations very slow with a complexity of O(n). The native journal file format allows O(log(n)) complexity or better for all important operations. For more reasons, refer to the sections above.
So yes, the idea is to totally replace plain-text logging and leave a gaping usability hole. The suggested workaround will only work until software starts using The Journal directly without going through syslog, which is I think the end plan since syslog presumably can't support all the neat extra functionality.
Not pointless pedantry. A lot of the Linux hacking incidents have involved someone either using an insecure password or using their password on an insecure machine, which is impossible to actually prevent.
Take a look at what vPro does sometime. If you have hardware that supports it there's an actual embedded processor in there, directly connected to your network cards (both wired and wireless) and with full access to your RAM, and there's no way to tell what code it's running. If you don't, your Intel-based computer still supports isolated processes whose memory can't be peeked into or scanned for malicious code.
The trouble is that AMD haven't been able to supply the volumes that companies like Apple need because they don't have the money and they can't be sure they'll be able to sell that volume. Intel's anti-competitive practices of a few years ago really hit them where it hurt...
In fact, consuming pure water can actually make some kinds of dehydration worse - and as far as I know there's no easy way for the person to tell from their symptoms which kind they have.
Of course, this was an article in the Daily Torygraph, which is ideologically opposed to the EU and tries to discredit them at every opportunity even if they have to bend the truth to do so.
Obviously you've been brainwashed by the patriarchy, as have they;-)
Further, the vast majority of porn actresses are not being "trafficked"... makes me wonder if you even know what the word means.
It means what anti-trafficking activists want it to mean, and pretty much all the anti-trafficking activists are anti-porn activists in a new guise. Don't think they've extended it to porn yet, but you get things like them defining "trafficked" as "being kidnapped and raped in exchange for money" when talking about how serious it is, and "being described as being from a foreign country" when they're talking about how common it is - and the press and government lap it up.
The trouble is that it turns out that in practice, the pebbles leak radioactive isotopes into the reactor in large quantities, making it very radioactive. I'm not quite sure why, and it's possible that no-one is; nuclear engineering seems to be a bit tricky to get right.
There have been loads of failures at Nuclear plants, you didn't hear about them because....nothing happened, they failed safe, no radiation leaked...
And every time one of those non-news accidents happened, there was a lot less stopping a dangerous failure from happening than there should have been. Then when there is an actual nuclear disaster all the pro-nuclear spokespeople talk about how incredibly unlikely it is and how many things had to go wrong in order for it to happen - ignoring all the times that didn't make the news when nearly enough things went wrong to cause a serious accident, because if they couldn't sweep those under the rug it'd be obvious that the accident wasn't so unlikely after all.
(This is a known problem in safety engineering. Having multiple layers of safeguards is only any use if you take failures of some of the levels of safeguards seriously every time it happens. In particular, often when there's a complex disaster that requires a lot to go wrong it turns out that there were a whole bunch of similar near-disasters previously that were ignored. It doesn't help that nuclear regulatory agencies always end up getting stuffed with members of the nuclear industry to the point that they become more like advocates for the industry than regulators.)
The radiation releases from nuclear reactor accidents, on the other hand, don't come in nice convenient bundles and are often in inconveniently bio-available forms.
Britain was still trying to hang on to its colonies until the mid-60's. And this wasn't some benign protective impulse, it was motivated by greed, exploitation, and racism.
Yeah, no kidding. Turns out we were doing such... interesting things as using castration as a way of torturing suspected rebels up until the 1960s.
Now if only they required states that do this to notify the police forces in other EU countries when they do this to child porn hosted in the EU. The UK filter maintainers don't, presumably so they can boast about how much child porn they're blocking.
Secure Boot is a Windows feature building on a UEFI feature. If I'm understanding it correctly, every stage in the chain needs to be secure in order for the boot to actually be secure - a security flaw in either the UEFI firmware or the Windows code could render it ineffective.
They're essentially using x86 cores for a vaguely GPU-style wide SIMD unit, from what I can tell. AMD's next generation of GPUs appear to be heading towards a similar destination from the opposite direction - they're adding a non-vector core to each 16-wide block of vector cores for control code that can't easily be vectorized.
Slashdot Mirror
Of course not. That's why the industry is heavily regulated and monitored.
By people from the nuclear industry who think that their job is to act as its PR wing rather than to actually hold them to account in any way, at least in most cases I've seen...
And lets not forget how reliable and predictable it is. A nuclear reactor is certain to output a set amount of energy in a certain configuration no matter what.
Until they have to unexpectedly shut it down for safety reasons. It's more common than you might think...
You're counting deaths from mining nuclear fuel there too, right? Right? sigh.
Chicken pox is fun because IIRC there's some evidence getting the actual disease once doesn't provide lifetime protection on its own - you need occasional low-level exposure to the virus in order to maintain your immunity, and vaccination removes that exposure.
Why not look a bit closer to home?
(Of course, vaccines actually fairly unambigously benefit those that take them, unlike forced sterilization or eugenics. Not sure if the GP was trolling or if he seriously believes that eugenics are OK...)
Yeah. Here in the UK, the NHS has historically been rather reluctant to vaccinate against chicken pox - immunity isn't life-long, and there's some evidence to suggest that vaccinating actually increases the risk of adults getting it, which is generally quite nasty.
In theory it should be possible to clone the identity of the HDCP sink and pretend to be it to multiple devices at once, not just one.
What they did was implementing a form of hyperthreading by throwing in an extra integer ALU into each core. They changed the name "core" to "module" and now falsely claim that each "module" now has two cores. If that were true then the old Sun UltraSPARC T1 would be 32 core, the Pentum D would actually be quad core (as it is also specified to have two ALUs per core), and all Intel processors that support hyperthreading can double their core count.
Actually, each of the two cores in a Bulldozer module has two ALUs all to itself just like a Pentium D core (plus two AGUs which IIRC can calculate some integer operations too). If they were actually counting cores in the ridiculous way you're claiming - which they're not, in case you didn't get the hint - they could claim four cores per module. In theory Bulldozer actually has the same amount of FPU power per core as the previous generation, too.
From the official FAQ linked in the summary:
My application needs traditional text log files on disk, can I configure journald to generate those?
No, you can’t. If you need this, just run the journal side-by-side with a traditional syslog implementation like rsyslog which can generate this file for you.
Why doesn’t the journal generate traditional log files?
Well, for starters, traditional log files are not indexed, and many key operations very slow with a complexity of O(n). The native journal file format allows O(log(n)) complexity or better for all important operations. For more reasons, refer to the sections above.
So yes, the idea is to totally replace plain-text logging and leave a gaping usability hole. The suggested workaround will only work until software starts using The Journal directly without going through syslog, which is I think the end plan since syslog presumably can't support all the neat extra functionality.
Don't worry - soon Lennart's going to kill off the ability to have seperate root and /usr partitions anyway. After all, who really needs it?
Windows Media Player used to be a major infection vector too, if I recall correctly.
On the other hand, it's more likely to decide that Google Chrome is a dangerous file that must be immediately purged.
Not pointless pedantry. A lot of the Linux hacking incidents have involved someone either using an insecure password or using their password on an insecure machine, which is impossible to actually prevent.
Take a look at what vPro does sometime. If you have hardware that supports it there's an actual embedded processor in there, directly connected to your network cards (both wired and wireless) and with full access to your RAM, and there's no way to tell what code it's running. If you don't, your Intel-based computer still supports isolated processes whose memory can't be peeked into or scanned for malicious code.
The trouble is that AMD haven't been able to supply the volumes that companies like Apple need because they don't have the money and they can't be sure they'll be able to sell that volume. Intel's anti-competitive practices of a few years ago really hit them where it hurt...
In fact, consuming pure water can actually make some kinds of dehydration worse - and as far as I know there's no easy way for the person to tell from their symptoms which kind they have.
Of course, this was an article in the Daily Torygraph, which is ideologically opposed to the EU and tries to discredit them at every opportunity even if they have to bend the truth to do so.
Obviously you've been brainwashed by the patriarchy, as have they ;-)
Further, the vast majority of porn actresses are not being "trafficked" ... makes me wonder if you even know what the word means.
It means what anti-trafficking activists want it to mean, and pretty much all the anti-trafficking activists are anti-porn activists in a new guise. Don't think they've extended it to porn yet, but you get things like them defining "trafficked" as "being kidnapped and raped in exchange for money" when talking about how serious it is, and "being described as being from a foreign country" when they're talking about how common it is - and the press and government lap it up.
The trouble is that it turns out that in practice, the pebbles leak radioactive isotopes into the reactor in large quantities, making it very radioactive. I'm not quite sure why, and it's possible that no-one is; nuclear engineering seems to be a bit tricky to get right.
There have been loads of failures at Nuclear plants, you didn't hear about them because....nothing happened, they failed safe, no radiation leaked ...
And every time one of those non-news accidents happened, there was a lot less stopping a dangerous failure from happening than there should have been. Then when there is an actual nuclear disaster all the pro-nuclear spokespeople talk about how incredibly unlikely it is and how many things had to go wrong in order for it to happen - ignoring all the times that didn't make the news when nearly enough things went wrong to cause a serious accident, because if they couldn't sweep those under the rug it'd be obvious that the accident wasn't so unlikely after all.
(This is a known problem in safety engineering. Having multiple layers of safeguards is only any use if you take failures of some of the levels of safeguards seriously every time it happens. In particular, often when there's a complex disaster that requires a lot to go wrong it turns out that there were a whole bunch of similar near-disasters previously that were ignored. It doesn't help that nuclear regulatory agencies always end up getting stuffed with members of the nuclear industry to the point that they become more like advocates for the industry than regulators.)
The radiation releases from nuclear reactor accidents, on the other hand, don't come in nice convenient bundles and are often in inconveniently bio-available forms.
On the other hand, there's usually all sorts of nasty images of real-life violence on news programs that are deemed suitable for kids...
Britain was still trying to hang on to its colonies until the mid-60's. And this wasn't some benign protective impulse, it was motivated by greed, exploitation, and racism.
Yeah, no kidding. Turns out we were doing such... interesting things as using castration as a way of torturing suspected rebels up until the 1960s.
Now if only they required states that do this to notify the police forces in other EU countries when they do this to child porn hosted in the EU. The UK filter maintainers don't, presumably so they can boast about how much child porn they're blocking.
Secure Boot is a Windows feature building on a UEFI feature. If I'm understanding it correctly, every stage in the chain needs to be secure in order for the boot to actually be secure - a security flaw in either the UEFI firmware or the Windows code could render it ineffective.
They're essentially using x86 cores for a vaguely GPU-style wide SIMD unit, from what I can tell. AMD's next generation of GPUs appear to be heading towards a similar destination from the opposite direction - they're adding a non-vector core to each 16-wide block of vector cores for control code that can't easily be vectorized.