I am glad that CmdrTaco is able to say what anyone else would say. I have no problem calling people idiots that I think deserve it. Right on Malda.. keep up the good work
Re:Notice something familiar about MS uptimes?
on
Server Uptimes Ranked
·
· Score: 2
Thats really not true at all. I dont recall if that problem even existed in NT, if so it was fixed long ago. The problem now is that GetTickCount() will only report 49 days uptime I believe, but you can easily use microsofts uptime utility to gather the uptime from the reboots in the system log. I have several NT servers well over 150 days uptime.
I administer 4 NT machines right now at work. The average uptime of them right now is about 115 days. The only reason I ever have to reboot these for the most part is when I install new software or a new service pack. Likewise i have a linux box with about the same uptime and the only reason I have to reboot it is to upgrade to a newer kernel... so whats your point? People like to trash on NT.. and its not my favorite os by any means... but it gets the job done.
Microsoft has an uptime.exe utility that can be found somewhere on their webpage. Just do a search for Uptime.exe. It actaully uses the event log to look at the last reboot compared to the new date. This isnt the best way but it works. It also queries network machines. I have several NT servers that have more than a 100 day uptime
I dont see any problem with them patenting the specific algorithim as long as they are not trying to patent the idea behind the alogorithim. I think its good buisness practice to make your competitors work a little. No need to get beat at your own game
I definatly agree. Applied Cryptography is a great place to start. Another book that is very interesting is called Dissapearing Cryptography. It is about Stenography, which is a type of cryptography, but also covers general cryptography at the beginning. Both are excellent resources.
We have used thin clients a bit were I work. From my experience, there are some huge beniefits to using this at a school, and one major downfall. The downfall? I know at my high school, there was no real IT person... just a teacher who knew a good bit about computers.. but anything to do with client/server? no way. But with users who can easily mess things up in a fat client area thin clients are great. No need to go in and fix everything after the little punk kids change all teh settings or what not. I remember a few years ago..... hehe
I have used Mindspring before, and if memory serves me correct, you can simply sign up over the web. It worked perfect in every OS I tried, Linux, FreeBSD, Windows 9x/NT, and BeOS. But, since my work has an 800 dialup, that makes my life much easier now.. and it too works with all OS's.. though they would hate it if they knew I wasnt using Windows... ARGGGGGG
Slashdot Mirror
I am glad that CmdrTaco is able to say what anyone else would say. I have no problem calling people idiots that I think deserve it. Right on Malda.. keep up the good work
Microsoft's website should smell like a skunk!
Thats really not true at all. I dont recall if that problem even existed in NT, if so it was fixed long ago. The problem now is that GetTickCount() will only report 49 days uptime I believe, but you can easily use microsofts uptime utility to gather the uptime from the reboots in the system log. I have several NT servers well over 150 days uptime.
I administer 4 NT machines right now at work. The average uptime of them right now is about 115 days. The only reason I ever have to reboot these for the most part is when I install new software or a new service pack. Likewise i have a linux box with about the same uptime and the only reason I have to reboot it is to upgrade to a newer kernel... so whats your point? People like to trash on NT.. and its not my favorite os by any means... but it gets the job done.
Microsoft has an uptime.exe utility that can be found somewhere on their webpage. Just do a search for Uptime.exe. It actaully uses the event log to look at the last reboot compared to the new date. This isnt the best way but it works. It also queries network machines. I have several NT servers that have more than a 100 day uptime
I dont see any problem with them patenting the specific algorithim as long as they are not trying to patent the idea behind the alogorithim. I think its good buisness practice to make your competitors work a little. No need to get beat at your own game
This is nothing new. You could always go to www.google.com/linux and get there. Its great to see it listed on the front page now though!
I definatly agree. Applied Cryptography is a great place to start. Another book that is very interesting is called Dissapearing Cryptography. It is about Stenography, which is a type of cryptography, but also covers general cryptography at the beginning. Both are excellent resources.
We have used thin clients a bit were I work. From my experience, there are some huge beniefits to using this at a school, and one major downfall. The downfall? I know at my high school, there was no real IT person... just a teacher who knew a good bit about computers.. but anything to do with client/server? no way. But with users who can easily mess things up in a fat client area thin clients are great. No need to go in and fix everything after the little punk kids change all teh settings or what not. I remember a few years ago..... hehe
I have used Mindspring before, and if memory serves me correct, you can simply sign up over the web. It worked perfect in every OS I tried, Linux, FreeBSD, Windows 9x/NT, and BeOS. But, since my work has an 800 dialup, that makes my life much easier now.. and it too works with all OS's.. though they would hate it if they knew I wasnt using Windows... ARGGGGGG