I just like the way that the Yoper people claim that it's the most stable system they've used for 20 years, and then turn around and point out that the current version is a release candidate with a testing version of KDE installed and that if you want stability they suggest you don't install KDE.... which sort of defeats the purpose of running Yoper rather than any other distro - the big difference between the distributions is how well they integrate the desktop environments and how sensible and stable their defaults are (not to mention linking tools against the desktop environments if possible for a cleaner behaviour).
I'm very impressed with the intelligent and humble discussion that is in that thread. They really are both trying to work out how to avoid the problem without breaking applications, rather than blamestorming or pretending it's not an issue.
Michael Jenning's comments that he's not an expert on security, but does try his best show a real sense of humour and concern for his users.
Ok, so I'm being a bit of a fanboy, but most links to discussions between open-source developers I see these days are the fights they have (on the very public mailing lists where we can see them). We tend to forget the good work they do the rest of the time.
(raises hat, or would if I was wearing one)... and glad I use konsole, at least until a bug is found there;)
I knew we were allies with the brits, but isn't this getting carried away?
I imagine it's something to do with the US Army using Paypal to pay for it. Maybe they got carried away bidding against Saddam for that 'leet "Leenix" thing on ebay.
HAL wins for more memorable death. Though I guess the Daisy bit wasn't really his death, that came with the whole Jupiter ignition thing...
I guess you haven't read the books then, or you would know it came when they uploaded the virus into him, and wasn't Clarke pissed about ID4 using the same idea just before he published.
Yeah, and Vietnam when it was attacked by those terrorists from somewhere in Northern America because they were... what was it? Starting to become one of those socialist countries which everybody loves.
what do they ship if they, for example, do an embedded linux port for a microwave? Do they ship a CD with the code with the microwave?
Um, you have read the GPL right? Section 3 as follows:
3.You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a. Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b. Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c. Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
You will notice what section 3 (b) says. All they need is a little slip of paper or note at the back of the manual saying "This product contain GNU Opensource program. Send mail Address MicrowaveCompany Tokyo for source get. Have nice day."
You obviously know very little about security. Granted, any sysadmin who lets anyone upload any CGI script is asking for trouble, however the ability to execute commands as the CGI user opens up a whole new can of security worms.
You obviously know very little about CGI if you don't realise that the ability to upload any CGI script _is_ the ability to run any command as the CGI user.
The only difference here is that the script allows the commands to be specified later, rather than explicity at upload time. Woohoo. Anyone with any sense has password protected this CGI anyway, and runs it on a HTTPS service to stop password snooping. Makes it like a shell that doesn't require IP access, only cache-forwarded HTTPS. I have places I can only get the later, and it's handy to have something like this then. It's the same reason I use webmail as well as mutt-on-Maildir.
Re:A little more information
on
Adopt a KDE Geek
·
· Score: 2, Informative
Building KDE on my modern desktop (1.4 GHz Athlon, 512 MB RAM) takes 6-8 hours. Many developers are working on systems which cannot fully build KDE in under 24 hours
Given that most source files don't get changed every build, the major problem is going to be disk space. We need to donate some of those old 10 Gig disks that are too small for our MP3 (sorry, Ogg) collections now.
Oh, and we should give them all a pointer to Compiler Cache while we're at it.
Must install that on my own system, it look sweeeeet.
I could be wrong, but in my experience, it's usually slashdot that's wrong.
Nope, you're wrong.
Specifically, 8 channel stereo sound means that it can play 8 different sounds at once, through two speakers. If you've ever used a keyboard (that's a music keyboard, you know - with black and white keys, not just ivory ones) with only a few channels, you will recognise the sound of not-enough-channels.
Playing chords sounds very different depending which keys you hit first...
Anyway, 8 channel sound means that the noise of your rockets exploding won't suddenly stop half way through when you grunt.
Bills are lying around waiting to be paid and I'm trying to send out resumes and find some work before my wife and kid leave me
And then the sig: I'm a slashdot subscriber, are you?
Dude, I'd really reconsider that slashdot subscription if I was you. In these hard economic times, you should be looking at all the ads you can to save money for your family.
Should cab drivers be allowed to show movies in their cabs?
This isn't the same thing. The question should read 'should cab drivers be allowed to show commercial TV in their cabs' - complete with all the commercials which are already being used to pay the fucking royalties on whatever is shown in the 'non-ad' breaks.
If each person in the cab had their own radio set it wouldn't be a public performance, but because they're listening to exactly the same material from a shared speaker it becomes public. This is definitely the sort of reasoning of someone who can afford to buy their own congressman. Any sane person would throw it straight out.
The radio station has already paid the right for a public performance, and anyone who wants to listen to that performance (and suffer the ads) should be free to do so.
Another thing... with high bitrate mp3.. when comparing between an original and the compressed version in a blind test, someone will be able to tell you they are different, but not which one is the original... becasue both sound good.
Well duh, then what's the problem? If they both sound good then you'll enjoy either one, so listen to the one that uses less bandwidth.
That would be version 2.2 then. 2.1 is a development series kernel which was never supposed to be put into production use - only testing. If a vendor chooses to branch one and support it themselves, that is their choice - but don't complain about it not being supported any further by the mainstream kernel.
2.0.x, 2.2.x and 2.4.x are all being supported right now - and you can consider 2.2.x to be the logical end of the 2.1.x development series.
Well, for routers I'd say Netfilter could be a good thing. Although I guess it depends on your needs.
As another coyote user, I'd have to agree. The problem is sticking everything you need for 2.4 kernel plus ipfilter userland on a single floppy. I've managed it (using uClibc) but only by throwing away SSH (don't get me started on how complex the SSH daemons are).
No simple equivalent of SHOW COLUMNS. Consequently, it's hard to find any high level language API that allows you to read the structure of a database. Python... nope. Tcl... nope. Perl... nope. (Or at least not the last time I checked).
$dbh->func($table, 'table_attributes');
works fine for me in perl.
Proper keyboard support for the psql client is broken by default on many of the linux installs I work on (debian seems to be particularly bad). It's *very* frustrating trying when the arrow keys and tab completion doesn't work.
So file a bug report with your distribution. You can't blame poor packaging on the postgres people. I really haven't had these same problems, and I would suggest that the client checks if a library it needs is installed, and doesn't provide readline without it. Perhaps the package only suggests libreadline as a recommends rather than a requires and you haven't installed it? (I don't have any potato machines still running postgres to check against)
The documentation is tough reading. Very formal. Obviously done by comp-sci academics.
True, the documentation sucks. This is the main thing that annoys me.
No matter how hard I try, I cannot grok the date-time functions, which I find to be extremely cryptic.
Not to mention changing the functions without changing the documentation with 7.2.1, fuckers. This cost me many hours of debugging only to find that ('oh, and we removed a couple of bits of functionality without EVEN LOOKING AT THE HOWTO ON THE WEBSITE') it was a compatibility change.
Moving right along. I don't do particularly many calculations with dates inside postgres, um - I think they should really import a decent date handling library and dispose of those icky functions - I remember writing expressions at least 3 lines long to work out the time period of a month (1st through [28-31]st of a calendar month) at least 11 days previously. Messy.
You're completely wrong and here's why. Pick up any magazine off the rack that has a fan-art or letters section. Find the address to give submissions to. Nearby I guarantee there will be fine print. The fine print will say approximately this. Any and all letters sent to this address become property of "insert magazine name here". "magzine" reserves the right to edit, reuse, publish, etc. etc. We wont return anything you send to us.
And what if I randomly made up an address and posted something to it - and it just happened to be the address of that magazine? I've never seen the fine print in this case.
An analogy to your analogy would be putting something on my website (www.example.com) saying that everything sent to addresses @example.com will be published however I want it to. Actually, my example is better, because it's reasonable to expect that information about example.com can be found at www.example.com, while mailing a P.O. Box is completely random, and the lookup of the owner is harder.
Nice try though - the law doesn't require me to have read that magazine to have the address.
Do they do _all_ possible cases? I seem to remember there are heaps of asian character sets that get rather huge - do you also do equivalence mapping between them? What about the different forms of period in each one - are they all valid for.ext extentions?
What it falls down to is that you don't want similar LOOKING characters to have different values - and you've forgotten all the accented characters, umlauts, etc - do you fold them as well?
The reason non-Unix systems that support Unicode don't chug along is that (a) they support all of Unicode and (b) they don't fold all possible cases, just the few you've mentioned above.
Outside of anal-retentiveness, I can't think of a single reason that you'd *WANT* to be able to support filenames that differ only by case.
As the AC said, speed. More the point, once you start supporting unicode filenames then getting it exactly the same each time is even more important - the map of upper and lower cases in the full unicode table is huge.
One of the reasons I hope unicode support becomes more common in the future - it will put paid to this stupid case collapsing thing.
, and fish can swim around them without getting sliced up.
But that doesn't mean they can't swim through them and get sliced up instead, does it?
I think you're confusing low head water turbines with aircraft engines. The turbine will probably be something like a Kaplan which has big wide blades and turns at quite low speeds. Fish tend to flow straight through (though it would be rather disorienting for them I'm sure)
What surprises me is that these things have been used for years - I'm sure I read about 5 or 6 different designs of tidal and wave based generators a good 10 years ago when I was interested in these things.
Disclaimer - I have a lot more experience with high speed/high head impulse turbines (my father still has an original 1896 pelton water wheel with 'patent pending' on its cast iron sides - we took it out of production about 6 years ago when we decided the bearings were going through too much oil, and the new peltons could get an extra 20% efficiency, especially with specially wound low-speed alternators rather than old DC motors and v-belts)
I'd like to see some of the more imaginative wave-power systems used though (think balloon on surface anchored to cable on seafloor with bi-directional pump and bigass spring)
Of course, getting into Linus's tree is the Holy Grail of OpenScource development
why would it be such an honor? It's like you people treat Linux as a motherf**king idol.
Correct.
The reason it's such an honour is that there are a large group of people (myself included) who trust Linus' decisions - so if it makes it into his tree, we're more likely to trust it.
One of the reasons I trust his decisions is because he doesn't include every little patch written by whiners.
He's not an idol, he's someone I trust - that is worth a lot. I would be honoured if he accepted a patch by me (not that I've written any (yet))
But as the docs point out, partition image requires an already existing partition to write to.
Here's a fragment of the script I use for this purpose...
# Prepare the disk /bin/dd of=/dev/hda if=/dev/zero bs=512 count=1 /sbin/sfdisk/dev/hda < partitions.sfdisk
# wipe the start of the DOS partition as well /bin/dd of=/dev/hda2 if=/dev/zero bs=512 count=1
# and mark the boot record properly!! /bin/dd if=mbr.dd of=/dev/hda bs=512 count=1
DISKSIZE=`/sbin/sfdisk -s/dev/hda2`
Notice that I'm grabbing the partition size for later checking. I use 8Gb Windows partitions on 20Gb disks, leaving space to add things later (and flexibility for buying different sized disks on new systems). Since all important files are on a server anyway, 8Gb is plenty for Win98.
All these tools are available on any decent Linux boot disk (I'm using a rescuecd with the image of the partition burned on as well to save network load - pop it in and clean up the machine in about 9 minutes). I'm also reading a.reg file from the hard disk which contains details like the computer's name, and then re-building that file to be added to the registry on next boot. It works nicely.
Help, I can't get through to slashdot to complain about the filter.
Re:how to avoid getting on The Map
on
Mapping the Spam
·
· Score: 2
Many spammers now seem to put the recipient as the From address. Presumably this helps the mail to avoid certain filters. So in all probability, you're the only one being spammed from your address.
The slimeball spammers will probably read this and steal my idea, oh well...
I have implemented a filter check that will automatically pass things from my domain, but only if the Message-ID header contains my domain as well. I also automatically get anything with an In-Reply-To header which contains my domain.
I guess I'll be updating this filter soon enough, as the spammers bypass it. I'm currently running a very restrictive 'whitelist' of people I want to hear of while I go on holiday, but the In-Reply-To header rule seems sane enough, and I hate 'Vacation' messages.
a) it's easier to hand out legal LARTs than implement technical solutions yourself.
b) it's much easier to do URL blocking on a proxy than to try and work out what some (possibly encrypted) port 80 traffic to a random IP is on high speed links.
c) real-time content filtering at line speed is really, _really_, expensive.
d) ISPs can get away with transparent proxies, but putting a transparent proxy on the big backbone links, I don't think so - plus the corporate customers wouldn't stand for it (wish I had enough power in a big enough company to get the transparent proxy off from upstream of me - I'm quite capable of pointing squid at the upstream and not having staleness issues if I don't want them).
There are two types of internet censorship, the more recent "ISPs must block bad stuff out there", and the "ISPs must not host bad stuff".
For the not host bad stuff, it works by issuing legal LARTs against anyone hosting anything the censors don't like.
I presume this is the list that we're discussing here, since the list of "ISPS must block bad stuff out there" would be almost impossible to hide unless every ISP must run a closed source/black box URL checker.
I don't think there's much point in having a list of sites that have been taken down anyway, of course there's nothing there, and the URL may or may not actually say something useful by itself (just knowing that http://users.bigpond.com/~foobar/ was blocked isn't going to tell you a whole lot about the subversive pictures of a naked Brian Harradine that were posted there).
On the other hand, a list of the _reasons_ that sites were issued with takedown notices (similar to a public court record) would be good. Unlikely though.
Slashdot Mirror
I just like the way that the Yoper people claim that it's the most stable system they've used for 20 years, and then turn around and point out that the current version is a release candidate with a testing version of KDE installed and that if you want stability they suggest you don't install KDE. ... which sort of defeats the purpose of running Yoper rather than any other distro - the big difference between the distributions is how well they integrate the desktop environments and how sensible and stable their defaults are (not to mention linking tools against the desktop environments if possible for a cleaner behaviour).
I'm very impressed with the intelligent and humble discussion that is in that thread. They really are both trying to work out how to avoid the problem without breaking applications, rather than blamestorming or pretending it's not an issue.
... and glad I use konsole, at least until a bug is found there ;)
Michael Jenning's comments that he's not an expert on security, but does try his best show a real sense of humour and concern for his users.
Ok, so I'm being a bit of a fanboy, but most links to discussions between open-source developers I see these days are the fights they have (on the very public mailing lists where we can see them). We tend to forget the good work they do the rest of the time.
(raises hat, or would if I was wearing one)
£26 billion dollars ?????
I knew we were allies with the brits, but isn't this getting carried away?
I imagine it's something to do with the US Army using Paypal to pay for it. Maybe they got carried away bidding against Saddam for that 'leet "Leenix" thing on ebay.
HAL wins for more memorable death. Though I guess the Daisy bit wasn't really his death, that came with the whole Jupiter ignition thing...
I guess you haven't read the books then, or you would know it came when they uploaded the virus into him, and wasn't Clarke pissed about ID4 using the same idea just before he published.
Yeah, and Vietnam when it was attacked by those terrorists from somewhere in Northern America because they were... what was it? Starting to become one of those socialist countries which everybody loves.
Hmm....
what do they ship if they, for example, do an embedded linux port for a microwave? Do they ship a CD with the code with the microwave?
Um, you have read the GPL right? Section 3 as follows:
3.You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a. Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b. Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c. Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
You will notice what section 3 (b) says. All they need is a little slip of paper or note at the back of the manual saying "This product contain GNU Opensource program. Send mail Address MicrowaveCompany Tokyo for source get. Have nice day."
(excuse my engrish)
You obviously know very little about security. Granted, any sysadmin who lets anyone upload any CGI script is asking for trouble, however the ability to execute commands as the CGI user opens up a whole new can of security worms.
You obviously know very little about CGI if you don't realise that the ability to upload any CGI script _is_ the ability to run any command as the CGI user.
The only difference here is that the script allows the commands to be specified later, rather than explicity at upload time. Woohoo. Anyone with any sense has password protected this CGI anyway, and runs it on a HTTPS service to stop password snooping. Makes it like a shell that doesn't require IP access, only cache-forwarded HTTPS. I have places I can only get the later, and it's handy to have something like this then. It's the same reason I use webmail as well as mutt-on-Maildir.
Building KDE on my modern desktop (1.4 GHz Athlon, 512 MB RAM) takes 6-8 hours. Many developers are working on systems which cannot fully build KDE in under 24 hours
Given that most source files don't get changed every build, the major problem is going to be disk space. We need to donate some of those old 10 Gig disks that are too small for our MP3 (sorry, Ogg) collections now.
Oh, and we should give them all a pointer to Compiler Cache while we're at it.
Must install that on my own system, it look sweeeeet.
I could be wrong, but in my experience, it's usually slashdot that's wrong.
Nope, you're wrong.
Specifically, 8 channel stereo sound means that it can play 8 different sounds at once, through two speakers. If you've ever used a keyboard (that's a music keyboard, you know - with black and white keys, not just ivory ones) with only a few channels, you will recognise the sound of not-enough-channels.
Playing chords sounds very different depending which keys you hit first...
Anyway, 8 channel sound means that the noise of your rockets exploding won't suddenly stop half way through when you grunt.
Bills are lying around waiting to be paid and I'm trying to send out resumes and find some work before my wife and kid leave me
And then the sig: I'm a slashdot subscriber, are you?
Dude, I'd really reconsider that slashdot subscription if I was you. In these hard economic times, you should be looking at all the ads you can to save money for your family.
Should cab drivers be allowed to show movies in their cabs?
This isn't the same thing. The question should read 'should cab drivers be allowed to show commercial TV in their cabs' - complete with all the commercials which are already being used to pay the fucking royalties on whatever is shown in the 'non-ad' breaks.
If each person in the cab had their own radio set it wouldn't be a public performance, but because they're listening to exactly the same material from a shared speaker it becomes public. This is definitely the sort of reasoning of someone who can afford to buy their own congressman. Any sane person would throw it straight out.
The radio station has already paid the right for a public performance, and anyone who wants to listen to that performance (and suffer the ads) should be free to do so.
Another thing... with high bitrate mp3.. when comparing between an original and the compressed version in a blind test, someone will be able to tell you they are different, but not which one is the original... becasue both sound good.
Well duh, then what's the problem? If they both sound good then you'll enjoy either one, so listen to the one that uses less bandwidth.
*sigh*
Fine, so go and find a patch for a 2.0 kernel. The point remains the same.
You would be talking about
this
perhaps?
When was the last 2.1 patch?
That would be version 2.2 then. 2.1 is a development series kernel which was never supposed to be put into production use - only testing. If a vendor chooses to branch one and support it themselves, that is their choice - but don't complain about it not being supported any further by the mainstream kernel.
2.0.x, 2.2.x and 2.4.x are all being supported right now - and you can consider 2.2.x to be the logical end of the 2.1.x development series.
Well, for routers I'd say Netfilter could be a good thing. Although I guess it depends on your needs.
As another coyote user, I'd have to agree. The problem is sticking everything you need for 2.4 kernel plus ipfilter userland on a single floppy. I've managed it (using uClibc) but only by throwing away SSH (don't get me started on how complex the SSH daemons are).
Oh well, another project for the spare time.
No simple equivalent of SHOW COLUMNS. Consequently, it's hard to find any high level language API that allows you to read the structure of a database. Python... nope. Tcl... nope. Perl... nope. (Or at least not the last time I checked).
$dbh->func($table, 'table_attributes');
works fine for me in perl.
Proper keyboard support for the psql client is broken by default on many of the linux installs I work on (debian seems to be particularly bad). It's *very* frustrating trying when the arrow keys and tab completion doesn't work.
So file a bug report with your distribution. You can't blame poor packaging on the postgres people. I really haven't had these same problems, and I would suggest that the client checks if a library it needs is installed, and doesn't provide readline without it. Perhaps the package only suggests libreadline as a recommends rather than a requires and you haven't installed it? (I don't have any potato machines still running postgres to check against)
The documentation is tough reading. Very formal. Obviously done by comp-sci academics.
True, the documentation sucks. This is the main thing that annoys me.
No matter how hard I try, I cannot grok the date-time functions, which I find to be extremely cryptic.
Not to mention changing the functions without changing the documentation with 7.2.1, fuckers. This cost me many hours of debugging only to find that ('oh, and we removed a couple of bits of functionality without EVEN LOOKING AT THE HOWTO ON THE WEBSITE') it was a compatibility change.
Moving right along. I don't do particularly many calculations with dates inside postgres, um - I think they should really import a decent date handling library and dispose of those icky functions - I remember writing expressions at least 3 lines long to work out the time period of a month (1st through [28-31]st of a calendar month) at least 11 days previously. Messy.
You're completely wrong and here's why. Pick up any magazine off the rack that has a fan-art or letters section. Find the address to give submissions to. Nearby I guarantee there will be fine print. The fine print will say approximately this. Any and all letters sent to this address become property of "insert magazine name here". "magzine" reserves the right to edit, reuse, publish, etc. etc. We wont return anything you send to us.
And what if I randomly made up an address and posted something to it - and it just happened to be the address of that magazine? I've never seen the fine print in this case.
An analogy to your analogy would be putting something on my website (www.example.com) saying that everything sent to addresses @example.com will be published however I want it to. Actually, my example is better, because it's reasonable to expect that information about example.com can be found at www.example.com, while mailing a P.O. Box is completely random, and the lookup of the owner is harder.
Nice try though - the law doesn't require me to have read that magazine to have the address.
Do they do _all_ possible cases? I seem to remember there are heaps of asian character sets that get rather huge - do you also do equivalence mapping between them? What about the different forms of period in each one - are they all valid for .ext extentions?
What it falls down to is that you don't want similar LOOKING characters to have different values - and you've forgotten all the accented characters, umlauts, etc - do you fold them as well?
The reason non-Unix systems that support Unicode don't chug along is that (a) they support all of Unicode and (b) they don't fold all possible cases, just the few you've mentioned above.
Outside of anal-retentiveness, I can't think of a single reason that you'd *WANT* to be able to support filenames that differ only by case.
As the AC said, speed. More the point, once you start supporting unicode filenames then getting it exactly the same each time is even more important - the map of upper and lower cases in the full unicode table is huge.
One of the reasons I hope unicode support becomes more common in the future - it will put paid to this stupid case collapsing thing.
, and fish can swim around them without getting sliced up.
But that doesn't mean they can't swim through them and get sliced up instead, does it?
I think you're confusing low head water turbines with aircraft engines. The turbine will probably be something like a Kaplan which has big wide blades and turns at quite low speeds. Fish tend to flow straight through (though it would be rather disorienting for them I'm sure)
What surprises me is that these things have been used for years - I'm sure I read about 5 or 6 different designs of tidal and wave based generators a good 10 years ago when I was interested in these things.
Disclaimer - I have a lot more experience with high speed/high head impulse turbines (my father still has an original 1896 pelton water wheel with 'patent pending' on its cast iron sides - we took it out of production about 6 years ago when we decided the bearings were going through too much oil, and the new peltons could get an extra 20% efficiency, especially with specially wound low-speed alternators rather than old DC motors and v-belts)
I'd like to see some of the more imaginative wave-power systems used though (think balloon on surface anchored to cable on seafloor with bi-directional pump and bigass spring)
Of course, getting into Linus's tree is the Holy Grail of OpenScource development
why would it be such an honor? It's like you people treat Linux as a motherf**king idol.
Correct.
The reason it's such an honour is that there are a large group of people (myself included) who trust Linus' decisions - so if it makes it into his tree, we're more likely to trust it.
One of the reasons I trust his decisions is because he doesn't include every little patch written by whiners.
He's not an idol, he's someone I trust - that is worth a lot. I would be honoured if he accepted a patch by me (not that I've written any (yet))
Here's a fragment of the script I use for this purpose...Notice that I'm grabbing the partition size for later checking. I use 8Gb Windows partitions on 20Gb disks, leaving space to add things later (and flexibility for buying different sized disks on new systems). Since all important files are on a server anyway, 8Gb is plenty for Win98.
All these tools are available on any decent Linux boot disk (I'm using a rescuecd with the image of the partition burned on as well to save network load - pop it in and clean up the machine in about 9 minutes). I'm also reading a
I just did the same to /. ;)
Help, I can't get through to slashdot to complain about the filter.
Many spammers now seem to put the recipient as the From address. Presumably this helps the mail to avoid certain filters. So in all probability, you're the only one being spammed from your address.
The slimeball spammers will probably read this and steal my idea, oh well...
I have implemented a filter check that will automatically pass things from my domain, but only if the Message-ID header contains my domain as well. I also automatically get anything with an In-Reply-To header which contains my domain.
I guess I'll be updating this filter soon enough, as the spammers bypass it. I'm currently running a very restrictive 'whitelist' of people I want to hear of while I go on holiday, but the In-Reply-To header rule seems sane enough, and I hate 'Vacation' messages.
Why do they need to block sites at the ISP level?
a) it's easier to hand out legal LARTs than implement technical solutions yourself.
b) it's much easier to do URL blocking on a proxy than to try and work out what some (possibly encrypted) port 80 traffic to a random IP is on high speed links.
c) real-time content filtering at line speed is really, _really_, expensive.
d) ISPs can get away with transparent proxies, but putting a transparent proxy on the big backbone links, I don't think so - plus the corporate customers wouldn't stand for it (wish I had enough power in a big enough company to get the transparent proxy off from upstream of me - I'm quite capable of pointing squid at the upstream and not having staleness issues if I don't want them).
Grumble stupid control-freak politicians anyway.
Are IP's blocked? Are DNS lookups merely prohibited?
Some people's slashdot memory is obviously rather short, since I'm sure the Australian law has been posted about before. Specifically, basically the same story as this, New South Wales law on end users, Censorship law passed, Even older article on the same thing.
Ok, that's just 4 of them.
There are two types of internet censorship, the more recent "ISPs must block bad stuff out there", and the "ISPs must not host bad stuff".
For the not host bad stuff, it works by issuing legal LARTs against anyone hosting anything the censors don't like.
I presume this is the list that we're discussing here, since the list of "ISPS must block bad stuff out there" would be almost impossible to hide unless every ISP must run a closed source/black box URL checker.
I don't think there's much point in having a list of sites that have been taken down anyway, of course there's nothing there, and the URL may or may not actually say something useful by itself (just knowing that http://users.bigpond.com/~foobar/ was blocked isn't going to tell you a whole lot about the subversive pictures of a naked Brian Harradine that were posted there).
On the other hand, a list of the _reasons_ that sites were issued with takedown notices (similar to a public court record) would be good. Unlikely though.