IMHO, in rough order of value: SpamCop - Catches by far the most spam. Falses rarely, though yahoo shows up from time to time. Spews - Known spam sources. Never falses. ORDB - Fair false rate, and a lot of overlap with SpamCop.
I'd imagine that having detailed aural access to what is behind you could be a distinct advantage over just that tiny window in front of seeing players.
When reading the submission, I was expecting an argument along the lines of "Do it for the community. If you leave, your previous employer will be nudged toward being more proactive in compensating everyone else."
That's a more interesting reason to consider. The listed arguments are pretty weak.
So the problem is that computers check the data tracks before playing the audio, and give up when the data track is bad. Is it the CD drive doing this, or could the OS be modified to accept these CDs?
What I really want is a product that record scheduled audio programming of interest and syncs it to a portable player. The source of the audio is not important.
compressed filenames for one issue, also a whole lot of other news with the database format beeing changed. and if you stop the complaints before looking deeper into things you might get some more info for yourself.
It wasn't a complaint, it was a question. The resolution of the "redhat as evil empire" question rests on their motivation for making the
imcompatible changes that we are seeing. The gcc issue has been hashed out pretty well. The RPM changes could use some scrutiny.
As you say, I could (should) find out what changed with some looking. The harder question is why. That requires some thought/discussion. Hence the question.
So tell me again. The reason for forcing people to choose between tracking RedHat and giving up on rpms is... compressed filenames?
The backend database part has been completely rewritten. Sometimes you just have to break backward compatibility in order to move on. Besides, there's an updated RPM version available for 6.0-6.2 that fixes bugs and also allows you to install RPM4 RMP's.
But this need not have anything to do with the RPM file format. So again, what is the killer feature that caused the file incompatibility?
A cynic might say it was to force the market to track RedHat more closely. I'm looking to be dissuaded from that view by the facts. So what are they?
Slashdot Mirror
This could be a lot easier if P2P had it's act together.
BitTorrent
... from the man who pronounced it lame.
George Reeves, the first TV superman, committed suicide.
Christopher Reeve is paralyzed.
Hope Keanu has better luck.
Is there some method to make the picture flash at just the right point? Otherwise, you would just see a smear.
(something equivalent to the slits on the old rotoscopes)
IMHO, in rough order of value:
SpamCop - Catches by far the most spam. Falses rarely, though yahoo shows up from time to time.
Spews - Known spam sources. Never falses.
ORDB - Fair false rate, and a lot of overlap with SpamCop.
I'd imagine that having detailed aural access to what is behind you could be a distinct advantage over just that tiny window in front of seeing players.
Sounds like it would be fun to try.
But it is lame!
When reading the submission, I was expecting an argument along the lines of "Do it for the community. If you leave, your previous employer will be nudged toward being more proactive in compensating everyone else."
That's a more interesting reason to consider. The listed arguments are pretty weak.
...of this story
So the problem is that computers check the data tracks before playing the audio, and give up when the data track is bad. Is it the CD drive doing this, or could the OS be modified to accept these CDs?
it is a bit of a pain in the butt having to apply patches to my RedHat server each month
Try AutoUpdate. It does a good job keeping RedHat up to date.
That should go a long way towards taking care of the problem.
"You're listening to WKRC in Cincinnati, my children. Let your soul be soothed by the mellow sounds of Venus."
As mentioned that was WKRP, though the picture used at the beginning of the show was the WKRC tower on the hill overlooking the city.
What I really want is a product that record scheduled audio programming of interest and syncs it to a portable player. The source of the audio is not important.
Predator has the same strange looking tail. Anyone know why?
I think you just said that you want a .NET environment.
Use an MTA that supports the SMTP STARTTLS command, such as Sendmail or Exchange, and then configure it.
compressed filenames for one issue, also a whole lot of other news with the database format beeing changed. and if you stop the complaints before looking deeper into things you might get some more info for yourself.
It wasn't a complaint, it was a question. The resolution of the "redhat as evil empire" question rests on their motivation for making the
imcompatible changes that we are seeing. The gcc issue has been hashed out pretty well. The RPM changes could use some scrutiny.
As you say, I could (should) find out what changed with some looking. The harder question is why. That requires some thought/discussion. Hence the question.
So tell me again. The reason for forcing people to choose between tracking RedHat and giving up on rpms is ... compressed filenames?
The backend database part has been completely rewritten. Sometimes you just have to break backward compatibility in order to move on. Besides, there's an updated RPM version available for 6.0-6.2 that fixes bugs and also allows you to install RPM4 RMP's.
But this need not have anything to do with the RPM file format. So again, what is the killer feature that caused the file incompatibility?
A cynic might say it was to force the market to track RedHat more closely. I'm looking to be dissuaded from that view by the facts. So what are they?
OK, we've heard plausible reasons for breaking binaries. What I haven't heard is why the RPM file format was changed incompatibly.
I don't see any new features in the new RPM. What was the reason for forking here?
The Good Times "social virus" is one of the best examples of an effective, low effort hacks.