|
|
|
|
|
| Thursday, 10 January 2008 | ||||||
|
I got home today and noticed my light and an appliance was switched on. No biggy I thought, perhaps I'd left it on, but in my geeky nature it occured to me the appliance was running Linux and I could issue an uptime command to check how long it had been running.
I fired up a command prompt window and executed telnet. Command not found. Ugg. A quick google and it seems Vista ships with telnet disabled. A quick Start -> Settings -> Control Panel -> Programs and Features -> Turn Windows features on or off -> Windows needs your permission to continue (continue) -> Scroll down -> Tick Telnet Client -> Apply -> Wait 5 minutes (literally) -> finished -- and there was telnet in all its glory.
I then connected to the appliance and did a quick uptime showing me it had been on for 5 hours and 25 minutes.
The reason I bring this up? Another simple example of where Linux gets it right and Windows gets it oh so wrong. Telnet it only a 75Kb app. It wouldn't have increased the footprint too much installing it by default, and it would have been quicker to download from the internet and compile from source on Linux than it was to install the binary from the local disk under Windows. Should it really have taken 5 minutes to install a 75Kb app? TCO anyone?
Linux 2 - Windows 0  Quote this article on your site
Only registered users can write comments.
|
||||||
Comments (2)
