Snag the Red Hat 9 ISOs, via Cash or BitTorrent
Tectonic Rumblings
Every so often a new tool comes along that causes a shift from Bronze to Iron, that divides history into "before" and "after." The peer-to-peer world has certainly seen its share. Those who used 486s to encode and play MP3s remember it wasn't just abysmal modem speeds that kept people from casual trading, but the tiresome process of finding users and content; Napster freed us from that bondage, letting the computer do the heavy lifting and freeing people to do what they do best.
When the weaknesses began to show in Napster's overly centralized model, Gnutella stepped in with a distributed, decentralized network. Audiogalaxy gave us astounding variety (even the most obscure music could always be found sooner or later) and a rich sense of community that is still sorely missed. WinMX offered the ability to connect to multiple Napster-compatible networks; with the advent of multi-source downloading, Morpheus and similar programs allowed us to rise above the limitations of slow upstream (until it's hard now to find any P2P applications that don't use it); and EDonkey added the nice touch of being able to share files before they were done downloading.
So what's the next stage of P2P evolution?
Enter BitTorrent -- a "swarming, scatter and gather" file transfer protocol developed by Bram Cohen that's taking the net by storm. Even without a friendly, unified interface, BT's ability to scale in the face of overwhelming demand while minimizing the free rider problem ("leeching") has attracted a flood of new users. But as with any tool, understanding how and why it works will always make using it easier and more fun.
All technical references are taken from the BT server tutorial and the official documentation.
Let's Start with the Basics
BitTorrent is not a 'website' or a 'network', and strictly speaking is not even a program -- it's a protocol with a number of functional implementations.
Instead of jumping right into downloading, first we'll discuss how files are served. Most new BT users are familiar with going to a website and clicking on links to .torrent files, but this just provides a friendlier interface and isn't actually necessary. All you really need to serve is a public Internet machine. The "tracker" will "keep track" of who is connected and who has which pieces of the file(s) in question. Like any public Internet service, a static IP address and/or valid hostname will make it easier for people to connect to your tracker.
To start serving, you choose a file or directory to serve and run a program which generates a .torrent file. This contains a 'hash,' which serves as a checksum to ensure the file is the same on all systems, as well as the address of a tracker. A typical .torrent file is quite small, typically 5-50k in size.
The second step is to load the .torrent file into a BT client. The client asks you where to save the file, you point it at the existing and complete copy, it verifies that the file hash matches, says the download is done and sits there uploading when necessary until you cancel it.
Here's an animated graphic (.mng, currently viewable only in Mozilla) of a torrent transfer.
Getting Started
The official BT client is available for Win32, Mac OS X, as an unstable Debian package, and as Python source code.
Getting started is quite simple; the Windows installer asks no questions and provides no options, and the only behind-the-scenes addition is that Internet Explorer now launches BT when you click on links to .torrent files. (Mozilla users will need to edit Preferences, Navigator, Helper Applications and add the mime type "application/x-bittorrent", to be launched by the btdownloadprefetched executable.) You can also download .torrent files and load them locally without going through a website.
Once the .torrent has been invoked, the client will prompt you for a location to save the file to. The client then creates a file of the appropriate size containing all zeros, and connects to the tracker to get a starting list of some random subset of available peers (other users connected to the 'swarm'). BT then starts connecting to peers and downloading random chunks of the file, and begin uploading to other peers as soon as you have enough for it to bother.
Every time your client verifies another piece of the download, it tells the tracker it has a good copy of that piece. By directly utilizing each user's outgoing bandwidth, downloads can be generally be completed very quickly while minimizing the load on the original server, in effect turning the dreaded "Slashdot Effect" against itself -- the more who want to download, the more there are to upload. Sooner or later (usually sooner), the download is done, and the client continues to upload pieces to other users.
What's In It For Me?
Now your first instinct at this point might be to close the program, but you really ought to leave it open as long as possible afterward, to help seed the file into the network. But this is really a social and cultural issue which can't necessarily be addressed through technical measures; BT can enforce fairness during the transfer with its algorithms, but no software can force the user to keep the client open. Many tracker owners keep a close eye on such things, and will generally ban repeat offenders. In any event, "giving back" your bandwidth has never been easier, even for users behind firewalls or NAT (although as always, being able to avoid or go through these will make the transfers more efficient).
Alternative Clients and Other Tools
That said, there are perfectly valid reasons to want some control over the amount of bandwidth a P2P application uses, and an experimental, unofficial client (Win32, Python source) has been created to provide a friendly interface for this. BT will automatically adjust your download speed appropriately if you set a slower upload speed, but it's still an invaluable tool for some cable and DSL users whose downloads will choke and abort if they use too much upstream, or for anyone with limited upstream who wants to reserve some of it for other uses.
Currently, both the official and experimental GUI clients use a separate window for each transfer. BT++ (Win32, Python source) has made an initial attempt at combining all transfers into one window, as well as offering some other enhancements, but users report mixed results, with some saying "it works for me" and others that it's buggy to the point of unusable; still, it's one to keep an eye on. (Caveat: BT++ provides an option to automatically stop uploading when the download is completed. I believe this deliberately encourages people to do so even if there is no real need to do so, and would advise anyone using BT++ to refrain from using this option; it's unnecessary, detrimental to the BT networks, and may lead to your IP being banned as described above.)
TorrentSpy (Win32) is another useful tool that shows various statistics about your transfers, including which files of a multi-file torrent are complete. It's not meant to replace a downloading client, but to complement it.
I should add that the speed and time-to-completion numbers may not be wholly accurate, and will typically fluctuate wildly to some extent during a transfer. (After all, do you believe Windows when it tells you how long it will take to copy a file?) The "percentage completed" at least is accurate, and you may be able to get more accurate information using TorrentSpy. A new version of BT has just been released (3.2) and its reported changes include "more even and consistent download rates".
A Few Miscellaneous Points
It's quite possible to generate .torrents for files you want to serve and then advertise them on someone else's tracker. Since anyone can run a tracker, BT is more like IRC, Usenet or Direct Connect than something like Kazaa. Like Freenet, it works best if the content is highly in demand; it's also more effective on recently released stuff. One highly recommeded website is Bstark. It doesn't provide .torrents for anyone to download, but functions as a "metatracker", that is, a tracker that keeps track of trackers. If you're a statistics geek, the graphs are a lot of fun, and even for the average user it's a simple way to check what files are most in demand and most in need of someone to serve them. This is even more effective when you combine it with an alternate means of communication such as IRC or email, making it easy for users to check supply and meet demand. The .torrent file can also be distributed by any means, be it a website, IRC channel, email attachments or perhaps carrier pigeon.
Conclusion
With the 'entertainment industry' finally focusing their attention on IRC, the cantankerous and difficult granddaddy of Internet file sharing, BitTorrent has found a niche and filled it admirably. The author understandably wishes to focus upon using BT in a legal manner. As with any new invention, "the street finds its own use for technology," and BitTorrent will undoubtedly continue to be rapidly adopted for both licit and illicit use.
Given the decentralized nature of BT networks and the rapid development of new tools, it's only a matter of time before someone writes a GUI wrapper for an IRC client, web browser and all-in-one BitTorrent interface. After all, Napster did it, as do most other mainstream P2P apps like Kazaa. Like Direct Connect with its 'hubs,' there will always be multiple BT servers available, and a unified interface would not only make it easier for users to find and download content, but free them to focus on forming the social and cultural networks that are also needed. A website typically uses far too much CPU and bandwidth to handle popular traffic, but a BT tracker uses minimal bandwidth by itself. Perhaps the next-generation clients will try to automatically locate trackers, or help the user find and serve older content as well as new releases.
The late great Audiogalaxy had many strengths, but one of its most fundamental was the sense of community it encouraged. BitTorrent wisely fills a narrow set of technical requirements, leaving a great deal to human need and will. The ad hoc arrangements and customs that have so far sprouted as expressions of the will to fill these needs are often chaotic and messy -- but that's human action for you.
The best way to help Open Source Companies (a la RedHat) survive is to circumvent their income strategies!
Tell RedHat to screw off! Circumvent the subscription policy with P2P!
Is that a bullethole in your foot?
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
Correct me if I've got the facts wrong. But it sounds to me like a week long wait is not really long, and that this announcement in Slashdot is not really ethical ...
This is a welcome to change to the usual copy/paste from the linked articles we usually get. This is so decent it's alomst as useful as the time that guy posted the step-by-step on Gentoo that was so good I went home and installed on the spare PC. Bravo!
Otherwise I'm glad to see the P2P community keeping pace (or should I say, one step ahead of) with the best in file serving. I'm not sure that RedHat would be pleased about it, but it was bound to happen that the ISOs would be released back to the community in record time regardless of paid subscriptions. In the end, I think they'll find it difficult to release anything without the inevitable leaks. This seems to hold true for Microsoft as well, as they contend with leak after leak of their beta and developer images. Information wants to be free!!
RedHat is a business. Business want to make money. The community support this. So therefore we get rid of their revenue streams by getting what will be free in a week now and stopping potential subscribers?
Rus
Cheap UK and US VPS
So ok. You can get it with Bit Torrent, you can get it off of the FTP if you are a member. But what the heck is it? All I've seen about Red Hat 9 is that it's out. What are the new features? Anything cool/not-cool. I just recently got 8.0 and was expecting the usual RH path of 8.1 and 8.2 before the next version. Anyone using 9 currently?
Comment removed based on user account deletion
I am a Red Hat subscriber and I am pushing a measly 14 kb/sec to download three 600+ MB ISOs. I'm on ISO #1 with 9 hours to go!
So what exactly is the advantage of getting the distro a week ahead of everyone else when the servers for "subscriber use" are so overloaded it will take me a week to download it!?!
On the one hand, BitTorrent is an excellent way of reducing bandwidth for Open Source companies... if they release their files only on bittorrent, then they can get the distro out to more people & save money on bandwidth at the same time. In that regard, I think all Linux distro companies should adopt it.
On the other hand, this is a massive leak for RedHat... if BitTorrent can always be relied upon to get the ISOs the day they're released to subscribers, then there is no incentive to become a RedHat subscriber... and thus RedHat loses money.
In the future, it would be nice if BitTorrent users could wait until after the distro is released to the public before mirroring it... Yeah, then companies like RedHat still get their 1 week advance for subscribers, AND they get to not have their servers flooded on public release day.
*sigh*... I better go buy a RH9 boxed set, I feel all dirty now.
I personally ponied up my 60 bucks, but then again I also go out and buy boxed copies.
I already pony up the 60 per year anyway, have for two years. Its a good service they provide, well worth the money.
As to them making money, once again what I see is giving a little more to those of us that give a little more to them. I didn't like the way they marketed it, but the fact is they give alot more bandwidth to people who have NEVER given them a dime than anyone else. The GPL requires you make the source available. They COULD put all their files on a 64k throttle except for subscribers, and meet the requirements of the GPL. But they don't.
I personally hope they do make some money, get back in the black, and gain some market share. Linux is never going to become mainstream without companies like Redhat who have somewhat viable business plans. I WANT them to be here 10 years from now, because I like their products.
Reminds of the gag: How do you make a profit by giving stuff away?
VOLUME!
Tequila: It's not just for breakfast anymore!
And anyhow, RH 9 actually does include something much more than "a little gloss" - NPTL (warning - link is to a pdf)
Now if you've ever tried to debug a core file of a multi-threaded app, or dealt with signal propagation with the old... aw, shucks never mind, but take my word for it, NPTL - woot woot
Oh, woot woot BT too by the looks of things...
Redhat was giving me 8.7kB/s down before I found this article.
Revolutions are never about freedom or justice. They're about who's going to be top dog. -- Kilgore Trout
Okay, as a user that never runs a gui on the machine, only ever goes in via ssh over the local intranet, and has a cluster of servers all behind a hardware firewall that blocks all incoming attempts...
What is different about RedHat 9.0 that is applicable to me?
I'm just curious if I should bother with upgrading or not - I would guess no since I can just download any one particular thing that I want/need.
The one thing that I can think of justifying it would be that I'd like a working lm_sensors. The existing lm_sensors that it came with for me didn't have anything for my motherboard (epox 8kmm+). I'll admit it - I tried installing lm_sensors on my own and couldn't do it successfully (so much for "following the instructions").
So were there some way that was RetardEasy to get that in... ie "upgrading" - then I'd go for it.
Otherwise, it is just another big number jump in a short period of time that I'm not sure has any real bearing on me - yet leaves me curiously watching all those about me rush to get it.. wondering... why?
There are some odd things afoot now, in the Villa Straylight.
Until recently (and possibly even now), BitTorrent had a problem that often caused the completion meter to climb above 100%. (This occurred when corrupt data was received and had to be redownloaded.) As a result, many people terminated the transfer before BitTorrent had reported, "Succeeded!" Hence, corrupt files.
.torrent file was created by someone with a legitimate copy, the result should be just as good. Since BitTorrent is really meant to be used directly by file distributors, this shouldn't pose a problem in the future.
On the other hand, the torrent initiator may have had a corrupt image to work with. It can happen.
In any case, BitTorrent uses the SHA1 secure hash algorithm, which is comparable to MD5, to verify downloads. So long as the
i've always thought this was a good comporomise between letting the dedicated and the geeky get what they are entitled to (the source to play with) while encouraging the moms and pops to chip into the corporate kitty. note that the price of openbsd producst is low
Also note that the number of systems running it are low, too, even tho it is an exceptional OS. I have no prob with them distributing it this way, but it IS part of the reason I don't use openBSD, even tho I KNOW its better for some tasks (pure web servers, for instance).
I cut my teeth on Redhat (4.2) because I could get it free, and then when I needed service, I didn't mind paying for it. Like all distros, it has weaknesses and strengths. Its not that RH is better, its that they made it easy for me to get used to it, and eventually, prefer it. Oh, and I have messed with mandrake, solaris, lindows (really), and slackware (ug).
While there is nothing WRONG with distributing an OS like this, it is not conducive to winning over the largest possible customer base, which is what Redhat is trying to do. Keep in mind, BSD is a very different animal anyway. BSD advocates tend to be more "purist" while Redhat tends to be more capital driven. Takes all kinds.
Tequila: It's not just for breakfast anymore!
They are not selling what they do not own, they are in business of selling ease of installation and configuration for those things, as well as support.
Check out the list of packages included with Red Hat Linux 9. You'll find exactly zero non-free software.
Only because you brought the subject up:
"pine 4.44 A commonly used, MIME compliant mail and news reader." This code is source-available, but licensed under proprietary terms (no right to fork).
In pointing out this inclusion of the proprietary pine/pico/pilot package, I intend no criticism of Red Hat Software, Inc., which does it for perfectly understandable reason, given the pine MUA's wide appeal and lack of an open-source replacement acceptable to that customer base that doesn't suffer the same copyright encumbrance (as MANA does). Chris Allegretta's "nano" has nicely eliminated the pico problem, but ditching pine itself without seriously ticking off a fair number of people remains difficult.
When I saw that Red Hat had (by the 8.0 release) reduced the number of proprietary packages to just this one -- having pushed the envelope in jettisoning the old proprietary Java packages, ditched Navigator/Communicator in favour of Mozilla and Acrobat Reader in favour of xpdf, and actually helped write a replacement for xv -- I was (and remain) quite impressed. They've shown impressive leadership, in this area.
But it remains a (small) factual error to claim that the distribution is 100% free / open-source software.
Rick Moen
rick@linuxmafia.com
Or, failing that, mount the CDs using loopback, and then check the signature. Something like this:
mount -o loop shrike-i386-disc3.iso /mnt/cdrom /mnt/cdrom/RedHat/RPMS/*.rpm
rpm --checksig
You'll need to have downloaded the RedHat public key, which you can get from "pub/redhat/linux/8.0/en/os/i386/RPM-GPG-KEY" of your favourite RedHat mirror, and then import with a command like:
rpm --import RPM-GPG-KEY