ventrilo and teamspeak PTT key? When I'm not on some voice chat I use it for any number of macros cause of it's position opposite enter (left pinky) makes it easy to remember (for me) whenever I use scroll-lock etc and I want to copy my macros to a laptop it's a pain finding the scroll lock (and sometimes you've gotta hold function to hit the thing.)
Well the first point, being that software is the IP of the software development company they've every right to follow their licensing contract to the letter. Now whether that gives you, and their customers, a warm squishy feeling I don't know. You would hope that people will certainly be more careful in the future, to be sure, when buying huge complex automation systems without control over the codebase that runs it. But that probably won't be the case, to the average person it's a simple contract dispute, and some people are pissed cause they can't get their cars. The employees at Sirius Cybernetics will no doubt be the first to go up against the wall when the revolution comes, but until then their creation will end up mothballed as another failed attempt at robotics.
The whole thing was done wrong to begin with, the city wasn't thinking they would be held hostage for their licensing. They need to have it redeveloped, but that kinda coding would take some good management and even better engineers to be done right, not to mention smarter purchasers who would only take open source/shared source proposals.
Now as far as "proprietary" development goes, I'm sure you're whiz-bang at managing it, and your team is spot on when it comes to their trade. I would wager that most aren't cut out to code only based on merit with dozens of eyes poking holes in their creations. It takes a strong sense of community, and a suppression of ego to do that; rather than just dollars.
Someone who is willing to work in that environment long enough, and thinks of his future replacements as drug-using malcontents, should stay working in that environment until they get old and retire so us idealistic dreamers can get on with our fantastic visions of parking lots that work without essentially leasing the "on" switch month to month.
Disney was crazy too but his crazy struck a chord with millions, dreamers are all at least a little loopy but your loopy just doesn't jive with my loopy. The problem traditional developers aren't facing is that free and open has nearly no limits to distribution. A line of code in some proprietary system may be used by thousands, maybe even tens/hundreds of thousands of users for a decade or so. I needn't mention the socket API implementation ponying along inside some proprietary code. I'm not even sour about that, more distribution gives OSS more weight in the real world. I mean, it's not like the worlds most successful internet companies run everything off open source platforms...
The smart companies and government institutions in the world are running open source because they're tired of dealing with idiots telling them they have to pay for crap that's still in development the day it's "released." "To hell with them, I'll code it myself." the enterprising dreamer says. And three days, six pots of coffe and an onset of blurred vision later, and there's *something* that can do the 4-5 things they were going to pay for that hasn't been released from Proprietary Bloatware Inc.
Your apps may be impressive and even have nearly a million users, but when anyone types ftp at a command prompt in windows, they're running Berkley code.
Microsoft may go bankrupt tomorrow, but the code they have reused will live on without them. Their code will shrivel up and the fruits of thousands of developers will go with the last platform they coded for. But OSS will keep on trucking, the socket API code will probably be reused AGAIN in the X96 139q-bit operating system, while we're all remeniscing about computers that you didn't really own, only leased.
If you have highschool students, the next thing they'll probably do is start using ssl based proxies. Port 443 is open wide in most situations, so https://kproxy.com/ and the like are likely going to be showing up in Internet Explorer Histories everywhere if they haven't started to already.
Now ssl sites are added to the allow lists only if they are requested.
Since the primary use of the internet (outside myspace through anonssl-proxies) has always been flash based game sites, I've been seriously considering blocking.swf entirely as well. It's one thing to ocassionally play games, but the unattended use of internet connected systems in schools is very high. You can only do so much technically before you begin hindering legitimate use, if nobody is there helping keep students on task it just degenerates into screwing around 99% of the time. And some of the staff & teachers aren't much better!
Look, the honest truth is people cheat to gain advantage, so we must expect this, and mitigate it whenever we (as engineers) can. So, as such the perfect Nevada Gaming Comission approved paper trail keeping, encrypted output, design would still be vulnerable to fraudulent paper ballot injection. One candidate (be they crooked or not) would demand a recount, (thinking the equipment faulty) and the paper votes would return a slightly different result in their favor.
You can't trust a citizen to be non-political completely if the vote will affect them in any way. So, essentially you need to pay someone to be your referee. And it would have to be someone who wouldn't be affected at all by the result of the vote.
So by those qualifiers we can't guarantee, ever, that every element of the existing paper vote is secure.
Two copies of your vote, one right after the other, printed and spewed into two different physical ballot boxes. The second box would contain tamper proof seals and would only be opened in the case of a full manual recount by a third party. As well as two digital copies, signed with a hash which was printed on a receipt (and mailed to an email if you like) you could verify against the other copy sent to the national voting database. Might be marginally better.
That way you can count all the votes all night and as the final results are tallied any innacuracies between the national and local databases would have to be rectified before any results were accepted from the precinct with invalid data.
Oh for f*cks sake, no more scantrons. I work in public ed and I can attest to the innacuracies associated with the "modern" scanning devices used in schools. THEY SUCK. The older models that companies stopped servicing were more reliable, had fewer moving parts and were made out of concrete (ok steel, but still.) The new ones are too fragile and sensitive to misalignment to give to a government employee, ESPECIALLY a volunteer employee.
Please please please, no more half bubbles, or partial bubbles or erased bubbles. This would be worse than hanging chads.
It's in large part inherent system design. The basic design point: the seperation between ordinary users and the administrative user (root). That seperation means that, even if you do get infected with malware, the malware can't spread into the system itself. It can't tie into system libraries, it can't have itself started at system startup, it can't disable system services (like the firewall or the malware scanner) and it can't hide itself from the administrative user. This provides a two-layer defense similar to the layout of a medieval castle: once the attackers break through the outer wall, they have to start all over again breaking through the defenses of the inner keep (while being stuck in the yard between the keep and the wall, easy prey for the defenders in the keep). Changes in market share and declining user sophistication won't have any effect on this aspect of things.
Yes. Security in rings means doing things right on every layer. In past Microsoft has had to apply security to where things should have been secure to begin with. If UAC (aka gui sudo/runas)is enabled by default in vista with the default user a standard user their security planning *might* be pointed in the right direction.
But most artists I know have to leave their parent's basement occasionally or they get geekitis and loose their artistic ability in exchange for a pocket protector, or a lvl 60 paladin.
Artists can't eat good video games. Maybe a donation center just for open source art (models, skins etc) needs to be established with a system for comissioning artists renderings.
From what I gathered from a previous poster Skype TCP traffic may pass over 443, but it's not necessarily ssl encrypted (unless that's your method of browser defined proxy) the traffic is partially RC4'd and partially unencrypted.
You could probably sniff a skype data stream, find some common indicators among all the unencrypted data and write a signature to stop certain skype traffic on your IPS. It may not stop skype from operating entirely, but it would no doubt cripple it much more than simply blocking UDP.
As far as SSL connections through a proxy, if the "man in the middle" you described were patently illegal every company that uses GPOs to distribute explicit proxy information would be violating privacy laws. Now, if you or I did this surruptitiously, we'd go to jail. But if a corporation does it, it's good business practice. Since every SSL session is sent and recieved from the predefined Proxy, and not the user sniffing the unecrypted data would be trivial.
Well, as the handout (and others here) states you can block UDP, but it's not enough to keep Skype from functioning. You need more drastic measures. From reading this, my oppinion has changed. Using an IPS you might be able to write a signature to keep it from working, as not all of the data is encrypted.
You could proxy all SSL through a controlled host, and keep regular SSL blocked to maintain some modicum of control over the users SSL use. Otherwise, barring unsavory techniques it's not really supposed to be possible.
Skype started using the default option "Use port 443 and port 80 for incoming connections" Unless you do layer 7 (basically content based) filtering of those packets you can't see them from regular web traffic.
You mean like, MORPGs? Diablo I, Diablo II, Dungeon Siege I, Dungeon Siege II, Guild Wars etc? Not *exactly* the same experience as a pay by the month but certainly lots of replay value.
and probably without too much effort either. Think Dnet client, only XPnet (or soon to be Vnet) clients built into the OS.
The new status quo would be distributed processing. Think how Microsoft could leverage it's inefficient software and operating systems by leeching processor power and memory from the workstations themselves especially with 10/100/1000 switches fast becoming the norm. Forget client side processing, client side serving could give M$ a huge leap forward without actually having to develop the leanest, most secure, or efficient code.
Don't hate, just cause my wife is more vulgar than you isn't any reason to feel emasculated. It's not like she also runs an erotic link blog, but we won't even go there.
It's also not like she isn't educated enough to understand the original etymology either and having been on the recieving end of her explanations of the pejorative usage (sometimes also spelled ghey) I'd say she's a far sight removed from ignorant.
If it helps you any, think of it as equivalent to Michael Jackson's bad. If you feel it is derogatory, then get over it.
Me: So, the XBOX 360 won't let you play your older Xbox games unless they are specifically supported. Her: That's gay. Why would I want to have to buy the same games again with 360 tacked on? Me: I dunno, but the playstation 3 will be 100% backwards compatible. Her: It better be or I'll just buy another PS2.
Her game library is somewhere around 40-50 games on the PS2 not including her PS1 games.
PS1 games only recently were pushed off the shelves at Gamestops... and the PS1 hasn't been sony's the flagship console for a very long time. I bet the main reason they were around so long is because not only do people with PS1/one/PSX consoles have the ability, but everyone with PS2's also have the ability to run them.
When the PS3 comes out, the available library will start inbetween 4 and 5 digits worth of content... That's massive in comparison to the barely triple digits the 360 squeeked out on release. There's incentive for buying the console just based on features at that point. Even if there's no game you want for the PS3 you can still get rid of your clicking-whirring 5+ year old PS2 and have a HD capable nextgen movie player without sacrificing your investment in content that could potentially go back over 10 years.
She's an adventure/horror survival buff, so the exlusive releases are definitely her draw to the PS3, but the fact that we can rotate a dusty beast out of the entertainment center is also a plus imo.
I concur with the parent as far as building unattended installs goes: a few resources (some of which were mentioned earlier): MSFN.org nlite BartPE Technet XP Deployment ref Disclaimer: Scan anything you download thoroughly for viruses. The worst thing you could do is inject a vulnerability in your image framework.
If you are in the position to need to reload your systems for any reason remotely I would suggest using a PXE deployment solution of some kind. Ghost/Altiris both provide good PXE and post-install config utilities. We use altiris and deploy our images through PXE. This allows for imaging in place after the fact, something that we try do semi-anually.
Every major vendor provides UNDI-Driver capable on-board nics now-a-days, so the headache of PXE (nic specific) boot images is pretty much a thing of the past (unless you were one of the saps who bought the Gateway E-4300s.)
There's something about booting to your nic, loading an image on a station in 8 minutes and monitoring the unattended install from a remote TS console miles away from the station you're reloading.
98 (even SE) is still just a rehash of 95b, which was just an addon to fix 95 Plug n Pray, which was an added network stack and a pretty face to the win32api which was incepted circa win3.11, all of which ran on top of the old horse glue of x86: DOS.
So yes, you should not be running the os which made: "bad command or file name" famous on the internet.
As far as TFM it's qualifications draw my suspision. Did they include "devices" running linux as well or just full blown rigs? I can tell you *nix based appliances (unless they're really bad) have very few problems, and don't typically require the constant reboots for system updates that drives down your 99.99..999999 uptime.
Whatever happened to limiting exploitable processes? Windows method of protecting the services is all based around their firewall. Ever try and configure a windows box to run slimmed down? It's a pain in the ass. How about hardened? Good luck, apply the NIST standard lockdown SecPol to a 2k3 box and you'll see what I mean.
Take a *BSD/Trustix(+SELINUX)/Debian(+SELINUX) box install with 3 services AND a firewall in a 100meg footprint, and call it a day. Windows can't compete with the kinda uptime you get out of a stripped down OS. Oh they try with XP-Embedded and the likes but it's certainly not within the same realm of ease to create and deploy the OS that the *nixes give you. Not to mention, how many times have you had to troubleshoot a problem in Windows that ended up being caused by some unrelated service? I can tell you from my experience, it doesn't happen very often on a machine running single digit numbers of services.
On top of which they nicely avoided shops smart enough not to run Windows devices in their nocs, who probably have much better trained staff on the unix hardware and would throw their numbers with nearly 0 downtime figures. How many untrained people new to unix reboot when they could have just restarted a service? etc. This whole thing smells fishy.
AOL didn't begin giving access to tha intarweb until about 1993-1995 if I recall. Back then it wasn't the killer app. In fact, everybody had their own sets of 'killa-yer-wallet' apps. I would bet AOL's bread n butter back then were it's online entertainment services that were pay by the hour.
Everybody had those, Prodigy, Compuserv etc. The pay by the hour service model was all the rave. They were all pretty similar, with a few notable exceptions (TSN later INN was the most unique IMO). I ended up ditching all the pretty foo-foo graphical BBS's for Concentric Research back in 95 once they became a full PPP based ISP. The benefit of AOL over the other embrionic ISPs was that it did all the garbage Wintrumpet BS transparent to the user. The graphical garbage can that is AOL drew users in with simple graphics that said "mail" and "news" etc. It is/was information organized for 6th graders... which apparently is all the average American wants.
So, I guess in the same way the tabloid was a terrible invention, AOL is a very marketable product even if it is flavorless and tasteless for the discriminating user.
Why would MCSE's primarily use Terminal Services when NTLM authenticated telnet allows you to manage the server through a text based console without a hit on the proc that a gui entails?
Because it's not easy, intuitive or picture based. Different minds, different methods. Ubuntu's biggest advantage is that it's debian based (dpkg, apt etc.) It's secondary advantage of being easy to navigate makes it's possible installbase much broader. Sure a gui will eat up some cycles, but the training time you save is substantial.
Not everyone is a console commando and if they are, they probably already use *nix.
Slashdot Mirror
ventrilo and teamspeak PTT key? When I'm not on some voice chat I use it for any number of macros cause of it's position opposite enter (left pinky) makes it easy to remember (for me) whenever I use scroll-lock etc and I want to copy my macros to a laptop it's a pain finding the scroll lock (and sometimes you've gotta hold function to hit the thing.)
Well the first point, being that software is the IP of the software development company they've every right to follow their licensing contract to the letter. Now whether that gives you, and their customers, a warm squishy feeling I don't know. You would hope that people will certainly be more careful in the future, to be sure, when buying huge complex automation systems without control over the codebase that runs it. But that probably won't be the case, to the average person it's a simple contract dispute, and some people are pissed cause they can't get their cars. The employees at Sirius Cybernetics will no doubt be the first to go up against the wall when the revolution comes, but until then their creation will end up mothballed as another failed attempt at robotics.
The whole thing was done wrong to begin with, the city wasn't thinking they would be held hostage for their licensing. They need to have it redeveloped, but that kinda coding would take some good management and even better engineers to be done right, not to mention smarter purchasers who would only take open source/shared source proposals.
Now as far as "proprietary" development goes, I'm sure you're whiz-bang at managing it, and your team is spot on when it comes to their trade. I would wager that most aren't cut out to code only based on merit with dozens of eyes poking holes in their creations. It takes a strong sense of community, and a suppression of ego to do that; rather than just dollars.
Someone who is willing to work in that environment long enough, and thinks of his future replacements as drug-using malcontents, should stay working in that environment until they get old and retire so us idealistic dreamers can get on with our fantastic visions of parking lots that work without essentially leasing the "on" switch month to month.
Disney was crazy too but his crazy struck a chord with millions, dreamers are all at least a little loopy but your loopy just doesn't jive with my loopy. The problem traditional developers aren't facing is that free and open has nearly no limits to distribution. A line of code in some proprietary system may be used by thousands, maybe even tens/hundreds of thousands of users for a decade or so. I needn't mention the socket API implementation ponying along inside some proprietary code. I'm not even sour about that, more distribution gives OSS more weight in the real world. I mean, it's not like the worlds most successful internet companies run everything off open source platforms...
The smart companies and government institutions in the world are running open source because they're tired of dealing with idiots telling them they have to pay for crap that's still in development the day it's "released." "To hell with them, I'll code it myself." the enterprising dreamer says. And three days, six pots of coffe and an onset of blurred vision later, and there's *something* that can do the 4-5 things they were going to pay for that hasn't been released from Proprietary Bloatware Inc.
Your apps may be impressive and even have nearly a million users, but when anyone types ftp at a command prompt in windows, they're running Berkley code.
Microsoft may go bankrupt tomorrow, but the code they have reused will live on without them. Their code will shrivel up and the fruits of thousands of developers will go with the last platform they coded for. But OSS will keep on trucking, the socket API code will probably be reused AGAIN in the X96 139q-bit operating system, while we're all remeniscing about computers that you didn't really own, only leased.
If you have highschool students, the next thing they'll probably do is start using ssl based proxies. Port 443 is open wide in most situations, so https://kproxy.com/ and the like are likely going to be showing up in Internet Explorer Histories everywhere if they haven't started to already.
.swf entirely as well. It's one thing to ocassionally play games, but the unattended use of internet connected systems in schools is very high. You can only do so much technically before you begin hindering legitimate use, if nobody is there helping keep students on task it just degenerates into screwing around 99% of the time. And some of the staff & teachers aren't much better!
Now ssl sites are added to the allow lists only if they are requested.
Since the primary use of the internet (outside myspace through anonssl-proxies) has always been flash based game sites, I've been seriously considering blocking
Look, the honest truth is people cheat to gain advantage, so we must expect this, and mitigate it whenever we (as engineers) can. So, as such the perfect Nevada Gaming Comission approved paper trail keeping, encrypted output, design would still be vulnerable to fraudulent paper ballot injection. One candidate (be they crooked or not) would demand a recount, (thinking the equipment faulty) and the paper votes would return a slightly different result in their favor.
You can't trust a citizen to be non-political completely if the vote will affect them in any way. So, essentially you need to pay someone to be your referee. And it would have to be someone who wouldn't be affected at all by the result of the vote.
So by those qualifiers we can't guarantee, ever, that every element of the existing paper vote is secure.
Two copies of your vote, one right after the other, printed and spewed into two different physical ballot boxes. The second box would contain tamper proof seals and would only be opened in the case of a full manual recount by a third party. As well as two digital copies, signed with a hash which was printed on a receipt (and mailed to an email if you like) you could verify against the other copy sent to the national voting database. Might be marginally better.
That way you can count all the votes all night and as the final results are tallied any innacuracies between the national and local databases would have to be rectified before any results were accepted from the precinct with invalid data.
Oh for f*cks sake, no more scantrons. I work in public ed and I can attest to the innacuracies associated with the "modern" scanning devices used in schools. THEY SUCK. The older models that companies stopped servicing were more reliable, had fewer moving parts and were made out of concrete (ok steel, but still.) The new ones are too fragile and sensitive to misalignment to give to a government employee, ESPECIALLY a volunteer employee.
Please please please, no more half bubbles, or partial bubbles or erased bubbles. This would be worse than hanging chads.
Yes. Security in rings means doing things right on every layer. In past Microsoft has had to apply security to where things should have been secure to begin with. If UAC (aka gui sudo/runas)is enabled by default in vista with the default user a standard user their security planning *might* be pointed in the right direction.
But most artists I know have to leave their parent's basement occasionally or they get geekitis and loose their artistic ability in exchange for a pocket protector, or a lvl 60 paladin.
Artists can't eat good video games. Maybe a donation center just for open source art (models, skins etc) needs to be established with a system for comissioning artists renderings.
From what I gathered from a previous poster Skype TCP traffic may pass over 443, but it's not necessarily ssl encrypted (unless that's your method of browser defined proxy) the traffic is partially RC4'd and partially unencrypted.
You could probably sniff a skype data stream, find some common indicators among all the unencrypted data and write a signature to stop certain skype traffic on your IPS. It may not stop skype from operating entirely, but it would no doubt cripple it much more than simply blocking UDP.
As far as SSL connections through a proxy, if the "man in the middle" you described were patently illegal every company that uses GPOs to distribute explicit proxy information would be violating privacy laws. Now, if you or I did this surruptitiously, we'd go to jail. But if a corporation does it, it's good business practice. Since every SSL session is sent and recieved from the predefined Proxy, and not the user sniffing the unecrypted data would be trivial.
Well, as the handout (and others here) states you can block UDP, but it's not enough to keep Skype from functioning. You need more drastic measures. From reading this, my oppinion has changed. Using an IPS you might be able to write a signature to keep it from working, as not all of the data is encrypted.
You could proxy all SSL through a controlled host, and keep regular SSL blocked to maintain some modicum of control over the users SSL use. Otherwise, barring unsavory techniques it's not really supposed to be possible.
Skype started using the default option "Use port 443 and port 80 for incoming connections" Unless you do layer 7 (basically content based) filtering of those packets you can't see them from regular web traffic.
Same thing happened to my wife, only the culprit was one of the P-touch style labels causing the cd to slightly oscillate inside the lite-on drive.
I'm sure I'm not the first to speculate that perhaps Cisco doesn't want to release a sub $100 WAP+router that competes with their $1000+ waps
You mean like, MORPGs? Diablo I, Diablo II, Dungeon Siege I, Dungeon Siege II, Guild Wars etc? Not *exactly* the same experience as a pay by the month but certainly lots of replay value.
and probably without too much effort either. Think Dnet client, only XPnet (or soon to be Vnet) clients built into the OS.
The new status quo would be distributed processing. Think how Microsoft could leverage it's inefficient software and operating systems by leeching processor power and memory from the workstations themselves especially with 10/100/1000 switches fast becoming the norm. Forget client side processing, client side serving could give M$ a huge leap forward without actually having to develop the leanest, most secure, or efficient code.
Don't hate, just cause my wife is more vulgar than you isn't any reason to feel emasculated. It's not like she also runs an erotic link blog, but we won't even go there.
It's also not like she isn't educated enough to understand the original etymology either and having been on the recieving end of her explanations of the pejorative usage (sometimes also spelled ghey) I'd say she's a far sight removed from ignorant.
If it helps you any, think of it as equivalent to Michael Jackson's bad. If you feel it is derogatory, then get over it.
is the main selling point.
I think my wife said it best:
Me: So, the XBOX 360 won't let you play your older Xbox games unless they are specifically supported.
Her: That's gay. Why would I want to have to buy the same games again with 360 tacked on?
Me: I dunno, but the playstation 3 will be 100% backwards compatible.
Her: It better be or I'll just buy another PS2.
Her game library is somewhere around 40-50 games on the PS2 not including her PS1 games.
PS1 games only recently were pushed off the shelves at Gamestops... and the PS1 hasn't been sony's the flagship console for a very long time. I bet the main reason they were around so long is because not only do people with PS1/one/PSX consoles have the ability, but everyone with PS2's also have the ability to run them.
When the PS3 comes out, the available library will start inbetween 4 and 5 digits worth of content... That's massive in comparison to the barely triple digits the 360 squeeked out on release. There's incentive for buying the console just based on features at that point. Even if there's no game you want for the PS3 you can still get rid of your clicking-whirring 5+ year old PS2 and have a HD capable nextgen movie player without sacrificing your investment in content that could potentially go back over 10 years.
She's an adventure/horror survival buff, so the exlusive releases are definitely her draw to the PS3, but the fact that we can rotate a dusty beast out of the entertainment center is also a plus imo.
I concur with the parent as far as building unattended installs goes:
a few resources (some of which were mentioned earlier):
MSFN.org
nlite
BartPE
Technet XP Deployment ref
Disclaimer: Scan anything you download thoroughly for viruses. The worst thing you could do is inject a vulnerability in your image framework.
If you are in the position to need to reload your systems for any reason remotely I would suggest using a PXE deployment solution of some kind. Ghost/Altiris both provide good PXE and post-install config utilities. We use altiris and deploy our images through PXE. This allows for imaging in place after the fact, something that we try do semi-anually.
Every major vendor provides UNDI-Driver capable on-board nics now-a-days, so the headache of PXE (nic specific) boot images is pretty much a thing of the past (unless you were one of the saps who bought the Gateway E-4300s.)
There's something about booting to your nic, loading an image on a station in 8 minutes and monitoring the unattended install from a remote TS console miles away from the station you're reloading.
98 (even SE) is still just a rehash of 95b, which was just an addon to fix 95 Plug n Pray, which was an added network stack and a pretty face to the win32api which was incepted circa win3.11, all of which ran on top of the old horse glue of x86: DOS.
So yes, you should not be running the os which made: "bad command or file name" famous on the internet.
As far as TFM it's qualifications draw my suspision. Did they include "devices" running linux as well or just full blown rigs? I can tell you *nix based appliances (unless they're really bad) have very few problems, and don't typically require the constant reboots for system updates that drives down your 99.99..999999 uptime.
Whatever happened to limiting exploitable processes? Windows method of protecting the services is all based around their firewall. Ever try and configure a windows box to run slimmed down? It's a pain in the ass. How about hardened? Good luck, apply the NIST standard lockdown SecPol to a 2k3 box and you'll see what I mean.
Take a *BSD/Trustix(+SELINUX)/Debian(+SELINUX) box install with 3 services AND a firewall in a 100meg footprint, and call it a day. Windows can't compete with the kinda uptime you get out of a stripped down OS. Oh they try with XP-Embedded and the likes but it's certainly not within the same realm of ease to create and deploy the OS that the *nixes give you. Not to mention, how many times have you had to troubleshoot a problem in Windows that ended up being caused by some unrelated service? I can tell you from my experience, it doesn't happen very often on a machine running single digit numbers of services.
On top of which they nicely avoided shops smart enough not to run Windows devices in their nocs, who probably have much better trained staff on the unix hardware and would throw their numbers with nearly 0 downtime figures. How many untrained people new to unix reboot when they could have just restarted a service? etc. This whole thing smells fishy.
AOL didn't begin giving access to tha intarweb until about 1993-1995 if I recall. Back then it wasn't the killer app. In fact, everybody had their own sets of 'killa-yer-wallet' apps. I would bet AOL's bread n butter back then were it's online entertainment services that were pay by the hour.
Everybody had those, Prodigy, Compuserv etc. The pay by the hour service model was all the rave. They were all pretty similar, with a few notable exceptions (TSN later INN was the most unique IMO). I ended up ditching all the pretty foo-foo graphical BBS's for Concentric Research back in 95 once they became a full PPP based ISP. The benefit of AOL over the other embrionic ISPs was that it did all the garbage Wintrumpet BS transparent to the user. The graphical garbage can that is AOL drew users in with simple graphics that said "mail" and "news" etc. It is/was information organized for 6th graders... which apparently is all the average American wants.
So, I guess in the same way the tabloid was a terrible invention, AOL is a very marketable product even if it is flavorless and tasteless for the discriminating user.
XMCF
Why would MCSE's primarily use Terminal Services when NTLM authenticated telnet allows you to manage the server through a text based console without a hit on the proc that a gui entails?
Because it's not easy, intuitive or picture based. Different minds, different methods. Ubuntu's biggest advantage is that it's debian based (dpkg, apt etc.) It's secondary advantage of being easy to navigate makes it's possible installbase much broader. Sure a gui will eat up some cycles, but the training time you save is substantial.
Not everyone is a console commando and if they are, they probably already use *nix.
Jehovah's Witnesses carry cards, or wear wrist straps that say "No Blood" there have been court cases surrounding this.
Link here