This oughta be just _GREAT_ -- MS is again trying to use sysadmins all around the world as their pawns -- Imagine:
Ignorant MS-using sysadmins have already promised to migrate corporate network to Win1900 as soon as it is released
Ignorant MS-using sysadmins cannot back down NOW, just because of some silly addressing thing they don't really understand
Ignorant MS-using sysadmins already dislike UNIX sysadmins for being 'stuck with 20 year old technology' ( Ignore this if you administrate both..:) )
Ignorant MS-using sysadmin is now Microsoft's pawn in their latest Embrace/Extend/Extinguish attempt...
Can 'The Government' sue them for THAT, please? This is somewhat hypocritical in the face of MS wanting AOL to release a spec so 'everyone' can conform (those AIM thingys), and here they want to cause more division...
I use a perl script called ripit.pl that rips the tracks from a cd, uses CDDB to name them, and encode them into mp3s. I can't remember where I got it but all the credits are still there, I wish the author had put their email or web address in the info block.. Anyway, it rocks, but it uses cdparanoia and bladeenc so I'm modifing it to use Xing with cdparanoia.
The prefix Giga is really supposed to be pronounced 'Jiga', like Doc and Marty in 'Back to the Future' ( 1 POINT 21 GIGAWATTS?!?! WHAT THE HELL IS A GIGAWATT! ), and people don't pronounce _that_ correctly -- I mean, who wants a 10 'Jig' Hard Drive..:) Compared to this, the new prefixes look like they WANT us to mis-pronounce them...
2200 hits/second of **HTML**... No one has such a problem, because that's a damn lot of hits, fast -- The problem with NT is UPTIME... Let's subject both OS's on the same hardware to the same load, have them serving cgi/php, and see which one crashes first.... Uptime is a MUCH bigger concern with a webserver than if it can serve 1000 or 2000 _TEXT_ pages per second...
Slashdot Mirror
- Ignorant MS-using sysadmins have already promised to migrate corporate network to Win1900 as soon as it is released
- Ignorant MS-using sysadmins cannot back down NOW, just because of some silly addressing thing they don't really understand
- Ignorant MS-using sysadmins already dislike UNIX sysadmins for being 'stuck with 20 year old technology' ( Ignore this if you administrate both..
:) ) - Ignorant MS-using sysadmin is now Microsoft's pawn in their latest Embrace/Extend/Extinguish attempt...
Can 'The Government' sue them for THAT, please? This is somewhat hypocritical in the face of MS wanting AOL to release a spec so 'everyone' can conform (those AIM thingys), and here they want to cause more division...I use a perl script called ripit.pl that rips the tracks from a cd, uses CDDB to name them, and encode them into mp3s. I can't remember where I got it but all the credits are still there, I wish the author had put their email or web address in the info block.. Anyway, it rocks, but it uses cdparanoia and bladeenc so I'm modifing it to use Xing with cdparanoia.
The prefix Giga is really supposed to be pronounced 'Jiga', like Doc and Marty in 'Back to the Future' ( 1 POINT 21 GIGAWATTS?!?! WHAT THE HELL IS A GIGAWATT! ), and people don't pronounce _that_ correctly -- I mean, who wants a 10 'Jig' Hard Drive.. :) Compared to this, the new prefixes look like they WANT us to mis-pronounce them...
2200 hits/second of **HTML**... No one has such a problem, because that's a damn lot of hits, fast -- The problem with NT is UPTIME... Let's subject both OS's on the same hardware to the same load, have them serving cgi/php, and see which one crashes first.... Uptime is a MUCH bigger concern with a webserver than if it can serve 1000 or 2000 _TEXT_ pages per second...