I have Verizon phone "service" in rural central Illinois. It's an old GTE network, I believe. You guys are worried about DSL? I can't even get CallerID! Lucky for me that I have a local ISP providing 3Mb/s 802.11B off of a nearby antenna tower for me and a couple of neighbors.
Transcript of typical phone service call: VZ: Go outside to your NIB. ME: I don't have one. VZ: Everyone has one. ME: You said you won't install one unless there's a problem. VZ: Oh, you have to call someone else. ME: What about my lack of phone service? VZ: Well, it's probably inside the house and we'll charge you.
VZ (Other people): We won't install a NIB unless you're having a problem. Are you having a problem? ME: No, they seem to have fixed it. VZ: Sorry...
When things break at our small engineering firm, our "consultant" sysadmin likes to make things himself. Why buy a cable, when you could spend 1/2 as much and build it yourself in a couple of days.
'Hey, what's that smell??' 'Oh, my $0.50 RadioShack soldering iron is burning through the box I set it on. Don't worry, the server will be back up later in the week.'
It seems that one problem Linux will encounter going forward against the Old School xNIX's is it is VERY portable. The OS supports a huge array of hardware. When people want linux to work, they want it to work on whatever PC they have in the back room. If it doesn't work with this, something gets changed in the code so that it eventually works. This provides a huge number of input factors to the linux code base.
"Old School" UNIX traditionally runs on a small set of proprietary hardware. Less support means more bandwidth for features and hardware-specific implementations. Also, this means fewer hardware configurations need to be tested for reliability.
Slashdot Mirror
I have Verizon phone "service" in rural central Illinois. It's an old GTE network, I believe. You guys are worried about DSL? I can't even get CallerID!
Lucky for me that I have a local ISP providing 3Mb/s 802.11B off of a nearby antenna tower for me and a couple of neighbors.
Transcript of typical phone service call:
VZ: Go outside to your NIB.
ME: I don't have one.
VZ: Everyone has one.
ME: You said you won't install one unless there's a problem.
VZ: Oh, you have to call someone else.
ME: What about my lack of phone service?
VZ: Well, it's probably inside the house and we'll charge you.
VZ (Other people): We won't install a NIB unless you're having a problem. Are you having a problem?
ME: No, they seem to have fixed it.
VZ: Sorry...
When things break at our small engineering firm, our "consultant" sysadmin likes to make things himself. Why buy a cable, when you could spend 1/2 as much and build it yourself in a couple of days.
'Hey, what's that smell??'
'Oh, my $0.50 RadioShack soldering iron is burning through the box I set it on. Don't worry, the server will be back up later in the week.'
It seems that one problem Linux will encounter going forward against the Old School xNIX's is it is VERY portable. The OS supports a huge array of hardware. When people want linux to work, they want it to work on whatever PC they have in the back room. If it doesn't work with this, something gets changed in the code so that it eventually works. This provides a huge number of input factors to the linux code base.
"Old School" UNIX traditionally runs on a small set of proprietary hardware. Less support means more bandwidth for features and hardware-specific implementations. Also, this means fewer hardware configurations need to be tested for reliability.