I don't know about the encoder per se, but is your ripping program slowing the actual read of the audio data by forcing it to go at the same rate as the encode? It should do the two in parallel, but not slow the rip by the decode.
[...] and I don't see much content using this at all. I got my Red Hat ISOs from Red Hat with no problem.
The example you used (the red het ISOs) is irrelevant. Bittorrent only works if people are still using the torrent - if nobody's using it, there's nowhere to download it from. Wait for the next distro release.
[...] why it uses an out-of-band.torrent file instead of some other communications protocol that replaces http.
I don't see any analysis of why I might want to "donate" my bandwidth to some person I don't know, or why I should expect bandwidth from anyone except the person I'm downloading from.
Because it works faster. If you don't want to donate bandwith, then you're only slowing the network. The network will then shun you, as that kind of behavior is detrimental to the speed of the network.
Personally, I'd do it with procmail - you could more easily return a message that dosen't look like a bounce, and thus isn't ignored by the typical AOL luser.
There's no good way to prevent this. If a new company gets a domain name, should they have to wait for every sysadmin in the world to mark their key trusted before they can send email? If so, sysadmins will disable the functionality. If not, the problem isn't solved and better than the blacklists do it.
Let's face it: SMTP is broken and it needs to be fixed. There has to be some way of authenticating senders and attachments to messages?
There is - it's called PGP. SMTP is only intended to transport mail, not to authenticate it. It's the client's job to determine if it should be accepted.
I don't mind using a binary driver provided and supported by a manufacturer for their product, rather than being totally unable to use their product because of the lack of an open-source driver.
I don't buy the product.
Maybe you don't, but most people do. And unless those people get their drivers, they won't use linux. Once there's enough market share, Linux can reject binary drivers and the manufacturers will have to provide OS drivers - but for the moment there's just no reason for the manufacturers to release OS drivers, and without the binary drivers there will never be an OS driver.
But in reality, what people in their right mind would do that? I mean, assuming: The hacker was benevolent and wanted the 6 monthes. If you hacked the system - you have unlimited, forever usage of the system, hence the word "0wnz," I believe?
No, the sysadmins boot from Knoppix or something, do some forensics and haul you into jail while restoring from backups.
I have a server not in the dynamic range - I can relay off it. Interestingly, ORDB's mail server rejects my 24.25 IP, but it's not listed in their open relay list...
Slashdot Mirror
What about Star wars in ASCII in barcode?
Good point, but (AFAIK) the protocol dosen't specify how to get .torrents from the trackers.
I don't know about the encoder per se, but is your ripping program slowing the actual read of the audio data by forcing it to go at the same rate as the encode? It should do the two in parallel, but not slow the rip by the decode.
Will this be added to the Section bar on the right-hand side?
Well, if slashdot posted a direct link to the donations page...
Personally, I'd do it with procmail - you could more easily return a message that dosen't look like a bounce, and thus isn't ignored by the typical AOL luser.
There's no good way to prevent this. If a new company gets a domain name, should they have to wait for every sysadmin in the world to mark their key trusted before they can send email? If so, sysadmins will disable the functionality. If not, the problem isn't solved and better than the blacklists do it.
There is - it's called PGP. SMTP is only intended to transport mail, not to authenticate it. It's the client's job to determine if it should be accepted.
It's possible to hack DS to work without the servers: Use the login disabler at http://mainframe.chani3.com/
We know you submitted the article. If you want hardware, why didn't you just say so?
So, 1,234.5 becomes 1.234,5?
Only Microcode bugs really affect everyone. Not everyone has BIOS, a kernel, and not everyone has Windows installed by default.
I'd block Korean IPs, but I don't know what ranges to enter.
The key ID is the last 8 hex digits of the fingerprint, so you don't need to verify that.
Opendivx then. Or libavcodec.
I have a server not in the dynamic range - I can relay off it. Interestingly, ORDB's mail server rejects my 24.25 IP, but it's not listed in their open relay list...
If you check the sequence number for fragmented IP packets you can count it. There was an article some time ago about it.