Just for fun -- this is just a machine for screwing around. Its also headless. I don't generally use either kde or gnome -- if I need a GUI at all, I just use FVWM.
Still, I like to see what's new every now and then. Besides, once I started the emerge, I was loathe to stop it.
Wow -- I should have a look at those compiler flags -- this machine only has around 160 meg as well. Emergeing KDE was done pretty much just for fun (I don't actually use it)
The next machine to be switched to GenToo is a dual processor PIII -- I'll definitely pay more attention to the compiler flags when time comes to upgrade.
That should be about enough time to get KDE built. (seriously -- I emerged kde a c ouple of weeks ago, qt and all, on a P-450. Took about 5 days -- a bit more if you count fixing some hickups in the qt ebuild).
You can generally get excellent deals on analog, non-pc based scopes on eBay. I use a Tektronix 2235 100mz dual trace unit that only ran me around USD $200 -- and this was a few years ago.
I also have an Ozi-Fox handheld that has a PC and/or palm-based interface. It only does 20mhz and is single trace, but they are fairly inexpensive (< $90.00 USD) -- you could buy multiple units for classroom use. The display on the unit itself is not great, but works well for quick-and-dirty work.
As good consumers we should welcome the departure of out privacy. It is, after all, a fair trade-off given the great (and personalized!) deals we'll all get in return. So let's all just relax and "go with the flow", shall we?
And I'd remind you that igneous rock appears nowhere on the Sophos list. Igneous rock originates very little spam -- a side effect of its natural cultural superiority.
...maybe Sophos could also get around to changing their default "notify recipient" setting on their email virus scanner.
That way, Sophos themselves might produce a little less spam...
Re:Postfix shortcomings
on
Postfix
·
· Score: 3, Interesting
To avoid duplicating the zillion responses you shall receive pointing out that you can use procmail directly as the delivery agent (google or just check main.cf), I'll just point out postfix also honors sendmail.forward files as well, allowing procmail to be invoked that way as well. If you were invoking procmail this way using sendmail, you should have to make 0 changes when you switch to postfix. The only thing I've seen it break so far is the majordomo approval function, and this is covered in the faq.
Hmmm -- that's too bad. I find that the spamcop and spamhaus blacklists give great results and (thus far) 0 false positives. Of course, the thing about blacklists and false positives, is that when false hits start occuring, you frequently get them in significantly large numbers (when it rains, it pours).
Just a suggestion, but make sure that spamassassin is doing the black list checks properly. Mine wasn't, and I got abyssmal results. After an upgrade and a reinstall (and an upping of the score for the spamcop and spamhaus checks), I'm back to a better than 99% sucess rate (no false positives yet).
Not all of the dns blacklists are created equal, but I have enough confidence in both the spamhaus and spamcop lists to automatically mark a message as spam if either of those tests fail.
Actually, the tricky bit here is that the resulting data has to be text. The best solution I've seen so far involves generic compression and then base64 encoding, but I'm just wondering what other options might exist.
I guess MUTE tries to solve this in two ways (I haven't been able to get the software yet, and the doc details are a little thin:
Traffic would appear to be encrypted, making it difficult to identify exactly what is being shared, and ultimately by whom.
The sheer number of nodes -- assuming a large network -- would make this approach prohibitively expensive considering that it would be impossible to identify large sharers -- only nodes carrying traffic.
In the end, I guess a more effective attack would be to become a node, compromise your neighbors, use the compromised neighbors to compromise more neighbors, and so on. Again, though, this seems to be extremely cost ineffective (and difficult, requiring a lot of cooperation from ISPs) in terms of rewards reaped.
Didn't Banyan VINES use a similar method of discovering routes to a remote node via this kind of nearest-neighbor arrangment? Been a while, but this rings a bell.
This looks pretty cool, but it seems like there will be problems when nodes go on and offline, since broadcasts get used to find nodes. Won't nodes that come and go periodically cause problems -- or is this a non-issue?
What ever became of that? Much of my work back in the day used to consist of various mods and extensions to ASK's MANMAN product -- FORTRAN-66, baby! I hated their product, though -- it was, as we used to say, fugly -- even for F-66.
Ah -- but my original reply was intended to be ironic. As was my subsequent misspelling of "misattribution". As were my extensive investments in NASDAQ futures in the late 90s...
You'll want to be sending that apology to Alfred Joyce Kilmer, not Ogden Nash.
Re:Kind of emphasizes a major point.
on
Global Dimming
·
· Score: 1, Funny
I agree completely, and feel that this article vindicates my longstanding belief that our planet is really saucer-shaped and borne on the back of a rather cosmically large turtle.
I bet those arrogant bastards aren't laughing at me now.
I don't really get the advantages of XML Data storage either, but when it comes to emitting data in a generic, interoperable, self-describing format, XML works quite nicely, even if it is a tad verbose.
Which (slightly OT) reminds me: has anyone here used an XML compression tool, that they'd like to share opinions on? I've looked at XMLPPM briefly but not worked with it yet. Any others?
Uh -- yes, although apparently the project planners didn't. To be fair, this was NOT 2.0 -- on the platform they had targeted major features were missing (like stored procedures, although cascading deletes were available).
"SQL Lite" would be a far more fitting name -- it is obviously NOT the same product. It's not really a bad product as far as it goes -- but calling it "SQL Server" was a really unfortunate decision (I would have guessed that their marketing dept. came up with this one).
Geez -- a crippled db platform if there ever was one. Calling it "SQL Server" is really a major misnomer -- the two are not even remotely similar in even basic features. Obviously, this would be expected to some extent -- but the name tends to mislead. I had the misfortune of working for an employer who wanted the same application working on both SQL Server and a handheld version on CE. They expected significant code to be shared between the two, and ultimately got a nasty surprise when this proved infeasable, given the alotted dev time frame.
Slashdot Mirror
Still, I like to see what's new every now and then. Besides, once I started the emerge, I was loathe to stop it.
The next machine to be switched to GenToo is a dual processor PIII -- I'll definitely pay more attention to the compiler flags when time comes to upgrade.
That should be about enough time to get KDE built. (seriously -- I emerged kde a c ouple of weeks ago, qt and all, on a P-450. Took about 5 days -- a bit more if you count fixing some hickups in the qt ebuild).
I also have an Ozi-Fox handheld that has a PC and/or palm-based interface. It only does 20mhz and is single trace, but they are fairly inexpensive (< $90.00 USD) -- you could buy multiple units for classroom use. The display on the unit itself is not great, but works well for quick-and-dirty work.
Good luck -- m
Thanx for listening,
Consumer 0556672GXX89F2
And I'd remind you that igneous rock appears nowhere on the Sophos list. Igneous rock originates very little spam -- a side effect of its natural cultural superiority.
I believe I have won the idiotic jingoistic posting contest.
That way, Sophos themselves might produce a little less spam...
To avoid duplicating the zillion responses you shall receive pointing out that you can use procmail directly as the delivery agent (google or just check main.cf), I'll just point out postfix also honors sendmail .forward files as well, allowing procmail to be invoked that way as well. If you were invoking procmail this way using sendmail, you should have to make 0 changes when you switch to postfix. The only thing I've seen it break so far is the majordomo approval function, and this is covered in the faq.
Hmmm -- that's too bad. I find that the spamcop and spamhaus blacklists give great results and (thus far) 0 false positives. Of course, the thing about blacklists and false positives, is that when false hits start occuring, you frequently get them in significantly large numbers (when it rains, it pours).
Not all of the dns blacklists are created equal, but I have enough confidence in both the spamhaus and spamcop lists to automatically mark a message as spam if either of those tests fail.
Clearly, you've never done any NLM development...
Actually, the tricky bit here is that the resulting data has to be text. The best solution I've seen so far involves generic compression and then base64 encoding, but I'm just wondering what other options might exist.
In the end, I guess a more effective attack would be to become a node, compromise your neighbors, use the compromised neighbors to compromise more neighbors, and so on. Again, though, this seems to be extremely cost ineffective (and difficult, requiring a lot of cooperation from ISPs) in terms of rewards reaped.
This looks pretty cool, but it seems like there will be problems when nodes go on and offline, since broadcasts get used to find nodes. Won't nodes that come and go periodically cause problems -- or is this a non-issue?
What ever became of that? Much of my work back in the day used to consist of various mods and extensions to ASK's MANMAN product -- FORTRAN-66, baby! I hated their product, though -- it was, as we used to say, fugly -- even for F-66.
No -- that was the original trial judge, not the appeals panel. That original runing has been overturned. (I read it the wrong way at first as well.)
Ah -- but my original reply was intended to be ironic. As was my subsequent misspelling of "misattribution". As were my extensive investments in NASDAQ futures in the late 90s...
I must have missed the moment when missattribution became ironic. Damn -- I need to get back to grad school, cause life's jus' a-passin me by...
You'll want to be sending that apology to Alfred Joyce Kilmer, not Ogden Nash.
I bet those arrogant bastards aren't laughing at me now.
Which (slightly OT) reminds me: has anyone here used an XML compression tool, that they'd like to share opinions on? I've looked at XMLPPM briefly but not worked with it yet. Any others?
Uh -- yes, although apparently the project planners didn't. To be fair, this was NOT 2.0 -- on the platform they had targeted major features were missing (like stored procedures, although cascading deletes were available).
"SQL Lite" would be a far more fitting name -- it is obviously NOT the same product. It's not really a bad product as far as it goes -- but calling it "SQL Server" was a really unfortunate decision (I would have guessed that their marketing dept. came up with this one).
Geez -- a crippled db platform if there ever was one. Calling it "SQL Server" is really a major misnomer -- the two are not even remotely similar in even basic features. Obviously, this would be expected to some extent -- but the name tends to mislead. I had the misfortune of working for an employer who wanted the same application working on both SQL Server and a handheld version on CE. They expected significant code to be shared between the two, and ultimately got a nasty surprise when this proved infeasable, given the alotted dev time frame.