runs on _your_ machine.
83 posts • joined 30 Apr 2010
... and have risen slightly since the Parity snafu."
This community *does* deserve everything that happens to them. Reminds one of the immortal passage from Mackay's Memoirs of Extraordinary Popular Delusions:
"But the most absurd and preposterous of all, and which shewed, more completely than any other, the utter madness of the people, was one started by an unknown adventurer, entitled "A company for carrying on an undertaking of great advantage, but nobody to know what it is." Were not the fact stated by scores of credible witnesses, it would be impossible to believe that any person could have been duped by such a project. Next morning, at nine o'clock, this great man opened an office in Cornhill. Crowds of people beset his door, and when he shut up at three o'clock, he was thus, in five hours, the winner of 2000l. He was philosopher enough to be contented with his venture, and set off the same evening for the Continent. He was never heard of again"
Rust safety features (as well as similar features of other languages) are mostly irrelevant in the context of kernel development. They rely on the underlying model of fully separated protected address spaces. And kernel's task is to *implement* this model, so it cannot rely on this model. The bugs in the Redox where not some kind of wild pointer dereferences or use-after-free-s (these are eliminated by the language), they were perfectly legitimate memory accesses, but they still caused crashes, because the memory locations in question happen to contain page tables or DMA setup structures, etc. That is, those were not typical "segfault" kind or errors, they were logical errors, from which Rust protects no better than C. (And yes, such errors can stay dormant for years.)
I spent (<counts with fingers...>) about 10 years doing kernel programming for multiple operating systems and I can say that chasing pointer errors definitely wasn't anywhere close to the top problems.
The amazing progress of Redox OS includes re-writing the kernel from scratch, because existing virtual memory sub-system caused multiple memory corruptions and crashes in user land (https://www.redox-os.org/news/this-summer-in-redox-15/) that developers couldn't fix. So much for "safe" languages.
The civilian agencies got access to the presumed secret evidence that the government used to place the blame? Or they just happily echo-chambering each other, 17 or more times?
The only bit of concrete technical information I was able to find in all the reports was that the source IP was in Russia. Yeah, the chain of VPNs used for attack had last hop from Moscow, so what?
according to our theories about formation of the Universe, based on evidence that we collect from within our event horizon. So we are perhaps as clueless about real evolution and age of the Universe (relative to the older races) as inhabitants of these yet to be created planes are relative to us.
> At the risk of being a pedant, a government cannot grant rights.
I find it hard to believe people still subscribe to this 18 century nonsense about "natural rights" (which was a politically charged agitation piece in the first place) ignoring all the overwhelming historical evidence to the contrary. Systems of rights and responsibilities are always created by authority, from the earliest theocratic villages in Mesopotamia to the European parliaments, created by the kings to curb nobles.
> where the countries annexed by a EU or NATO member during the last 30 years?
This is exactly the point: NATO bombs remote nations from the Bronze Age back to the Stone Age *without* providing the inhabitants with health care and pension system, not to say about allowing them to freely move into invaders' own countries.
> You are quite right, you can't rebuild a 4TB single disk in minutes. It's utterly impossible.
It is entirely possible and reasonable. There are 2 ingredients here:
0. Parity declustering. In a parity declustered array, e.g., 8+2 RAID6 can be used to stripe data across a large number of drives, say, 100 (rather than 10, as in standard RAID). This means, that only a small fraction (10% in this example) of each drive has to be read during rebuild. See Holland's thesis (http://www.pdl.cmu.edu/PDL-FTP/Declustering/Thesis.pdf) for details.
1. Distributed spare. By allocating spare space on each device, a fraction of *total* array bandwidth can be used for rebuild. That is, the wider is the array, the faster is the rebuild.
The funny thing is that this technology is 20 years old.
I beg to differ. Fundamental Hellenistic heritage are not natural sciences, but humanities. And this was preserved through the entire history of the Roman empire and bootstrapped Renaissance. Homer and Plato were studied and commented all they way down (vide http://en.wikipedia.org/wiki/Gemistus_Pletho). And there was no need for Italian cities to re-establish trade: it was never broken. In fact up to 12 century, Naples, Amalfi, etc. were *part* of the empire, formally, politically and economically. Funny enough, Naples was even a staunch supporter of iconoclasm (if I still know my Gibbon).
that people persist in this silly anachronistic nonsense started by the 18th century propaganda, which chose Byzantium as a strawmen monarchy. There was no need to keep the "knowledge": up until 1453, the continuous tradition of Hellenistic education and scholarship was maintained in the Roman empire and its capital---Constantinople. There was almost at all times cultural exchange between the empire and Western Europe (sometimes, alas, in the form of Crusades).
Biting the hand that feeds IT © 1998–2019