Hi. I'm jon.404, a Unix/Linux/Database/Openstack/Kubernetes Administrator, AWS/GCP/Azure Engineer, mathematics enthusiast, and amateur philosopher. This is where I rant about that which upsets me, laugh about that which amuses me, and jabber about that which holds my interest most: *nix.
Warning: Rant Ahead!
Today a thought occurred to me...
If I want to "kill -2 1" any one of my Linux boxen, I can. Linux will happily oblige, and I will have shot myself in the foot and upset both customers and management. Obviously this isn't something I want to do, but Linux (and the BSD's, for that matter), make no judgement call. They simply do what you tell them to do.
Not so with Windows. Today I found the evil ATI driver bug that causes Terminal Services to go brain dead. Three things are disturbing about this...
1) Why did Dell deem it necessary for me to have a 2D accelerated graphics driver in a *server*?
2) How can a buggy graphics driver take down Terminal Services (no more Remote Desktop...devs complain company-wide!)?
3) Why can't I Start -> Settings -> Administrative Tools -> Services -> right-click Terminal Services -> Restart?
I'm well aware of how layering services in Windows gets some strange dependency graphs going (can't restart this service without restarting a seemingly unrelated service), but I fail to see how Terminal Services is a required service that it takes a reboot to restart...
Perhaps my Microsoft-fu needs some work.
If I want to "kill -2 1" any one of my Linux boxen, I can. Linux will happily oblige, and I will have shot myself in the foot and upset both customers and management. Obviously this isn't something I want to do, but Linux (and the BSD's, for that matter), make no judgement call. They simply do what you tell them to do.
Not so with Windows. Today I found the evil ATI driver bug that causes Terminal Services to go brain dead. Three things are disturbing about this...
1) Why did Dell deem it necessary for me to have a 2D accelerated graphics driver in a *server*?
2) How can a buggy graphics driver take down Terminal Services (no more Remote Desktop...devs complain company-wide!)?
3) Why can't I Start -> Settings -> Administrative Tools -> Services -> right-click Terminal Services -> Restart?
I'm well aware of how layering services in Windows gets some strange dependency graphs going (can't restart this service without restarting a seemingly unrelated service), but I fail to see how Terminal Services is a required service that it takes a reboot to restart...
Perhaps my Microsoft-fu needs some work.
Total Comments 0
