Reason for me at least is that Linux isn't interesting as a kernel when there's formally proven kernels like the se:l4 microkernel or a vm based / language verified (read: everything runs in ring0) such as Microsofts Midori. I don't want to dedicate my time to something that is good enough when theres something much better being created right now.
I agree with the distributed part but not the web browser based interface, I believe things will be headed towards what inferno or even better microsoft's midori where the compiler is verified and there is no kernel (single address space) and architectures simply need a rewritten VM. It should also be simple to distributed tasks imagine doing a long high cpu usage calculation the VM/OS could simply and automatically distribute it no matter what OS it is distributed to. Old bad unix ideas need to die.
I thought windows 7 introduced full ALSR (address space layout randomization) with windows core software protected against stack smashing as well with canaries? Just as GRSecurity patched Linux or a smart OS like OpenBSD by default How can these viruses work against full ALSR and protection against stack smashing?
I want none of this, I want actual benchmarks that benchmark the *SYSTEMS* and not an aggregate of every single system.. I want to know scheduler throughput and latency, file system overhead, etc basicly I want deep statistics that show how well the kernels perform and not how some randomly written application performs.
Correct me if I'm wrong but a single address operating system with a JIT VM within the kernel could be *faster* due to static compilation before into some sort of bytecode / machine code and than the VM can simply optimize depending on how the program is executing, something like HP's Dynamo http://www.hpl.hp.com/techreports/1999/HPL-1999-78.html
If it's simply using bnet to authenticate I'm fine with that but if everything is hosted online I hope blizzard is ready to have the bnet protocol for starcraft II reverse engineered, becasue thats one hell of a way to piss off your user base
Slashdot Mirror
Reason for me at least is that Linux isn't interesting as a kernel when there's formally proven kernels like the se:l4 microkernel or a vm based / language verified (read: everything runs in ring0) such as Microsofts Midori. I don't want to dedicate my time to something that is good enough when theres something much better being created right now.
Isn't dom0 itself a hypervisor kernel? If so I highly doubt Linux will integrate a kernel within itself.
I agree with the distributed part but not the web browser based interface, I believe things will be headed towards what inferno or even better microsoft's midori where the compiler is verified and there is no kernel (single address space) and architectures simply need a rewritten VM. It should also be simple to distributed tasks imagine doing a long high cpu usage calculation the VM/OS could simply and automatically distribute it no matter what OS it is distributed to. Old bad unix ideas need to die.
I thought windows 7 introduced full ALSR (address space layout randomization) with windows core software protected against stack smashing as well with canaries? Just as GRSecurity patched Linux or a smart OS like OpenBSD by default How can these viruses work against full ALSR and protection against stack smashing?
I want none of this, I want actual benchmarks that benchmark the *SYSTEMS* and not an aggregate of every single system.. I want to know scheduler throughput and latency, file system overhead, etc basicly I want deep statistics that show how well the kernels perform and not how some randomly written application performs.
Correct me if I'm wrong but a single address operating system with a JIT VM within the kernel could be *faster* due to static compilation before into some sort of bytecode / machine code and than the VM can simply optimize depending on how the program is executing, something like HP's Dynamo http://www.hpl.hp.com/techreports/1999/HPL-1999-78.html
I don't want to bash BIND but it has had a fair amount of sec issues (well a lot), try unbound or nsd instead http://unbound.nlnetlabs.nl/ http://www.nlnetlabs.nl/projects/nsd/
If it's simply using bnet to authenticate I'm fine with that but if everything is hosted online I hope blizzard is ready to have the bnet protocol for starcraft II reverse engineered, becasue thats one hell of a way to piss off your user base