-----------
I think my router is probably as much the culprit
as anything, but someone knowledgable would
have to help me at this point.

I read the BitTorrent file I mentioned above,
and if it requires a web server like is says,
then I'm out of luck. Don't have one running,
and don't intend to, either.
-------------------

i'm also behind an adsl-modem/router and it normally works ok.
also. you don't need to run a server to use torrent.

when you start a torrent, your machine connects to a tracker, that gives info
about other machines on the net that are currently downloading the same file ( peers ) and those
that already have the complete file but are still connected ( seeds )

then your machine will try to get parts of the file from the seeds/peers

so, as i'm running these torrents for over an hour now, and i still see 0 seeds/peers
i'm loosing hope....

also checked a lot of mirrors, ( they have a Slack10.1 directory, and md5/asc files)
but not the iso's.
not even on the official Slack-ftp-site.

i guess it's just all starting-up and will need some more time.

egag

egag,

since this is my first experience with BitTorrent
I don't know if I'm doing it right or not. But it's
getting up to 30 KB/s down every now and then,
so I guess that's improving. Interesting that the
d2-iso has 18.9MB down and 45.6 up, so I guess
I'm doing somebody else some good there.

If anything gets back out past the Great Chinese
Firewall it's rather amazing in the first place.

When my d/ls finish, what do I do to keep
seeding this for others? Do I just leave those
2 btdownloadcurses.py windows open?

-------------
When my d/ls finish, what do I do to keep
seeding this for others? Do I just leave those
2 btdownloadcurses.py windows open?
-------------

yep, you become a seeder then, to serve others. ( that's good for the network )
it's good use to give back as many bytes ( +/- ) as you got.

and when loading through torrent, it's normal that the speed goes up while downloading.

good luck,

egag

ftp://slackware.mirrors.tds.net/pub/slackware/

they have the 4th iso

yeah...thanks.
( btw....that one is only 278 MB ? )

but i already found a mirror with all the iso's in the Netherlands, so i'm using that now.

egag

Quick question. I already have KDE-3.3.2, GTK-2.6.1, Xorg 6.8.1, Gimp 2.2.3 and am using a custom 2.6.7 kernel. I also use XFce 4.2.0 as my desktop environment anyway. So would there be much benifit in me upgrading to slackware 10.1 or should I just wait for 11.0.?

I normally get very fast Bittorrent downloads, but today, I'm getting almost nothing. I did find a mirror that's working fairly well. I'll seed the first two iso's once they're downloaded.

Hopefully, that'll help, but I'm curious why Bittorrent is working so slowly. Are there really no people using it to get Slack iso's? That's kind of disturbing.

hoi Phathead

i also tried torrent, but i'm loading from a mirror now.
but if i want to seed them as torrent, is there a way to connect to the
existing tracker, instead of putting out a new torrent,
that only has one seeder to start ( me ).

if it's possible can you tell me how ?

egag

I've never done it before, but what I plan to do is copy the iso I'm downloading over the iso file Bittorrent created. (I tried Bittorrent for a few minutes, so I have pieces of the files) Then, I'll start up the torrent again. As long as the iso is a bit-perfect match, bittorrent won't care where it came from. Bittorrent will check the files and start offering the iso for upload.

Like I said, I've never tried it, but in theory, I think it will work. I'll let you know in about 20 minutes once I've tried it.

ah, good idea
they should be the same files eh.....

i'll try that also.

egag

What happens if you start a d/l before the file is complete?
Will it only load that amount, or load the whole file (since it
will obviously finish loading into the ftp server before it is
d/led to my local machine -- btw, that one you mentioned
never grew any larger in gftp menu -- d4 -- but on another
server it did :/

This is great news!!!!

I can't wait for my subscription disks to arrive.

I got a quick question for those who stay ontop of these matters:

Whats the difference between /current yesterday and /10.1 today?
Since in the change log, there hasn't been any changes since
Wed Feb 2 17:46:02 PST 2005 - shouldn't they be the same?
http://slackware.com/changelog/i386/...Log-stable.txt
Just trying to clarify.
thanks in advance
-tw

It looks like the last change was on Feb. 2nd (according to the changelog) You should have the most current version if you updated using slackware-current since then.

However, I changed my swaret config from current to 10.1 and swaret found three new packages to upgrade. Not sure why, maybe I hadn't upgraded since Wednesday.

-current and 10.1 are now the same.

As I rsync -current to a local directory, I have made a copy of that directory and re-named it slackware-10.1. The reason for this is that PV has mentioned that -current, as it makes it's way toward 11.0, will have major structural changes that might be incompatable with the setup of 10.1 and lead to a greater ammount of instability at times than we may be used to from -current. The changes required for making 2.6.xx the default kernel is but a small example. This way I will just continue rsync -current with the knowledge that I have a stable tree to use in case things get borked.

Depending on what server you use to rsync, you may also find that the -current directory becomes empty for a short period. If you are unlucky enought to perform an automated rsync during this period you can end up with an empty directory.

Has not happened to me, but I've seen people complain about such an event.