thundersnows:

Nope!... Don't download all CDs! You only need the 2 install CDs... The 2 source CDs are for geeks who likes to modify their distro...

And if you use KDE and/or Gnome, you NEED the install disc2...

Yes I agree, Monday night, just after it was released, I got both CD 1 & 2, the speed typically was over 100 kb/sec and seemed to peak around 165 kb/sec. I think this is a great idea because it used to take me over a month to get it previously, it was faster to just order it and wait.

Someone needs to do a little BitTorrent how-to. I took me awhile to figure it out. Better yet, a network install boot floppy complete with a script to run CD-Record would be ideal. I ended up "Apt-get"ing it using my Debian-Unstable computer. Seemed like a "cart-before-the-horse" problem.

omg I have sound after 9.1 install.

first time i've ever had sound since slack 8

woohoo

instalation was good.
my AC97 soundcard was configure automatically so was the Broadcomm NIC. no problems booting. now gonna try to make kernel 2.6 work

Slack 9.1 is now officially an alsa distro... Oh, bye bye oss, you served us well. I would check /etc/hotpluging/blacklist to see if hotplugging has all of the oss modules blacklisted, of course after checking to see if you can just modprobe the right module home.

Cheers,

Finegan

The total speed of over 700 kB/s I gave in previous post is the total bandwidth of all peers n seeds participated on Bittorrent I bet, it is not the bandwidth of one particular participant ..

My peak rate is about 17kB/s only, but it is more stabile at 12/13 kB/s rather than downloading from mirrors, because the seed is fixed in that case.

I just curious about how those ISPs limit the bandwidth of users sharing the same segment of cable .. Is that through packages prioritising for more $ ?

Wut happened with those packages on the way to an user just getting priority limited ? Do they just go to ground//dev/null of the ISP networkserver, n then the waiting user have to reguest them again even the bandwidth isn't full used at night ?

Must be genial Idea, but wut do those suxy ISPs not do ?

Possibly to decrease the time of DHCP lease to some hours ..

It's all done in the customers cable modem and is programmed from the ISP (CCTV cable-side) on demand. It's all part of the "DOC-SIS" standard. I guess there were a few out there that could be programmed from the customer's ethernet side, I don't know if any of these are still functional.

After you posted this I just check and sure enough, so did I . I had forgot that ALSA defaults the volumes on everything all the way down. I hate that. Otherwise ALSA has always worked great for me once I took the time to get it set up. I guess no more editing rc.modules.

Anyway, just getting the kinks out of my brand new Slack 9.1 install. To the person that commented about how nice Slack 8.1 was, I agree, Slack 8.1 always just worked out-of-the-box on just about every hardware I threw at it. Today, for some reason XF86 couldn't get DPMS info from my monitor, so it gave me crappy 640x480, I ended up sticking in a modeline to get my high res. Of course I had to do the ZAxisMapping entry to get my mouse wheel working too.

KDE is working great, but Gnome has problems, Nautilis won't come up and several other Gnome Apps won't run. It's like a library is missing or something. I'll have to track this one down because it will be nice to have Galeon back after it's absence from Slack 9.0. I still like it a little better than Mozilla-Firebird, but the race is getting close. Who was having font problems in KDE? They seem to be working fine for me, however I just checked and I don't seem to have xfs running so maybe I do have a problem.

I'm not sure I like the new XFCE. I used to like it because it was simple and fast (like fluxbox). The new File-&-App manager acts like a bloated pig. I liked the old xftree much better . It's nice to have fluxbox included in the main distribution however.

Otherwise, things are going okay. I did have XF86 crash on me a few time while playing around with xvidtune. I suspect the i740 video driver is not perfectly stable, but then this whole computer is pretty messed up, I wonder if the scsi.s kernel has all the VIA Apollo bug fixes enabled? I'll compile my own kernel eventually.

I maybe stoned to death for saying this but, isn't all Slackware user geeks?

Cheers!!!

Long live Slackware!!!!!

Alright, I am no authorative person to answer this, but I just want to share with you what I did. If you have a spare partition. As in you used it for /home or /nouse. What you can do is, you can move all the current data inside that spare partition into a folder within that partition itself, name it something like homebackup.

After that copy whatever files in /var to your /home(your spare partition). do this cp -rf * /home from /var

after that edit the fstab to make current /home(spare partition) to be mounted as /var.

I did it before and no probs at all.

oh the other hand... can' you make swaret dump into a partition which is big enough?

I bought my motorola sb4200i modem self, so it is not from the Cable-Site. It must be done by them remotely through the cable. The cable-site has surely interest to limits that, for marketing the rest bandwidth of the cable ..

But how those ISPs limit the bandwidth of say a leased line or adsl user ? If it is also through device limitation programed like above then I still interested on how to do that per software ?


Yes slackware is really cool like democracy ..
Really enjoy it .., must install it more often like never get enough

Yes, that's right. It's when you report to them the MAC address of the thing. They then send periodic updates & re-autthorizations. I know, my ISP keys it's data base from the unit's serial number instead the the obvious MAC address, which in my case was too long for their database. Every 3 months my modem would quit working because I wouldn't get the update. Some smart person at the ISP finally figured it out. Unfortunatley at no time was my modem allowed to run wide open, which I understand was often the case when that now defunct @home company ran ISP for Comcast.

When I had adsl, it was a PPP connection from somewhere so they could limit it from there. I don't know if this is how it was done however. Leased line is dedicated as well, so they can limit things from their end too.

When I'm downloading the 2nd CD, I saw most IPs have such a limited download rate (some under 10 or even 5 kbs), but any did have such download rate of over 70kB/s, one of them even have over 1000kB/s as it just started to download from 0%. I traced that IP with nslookup, n it has the domain ends with comcast something (if am not false remembered), the other IP I with such high download rate I traced has domain something with springmind so .. They r the caused for the total bandwidth peaks of something over 700kB/s ..

Yeah, adsl, lease line have p2p connection to ISP, but they r able also to limit the bandwidth something like (64,128,256..) kB/s depend on the customer payablity .. Actually the bandwidth of the p2p connection of ADSL/leased -lines are far higher than that.

Am just curious about wut software do they used (there must be some of such there on the kernel tree, or on the sourceforge site ..), maybe wonna try to apply that for LAN for probing-wise ..

I think Comcast has their own infrastructure that includes caching servers. I know because they got in trouble a year or so ago because they were storing internet data on a per user basis which was thought to be an invasion of privacy. So maybe you are seeing these high peaks when Comcast can deliver a series of IP packets that are stored in their caches instead of being delivered from their customer's machines.