Is that so? My school has a whole library of brand new PIII's. Every day there are at least two "out of order," and the ones that do work are used for what? Games and shockwave.com. Gee, such wonderful use of brand new technology!
My old school had older machines in the library and people used them only for useful things, such as typing and basic web browsing because they didn't have the new toys of the fast machines.
To tell you the truth, the old machines were faster.
THROW OUT A PII? What is wrong with you? My main machine up until a few months ago was a P166, and it did everything I needed. I only got a new machine because my mom needed one (she now uses the 166 every day.. works fine for her!) and I got a k6 550. Oh, but I guess I should throw that away, right? It couldn't possibly be of any use!
I had a server running on a p120 until a few weeks ago when I got a k6 300 for it. I guess I should throw not only the old board away but the new one as well! Never mind the fact that it is in use and is working perfectly for the server (apache,web,irc and some other things, all on a T1).
Maybe I should throw away the 486's at my house that allow me to use the web, telnet/ssh, email, and everything else. They couldn't be of any use, of course.
And most of all, I should trash the 486/25 that routes my DSL connection! It couldn't POSSIBLY be of any use! Neither could that 386/16 I use to learn to program assembly. Nope, no use whatsoever.
Not all of us can afford brand new machines every month.
Let's let the ping times speak on this one.
I realize that throughput often comes above latency when considering bandwidth options, but when the routing is this shitty, one has to wonder where all the bandwidth goes.
From gwyn.tux.org to my home host, 144k IDSL.
--- xxxxxxx.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 39.806/40.738/41.747/0.690 ms
From gwyn.tux.org to my friend's RR box, about 5 miles from my house.
--- xxx.dynip.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 343.826/483.237/680.057/113.163 ms
Yes, cable rocks!
I'm a Northpoint customer, so I could be shut off as early as mid March. That's after being hooked up only since early January.
The new versions can be annoying to compile in NetBSD (which currently seems to have less-than-perfect pthreads support), and they're slow on my p60. Someone with some time and some coding experience should convert the 0.9.10 release to support whatever they did to make the new releases login.
Several friends have experienced similar problems. The server machines all vary in speed, but I don't think encryption time matters in this case. SSH1 sessions have always been smoother and less laggy for me (I use CompressionLevel 9) than SSH2, even with compression enabled.
I don't experience the halting problem too often, it's more of a matter of speed and compatibility that make me hate ssh2. There aren't any new features that are of any use to the average person (except maybe sftp), so I see no reason to upgrade.
For those of us who still have to suffer with modems, SSH version 2 is absolute crap. Sessions are extremely slow, and often halt for no reason. When both sides are on modems, results are even worse. It is absolutely impossible to do anything that requires frequent keypresses (try editing a file, its horrible) because of the extreme latency.
SSHv1 and the old OpenSSH have none of these problems. SSHD2 with fallback to SSHD1 still has all these problems, even though it is using the SSH1 client.
I always loved the fact that SSHv2 had bad licensing, so most people didn't use it. Now with this, more intelligent people will be using version 2 daemons, which means the rest of us who aren't lucky enough to have fast connections will suffer.
Slashdot Mirror
Is that so? My school has a whole library of brand new PIII's. Every day there are at least two "out of order," and the ones that do work are used for what? Games and shockwave.com. Gee, such wonderful use of brand new technology!
My old school had older machines in the library and people used them only for useful things, such as typing and basic web browsing because they didn't have the new toys of the fast machines.
To tell you the truth, the old machines were faster.
THROW OUT A PII? What is wrong with you? My main machine up until a few months ago was a P166, and it did everything I needed. I only got a new machine because my mom needed one (she now uses the 166 every day.. works fine for her!) and I got a k6 550. Oh, but I guess I should throw that away, right? It couldn't possibly be of any use!
I had a server running on a p120 until a few weeks ago when I got a k6 300 for it. I guess I should throw not only the old board away but the new one as well! Never mind the fact that it is in use and is working perfectly for the server (apache,web,irc and some other things, all on a T1).
Maybe I should throw away the 486's at my house that allow me to use the web, telnet/ssh, email, and everything else. They couldn't be of any use, of course.
And most of all, I should trash the 486/25 that routes my DSL connection! It couldn't POSSIBLY be of any use! Neither could that 386/16 I use to learn to program assembly. Nope, no use whatsoever.
Not all of us can afford brand new machines every month.
Let's let the ping times speak on this one.
I realize that throughput often comes above latency when considering bandwidth options, but when the routing is this shitty, one has to wonder where all the bandwidth goes.
From gwyn.tux.org to my home host, 144k IDSL.
--- xxxxxxx.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 39.806/40.738/41.747/0.690 ms
From gwyn.tux.org to my friend's RR box, about 5 miles from my house.
--- xxx.dynip.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 343.826/483.237/680.057/113.163 ms
Yes, cable rocks!
I'm a Northpoint customer, so I could be shut off as early as mid March. That's after being hooked up only since early January.
The new versions can be annoying to compile in NetBSD (which currently seems to have less-than-perfect pthreads support), and they're slow on my p60. Someone with some time and some coding experience should convert the 0.9.10 release to support whatever they did to make the new releases login.
Several friends have experienced similar problems. The server machines all vary in speed, but I don't think encryption time matters in this case. SSH1 sessions have always been smoother and less laggy for me (I use CompressionLevel 9) than SSH2, even with compression enabled.
I don't experience the halting problem too often, it's more of a matter of speed and compatibility that make me hate ssh2. There aren't any new features that are of any use to the average person (except maybe sftp), so I see no reason to upgrade.
For those of us who still have to suffer with modems, SSH version 2 is absolute crap. Sessions are extremely slow, and often halt for no reason. When both sides are on modems, results are even worse. It is absolutely impossible to do anything that requires frequent keypresses (try editing a file, its horrible) because of the extreme latency.
SSHv1 and the old OpenSSH have none of these problems. SSHD2 with fallback to SSHD1 still has all these problems, even though it is using the SSH1 client.
I always loved the fact that SSHv2 had bad licensing, so most people didn't use it. Now with this, more intelligent people will be using version 2 daemons, which means the rest of us who aren't lucky enough to have fast connections will suffer.