jfm3 writes "The lack of diplomacy, ecological consciousness, and ability to think critically since September 2001 is fuelling the campaigns of many candidates for the country's American President role, with many pushing for a politer and more intelligent foreign policy to stop Americans heading for greener and more peaceful pastures."
Perhaps this does not appear on topic, a crime against slashdot of the highest caliber. Of course, both statements are equally absurd because of their obviousness (at least to me).
Most ISPs do spam filtering these days. Users demand it.
Spam is put in a special IMAP folder rather than being deleted outright, so you can double check if you want. This is the same thing you get with a client side spam filter, right?
I'd rather have client side spam filtering than not, I agree, but I still think the ideal place to do it is on the server side.
Have you tried server side Spam filtering? For example, spamassassin and procmail? This works much better for me, since I don't have to waste a lot of bandwidth downloading the spam just to determine that it is spam and should be discarded. AFAIC, it's the only way to go.
"SCO claims that they were duped into releasing the source code initially, that they didn't realise that the Linux kernel had their source code. There has also been much discussion about legal precedent on this, relating to the selling of pregnant cows."
For some reason, pregnant cow selling laws sound very funny to me. I googled a bit but couldn't come up with anything. Can somebody clarify what what "legal precedent" relating to pregnant cows they're refering to?
The article is peppered with subtle jabs at Linux. For example, this gem:
"Until recently, interacting with Linux was almost entirely text-driven -- much like Windows' precursor, DOS. So converting meant learning an arcane vocabulary of computerese to give the PC even the simplest commands."
That's some good crack they've got over there in MSNBC land. Information technology journalism inevitably sucks. It's all either lies or damned lies. That goes for/. too.
"BTW, the currently available Companion CD already include the RedHat package manager (RPM), but for the time being we'll continue to support the System 5 pkgadd format because it is the consistent choice for our customer base and they tell us it still provides several advantages."
He's lying. Their customer base has been bitching for years about pkgadd format and how insanely bad it is. Even the Ximian guys won't go along with pkgadd, and they're on the Sun payroll. For a real alternative, look at http://rpm.rutgers.edu.
Our best stop-thrust against embrace-and-extend is to point out that Microsoft is trying to close up the Internet. -- Eric Raymond
Commentary:
So long as one bit can be transmitted from node to node, the Internet will remain open. With strong crypto and decentralized control as your only weapons, you are undefeatable. Continue hacking.
Microsoft tries to damn the ocean as it would a river. There is no understanding.
The man page is available at http://www.npsnet.com/danf/software/autospec(1). html. See http://www.npsnet.com/danf/software/ for more details or http://www.npsnet.com/danf/software/pub/autospec -0.3-1.noarch.rpm to download. There are other RPM developer resources listed at http://www.rpm.org/software.html.
I haven't tried it, but there's a program to automatically generate RPM spec files from projects that use autoconf/automake/libtool/etc. Here is the relevant snippet from the RPM mailing list.
I've created a program called autospec that can create spec files automatically from the contents of a.tar.gz archive. If the archive contains a Linux Software Map (.lsm) file, then there's a good chance that the resulting spec file will require no tweaking, but in most cases you'll probably need to edit the result somewhat. It does eliminate most of the grunt work involved in creating a new spec file from scratch, however.
The man page is available at . See for more details or to download. There are other RPM developer resources listed at .
This sounds like it will bring one a long way towards.tar.gz ->.rpm.
Rutgers University has a long range plan to produce a distribution of Linux that is not so prone to casual network vandalism as RedHat is out of the box. We have similar problems with all other operating systems.
There is a lot of Linux at Rutgers. Many students run RedHat in their dorms. There are at least two Beowulf clusters that I know of. At least one very large lab full of X display servers will be moving to commodity hardware running Linux. Central computing services recognizes RedHat, Debian, and SuSE as supported platforms. (It's what the "supported" means that still isn't clear.)
I'll be emailing the man from Boston University doing something similar tomorrow when I'm at my desk.
This card, or pretty much any other, is pointless unless they make their own ALSA or OSS/Free driver for it. Simply publishing the hardware details usually isn't enough to generate a sound card driver these days.
Those looking for a Linux soundcard should read the Linux Audio Quality HOWTO. Also, recently, kernel hacks have been posted that claim better latency in real time audio applications than is available with MacOS, BeOS, or any of the 31 flavors of Windows. I have links to draft versions of papers on doing so: email me if you're really interested. While I'm at the link game, I should also mention the Linux Music Station as important for anybody doing even batch audio processing with Linux.
Another month or so and we'll be able to turn a beefy Linux box into a complete music composition and performance workstation!
You won't get decent under $200. You'll be really unhappy with any mixer you buy at Rat Shock.
You will get a Mackie 1202 ("classic", not "VLZ" or "VLZ Pro") on eBay for around $200.
You can have my 1202 when you pry it from my cold dead fingers. They solve one million problems. I'm using one right now to run 3 sound cards, 3 synths, 3 effects boxen (side chained), 4 cdrom drive audio outputs, and a phone!
I think MIDIMAN makes tiny analogue mixers... but I'd still suggest the Mackie. A Mackie will last you for the rest of your life in both maintainability (bulit like a tank) and usefulness.
Slashdot Mirror
jfm3 writes "The lack of diplomacy, ecological consciousness, and ability to think critically since September 2001 is fuelling the campaigns of many candidates for the country's American President role, with many pushing for a politer and more intelligent foreign policy to stop Americans heading for greener and more peaceful pastures."
Perhaps this does not appear on topic, a crime against slashdot of the highest caliber. Of course, both statements are equally absurd because of their obviousness (at least to me).
Most ISPs do spam filtering these days. Users demand it.
Spam is put in a special IMAP folder rather than being deleted outright, so you can double check if you want. This is the same thing you get with a client side spam filter, right?
I'd rather have client side spam filtering than not, I agree, but I still think the ideal place to do it is on the server side.
Have you tried server side Spam filtering? For example, spamassassin and procmail? This works much better for me, since I don't have to waste a lot of bandwidth downloading the spam just to determine that it is spam and should be discarded. AFAIC, it's the only way to go.
"SCO claims that they were duped into releasing the source code initially, that they didn't realise that the Linux kernel had their source code. There has also been much discussion about legal precedent on this, relating to the selling of pregnant cows."
For some reason, pregnant cow selling laws sound very funny to me. I googled a bit but couldn't come up with anything. Can somebody clarify what what "legal precedent" relating to pregnant cows they're refering to?
Does anyone have actual numbers on battery power, or projected battery life comparisons between the 5500 and 5600?
... of the Internet.
WTF is this a picture of anyway? There seem to be a lot of spooks like this in here.
The article is peppered with subtle jabs at Linux. For example, this gem:
/. too.
"Until recently, interacting with Linux was almost entirely text-driven -- much like Windows' precursor, DOS. So converting meant learning an arcane vocabulary of computerese to give the PC even the simplest commands."
That's some good crack they've got over there in MSNBC land. Information technology journalism inevitably sucks. It's all either lies or damned lies. That goes for
There are no exams that are fair for everyone. One could even argue that there are no exams that are fair for anyone.
Are you being tested on your knowledge of coding, or your understanding of principles?
Study principles. Code is completely secondary.
"BTW, the currently available Companion CD already include the RedHat package manager (RPM), but for the time being we'll continue to support the System 5 pkgadd format because it is the consistent choice for our customer base and they tell us it still provides several advantages."
He's lying. Their customer base has been bitching for years about pkgadd format and how insanely bad it is. Even the Ximian guys won't go along with pkgadd, and they're on the Sun payroll. For a real alternative, look at http://rpm.rutgers.edu.
"... a CD-R as standard equipment ... is unparalleled as a backup medium. ... (DDS tapes do NOT fill all needs; CD-R is FAR more robust.)"
..."
You are out of your mind.
"I'd have been glad to buy CD-R drives from Sun at the usual drastic markup
You are totally and completely out of your mind.
Lisp may be fast, but assembly is the fASTeST.
Have them program a video game.
They're probably doing it anyway.
Wisdom:
How much space is in a tab?
Commentary:
Any C style guide that describes tab stops will fail. Why then build it into the language syntax?
And when did we all stop believing in real garbage collectors?
Wisdom:
Worse is better.
Commentary:
It has been said that Lisp programmers know the value of everything, but the cost of nothing.
Anyone who doubts the efficacy of Lisp systems needs look no further than GNU Emacs for true insight.
Wisdom:
Imminent Death Of The Net Predicted!
Commentary:
Some would emphasize privacy -- who is reading what. This is not the true way.
Emphasize content -- what is being read. This is the true way.
Would Mr. Cringely's articles attract commercial advertising if they were not inflamatory?
Wisdom:
Our best stop-thrust against embrace-and-extend is to point out that Microsoft is trying to close up the Internet.
-- Eric Raymond
Commentary:
So long as one bit can be transmitted from node to node, the Internet will remain open. With strong crypto and decentralized control as your only weapons, you are undefeatable. Continue hacking.
Microsoft tries to damn the ocean as it would a river. There is no understanding.
Parable:
Before enlightenment, write code, fix bugs.
After enlightenment, write code, fix bugs.
Commentary:
Perhaps the author of the X Windows Must Die! article should get back to writing code and fixing bugs?
Also, it is important to remember that in this parable, the word enlightenment does not mean a window manager.
oops.
. html. See c -0.3-1.noarch.rpm to
here are the links.
The man page is available at
http://www.npsnet.com/danf/software/autospec(1)
http://www.npsnet.com/danf/software/ for more details or
http://www.npsnet.com/danf/software/pub/autospe
download. There are other RPM developer resources listed at
http://www.rpm.org/software.html.
damn you and your damn submit button!
I've created a program called autospec that can create spec files automatically from the contents of a .tar.gz archive. If the archive contains a Linux Software Map (.lsm) file, then there's a good chance that the resulting spec file will require no tweaking, but in most cases you'll probably need to edit the result somewhat. It does eliminate most of the grunt work involved in creating a new spec file from scratch, however.
The man page is available at . See for more details or to download. There are other RPM developer resources listed at .
This sounds like it will bring one a long way towards .tar.gz -> .rpm.
There is a lot of Linux at Rutgers. Many students run RedHat in their dorms. There are at least two Beowulf clusters that I know of. At least one very large lab full of X display servers will be moving to commodity hardware running Linux. Central computing services recognizes RedHat, Debian, and SuSE as supported platforms. (It's what the "supported" means that still isn't clear.)
I'll be emailing the man from Boston University doing something similar tomorrow when I'm at my desk.
It is a great time to be a UNIX hacker.
(jfm3)
This card, or pretty much any other, is pointless unless they make their own ALSA or OSS/Free driver for it. Simply publishing the hardware details usually isn't enough to generate a sound card driver these days.
Those looking for a Linux soundcard should read the Linux Audio Quality HOWTO. Also, recently, kernel hacks have been posted that claim better latency in real time audio applications than is available with MacOS, BeOS, or any of the 31 flavors of Windows. I have links to draft versions of papers on doing so: email me if you're really interested. While I'm at the link game, I should also mention the Linux Music Station as important for anybody doing even batch audio processing with Linux.
Another month or so and we'll be able to turn a beefy Linux box into a complete music composition and performance workstation!
I'm no expert, but every synth-DIYer I've ever talked with has said "if you're considering DIY building a mixer, don't."
That being said, there are some affordable DIY kit options from PAiA. I haven't tried these, but everything else I've built that's PAiA is excellent.
Just get the damn Mackie :)
You won't get decent under $200. You'll be really unhappy with any mixer you buy at Rat Shock.
You will get a Mackie 1202 ("classic", not "VLZ" or "VLZ Pro") on eBay for around $200.
You can have my 1202 when you pry it from my cold dead fingers. They solve one million problems. I'm using one right now to run 3 sound cards, 3 synths, 3 effects boxen (side chained), 4 cdrom drive audio outputs, and a phone!
I think MIDIMAN makes tiny analogue mixers... but I'd still suggest the Mackie. A Mackie will last you for the rest of your life in both maintainability (bulit like a tank) and usefulness.
Good luck!
The software and on line reconciliation system don't appear to be available yet. This is vaporware.
I got about as far as the first paragraph of page 2. His heart is there, but the words suck.