Re:ought to change the kernel version number to 4
on
Linux Nukes 386 Support
·
· Score: 4, Informative
Two major things: the WP bit doesn't work in supervisor mode on 386, which makes copy on write *very* painful to implement, and the CMPXCHG and XADD instructions which are extremely important to SMP primitives are missing. That has meant needing separate code that only works on 386, and it has not been well maintained and always gets in the way.
The whole point of private free enterprise is that risks can be taken, with the hope of a big payout. Well, guess what, sometimes it doesn't pan out. That's the system, it is how it is meant to work.
One thing that is not really covered is that launching a reactor (unlike *operating* a reactor in *low-earth orbit* like the Soviets did) is that it is substantially safer than launching an RTG. An RTG is at its maximum activity at the point of launch, and in the case of a low altitude launch failure could spread measurable radiation over an area. In contrast, the reactor isn't (shouldn't be) activated until already on an earth escape trajectory. "Virgin" (never irradiated) U-235 is not very radioactive: the specific activity is some 8,000,000 times less than Pu-238. If the reactor ends up having a failure and a meltdown it is already on its way away from Earth never to return, and there really is no better dump for nuclear waste than deep space.
Indeed, and the Amazon Cooperation Treaty Organization can be amazon.int (which is what the.int domain is for, although for some bizarre reason the biggest treaty organization of them all, the United Nations, is at un.org rather than un.int. Not to mention that having its own ISO 3166-1 code and a number of suborganizations a.un top-level domain would actually make sense.)
They were introduced at the same time, in the same RFC... but the bottom line is that it started out as an exclusively U.S. network, and one with a military bent at that (ever wondered by it is not.mil.gov?!) At this point it's a permanent quirk.
GPT vs MBR is irrelevant to BIOS, unless, of course, the BIOS tries to parse the MBR and draw conclusions from it. So of course many of them do, and get it wrong. However, it is one of those things that "it works unless actively broken."
Well, part of the reason it is all there (and other ISM bands like 915 MHz and 5.8 GHz) is because the stuff *can* work with interference. This property is useful both when dealing with other "intentional radiators" and with industrial emissions, so it makes sense to put them in the same area. Pretty much the FCC and other regulatory agencies put an (almost) free-for-all sign up and said "if you can make it work, go for it, just don't complain if it doesn't work at all."
However, you wouldn't be able to use the ISM bands -- or, quite frankly, any frequency close to them -- for weak-signal work like satellite. It would be like trying to whisper at Woodstock.
There are a number of things attractive with LLVM/Clang: the code base is cleaner, some people feel better about the license, and so on. The quality of the generated code, however, is significantly worse, at least at this time.
Given that Skype operates in countries (like India) where VoIP is illegal unless there is a back door, and Skype is said to be "in compliance", you *know* there is a back door.
"Maybe the idea of a heart transplant from a convicted killer weirds you out.... If so, on some level you believe in magic."
Either that or I believe that the death penalty will over time be seen as a source of harvestable organs.
This, of course, was a very dangerous case of insubordination on the part of the military, since the exact reason it was imposed on them was that the political leadership considered the risk of an unauthorized launch to be greater than the "last man standing" scenario, and, guess what, in the United States the political leadership is supposed to be supreme to the military.
Slashdot Mirror
Two major things: the WP bit doesn't work in supervisor mode on 386, which makes copy on write *very* painful to implement, and the CMPXCHG and XADD instructions which are extremely important to SMP primitives are missing. That has meant needing separate code that only works on 386, and it has not been well maintained and always gets in the way.
Neither. It was by me, but Ingo pushed it to Linus.
The whole point of private free enterprise is that risks can be taken, with the hope of a big payout. Well, guess what, sometimes it doesn't pan out. That's the system, it is how it is meant to work.
The use of Stirling engines has already been planned for future RTG missions, this is just a change of heat source.
One thing that is not really covered is that launching a reactor (unlike *operating* a reactor in *low-earth orbit* like the Soviets did) is that it is substantially safer than launching an RTG. An RTG is at its maximum activity at the point of launch, and in the case of a low altitude launch failure could spread measurable radiation over an area. In contrast, the reactor isn't (shouldn't be) activated until already on an earth escape trajectory. "Virgin" (never irradiated) U-235 is not very radioactive: the specific activity is some 8,000,000 times less than Pu-238. If the reactor ends up having a failure and a meltdown it is already on its way away from Earth never to return, and there really is no better dump for nuclear waste than deep space.
Indeed, and the Amazon Cooperation Treaty Organization can be amazon.int (which is what the .int domain is for, although for some bizarre reason the biggest treaty organization of them all, the United Nations, is at un.org rather than un.int. Not to mention that having its own ISO 3166-1 code and a number of suborganizations a .un top-level domain would actually make sense.)
They were introduced at the same time, in the same RFC... but the bottom line is that it started out as an exclusively U.S. network, and one with a military bent at that (ever wondered by it is not .mil.gov?!) At this point it's a permanent quirk.
GPT vs MBR is irrelevant to BIOS, unless, of course, the BIOS tries to parse the MBR and draw conclusions from it. So of course many of them do, and get it wrong. However, it is one of those things that "it works unless actively broken."
One of the many atrocities on the American Justice system already committed by this Supreme Court...
Hey, I resemble that remark.
... oh, wait, I'm 46 years old.
Wow, Slashdot's submission system is even slower than I thought.
Well, part of the reason it is all there (and other ISM bands like 915 MHz and 5.8 GHz) is because the stuff *can* work with interference. This property is useful both when dealing with other "intentional radiators" and with industrial emissions, so it makes sense to put them in the same area. Pretty much the FCC and other regulatory agencies put an (almost) free-for-all sign up and said "if you can make it work, go for it, just don't complain if it doesn't work at all." However, you wouldn't be able to use the ISM bands -- or, quite frankly, any frequency close to them -- for weak-signal work like satellite. It would be like trying to whisper at Woodstock.
I guess they were waiting for the recent Supreme Court decision which basically says that a company can say "you can't sue us because we told you so."
Linus doesn't scream. He obliterates with sarcasm.
But still not by default, what it sounds like, which means it is still marginal at best.
Round-trip latency can definitely be improved. It just means using LEO satellites instead of GEO.
There are a number of things attractive with LLVM/Clang: the code base is cleaner, some people feel better about the license, and so on. The quality of the generated code, however, is significantly worse, at least at this time.
Given that Skype operates in countries (like India) where VoIP is illegal unless there is a back door, and Skype is said to be "in compliance", you *know* there is a back door.
"Maybe the idea of a heart transplant from a convicted killer weirds you out. ... If so, on some level you believe in magic."
Either that or I believe that the death penalty will over time be seen as a source of harvestable organs.
"Streisand effect" anyone?
"Hey, mind if I take in this superconductor cooler through the checkpoint?"
This, of course, was a very dangerous case of insubordination on the part of the military, since the exact reason it was imposed on them was that the political leadership considered the risk of an unauthorized launch to be greater than the "last man standing" scenario, and, guess what, in the United States the political leadership is supposed to be supreme to the military.
It's easy to throw together a BASIC interpreter. However, in this day and age, why would you want one?
Well, let the distros know...
As the author of Syslinux/PXELINUX I found the article rather interesting and enjoyable. :)