The current system facillitates this as well -- I run 2.6.anything.somthinghigh on my servers and 2.6.anything at home and it works quite well. The -stable team are really providing an excellent service with their work beyond the 3rd dot, and they let the main line kernel move at a quicker pace than having the alternating odd/even system.
Sector size on hard disks is 512 bytes, not 512kbytes. WTF, don't act like an authority and be a dumbass. Imagine the data waste if we actually had 512k physical sectors on disks.
It is widely known that Reiser filesystems are heavy on CPU usage 4 more than 3. These benchmarks seem to show a CPU bound IO situation as opposed to an IO bound IO situation. As an earlier comment pointed out, the hardware used in this test was a 500mhz CPU. My slowest computer is a 1000mhz system, which is usually IO limited, not CPU limited. I'd be interested to see these same benchmarks run on real hardware, or some more complex benchmarks (random RW, DB load, etc.). The hardware used for this test would be suitable for a fileserver, but not much else. In that situation, E2, E3 or XFS are probably the right choices as it points out. What about desktop loads, enterprise loads, or something more interesting?
Good post! On my iRiver H340, I use a volume level of 15-20 with my big over-ear cans, 12-15 with my earbuds, and 3-4 with my Shure E3 (stock firmware levels). These levels give me equal difference between background and music, the total level of sound being experienced by my ears is of course lowest with the Shure E3. Probably about equal with earbuds or my over ear phones as both are very open to outside sound, the higher volume is needed because the over ears have higher impedence.
The only problem with the Shures is that I can't hear people talking to me at work at all w/o taking them out. I'm pretty sure that overall wearing them improves my hearing, because the music level that I listen to during the day is about the same as the ambient noise in my office, and less droning.
You're confused -- HIV is already a slow killer, and that is why it's scary. Death by HIV generally takes years, and it can go undetected for much of that time. Its speed-of-mortality is not what is stopping HIV from becoming epidemic, the fact that it is not yet airborne is what's stopping it.
See comments in the Bird Flu Pandemic article for more on this, but to summarize, a disease that kills its host before it has a chance to spread will become milder until it has a better chance to spread, just by natural germ selection. Even _if_ HIV's mortality is higher than ideal, the long lifespan of the infected means that there is no strong / fast reason for it to evolve weaker.
Keep in mind the new kernel development model, where anything outside of major architectural changes is permissable in the Y of W.X.Y releases, and there is now the stable W.X.Y.Z releases to provide stabilized security patched kernels for those who want a slower moving target.
Not only are they bittorrent links but they are hella faster than the mirrors.
I tried to get it from two mirrors and got stalled downloads, then downloaded from the torrent at 1 meg per second for the windows installer and 2.7 megs+ for the linux installer. (and am now seeding from that same connection for the rest of you)
That's not entirely true, for that matter, traffic from my home server to my leased server takes a route via sprint, and traffic in the other direction takes a route via telia (both have one end in ALTER.NET). Any good hosting provider, and any really good internet service provider should be truly multihomed.
The point being that as others have pointed out, you simply get what you pay for. If you buy cheap service, you get a cheap single homed connection.
You would only notice if you are on one of these two networks.
I am personally on UUNet at home and MCI at work, and my server is on SpringLink (via Schlund, who I am not familiar with). As a result, all of my traffic is completely unaffected.
Customers on a single-homed connection through Cogent, or through L3 cannot see other single homed customers on the other network. The rest of us don't know the difference.
The dumb thing that this article points out is that both Cogent and L3 are refusing to route packets destined for each other through the rest of the internet (probably for fear of fucking up other peering agreements by dumping too much traffic on their other peers). I believe there was a comment in the previous thread about this issue saying that traffic in one direction could be routed, but that even return packets were being null-routed at some point, preventing any type of connection from being established.
The writer of that article is an idiot. The linux kernel forks after every major release in order to accomodate large patches. How did we get to where we are today? Linux-2.4 forked into 2.4 and 2.5 to allow the major scheduler and other changes to be made on a non-production branch. Then 2.5 became 2.6 which was the new stable branch. Currently there are 4 maintained stable branches that I am aware of (2.0, 2.2, 2.4, and 2.6), having a new unstable branch is just the same path that Linux has been following for years. That writer needs to STFU and get a brain.
from his post why he isn't already on the antibiotics, it doesn't sound like it is for lack of money or lack of health care. It sounds more like the doctors won't give them to him.
At this point he just needs to get somewhere where they can put him in a hospital bed and monitor the infection 24/7 or he's going to die. Hopefully his doctors will be able to treat him correctly and in time, because it would be a tragedy for the linux community if Slackware died.
Slashdot Mirror
The current system facillitates this as well -- I run 2.6.anything.somthinghigh on my servers and 2.6.anything at home and it works quite well. The -stable team are really providing an excellent service with their work beyond the 3rd dot, and they let the main line kernel move at a quicker pace than having the alternating odd/even system.
And they are about equally supported on Rockbox as the iPod is. (Perhaps a tiny bit more)
Nope, can still break it, so you're right. 2 wks till 3.0, best have it right by then.
I think I have the kinks ironed out in the playback system :-P Note the last two "I'm an idiot" commits on the rockbox page if it ever loads.
Sector size on hard disks is 512 bytes, not 512kbytes. WTF, don't act like an authority and be a dumbass. Imagine the data waste if we actually had 512k physical sectors on disks.
Also the scaling numbers are completely hokey.
It is widely known that Reiser filesystems are heavy on CPU usage 4 more than 3. These benchmarks seem to show a CPU bound IO situation as opposed to an IO bound IO situation. As an earlier comment pointed out, the hardware used in this test was a 500mhz CPU. My slowest computer is a 1000mhz system, which is usually IO limited, not CPU limited. I'd be interested to see these same benchmarks run on real hardware, or some more complex benchmarks (random RW, DB load, etc.). The hardware used for this test would be suitable for a fileserver, but not much else. In that situation, E2, E3 or XFS are probably the right choices as it points out. What about desktop loads, enterprise loads, or something more interesting?
Good post! On my iRiver H340, I use a volume level of 15-20 with my big over-ear cans, 12-15 with my earbuds, and 3-4 with my Shure E3 (stock firmware levels). These levels give me equal difference between background and music, the total level of sound being experienced by my ears is of course lowest with the Shure E3. Probably about equal with earbuds or my over ear phones as both are very open to outside sound, the higher volume is needed because the over ears have higher impedence.
The only problem with the Shures is that I can't hear people talking to me at work at all w/o taking them out. I'm pretty sure that overall wearing them improves my hearing, because the music level that I listen to during the day is about the same as the ambient noise in my office, and less droning.
You're confused -- HIV is already a slow killer, and that is why it's scary. Death by HIV generally takes years, and it can go undetected for much of that time. Its speed-of-mortality is not what is stopping HIV from becoming epidemic, the fact that it is not yet airborne is what's stopping it. See comments in the Bird Flu Pandemic article for more on this, but to summarize, a disease that kills its host before it has a chance to spread will become milder until it has a better chance to spread, just by natural germ selection. Even _if_ HIV's mortality is higher than ideal, the long lifespan of the infected means that there is no strong / fast reason for it to evolve weaker.
Keep in mind the new kernel development model, where anything outside of major architectural changes is permissable in the Y of W.X.Y releases, and there is now the stable W.X.Y.Z releases to provide stabilized security patched kernels for those who want a slower moving target.
Not only are they bittorrent links but they are hella faster than the mirrors. I tried to get it from two mirrors and got stalled downloads, then downloaded from the torrent at 1 meg per second for the windows installer and 2.7 megs+ for the linux installer. (and am now seeding from that same connection for the rest of you)
That's not entirely true, for that matter, traffic from my home server to my leased server takes a route via sprint, and traffic in the other direction takes a route via telia (both have one end in ALTER.NET). Any good hosting provider, and any really good internet service provider should be truly multihomed.
The point being that as others have pointed out, you simply get what you pay for. If you buy cheap service, you get a cheap single homed connection.
http://ask.slashdot.org/comments.pl?sid=164413&cid =13726522
According to this post, it's not cogent that is blocking, it's L3.
You would only notice if you are on one of these two networks. I am personally on UUNet at home and MCI at work, and my server is on SpringLink (via Schlund, who I am not familiar with). As a result, all of my traffic is completely unaffected. Customers on a single-homed connection through Cogent, or through L3 cannot see other single homed customers on the other network. The rest of us don't know the difference. The dumb thing that this article points out is that both Cogent and L3 are refusing to route packets destined for each other through the rest of the internet (probably for fear of fucking up other peering agreements by dumping too much traffic on their other peers). I believe there was a comment in the previous thread about this issue saying that traffic in one direction could be routed, but that even return packets were being null-routed at some point, preventing any type of connection from being established.
The writer of that article is an idiot. The linux kernel forks after every major release in order to accomodate large patches. How did we get to where we are today? Linux-2.4 forked into 2.4 and 2.5 to allow the major scheduler and other changes to be made on a non-production branch. Then 2.5 became 2.6 which was the new stable branch. Currently there are 4 maintained stable branches that I am aware of (2.0, 2.2, 2.4, and 2.6), having a new unstable branch is just the same path that Linux has been following for years. That writer needs to STFU and get a brain.
from his post why he isn't already on the antibiotics, it doesn't sound like it is for lack of money or lack of health care. It sounds more like the doctors won't give them to him.
At this point he just needs to get somewhere where they can put him in a hospital bed and monitor the infection 24/7 or he's going to die. Hopefully his doctors will be able to treat him correctly and in time, because it would be a tragedy for the linux community if Slackware died.