I haven't tried the Bayesian filtering because it's apparently not well suited to a multi-user environment
I thought the same until I tried it. I added the following lines to/etc/mail/spamassassin/local.cf:
use_bayes 1 bayes_path/var/spamassassin/bayes
Since I make extensive use of whitelisting/blacklisting, the Bayes filter gets good examples of both spam and nonspam. Once SA had enough data collected, it started applying bayes scores.
Here are the SA scores of a spam which would have slipped through without the Bayes filtering:
5.4 BAYES_99 BODY: Bayesian spam probability is 99 to 100% [score: 0.9974] 0.6 WEIRD_PORT URI: Uses non-standard port number for HTTP 1.6 DATE_IN_FUTURE_06_12 Date: is 6 to 12 hours after Received: date
Without bayesian filtering this mail would have scored only 2.2 points. The spam itself was only 4 lines long trying to sell viagra without using the "v" word.
I really want to get a telescope for my kid, but until I move away from the lights of the city I'm near, it's pointless....
Go ahead and get a telescope. Learn how to use it. Go spend time with your kid. You will be surprised how much is visible from the middle of the city even in a small scope.
I started with a pair of 6X30 binoculars from my apartment balcony in the middle of San Jose, CA. I eventually moved up to an 8 inch Celestron.
I now live in the country with thousands of visible stars instead of forty or fifty, but my most memorable nights were on that balcony in San Jose. It was a great thrill to track down a 10th or 11th magnitude galaxy when it seemed that there were only 3 stars visible in the sky.
Last night I stayed up with my two kids to look at mars with my 20 year old telescope. I certainly don't regret buying a telescope back when I lived in the middle of a sea of light pollution.
After tallying up my whole experience with the Lindows Media Computer, I come to the conclusion that it was not a good one. While the price may be right for some folks, the system itself doesn't dignify the name of 'Media Computer.' I found it to be little more that a tiny low-end computer with special boot software that didn't deliver on its promise. It lacks both the power and features to truly compete, even in its own price range. Indeed, I went through and priced up a machine with more power and features that a true 'Media Computer' should have and came up $50 less that the cost of the Lindows box. True, I didn't have "Instant On" media access, but since it didn't fully work anyhow, I wasn't too bothered.
Would I buy this machine? Certainly not. Would I recommend it? Not under its claim of being a competitor in the media field. Actually, given the lack of upgrade options, I would be hard pressed to recommend this system to anyone. It does look good, fits into small spaces, and doesn't take up a whole lot of space. But I don't know anyone who has these items on the absolute top of their priority list.
Fortran is truly ugly, if you need to write fortran, at least do it an ratfor (Rational Fortran) described by Kernigan and Plauger in Structured Programming.
Ratfor adds "normal" structured programming constructs to fortran to make it readable by somebody less than 40 years old.
You write code that looks like:
for(i=1;i=100;i=i+1) {
fortran code here
}
Unisys will sue Forgent for not paying any royalties on the software used to generate the 42 gif images on their webpage.
While that is going on. Forgent will sue Unisys for not paying any royalties on the.JPG image on their webpage (http://www.unisys.com/corporate/images/home/home/ content/main_photo_homepage.jpg)
When the lawyers have taken all of their money, both of them will declare bankruptcy and go out of business.
Everybody knows that weak passwords are bad, but strong passwords are hard to remember. The situation is made even worse when the user is forced to change passwords once a week/month etc. Forcing password changes just forces the user to use easier to remember passwords and/or write it down.
Why not implement a password change policy based on the strength of the password? The stronger the password, the longer the period between forced changes. This way the system can encourage good passwords.
Example
7 or fewer alpha characters = password changeonce a week
8 or more alpha/numeric = password change once a month.
really long alpha/numeric/non alphanumeric = long time between password changes.
Back in the '80s, I worked on a DOS port of an Apple II game called "Robot Odyssey" where there were "guard 'bots" that guarded certain items. In order to win, you had to program a robot with digital logic circuits to bypass the guards, or solve a puzzle.
The game was way cool, but too hard for the casual gamer. I understand the game was even used in electronics classes to teach digital logic.
Here [members.aol.com] is a site where you can see screenshots or download copies of the Apple II and DOS version.
I recall that the DOS version only worked on 8086/286 machines with color monitor and joystick.
Restrict access to the cisco vty to a list of known hosts. You can use ssh to get from anywhere to one of the permitted hosts, from there you can telnet to the router. If you have the rackspace available, drop an old 486 running *bsd/linux physically right next to each of your routers.
Add an acl to restrict access to the virtual terminals as follows:
As with any cisco ACL, be careful that you dont "cut off the branch you are sitting on". If you dont understand what the above ACL does, try it out on a test router before you install it on a router 5 timezones away.
You have to start small and prove your solution each step of the way. If your solution is not better than the one in place, then it wont be used.
Years ago, I was hired to babysit an RS/6000 in a large international corporation whose idea of a network was a source route bridged token ring. The only protocols permitted on the network were NETBEUI/DLC/IPX. Ethernet was not used, and TCP/IP was strictly verboten.
I used the RS/6000 to demonstrate that TCP/IP could be used reliably, and it would not "crash" the network. The corporate "network managers" were astounded that I could transfer data across the country at wire speed instead of waiting for the silly NETBEUI ACK to travel back and forth at the speed of light. TCP/IP became an officially accepted protocol on the network as a result.
The next step was to introduce BSDI unix as mail servers. Again, Corporate MIS was astounded that SMTP could deliver mail across the corporation in a matter of seconds instead of waiting minutes (or hours) for the CC:mail gateway to poll the postoffice. SMTP became the official email "backbone".
With the advent of the WWW, the same unix systems stepped up with NCSA server and became the official web server for the company.
Today, this same corporation uses Linux/BSDI/Solaris for all of their Internet accessible servers. Not one is running anything from Microsoft.
I fought for years against the corporate mindset of "Nobody got fired for buying IBM". Today, the corporate mindset is "Nobody got fired for buying Microsoft".
You have to pick small battles that you can win. Don't go after the desktop unless your solution is better than what is in place.
Slashdot Mirror
Now all it takes is a $60 SIP adapter or a free softphone and you can let your friends call you for $.02 per minute.
rm -rf /
One of the reasons I love unix, is that it will let you shoot yourself in the foot, and it will steady the gun while you take aim at your toe.
cat quote*.txt |sort |uniq
A good shell programmer is lazy and always tries to eliminate wasted keystrokes.
sort q*|sort|uniq
Does the same thing, but eliminates one program (cat) and 14 keystrokes.
I thought the same until I tried it. I added the following lines to /etc/mail/spamassassin/local.cf:
Since I make extensive use of whitelisting/blacklisting, the Bayes filter gets good examples of both spam and nonspam. Once SA had enough data collected, it started applying bayes scores.Here are the SA scores of a spam which would have slipped through without the Bayes filtering:
Without bayesian filtering this mail would have scored only 2.2 points. The spam itself was only 4 lines long trying to sell viagra without using the "v" word.I really want to get a telescope for my kid, but until I move away from the lights of the city I'm near, it's pointless....
Go ahead and get a telescope. Learn how to use it. Go spend time with your kid. You will be surprised how much is visible from the middle of the city even in a small scope.
I started with a pair of 6X30 binoculars from my apartment balcony in the middle of San Jose, CA. I eventually moved up to an 8 inch Celestron.
I now live in the country with thousands of visible stars instead of forty or fifty, but my most memorable nights were on that balcony in San Jose. It was a great thrill to track down a 10th or 11th magnitude galaxy when it seemed that there were only 3 stars visible in the sky.
Last night I stayed up with my two kids to look at mars with my 20 year old telescope. I certainly don't regret buying a telescope back when I lived in the middle of a sea of light pollution.
After tallying up my whole experience with the Lindows Media Computer, I come to the conclusion that it was not a good one. While the price may be right for some folks, the system itself doesn't dignify the name of 'Media Computer.' I found it to be little more that a tiny low-end computer with special boot software that didn't deliver on its promise. It lacks both the power and features to truly compete, even in its own price range. Indeed, I went through and priced up a machine with more power and features that a true 'Media Computer' should have and came up $50 less that the cost of the Lindows box. True, I didn't have "Instant On" media access, but since it didn't fully work anyhow, I wasn't too bothered.
Would I buy this machine? Certainly not. Would I recommend it? Not under its claim of being a competitor in the media field. Actually, given the lack of upgrade options, I would be hard pressed to recommend this system to anyone. It does look good, fits into small spaces, and doesn't take up a whole lot of space. But I don't know anyone who has these items on the absolute top of their priority list.
Fortran is truly ugly, if you need to write fortran, at least do it an ratfor (Rational Fortran) described by Kernigan and Plauger in Structured Programming.
Ratfor adds "normal" structured programming constructs to fortran to make it readable by somebody less than 40 years old.
You write code that looks like:
for(i=1;i=100;i=i+1) {
fortran code here
}
Ratfor generates:
23002 if(.not.(i.le.100))goto 23004
fortran code here
goto 23002
23004 continue
I dont know about Linux, but ratfor is included in the FreeBSD ports.
Unisys will sue Forgent for not paying any royalties on the software used to generate the 42 gif images on their webpage.
.JPG image on their webpage (http://www.unisys.com/corporate/images/home/home/ content/main_photo_homepage.jpg)
While that is going on. Forgent will sue Unisys for not paying any royalties on the
When the lawyers have taken all of their money, both of them will declare bankruptcy and go out of business.
Why not implement a password change policy based on the strength of the password? The stronger the password, the longer the period between forced changes. This way the system can encourage good passwords.
Example
Back in the '80s, I worked on a DOS port of an Apple II game called "Robot Odyssey" where there were "guard 'bots" that guarded certain items. In order to win, you had to program a robot with digital logic circuits to bypass the guards, or solve a puzzle.
The game was way cool, but too hard for the casual gamer. I understand the game was even used in electronics classes to teach digital logic.
Here [members.aol.com] is a site where you can see screenshots or download copies of the Apple II and DOS version.
I recall that the DOS version only worked on 8086/286 machines with color monitor and joystick.
everyone running a cisco router should do this.
Restrict access to the cisco vty to a list of known hosts. You can use ssh to get from anywhere to one of the permitted hosts, from there you can telnet to the router. If you have the rackspace available, drop an old 486 running *bsd/linux physically right next to each of your routers.
Add an acl to restrict access to the virtual terminals as follows:
access-list 2 remark vty access list
access-list 2 permit 192.168.0.0 0.0.0.255
access-list 2 permit 192.168.200.0 0.0.0.255
....etc....
access-list 2 deny any
line vty 0 4
access-class 2 in
As with any cisco ACL, be careful that you dont "cut off the branch you are sitting on". If you dont understand what the above ACL does, try it out on a test router before you install it on a router 5 timezones away.
Hmmm. I thought the worlds largest telescope wouldn't have need for another mirror ;)
You have to start small and prove your solution each step of the way. If your solution is not better than the one in place, then it wont be used.
Years ago, I was hired to babysit an RS/6000 in a large international corporation whose idea of a network was a source route bridged token ring. The only protocols permitted on the network were NETBEUI/DLC/IPX. Ethernet was not used, and TCP/IP was strictly verboten.
I used the RS/6000 to demonstrate that TCP/IP could be used reliably, and it would not "crash" the network. The corporate "network managers" were astounded that I could transfer data across the country at wire speed instead of waiting for the silly NETBEUI ACK to travel back and forth at the speed of light. TCP/IP became an officially accepted protocol on the network as a result.
The next step was to introduce BSDI unix as mail servers. Again, Corporate MIS was astounded that SMTP could deliver mail across the corporation in a matter of seconds instead of waiting minutes (or hours) for the CC:mail gateway to poll the postoffice. SMTP became the official email "backbone".
With the advent of the WWW, the same unix systems stepped up with NCSA server and became the official web server for the company.
Today, this same corporation uses Linux/BSDI/Solaris for all of their Internet accessible servers. Not one is running anything from Microsoft.
I fought for years against the corporate mindset of "Nobody got fired for buying IBM". Today, the corporate mindset is "Nobody got fired for buying Microsoft".
You have to pick small battles that you can win. Don't go after the desktop unless your solution is better than what is in place.