Found a Great Site about Windows NT Kernel Internals from the University Of Tokyo while searching for a way to programatically muck about with processes. Its really good and I could see myself using this later.
Is this guy smoking crack or what?. Hacking the driver layer from windows onto the LINUX kernel? Its called NDIS, baby. Its been done.
Anyway, Mr John C. Dvorak it totally wrong. Hacking the driver layer from Windows onto Linux would not kill Linux - sure, the x86 version I’m sure many people would use, but what about all those other millions apon millions of SPARC, POWER and ALPHA (and about another billion platforms) out there? Those drivers are not controlled by Microsoft but rather the Hardware vendors. They won’t go around compiling drivers for a bunch of different architectures.
Besides, Microsoft would have to do a lot more for people to actually USE .MS-LINUX. . What about Microsoft.s .NET ?, what about all those apps out there that will need special libraries ported over to run on this new platform? It isn.t going to happen.
I won.t get too narky on Mr Dvorak, but the guy works in a market for Users (Writes for a mainstream computer magazine and hosts a show on TechTV). And really, what a sloppy article. No research and nothing strong to backup his points.
I guess it was a slow news day.
In the sprit of Erotic Cleft I give you a quote from Robert Jordans The Wheel Of Time.
“You are of no use to me or the Empire, unless you survive and you will not survive if you fail - page 425, line 19 Winters Heart
At my place of Employment, we use a distributed system for processing all of our 50 odd thousand unit tests. Anyway, what happens is that everynow and then one of the servers will start a tester on your local machine - automatically, the client steals half your RAM and CPU resources. This gets a bit horrible if you are debuging stuff from stack memory - everything gets hella slow and there is no way to stop it but kill off the process, but you know the bastard will back back in 10 mins. So I spent 2mins before going home and wrote this:
Process[] DatClient = Process.GetProcessesByName(”tester”);
foreach (Process testerProcess in DatClient)
{
testerProcess.Kill();
}
Every 100 seconds or so, this runs and kills of any tester process. Now I can actually work.