I’ll
Just mention write protect rings for tapes. Made really good cat toys.
1025 publicly visible posts • joined 23 Oct 2009
That:
“ I'd propose that people declare their age (without any verification) and if under 18 there is a total ban on all forms of advertising, data mining or use of the data by the companies - that way the social media companies wouldn't be so keen anymore.”
Then everyone can just say they are 16 and enjoy an ad free data protected service. Sound like a solution :)
Worse than that. After years of outsourcing the companies core IT systems and cloudifying everything; good security (and a whole load of other NFR's) is now impossible to achieve. The corporate obsession for lower costs (at a balance sheet level) at any cost (no moral values here) will always result in products and processes that only just work with 'work' defined very loosely. The corporate way out of this is to insure against the introduced risks, which like outsourcing, seems to make it someone else's problem; at a cost. The result of all of this is that the products and services are shit, yet cost the consumers more, but hey all of the companies in the gravy chain are indemnified.
Welcome to the machine...
Micro kernels have a sort of IPC style communication between the various OS actors but this in not necessarily the performance issue that you might imagine. The piece didn't mention the other main micro kernel around in the 70s/80s/90s; Chorus Systèmes offering.
As I've mentioned before, this was used in ICL's GoldRush system and specialist hardware was used to aid both intra and inter processor comms and memory management. The result was that, for it's time, it flew performance wise. Given that it used Sun UltrasSPARC IV processors, I would hope current tech would do better even without the MMU tweaks, especially given the amount of close to CPU memory that is now available. All micro kernels need is the amount of attention that the Linux kernel has had over the last thirty odd years and they would be equally performant.
Microkernels are, as Mr Tanenbaum argued (I did too but no one really listened to me ;), a much better solution than a monolithic kernel in so many ways. It's such a shame that they are languishing near the scrap heap. Let's give them some love...
I've often thought you should get a bill from the NHS at the end of your treatment/episode that would itemise the treatments and their price but at the grand total say that the cost to you is zero. This would both inform the people using the system of its value and force the various parts of the NHS's dismal infrastructure to play nice with each other.
Arguably part of the runtime environment but yes, the logic that is used to process your code is itself a security concern. Ken Thomson's essay is a good start down the trapdoor of paranoia into the land of the queen of hearts.
I was just trying to point out that having visible source code isn't any real form of security guarantee and that saying so is at best disingenuous but most likely downright dangerous as people might actually believe that it is.
Statement is at the heart of a great deal of peoples faith:
"You can't hide a back door in open source because it would be immediately visible and removable"
But it isn't true. You also need control, and trust, the rest of the compile time and runtime environment.
Only a very naive infiltrator would put a piece of malicious code in plain sight.