When my 2.4GHz phone was in use it would completely squash my 802.11b -- wich was very unfortunate, since its a 1 mile link to the nearest spot at which broadband is available, so when that goes, my Internet connectivity goes.
The answer was to buy an new 5.8Ghz phone.
I was tempted by the "802.11b friendly" phones -- they were a lot cheaper. But I didn't want to take the risk. All works just fine now.
Re:Spam is getting to be such BS
on
CAN-SPAM Is A Bust
·
· Score: 2, Informative
All I can say is that you obviously didn't do a good job of setting up your anti-spam system.
I use sendmail to check for lack of HELO etc, then to validate that the sender domain really exists, followed by two RBL lists - although Spamhaus alone is probably good enough - the second one catches maybe another 5 to 10%.
After that its Spamassassin, set up with individual beysian databases per user. Spam goes into the users SPAM folder for them to check, and I ask them to copy good mail into a NON-SPAM folder. Each night the users SPAM folder is scanned (via cron) with --spam and the NON-SPAM with --ham.
The end result is that 90% of spam is stopped before delivery by the sendmail and RBL checks in sendmail, and I see - maybe - one piece of spam per day, and never see any good mail end up in the SPAM folder - with the spam level set to 3.9.
The system runs itself, and it works well. It takes maybe a couple of weeks to stabilise, but then just tracks the changing spam patterns pretty quickly.
It gets worse. Try the site with Firefox on Linux and you get this:
Les navigateurs adaptés au surf sur ce site ne sont pas encore disponible pour le système d'exploitation que vous utilisez.
Voici la liste des plate-formes permettant d'accéder à toutes les fonctionnalités du site :
- Plateforme Windows (98 SE et supérieur)
Someone needs an attitude adjustment...
For the language impaired, this translates as:
The browsers suitable for surfing this site are not yet available for the operating system you are using. Here are the platforms permitting access to all the functionality of this site:- Windows 98 and later.
I would think that given MS's past history of "borowing" ideas, they are as open to patent issues as anyone else.
So what do they suggest Munich (and everyone else) do? Stop using software?
Vermont's Patrick Leahy, the top Democrat on the panel, echoed Hatch's comments. "Nobody wants to undermine the iPod or any other piece of technology out there," he said. "We have to understand that some people use P2P technology in ways that are wrong and illegal."
First comment - the people he refers to are already doing something illegal. If you prove it, go ahead and prosecute them. There is no need for any further action.
Next, his dimwitted view of "P2P technology". Its a term he doesn't understand. It has been applied to a particular sub-set of P2P technologies, which have actually been around for many, many years. Ban P2P technology and you ban SMTP - so no more e-mail for a start.
This whole thing is just a indication of an underlying problem - the view of our ruling criminal overlords that its not sufficient to make some act illegal, you also need to make illegal every innocent article that can potentially be used to commit that act.
This isn't as simple as you seem to think.
There is one light, which lights up, and stays lit after any fault condition. The fault conditions can be for something as simple and trivial as a loose gas cap to something which will cause the engine to leap out and land in your lap. You have no way of knowing without going along to your local friendly dealer to have them tell you what the problem is (was) and to re-set the warning light.
My Jeep Grand Cherokee had 27,000 miles on it when my warning light lit up. I took it along to the local Jeep shop, who connected the computer and diagnosed --- a loose gas cap. Now living in Oregon, you don't get to play with your own gas cap. In Oregon they really do believe those dire warnings that California churn out, that gasoline is a substance that can cause a multitude of serious health problems, and is a potential terrorist weapon, so you can't fill your own tank if you want to.
Anyway, I really thought it was improbable, but took them at their word - they tightened the gas cap and reset the light.
The next day, it came back on. Back to the Jeep merchant... loose gas cap. So I reminded them that they said the same thing yesterday, and tightened the gas cap themselves, and it hadn't been touched since.
The "cleaned" the gas cap and re-set the light.
Two days later the light came on...
"loose gas-cap" they said.... "Screw that" I said, "its something else - fix it under my bumper to bumper warranty."
They took the car in the next day, and called me late in the afternoon having done all the Jeep tests without any result. But they did mention that there were some tests that were only run by the on-board computer when the engine was cold, and hadn't run for several hours, and it was this one which was tripping the warning. They kept the car overnight.
Next day, it dutifully turned on the warning light for them.
With nothing left to check, they fitted a new gas-cap and sent me home (I am certain I saw them holding their fingers crossed behind their backs as I drove away...).
That fixed it. But it was interesting that there was no apparent way to test the system short of change a component, wait a day and try it. I just shudder to think how much this would have ended up costing me if it had happened out of warranty.
I was a Cygnus customer - yes, they did do development work and provided support for the GNU compiler which was much better than you would get from any commercial compiler vendor -- particularly hardware vendors (SUN, HP, IBM, etc).
One of the problems that they always had was that they were "customer driven", and tried to evolve the GNU compilers in the direction that favored their customers. This put them in direct conflict with the "official maintainer" of the GNU compiler suite, and, from time to time, with RMS himself.
I was rather sad to see Cygnus swallowed up by the RedHat monolith.
This problem really isn't specific to plasma displays, its inherent in the crappy digital TV standards. MPEG has two streams, audio and video. There are no sync indicators to lock the streams together, they just flow independently.
Slow processors can significantly delay the generation of the output video. Not only that, but the amount of work the processor has to do, which depends on how many changes from frame to frame take place, will cause varying delays.
The way the problem usually manifests itself is that the delta between video and audio gets biggere and bigger, the two slowly drift apart. The video is, of course, being backed up in memory. At some point it will run out of buffer capacity. The olde way of dealing with this was to just flush the buffer, which brings thing back into sync (for a while), but usually causes a nasty glitch in the video (blank screen for a few frames) in most cases.
Newer techniques involve dropping frames, more of them as the buffer fills up.
A good indicator that you are getting buffer overflow is when you change channel, then change back again and all is back in sync (for a while). This will have flushed the video stream buffer, and life will be good, untill it backs up again.
Faster processors can deal with the overall data rate without having to resort to these extremes, but the inherent delay caused by having to buffer a frame (or more) to be able to decode the next (because we are dealing with frame deltas in MPEG) will still cause varying delays in the video.
The real answer is to use adquate processing power, and to modify MPEG to insert timing marks into the video and audio streams, and allow the system to automatically and incrementally adjust the audio delay to keep it in sync with the video.
Expect to see a squadron of flying pigs before this happens...
An even better answer, of course, is to scrap this digital TV crap. The best digital TV signal doesn't hold a candle to the best analog TV signal. All that digital buys is the ability to squeeze another 150 shopping channels onto every satellite at the expense of video quality - but that doesn't matter, its marginally better than VHS, so what will the consumers ever know?
If the marketeers, manufacturers and caplitalists won't listen to you, and this is a huge untapped market, well, this is your chance to become richer than Bill Gates -- set yourself up in business and manufacture the players you want, and that you are so convinced would take the market by storm.
Comments often do exist in the code, and they are quite frequently misleading or wrong.
I used to work with someone who religeously avoided adding a single comment in his code. When questioned about it he would reel off a list of the times he had been screwed by comments which never got updated as the code did, and would add that your code should be written clearly enough that it could be read without needing the aid of explanatory comments.
Over time I came to pretty much agree with him (I do still comment my code - what little I write these days). A LOT of open source code is pretty much illegible, and appears to be written that way on purpose.
Anyway, user documentation is at a completely different level from code comments.
If a group of companies get together and set prices such that they are all the same, and particularly above what appears to be a reasonable market price, isn't that illegal in most countries ?
Yes, we have those in Oregon too. Even better, they are mailed to us at home, and we mail them back. Pols. hate this, because it means they can't do last minute blitzes of negative ads -- they just don't know when people are getting around to filling in the ballot and mailing it back.
But this would never fly in Florida. Apparently, Florida democrats are incapable of knowing which end of a pen makes the mark on the paper, so 50% of them would be disenfranchised.
It seems unlikely to me that Cisco would install this username/password as a matter of corporate policy just to allow them a backdoor to get into a device that a customer had screwed up.
Its much more likely that this was installed by an employee who thought it was a good idea (for any one of a thousand reasons), or by a product manager who similarly thought it a good idea.
Whatever the reason, I suspect that whoever did this will have poor career prospects with Cisco.
I would tend to disagree about #2.
I would prefer the tax to be 1/months+1, where months is the number of months the capital has been held.
This kills off day trading immediately, and makes INVESTING really an INVESTMENT - not playing the game as though they are betting chips.
So, but and sell the same day, tax = 100%
Keep it for a year, tax = 1/13th, 2 years 1/25th etc.
No, the industrial revolution started nearer to Newcastle and Stoke than Manchester. Manchester had little to do with the industrial revolution itself, but it did end up adopting a lot of the technology and as a result became as polluted and disgusting as the areas in which the rrevolution started.
So what if they do?
All they know is that someone with the IP 10.0.99.122 had a load of stuff available for download.
No ISP, no way to track who that might have been.
The USA has its own equivalent - the 2nd amendment to the constitution.
Just remember why that amendment is there next time some halfwit screams that some sppecifig gun is "only made to kill people" -- well, yes, those are the sort specifically protected by the constitution, and the people they are supposed to kill are th government (if they ever get beyond reasonable democratic control).
Oh... you mean like that splash screen on Win2k:
Based on NT Technology
What does NT stand for --- New technology, so we have :
Based on New Technology Technology
Some people just shouyldn't be left in charge of a pencil... let alone a computer, or even a mouth!
No, not impossible. Because of the incompetent layziness of my local Telco and cable providor I was left with no choice but a full-time 56k link.
I used a separate black-box modem/router to connect and Linux/Win2k for my machines - Linux is definately up to the job of running a web server, mail and DNS server with no downtime for many months. The Black Box was configured to re-dial when the connection dropped, which was variable, but about once every two weeks.
I lived like this for several years, until WiFi kit became cheap enough to set up a 1.5Km link to somwhere where 1.5Mbps DSL was available.
So why don't you use the Gnome desktop that comes as standard (if you choose to enable it) with Sun these days, and use either OpenOffice or Suns own version of that (which I believe also comes with the boxes these days?
Just built an SB51G for my Son (his Christmas present) - Intel P4 2.4GHz chip, 1GB or ram, Lite-on DVD/CD-RW, 160GB WD HD.
Its in our living room right now, and the final arbiter of what is too loud (my wife) hasn't mentioned it once.
There is probably more noise from the hard disk than from the fan - althoug we havn't been able to stress it enough for the fan to get beyond its idling mode yet.
Buy one.
Even if you do release your source, you can still be sued for the damages incurred during your copyright infringement. The only difference between releasing your source or not is that maybe the release would be seen as an act of contrition and the offended party would forgo his right to sue.
Effect on the sender(s): It depends on how the attack is orchestrated. If it is (as SCO claim, but I don't know how they would know this) the result of several thousand machines being compromised, and each of these machines, at a pre-determined time, sends out attack packets, there is zero effect or cost to the perpetrator. The attack machines will suffer from bandwidth hogging by the attack processes. remember this happened in the early morning, sp the owners of those machines (if they were in the US) probably wouldn't notice.
[I won't go near the claim by SCO that people were working at 4AM and were inconvenienced by not being able to send out 33,000 e-mails during the 4AM to 5AM periaod when their bandwidth was choked - maybe thats who sends all my SPAM ?].
The effect on the victims machine is simply that the TCP/IP stack runs out of resources and it can't communicate. It does no physical damage to the machine, and does no damage to the filestore or its contents. Bringing a machine back up depends a lot on the OS. If its any good, it just recovers itself as the load dissipates, at most you would need to re-boot.
Slashdot Mirror
The answer was to buy an new 5.8Ghz phone.
I was tempted by the "802.11b friendly" phones -- they were a lot cheaper. But I didn't want to take the risk. All works just fine now.
I use sendmail to check for lack of HELO etc, then to validate that the sender domain really exists, followed by two RBL lists - although Spamhaus alone is probably good enough - the second one catches maybe another 5 to 10%.
After that its Spamassassin, set up with individual beysian databases per user. Spam goes into the users SPAM folder for them to check, and I ask them to copy good mail into a NON-SPAM folder. Each night the users SPAM folder is scanned (via cron) with --spam and the NON-SPAM with --ham.
The end result is that 90% of spam is stopped before delivery by the sendmail and RBL checks in sendmail, and I see - maybe - one piece of spam per day, and never see any good mail end up in the SPAM folder - with the spam level set to 3.9.
The system runs itself, and it works well. It takes maybe a couple of weeks to stabilise, but then just tracks the changing spam patterns pretty quickly.
Les navigateurs adaptés au surf sur ce site ne sont pas encore disponible pour le système d'exploitation que vous utilisez. Voici la liste des plate-formes permettant d'accéder à toutes les fonctionnalités du site : - Plateforme Windows (98 SE et supérieur)
Someone needs an attitude adjustment...
For the language impaired, this translates as:
The browsers suitable for surfing this site are not yet available for the operating system you are using. Here are the platforms permitting access to all the functionality of this site:- Windows 98 and later.
I would think that given MS's past history of "borowing" ideas, they are as open to patent issues as anyone else. So what do they suggest Munich (and everyone else) do? Stop using software?
First comment - the people he refers to are already doing something illegal. If you prove it, go ahead and prosecute them. There is no need for any further action.
Next, his dimwitted view of "P2P technology". Its a term he doesn't understand. It has been applied to a particular sub-set of P2P technologies, which have actually been around for many, many years. Ban P2P technology and you ban SMTP - so no more e-mail for a start.
This whole thing is just a indication of an underlying problem - the view of our ruling criminal overlords that its not sufficient to make some act illegal, you also need to make illegal every innocent article that can potentially be used to commit that act.
This isn't as simple as you seem to think. There is one light, which lights up, and stays lit after any fault condition. The fault conditions can be for something as simple and trivial as a loose gas cap to something which will cause the engine to leap out and land in your lap. You have no way of knowing without going along to your local friendly dealer to have them tell you what the problem is (was) and to re-set the warning light. My Jeep Grand Cherokee had 27,000 miles on it when my warning light lit up. I took it along to the local Jeep shop, who connected the computer and diagnosed --- a loose gas cap. Now living in Oregon, you don't get to play with your own gas cap. In Oregon they really do believe those dire warnings that California churn out, that gasoline is a substance that can cause a multitude of serious health problems, and is a potential terrorist weapon, so you can't fill your own tank if you want to. Anyway, I really thought it was improbable, but took them at their word - they tightened the gas cap and reset the light. The next day, it came back on. Back to the Jeep merchant ... loose gas cap. So I reminded them that they said the same thing yesterday, and tightened the gas cap themselves, and it hadn't been touched since.
The "cleaned" the gas cap and re-set the light.
Two days later the light came on ...
"loose gas-cap" they said.... "Screw that" I said, "its something else - fix it under my bumper to bumper warranty."
They took the car in the next day, and called me late in the afternoon having done all the Jeep tests without any result. But they did mention that there were some tests that were only run by the on-board computer when the engine was cold, and hadn't run for several hours, and it was this one which was tripping the warning. They kept the car overnight.
Next day, it dutifully turned on the warning light for them.
With nothing left to check, they fitted a new gas-cap and sent me home (I am certain I saw them holding their fingers crossed behind their backs as I drove away...).
That fixed it. But it was interesting that there was no apparent way to test the system short of change a component, wait a day and try it. I just shudder to think how much this would have ended up costing me if it had happened out of warranty.
One of the problems that they always had was that they were "customer driven", and tried to evolve the GNU compilers in the direction that favored their customers. This put them in direct conflict with the "official maintainer" of the GNU compiler suite, and, from time to time, with RMS himself.
I was rather sad to see Cygnus swallowed up by the RedHat monolith.
Slow processors can significantly delay the generation of the output video. Not only that, but the amount of work the processor has to do, which depends on how many changes from frame to frame take place, will cause varying delays.
The way the problem usually manifests itself is that the delta between video and audio gets biggere and bigger, the two slowly drift apart. The video is, of course, being backed up in memory. At some point it will run out of buffer capacity. The olde way of dealing with this was to just flush the buffer, which brings thing back into sync (for a while), but usually causes a nasty glitch in the video (blank screen for a few frames) in most cases.
Newer techniques involve dropping frames, more of them as the buffer fills up.
A good indicator that you are getting buffer overflow is when you change channel, then change back again and all is back in sync (for a while). This will have flushed the video stream buffer, and life will be good, untill it backs up again.
Faster processors can deal with the overall data rate without having to resort to these extremes, but the inherent delay caused by having to buffer a frame (or more) to be able to decode the next (because we are dealing with frame deltas in MPEG) will still cause varying delays in the video.
The real answer is to use adquate processing power, and to modify MPEG to insert timing marks into the video and audio streams, and allow the system to automatically and incrementally adjust the audio delay to keep it in sync with the video.
Expect to see a squadron of flying pigs before this happens ...
An even better answer, of course, is to scrap this digital TV crap. The best digital TV signal doesn't hold a candle to the best analog TV signal. All that digital buys is the ability to squeeze another 150 shopping channels onto every satellite at the expense of video quality - but that doesn't matter, its marginally better than VHS, so what will the consumers ever know?
Off you go...
Actually, it was salt made by collecting seawater and evaporating it. Principle is the same though, so soap/salt really maks no difference.
Comments often do exist in the code, and they are quite frequently misleading or wrong. I used to work with someone who religeously avoided adding a single comment in his code. When questioned about it he would reel off a list of the times he had been screwed by comments which never got updated as the code did, and would add that your code should be written clearly enough that it could be read without needing the aid of explanatory comments. Over time I came to pretty much agree with him (I do still comment my code - what little I write these days). A LOT of open source code is pretty much illegible, and appears to be written that way on purpose. Anyway, user documentation is at a completely different level from code comments.
If a group of companies get together and set prices such that they are all the same, and particularly above what appears to be a reasonable market price, isn't that illegal in most countries ?
But this would never fly in Florida. Apparently, Florida democrats are incapable of knowing which end of a pen makes the mark on the paper, so 50% of them would be disenfranchised.
Its much more likely that this was installed by an employee who thought it was a good idea (for any one of a thousand reasons), or by a product manager who similarly thought it a good idea.
Whatever the reason, I suspect that whoever did this will have poor career prospects with Cisco.
I would tend to disagree about #2. I would prefer the tax to be 1/months+1, where months is the number of months the capital has been held. This kills off day trading immediately, and makes INVESTING really an INVESTMENT - not playing the game as though they are betting chips. So, but and sell the same day, tax = 100% Keep it for a year, tax = 1/13th, 2 years 1/25th etc.
No, the industrial revolution started nearer to Newcastle and Stoke than Manchester. Manchester had little to do with the industrial revolution itself, but it did end up adopting a lot of the technology and as a result became as polluted and disgusting as the areas in which the rrevolution started.
So what if they do? All they know is that someone with the IP 10.0.99.122 had a load of stuff available for download. No ISP, no way to track who that might have been.
Just remember why that amendment is there next time some halfwit screams that some sppecifig gun is "only made to kill people" -- well, yes, those are the sort specifically protected by the constitution, and the people they are supposed to kill are th government (if they ever get beyond reasonable democratic control).
Oh ... you mean like that splash screen on Win2k:
Based on NT Technology
What does NT stand for --- New technology, so we have :
Based on New Technology Technology
Some people just shouyldn't be left in charge of a pencil ... let alone a computer, or even a mouth!
if it were per day, until they changed their ways. Otherwise its a waste ov everyones time.
I used a separate black-box modem/router to connect and Linux/Win2k for my machines - Linux is definately up to the job of running a web server, mail and DNS server with no downtime for many months. The Black Box was configured to re-dial when the connection dropped, which was variable, but about once every two weeks.
I lived like this for several years, until WiFi kit became cheap enough to set up a 1.5Km link to somwhere where 1.5Mbps DSL was available.
It was slow, but it worked ...
So why don't you use the Gnome desktop that comes as standard (if you choose to enable it) with Sun these days, and use either OpenOffice or Suns own version of that (which I believe also comes with the boxes these days?
Just built an SB51G for my Son (his Christmas present) - Intel P4 2.4GHz chip, 1GB or ram, Lite-on DVD/CD-RW, 160GB WD HD. Its in our living room right now, and the final arbiter of what is too loud (my wife) hasn't mentioned it once. There is probably more noise from the hard disk than from the fan - althoug we havn't been able to stress it enough for the fan to get beyond its idling mode yet. Buy one.
Even if you do release your source, you can still be sued for the damages incurred during your copyright infringement. The only difference between releasing your source or not is that maybe the release would be seen as an act of contrition and the offended party would forgo his right to sue.
Sorce release and getting sued are independent.
[I won't go near the claim by SCO that people were working at 4AM and were inconvenienced by not being able to send out 33,000 e-mails during the 4AM to 5AM periaod when their bandwidth was choked - maybe thats who sends all my SPAM ?].
The effect on the victims machine is simply that the TCP/IP stack runs out of resources and it can't communicate. It does no physical damage to the machine, and does no damage to the filestore or its contents. Bringing a machine back up depends a lot on the OS. If its any good, it just recovers itself as the load dissipates, at most you would need to re-boot.