Only time I've ever been involved with something like this was when I needed to upload a gigabyte of data to my web server from home, over RoadRunner. That obviously took a long time with the upload bandwidth restrictions and such, but it got done.
Less that 24 hours later I get a phone call from the RoadRunner police, warning me about excessive usage of upstream bandwidth and obviously implying that I'm running some sort of server out of my house and had better stop. I told him why I was uploading data but that fell on deaf ears, and I was basically told that the only reason they were going to let it go this time was because I was paying for an additional IP address anyway. I got the distinct feeling from this rude guy that they wouldn't care if I'd downloaded a hundred gigabytes of data, but that if I used a hair more of their upstream bandwidth than they thought I should be they'd cancel service in a heartbeat.
I think they may also be embedding this in service packs, in addition to the standalone download, so you may easily install it without even knowing. I know for a fact that I saw this DRM component listed under Windows Update on a Windows 2000 box with SP3, but after it was updated to SP4 that component suddenly wasn't listed anymore. Hmmm....
Ack! So you think that Voyager was actually good?!?! I couldn't stand to watch it anymore after the episode where they "found" Amelia Earhart. Even sitting and waiting where we've never sat and waited before was better than Voyager...
So far as I see, all areas of Linux performance that they tested steadily improved over time with the singular exception of signal handling.
But isn't this at least partially the goal? You optimize the performance of commonly executed code (e.g. context switching) at the expense of code that is not executed as often (e.g. signal handling). It seems to me that any program firing off thousands of signals per second has a serious design flaw.
I got tired of the whole 60-80 hours a week thing a couple of years ago, and have been a relative "slacker" ever since (for the same pay). I currently average 40 hours a week, and though I still do 9-10 hour days sometimes they get balanced out by 6-7 hour days. Throwing yourself head first into work is just not worth it, considering the physical and social consequences.
Tell the school district exactly what you think!
on
Sean In The Middle
·
· Score: 2
Jon e-mailed me a few weeks ago on this very topic. I was apparently one of fifty subscribers selected as a random sampling to check on the accuracy of his subscriber database. All my info was good (apart from an out of date e-mail address...but that's my fault). So he's obviously doing his best to make sure that the subscription list is transferred as flawlessly as possible. Assuming that this resurrection takes place as planned, I certainly plan to renew based on the obviously huge amount of love and devotion Jon has put into it. Kudos!
Slashdot Mirror
Only time I've ever been involved with something like this was when I needed to upload a gigabyte of data to my web server from home, over RoadRunner. That obviously took a long time with the upload bandwidth restrictions and such, but it got done.
Less that 24 hours later I get a phone call from the RoadRunner police, warning me about excessive usage of upstream bandwidth and obviously implying that I'm running some sort of server out of my house and had better stop. I told him why I was uploading data but that fell on deaf ears, and I was basically told that the only reason they were going to let it go this time was because I was paying for an additional IP address anyway. I got the distinct feeling from this rude guy that they wouldn't care if I'd downloaded a hundred gigabytes of data, but that if I used a hair more of their upstream bandwidth than they thought I should be they'd cancel service in a heartbeat.
I think they may also be embedding this in service packs, in addition to the standalone download, so you may easily install it without even knowing. I know for a fact that I saw this DRM component listed under Windows Update on a Windows 2000 box with SP3, but after it was updated to SP4 that component suddenly wasn't listed anymore. Hmmm....
I guess this is a new sales technique for promoting domain names for sale...
Ack! So you think that Voyager was actually good?!?! I couldn't stand to watch it anymore after the episode where they "found" Amelia Earhart. Even sitting and waiting where we've never sat and waited before was better than Voyager...
So far as I see, all areas of Linux performance that they tested steadily improved over time with the singular exception of signal handling. But isn't this at least partially the goal? You optimize the performance of commonly executed code (e.g. context switching) at the expense of code that is not executed as often (e.g. signal handling). It seems to me that any program firing off thousands of signals per second has a serious design flaw.
I got tired of the whole 60-80 hours a week thing a couple of years ago, and have been a relative "slacker" ever since (for the same pay). I currently average 40 hours a week, and though I still do 9-10 hour days sometimes they get balanced out by 6-7 hour days. Throwing yourself head first into work is just not worth it, considering the physical and social consequences.
Jon e-mailed me a few weeks ago on this very topic. I was apparently one of fifty subscribers selected as a random sampling to check on the accuracy of his subscriber database. All my info was good (apart from an out of date e-mail address...but that's my fault). So he's obviously doing his best to make sure that the subscription list is transferred as flawlessly as possible. Assuming that this resurrection takes place as planned, I certainly plan to renew based on the obviously huge amount of love and devotion Jon has put into it. Kudos!