C++ is a joke on C, because in code, C++ is one greater than C on its own. By most coding standards, anything with an UPPERCASE name should be a constant, so incrementing the value would probably give you a compiler error. C# is "sharp". You'd be an idiot if you didn't use the "smarter" language...
Incidentally, if you turn down the kerning of "++" and make one of the symbols super/subscript, you get the pound/sharp symbol instead. Musically, C# is also D flat, which could be taken negatively, but the language C was borne of the language B, which was borne of A, something the amateur spin paramedics should take note of...
Second only to Y2K, Microsoft's.NOT initiative will be one of the biggest non events in computing history, so I'm not understanding why/bots and OSS gurus are so worked up about it.
I occasionally have to unit test with 400MHz G4 "tower". Now Apple and Adobe can benchmarket Photoshop as much as they want to, but the MHz gap is a huge problem. There are no 1.4 GHz G4's, and from what I've seen, I'm beginning to wonder if the G4 reaches performance parity per MHz, let alone the superiority they claim.
This was on a Mac with OS 9 -- I don't even want to imagine how bad things get with X.
Well, VA Linux does run adverts for that other Linux system integrator. I've seen their ads back to back while browsing the comments, then replying to you.
I don't have numbers on the Clawhammer, of course, but if its heritage is any guide, it will be very hot: http://www.tech-report.com/cpu/
Somehow, I manage to keep my overclocked K7-1050 at a relatively cool 42C, but I have the feeling that it could vaporise an ice cube in five seconds if I were to remove the heatsink.
I'd like to complain about people who hold things up by complaining about people complaining. It's about time something was done about it. (the sixteen-ton weight falls on him)
Northpoint is a fucked company in many senses of the word. They were fucked by their customers, and by their "buyers".
It is likely that Northpoint would have been doing much better if they hadn't needed to write off millions in debt from partner ISP's that never paid up. Phoenix DSL fell apart, and I don't think they ever got a cent from Flashcom. This is info given to me from friends of mine that worked there, and my memory of the details may be hazy, but that is the general idea.
I think about the ones that lost jobs and whose DSL connections are in peril.
I must admit that the customer service I got from them wasn't quite stellar, however. I wound up going through the local ILEC, simply because they had actually gotten back to me within a day or two, a month after I had requested information from Northpoint. By the time Northpoint had gotten back to me, my circuit was up and I was cruising along with an awesome local ISP.
I'm generally not an anti-corporatist, but I do hope that they win their suit and put at least a little chink in the evil keiretsu that is Verizon, which appears to have put their offer on the table as a bargaining chip in their labor disputes last summer.
RDRAM will never be accepted. The prices may have come down, and interleaving may boost its bandwidth sky high, but it still has problems with latency and power consumption. IIRC, DDR consumes even less power than SDRAM, which will also make it appealing in mobile devices, be it necessary or not:)
In most cases, even when using a multihomed ISP, the first several hops will follow a simple, fixed path. In the config I showed you, inbound traffic to a specific range is routed to interface eth0. (x)versely, it follows that outbound traffic should originate from the same range, correct?
As I stated, this filtering would happen at a very low level, where routing is rarely complicated, but at this point I see no point in trying to reason with you.
Kiddi3z will always be a nuisance, but my personal feeling is that the parties responsible for the death of the Internet will be a handful companies trying to milk or control it...
I think it's pretty clear that the router understands which IP's are on the LAN, and which ones aren't. The type of prevention I am talking about would happen at the first hop, which IME is rarely complicated. As usual, problems are better resolved within the home.
I am not, nor was I ever a smurf amplifier, but that does not stop attempts to do so from saturating my link.
As someone who had been getting repeatedly smurfed before finally getting the ISP to understand, I see a rather simple, yet effective way to manage this: don't allow forged packets!
A router already understands what IP addresses are behind it. *By default*, why should it route traffic from IP's that don't exist on the LAN to the WAN? I am not a TCP/IP expert, but it seems to me that there are no legitimate applications for bounced packets.
Forget about the theft of IP -- physical theft is much easier. Just slip the CD into your pocket, and...
Does anyone see another "longbox problem" on the horizon? How the hell can these be packaged in any kind of environmentally sane way?
Slashdot Mirror
Incidentally, if you turn down the kerning of "++" and make one of the symbols super/subscript, you get the pound/sharp symbol instead. Musically, C# is also D flat, which could be taken negatively, but the language C was borne of the language B, which was borne of A, something the amateur spin paramedics should take note of...
(As usual, ruining a good joke.)
(end comment) */ }
At least this isn't another Microsoft story...
(end comment) */ }
I occasionally have to unit test with 400MHz G4 "tower". Now Apple and Adobe can benchmarket Photoshop as much as they want to, but the MHz gap is a huge problem. There are no 1.4 GHz G4's, and from what I've seen, I'm beginning to wonder if the G4 reaches performance parity per MHz, let alone the superiority they claim.
This was on a Mac with OS 9 -- I don't even want to imagine how bad things get with X.
(end comment) */ }
(end comment) */ }
(end comment) */ }
(end comment) */ }
http://www.tech-report.com/cpu/
Somehow, I manage to keep my overclocked K7-1050 at a relatively cool 42C, but I have the feeling that it could vaporise an ice cube in five seconds if I were to remove the heatsink.
(end comment) */ }
(end comment) */ }
(end comment) */ }
(end comment) */ }
It is likely that Northpoint would have been doing much better if they hadn't needed to write off millions in debt from partner ISP's that never paid up. Phoenix DSL fell apart, and I don't think they ever got a cent from Flashcom. This is info given to me from friends of mine that worked there, and my memory of the details may be hazy, but that is the general idea.
(end comment) */ }
I must admit that the customer service I got from them wasn't quite stellar, however. I wound up going through the local ILEC, simply because they had actually gotten back to me within a day or two, a month after I had requested information from Northpoint. By the time Northpoint had gotten back to me, my circuit was up and I was cruising along with an awesome local ISP.
I'm generally not an anti-corporatist, but I do hope that they win their suit and put at least a little chink in the evil keiretsu that is Verizon, which appears to have put their offer on the table as a bargaining chip in their labor disputes last summer.
(end comment) */ }
This one's on Hemos
(end comment) */ }
(Sorry to step on the joke)
(end comment) */ }
"No, we aren't going to deorbit it"
(repeat 12x)
I'll believe that Mir is being deorbited when I see it. Oh, wait...
(end comment) */ }
(end comment) */ }
(end comment) */ }
(end comment) */ }
(end comment) */ }
As I stated, this filtering would happen at a very low level, where routing is rarely complicated, but at this point I see no point in trying to reason with you.
(end comment) */ }
Kiddi3z will always be a nuisance, but my personal feeling is that the parties responsible for the death of the Internet will be a handful companies trying to milk or control it...
(end comment) */ }
cisco675>sh route
[TARGET] [MASK] [GATEWAY] [M] [TYPE] [IF] [AGE]
0.0.0.0 0.0.0.0 0.0.0.0 1 SA WAN0-0 0
12.34.56.0 255.255.255.0 0.0.0.0 1 LA ETH0 0
1.2.3.0 255.255.255.0 0.0.0.0 1 A WAN0-0 0
1.2.3.4 255.255.255.255 0.0.0.0 1 AH WAN0-0 0
I think it's pretty clear that the router understands which IP's are on the LAN, and which ones aren't. The type of prevention I am talking about would happen at the first hop, which IME is rarely complicated. As usual, problems are better resolved within the home.
I am not, nor was I ever a smurf amplifier, but that does not stop attempts to do so from saturating my link.
(end comment) */ }
A router already understands what IP addresses are behind it. *By default*, why should it route traffic from IP's that don't exist on the LAN to the WAN? I am not a TCP/IP expert, but it seems to me that there are no legitimate applications for bounced packets.
(end comment) */ }
(end comment) */ }
(end comment) */ }