Posted by
CmdrTaco
on from the stress-those-pipes dept.
mkool writes "Exactly on schedule.
Fedora Core 2 is now officially available from Red Hat and at distinguished mirror sites near you, and is also available in the torrent."
Leaked .torrent Matches
by
Kalak
·
· Score: 5, Informative
The md5 sums match the "leaked" torrent, so if you have that, there is no need to re-download even to join the official torrent by getting the.torrent and renaming your directory appropriately.
-- I am, and always will be, an idiot.
Karma: Coma (mostly effected by.hack)
Fedora Core 2 is FAST!
by
nsandver-work
·
· Score: 5, Informative
I downloaded Fedora Core 2 using the.torrent that was posted yesterday, and it's fast. Very fast. The combination of the 2.6 kernel, and updated GNOME flies on my P-III 600 compared to FC1. Menus appear in probably half the time they did before, as do Nautilus windows. Download and enjoy! And 'thank you' to the crew who work on Fedora!
Re:Fedora Core 2 is FAST!
by
Jon+Pryor
·
· Score: 5, Informative
Nautilus isn't faster because it's spatial. It's faster because it uses file extensions for MIME-type checking instead of file sniffing. This greatly increases performance, as the disk doesn't need to be accessed for every file in a directory. This is particularly noticable if your directory has thousands of files...
File sniffing is still used in two circumstances:
When the file lacks an extension, such as README or configure.
When the user opens the file. The sniffed MIME-type is compared to the file extension, and if there's a mismatch, Nautilus complains loudly. This is to help prevent trojans, such as a shell script named README.txt, which would imply being a text/plain MIME type but are actually application/x-shellscript.
Bug When Dual Booting Windows XP and Fedora Core 2
by
cbowland
·
· Score: 5, Informative
Be sure to watch out for this one. It has already caught some folks here unaware.
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?i d=115980
--
Give a man a fish and he will eat for a day.
Teach him to eat and he will fish forever.
Two things worth noting....
by
HunterWare
·
· Score: 5, Informative
a) Per bugzilla bugs 113202 and 115980 people are getting corrupted partition tables after installing FC2 (and the previous test versions). This is a known bug, but the release shipped anyhow... (wierd)
b) NVidia drivers don't work with this release do to a kernel patch (the "4K Stack" patch). Seems to be an even split on who should fix this, but the end result is no nvidia drivers for people using this release (at the moment).
Re:shameless karma whoring
by
GundyRage
·
· Score: 5, Informative
While the web page doesn't show it (http://torrent.dulug.duke.edu/), the torrent is ready. Now jump on so I can get faster downloads;) http://torrent.dulug.duke.edu/tettnang-binary-i386 -iso.torrent
Newbs read below...
Just cd to the directory that you want the download to start in. Make sure you have at least 2.2 Gigs free on that partition, and run the command below. It will be slowish at first but it will pick up with time. The --max_upload_rate is the maximum kB/s you will upload to others. Use it if your connection is bit sensitive. If you couldn't care less, leave it off and help the rest of the world out.
Get bittorrent here: http://bitconjurer.org/BitTorrent/download. html Or for RH / Fedora users: http://torrent.dulug.duke.edu/btrpms/
Command for FC2 bittorrent: [user@system dir]$btdownloadcurses.py --url http://torrent.dulug.duke.edu/tettnang-binary-i386 -iso.torrent
That might save the newbie a google or two.
P.S. The above was just cut from an email I sent to a local LUG.
G
nVidia driver HOWTO
by
DennisZeMenace
·
· Score: 5, Informative
There are many forums out there that will explain in great details. For example, see here.
The fast version: the Nvidia driver will NOT work with FC2's kernel because of the 4KSTACKS problem. Unfortunately, FC2's kernel no longer has the config option to disable this new "feature", so you will need to:
- recompile a new kernel (i.e. a stock kernel). For example, 2.6.5-bk2, or 2.6.6-bk4
- make sure to use Fedora's own config files (from/usr/src/linux-2.6.5-1.358/configs), and turn off the options CONFIG_4KSTACKS and CONFIG_REGPARM
Fedora inlcudes support for apt and yum. I use yum and I love it. Handles all your dependencies for you. Give it a try. It will make you happy.
Re:getting around the IP blocks
by
pyros
·
· Score: 5, Informative
I know there is are several commonly used tools that are ommited from fedora to avoid the IP issues. playing DVDs, Samba and a couple of others. Does anyone have a link to howto on what needs to be installed after the install to make it a regular useful distro?
Samba is included, as is the new CIFs driver which replaces smbfs. What isn't included is the NTFS read-only driver module, which you can download as a binary RPM from linux-ntfs. As for the other stuff, I like to use the fedora.us + livna.org* repositories. There is also freshrpms, ATrpms, Dag Wieers, and Planet CCRMA. There are others, and be warned that Dag Wieers and Axel Thim (atrpms) are in a pissing match over Dag obsoleting at least one of Axel's packages for naming it "wrong". (look at the April acrhives of the freshrpms mailing list with some fresh popcorn).
* - The livna.org front page still says they are down and lists the mirror. The rpm.livna.org repo is actually back up, they just never bothered to update the main page to say so.
Re:Bug When Dual Booting Windows XP and Fedora Cor
by
Anonymous Coward
·
· Score: 5, Informative
You can joke all you want about not caring about windows booting, but the bug is potentially more serious than just not booting windows. It is very likely that bug is the same as this one: Bug 113201
Basically, you can get a screwed up partition table. It appears this is due to changes in the way that the 2.4 and 2.6 kernel reported hard disk geometry. These changes were not account for yet (to my knowledge) in parted, which is used in the FC2 install. This results in inconsistent (between FC2 and other OS'es, perhaps more than just windows) entries in your partition table.
I don't know how likely it is that this will cause a problem on any given machine. Perhaps for smaller disks the way the 2.4 vs 2.6 kernels report geometry will be the same, and there will be no problem. You might want to try to boot into a 2.6 kernel based live CD and compare values to what you see in a 2.4 kernel before installing FC2. For more information on this, see this thread:
This is a very serious problem, which sadly appears to have been known about for some time, and no warnings have appeared in any release notes (much less delaying releases to fix it). You can note the distress of some reporters in the bugzilla comments. I am distressed that the problem has gone unfixed this far, and more distressed about the very little attention it has gotten. I am not going to install FC2 until this is dealt with.
Re:So... Not so sure
by
ahaning
·
· Score: 5, Informative
As someone else mentioned, you'll need to forward at least ports 6881 to 6889 (or 6999 if you feel the need) from your router to your PC. Each window you open needs its own port.
You may also need to figure out how to get through your firewall, if you have one.
Regarding your question: BitTorrent does work through routers even if your ports are "closed", but in order for you to download anything, someone else's ports must be open. You are uploading at such a high rate because someone else has their ports open.
If everyone's ports are closed, no one will be able to connect to each other and nothing will happen. If the seeder's ports are open and all of the leecher's ports are closed, the leechers will not share with each other and you'll be back to having a very slow FTP site (basically).
If you open your ports, you will see drastically higher speeds. You may also want to limit your uploads a bit since you need some upload bandwidth to be able to download. Your PC needs to be able to tell the other peers that it got the pieces that they sent.
HTH.
-- Withdrawal before climax is very ineffective and those who try this are usually called "parents."
Re:very useful
by
Anonymous Coward
·
· Score: 5, Informative
A hash collision in MD5 has, to the best of my knowledge, been found.
It represented a considerable amount of work - even if the 128-bit hash was perfect, the workfactor would have been 2^64, and collisions in the compression function were found to affect the balance, thus slightly weighting the probabilities and allowing for a search on the order of 2^58; still a considerable amount of work and it took a couple of years.
I'd link the PDF, but it's gone walkabout; you should be able to find the precursors without too much trouble though.
Of course, that's just a birthday attack (find a pair of files, neither given, any length, with same md5sum), and it's just one time. You'd have to do it all over again to find another pair.
The attack presented here (given md5sum, find or pad file to match) is not currently feasible. That's workfactor 2^128 and it doesn't look like the compression function weaknesses can really help (much) - the work would be over 2^100, quite impossible today.
MD4 is weaker (as it exposes the compression function problems). SHA-1 is stronger (not least because it is a 160-bit hash, giving 2^80 birthday). RIPEMD-160 is also pretty good, as is TIGER192, and you can't discount the new breed of SHA-256, SHA-384 and SHA-512.
Slashdot Mirror
Fedora Core 2 Discussion, I've found that site to be very helpful.
The md5 sums match the "leaked" torrent, so if you have that, there is no need to re-download even to join the official torrent by getting the .torrent and renaming your directory appropriately.
I am, and always will be, an idiot. Karma: Coma (mostly effected by
I downloaded Fedora Core 2 using the .torrent that was posted yesterday, and it's fast. Very fast. The combination of the 2.6 kernel, and updated GNOME flies on my P-III 600 compared to FC1. Menus appear in probably half the time they did before, as do Nautilus windows. Download and enjoy! And 'thank you' to the crew who work on Fedora!
Look here at Wikipedia
Be sure to watch out for this one. It has already caught some folks here unaware. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?i d=115980
Give a man a fish and he will eat for a day.
Teach him to eat and he will fish forever.
a) Per bugzilla bugs 113202 and 115980 people are getting corrupted partition tables after installing FC2 (and the previous test versions). This is a known bug, but the release shipped anyhow... (wierd)
b) NVidia drivers don't work with this release do to a kernel patch (the "4K Stack" patch). Seems to be an even split on who should fix this, but the end result is no nvidia drivers for people using this release (at the moment).
See this link for details.
While the web page doesn't show it (http://torrent.dulug.duke.edu/), the torrent is ready. Now jump on so I can get faster downloads ;) http://torrent.dulug.duke.edu/tettnang-binary-i386 -iso.torrent
. html
6 -iso.torrent
Newbs read below...
Just cd to the directory that you want the download to start in. Make sure you have at least 2.2 Gigs free on that partition, and run the command below. It will be slowish at first but it will pick up with time. The --max_upload_rate is the maximum kB/s you will upload to others. Use it if your connection is bit sensitive. If you couldn't care less, leave it off and help the rest of the world out.
Get bittorrent here:
http://bitconjurer.org/BitTorrent/download
Or for RH / Fedora users:
http://torrent.dulug.duke.edu/btrpms/
Command for FC2 bittorrent:
[user@system dir]$btdownloadcurses.py --url http://torrent.dulug.duke.edu/tettnang-binary-i38
That might save the newbie a google or two.
P.S. The above was just cut from an email I sent to a local LUG.
G
There are many forums out there that will explain in great details. For example, see here.
:
/usr/src/linux-2.6.5-1.358/configs), and turn off the options CONFIG_4KSTACKS and CONFIG_REGPARM
The fast version: the Nvidia driver will NOT work with FC2's kernel because of the 4KSTACKS problem. Unfortunately, FC2's kernel no longer has the config option to disable this new "feature", so you will need to
- recompile a new kernel (i.e. a stock kernel). For example, 2.6.5-bk2, or 2.6.6-bk4
- make sure to use Fedora's own config files (from
-DZM
Fedora inlcudes support for apt and yum. I use yum and I love it. Handles all your dependencies for you. Give it a try. It will make you happy.
Samba is included, as is the new CIFs driver which replaces smbfs. What isn't included is the NTFS read-only driver module, which you can download as a binary RPM from linux-ntfs. As for the other stuff, I like to use the fedora.us + livna.org* repositories. There is also freshrpms, ATrpms, Dag Wieers, and Planet CCRMA. There are others, and be warned that Dag Wieers and Axel Thim (atrpms) are in a pissing match over Dag obsoleting at least one of Axel's packages for naming it "wrong". (look at the April acrhives of the freshrpms mailing list with some fresh popcorn).
* - The livna.org front page still says they are down and lists the mirror. The rpm.livna.org repo is actually back up, they just never bothered to update the main page to say so.
You can joke all you want about not caring about windows booting, but the bug is potentially more serious than just not booting windows. It is very likely that bug is the same as this one:
Bug 113201
Basically, you can get a screwed up partition table. It appears this is due to changes in the way that the 2.4 and 2.6 kernel reported hard disk geometry. These changes were not account for yet (to my knowledge) in parted, which is used in the FC2 install. This results in inconsistent (between FC2 and other OS'es, perhaps more than just windows) entries in your partition table.
I don't know how likely it is that this will cause a problem on any given machine. Perhaps for smaller disks the way the 2.4 vs 2.6 kernels report geometry will be the same, and there will be no problem. You might want to try to boot into a 2.6 kernel based live CD and compare values to what you see in a 2.4 kernel before installing FC2. For more information on this, see this thread:
This is a very serious problem, which sadly appears to have been known about for some time, and no warnings have appeared in any release notes (much less delaying releases to fix it). You can note the distress of some reporters in the bugzilla comments. I am distressed that the problem has gone unfixed this far, and more distressed about the very little attention it has gotten. I am not going to install FC2 until this is dealt with.
As someone else mentioned, you'll need to forward at least ports 6881 to 6889 (or 6999 if you feel the need) from your router to your PC. Each window you open needs its own port.
You may also need to figure out how to get through your firewall, if you have one.
This site might prove helpful, if it is up.
Regarding your question: BitTorrent does work through routers even if your ports are "closed", but in order for you to download anything, someone else's ports must be open. You are uploading at such a high rate because someone else has their ports open.
If everyone's ports are closed, no one will be able to connect to each other and nothing will happen. If the seeder's ports are open and all of the leecher's ports are closed, the leechers will not share with each other and you'll be back to having a very slow FTP site (basically).
If you open your ports, you will see drastically higher speeds. You may also want to limit your uploads a bit since you need some upload bandwidth to be able to download. Your PC needs to be able to tell the other peers that it got the pieces that they sent.
HTH.
Withdrawal before climax is very ineffective and those who try this are usually called "parents."
A hash collision in MD5 has, to the best of my knowledge, been found.
It represented a considerable amount of work - even if the 128-bit hash was perfect, the workfactor would have been 2^64, and collisions in the compression function were found to affect the balance, thus slightly weighting the probabilities and allowing for a search on the order of 2^58; still a considerable amount of work and it took a couple of years.
I'd link the PDF, but it's gone walkabout; you should be able to find the precursors without too much trouble though.
Of course, that's just a birthday attack (find a pair of files, neither given, any length, with same md5sum), and it's just one time. You'd have to do it all over again to find another pair.
The attack presented here (given md5sum, find or pad file to match) is not currently feasible. That's workfactor 2^128 and it doesn't look like the compression function weaknesses can really help (much) - the work would be over 2^100, quite impossible today.
MD4 is weaker (as it exposes the compression function problems). SHA-1 is stronger (not least because it is a 160-bit hash, giving 2^80 birthday). RIPEMD-160 is also pretty good, as is TIGER192, and you can't discount the new breed of SHA-256, SHA-384 and SHA-512.