When the car industry replaced horses (in the U.S.), that created a wide range of American jobs for a broad range of people with a broad range of skill/education levels. Manufacturing jobs, engineering jobs, repair jobs (your neighbourhood mechanic, anyone?), construction jobs (all the roads needed for cars), etc.
Apple (or most modern technology companies) doesn't. They create engineering jobs (until those get moved to India). They create jobs flipping burgers (the only jobs left for unskilled workers in America) in their cafeteria for the engineers and marketeers. Jobs for FedEx airline pilots who fly planes full of iPads from China. Retail jobs in the Apple stores. But unlike most innovations of an earlier era (cars, airplanes, trains, whatever), iPads (or iPhones or iPods) create next to no blue-collar jobs in the country that invented it. No repair jobs (what repair? send it back to China for refurbishment) and no manufacturing/assembly jobs (all done overseas). And the suppliers' manufacturing jobs (along with many high-skilled engineering jobs, e.g. for the LCD panels) are all overseas too...
I had a BlackBerry a few years ago. It was made in Canada. If RIM can do some of their manufacturing in their home country (I believe they also outsource some production), so could Apple.
Perhaps because slashdot has multiple servers with lots of big hardware located at Exodus, and that few other people (except for big names like Yahoo, CNN, etc) can afford big connectivity?
So, would you rather that we lie to you and tell you everything works well? Things break in any business, and you'd be an idiot to base your attitude on the opposite assumption. The difference, folks, lies not in whether one's service seems to break or not, but in how the operators of this service respond to the failure.
Actually, blocking incoming port 25 is effective against spam because it prevents open sendmails from being used as a relay.
If you block outgoing port 25, people will set their sendmails' smart host option to the local mail server, and then the spam will go through that box AND the university mail server as well. Sure, there'll be a LARGE trail of logs, but...
The @Home network? The only reason the @Home network has LOTS of hops is that they're running optical stuff (packet over DWDM), and with that, as opposed to ATM-type links, EVERY link is visible in a traceroute.
BTW, traceroute to Slashdot from @Home: Tracing route to slashdot.org [206.170.14.75] over a maximum of 30 hops:
1 27 ms 30 ms 3 ms ottawa-fe.net.rogers.wave.ca [24.112.33.1] 2 16 ms 35 ms 24 ms 10.0.184.53 3 41 ms 22 ms 30 ms 24.2.9.9 4 15 ms 26 ms 27 ms c1-pos9-1.bflony1.home.net [24.7.72.245] 5 17 ms 29 ms 33 ms c1-pos1-0.clevoh1.home.net [24.7.65.5] 6 28 ms 30 ms 30 ms c1-pos5-3.cmdnnj1.home.net [24.7.67.158] 7 33 ms 29 ms 30 ms c1-pos1-0.washdc1.home.net [24.7.65.85] 8 35 ms 32 ms 56 ms bb1-pos2-1-0.mae-e.nap.home.net [24.7.72.54] 9 72 ms 72 ms 43 ms mae-east.ibm.net [192.41.177.110] 10 59 ms 66 ms 52 ms beth1sr2-11-0-0.md.us.ibm.net [198.133.27.10] 11 68 ms 71 ms 60 ms bethjbr1-ge-1-0-0-0.md.us.ibm.net [165.87.29.122 ] 12 106 ms 95 ms 93 ms sfra1br1-at-2-0-0-2.ca.us.ibm.net [165.87.230.98 ] 13 121 ms 89 ms 91 ms sfra1sr3-so-0-0-0-0.ca.us.ibm.net [165.87.13.30]
14 101 ms 112 ms 93 ms 165.87.161.73 15 97 ms 122 ms * ded1-fa11-1-0.snfc21.pbi.net [209.232.130.4] 16 113 ms 95 ms 92 ms 209.232.138.214 17 111 ms 92 ms 92 ms slashdot.org [206.170.14.75]
Personally, I'd say the reason for LOTS of hops is because Slashdot uses PacBell's backbone, which seems to ONLY talk to the world via IBM, etc...
@Home uses Solaris hardware. I knew from Netcraft that their web server (the local one for here, www.slnt1.on.wave.home.com - their portal) ran Solaris, and I had somebody queso the mail server, Solaris again. @Home's main network architect said just today that they use all Suns.
BTW, Bell is the one who is going to be implementing PPP over Ethernet very soon. (see http://www.redback.com/) Just so you know, Linux doesn't support PPPoE yet, and the ONLY clients for it at the moment are for Win9X. Of course, it is an RFC, so I'm sure somebody will add it to Linux within a few months, but....
Look at the specs around http://www.bellnexxia.com. They are deploying RedBack SMS-based (http://www.redback.com) equipment so that they can resell one megabit modem service. Right now, RedBack only has a client for Win9X... so no NT, no Linux, no Mac OS. Linux is actually probably reasonably easy to add support for, somebody with the RFC can probably do it in a few days. [ah, the beauty of open source].
Still, they are basically dialupizing DSL. They will be able to bill per second, etc.
They make it sound like they're using fancy servers.
They're not, they're using two proprietary IBM Aptivas, low end machines. (I should know, I have one of them, the same model they used). Firstly, the E56 has a 266 mhz K6, unless IBM lied to me too:) Secondly, 48 megs of RAM seems a bit low for NT. Thirdly, the hard drive systems in there are probably also low quality to say the least.
Couldn't they have borrowed Mindcraft's server or something? At least THEY could tune an NT box:), although not a Linux box... and it was a server. I don't call a home system a server that will be pumping 90 megabits/sec.
Slashdot Mirror
When the car industry replaced horses (in the U.S.), that created a wide range of American jobs for a broad range of people with a broad range of skill/education levels. Manufacturing jobs, engineering jobs, repair jobs (your neighbourhood mechanic, anyone?), construction jobs (all the roads needed for cars), etc.
Apple (or most modern technology companies) doesn't. They create engineering jobs (until those get moved to India). They create jobs flipping burgers (the only jobs left for unskilled workers in America) in their cafeteria for the engineers and marketeers. Jobs for FedEx airline pilots who fly planes full of iPads from China. Retail jobs in the Apple stores. But unlike most innovations of an earlier era (cars, airplanes, trains, whatever), iPads (or iPhones or iPods) create next to no blue-collar jobs in the country that invented it. No repair jobs (what repair? send it back to China for refurbishment) and no manufacturing/assembly jobs (all done overseas). And the suppliers' manufacturing jobs (along with many high-skilled engineering jobs, e.g. for the LCD panels) are all overseas too...
I had a BlackBerry a few years ago. It was made in Canada. If RIM can do some of their manufacturing in their home country (I believe they also outsource some production), so could Apple.
Perhaps because slashdot has multiple servers with lots of big hardware located at Exodus, and that few other people (except for big names like Yahoo, CNN, etc) can afford big connectivity?
So, would you rather that we lie to you and tell you everything works well? Things break in any business, and you'd be an idiot to base your attitude on the opposite assumption. The difference, folks, lies not in whether one's service seems to break or not, but in how the operators of this service respond to the failure.
Actually, blocking incoming port 25 is effective against spam because it prevents open sendmails from being used as a relay.
If you block outgoing port 25, people will set their sendmails' smart host option to the local mail server, and then the spam will go through that box AND the university mail server as well. Sure, there'll be a LARGE trail of logs, but...
The @Home network? The only reason the @Home network has LOTS of hops is that they're running optical stuff (packet over DWDM), and with that, as opposed to ATM-type links, EVERY link is visible in a traceroute.
BTW, traceroute to Slashdot from @Home:
Tracing route to slashdot.org [206.170.14.75]
over a maximum of 30 hops:
1 27 ms 30 ms 3 ms ottawa-fe.net.rogers.wave.ca [24.112.33.1]
2 16 ms 35 ms 24 ms 10.0.184.53
3 41 ms 22 ms 30 ms 24.2.9.9
4 15 ms 26 ms 27 ms c1-pos9-1.bflony1.home.net [24.7.72.245]
5 17 ms 29 ms 33 ms c1-pos1-0.clevoh1.home.net [24.7.65.5]
6 28 ms 30 ms 30 ms c1-pos5-3.cmdnnj1.home.net [24.7.67.158]
7 33 ms 29 ms 30 ms c1-pos1-0.washdc1.home.net [24.7.65.85]
8 35 ms 32 ms 56 ms bb1-pos2-1-0.mae-e.nap.home.net [24.7.72.54]
9 72 ms 72 ms 43 ms mae-east.ibm.net [192.41.177.110]
10 59 ms 66 ms 52 ms beth1sr2-11-0-0.md.us.ibm.net [198.133.27.10]
11 68 ms 71 ms 60 ms bethjbr1-ge-1-0-0-0.md.us.ibm.net [165.87.29.122
]
12 106 ms 95 ms 93 ms sfra1br1-at-2-0-0-2.ca.us.ibm.net [165.87.230.98
]
13 121 ms 89 ms 91 ms sfra1sr3-so-0-0-0-0.ca.us.ibm.net [165.87.13.30]
14 101 ms 112 ms 93 ms 165.87.161.73
15 97 ms 122 ms * ded1-fa11-1-0.snfc21.pbi.net [209.232.130.4]
16 113 ms 95 ms 92 ms 209.232.138.214
17 111 ms 92 ms 92 ms slashdot.org [206.170.14.75]
Personally, I'd say the reason for LOTS of hops is because Slashdot uses PacBell's backbone, which seems to ONLY talk to the world via IBM, etc...
My dear AC, you are wrong.
@Home uses Solaris hardware. I knew from Netcraft that their web server (the local one for here, www.slnt1.on.wave.home.com - their portal) ran Solaris, and I had somebody queso the mail server, Solaris again.
@Home's main network architect said just today that they use all Suns.
BTW, Bell is the one who is going to be implementing PPP over Ethernet very soon. (see http://www.redback.com/) Just so you know, Linux doesn't support PPPoE yet, and the ONLY clients for it at the moment are for Win9X. Of course, it is an RFC, so I'm sure somebody will add it to Linux within a few months, but....
Well, read what krs said too.
Look at the specs around http://www.bellnexxia.com. They are deploying RedBack SMS-based (http://www.redback.com) equipment so that they can resell one megabit modem service.
Right now, RedBack only has a client for Win9X... so no NT, no Linux, no Mac OS. Linux is actually probably reasonably easy to add support for, somebody with the RFC can probably do it in a few days. [ah, the beauty of open source].
Still, they are basically dialupizing DSL. They will be able to bill per second, etc.
They make it sound like they're using fancy servers.
:) Secondly, 48 megs of RAM seems a bit low for NT. Thirdly, the hard drive systems in there are probably also low quality to say the least.
:), although not a Linux box... and it was a server. I don't call a home system a server that will be pumping 90 megabits/sec.
They're not, they're using two proprietary IBM Aptivas, low end machines. (I should know, I have one of them, the same model they used). Firstly, the E56 has a 266 mhz K6, unless IBM lied to me too
Couldn't they have borrowed Mindcraft's server or something? At least THEY could tune an NT box