It just occurred to me that OSDN should really get into hosting. Considering the massive contributions they make to OSS (especially sourceforge), I would be happy to support them.
I'm currently buying shared hosting from an EV1 reseller. My contract isn't up for a couple of months but I'm ready to go as soon as I find a new home.
I don't think a bandwidth limitation is going to be effective for this situation. They're still going to consume the same amount of bandwidth, just over a longer term. It's not like people usually sit and wait for the site sucker to do it's thing. Bandwidth limiters like you suggested are usually used to reduce the effects of slashdotting and the like.
What you need is an anti-leech mod to limit the amount of data that can be downloaded from a specific IP. I know they're out there. Just do a bit of googling.
It would be interesting if there were a way to find out more about motivations of those who filed. I would see them falling into one of three categories.
1) People who agree with the claim and want to hurt MS, even though the settlement causes no changes in their operation.
2) People who don't really understand what this is all about but want the free money (fatwallet types)
3) People who disagree with the whole lawsuit, but whose greed overtakes their principles.
The first time was in '97 when I was sent to a vendor site to fix a PC application. I talked to the supervisor there before I got started and was told something to the effect of "do whatever you need to - just get it running". I went to work on it and determined the OS (Win95) had some serious issues and decided a reinstall was most expedient. I reformatted, reinstalled, and put the application on. When I was done I told the supervisor what I had done and that everything was honky dory. That's when he tells me other customers application data was on there and 'I had no business doing that'. They had no backup. My company was charged for the rebuild work, and I ate crow.
The other big mistake was when I was doing a hardware upgrade on a database server. I was new at this division of the company, having transferred only a few weeks before. IIRC I was repartioning a RAID array. I started around 8pm. I made my backup of the database, added disks, and went to restore. The SQL database backup was corrupted. I panicked hard. Why hadn't I tested the backup?! I called Microsoft support but a full restore was not possible. At 4 am, I ended up going back to the previous nights backup. It actually gets worse, but it's too long to document here and it depresses me to think about it.
On my own machines at home, I'm always switching hard disks, reinstalling OS's, etc., and many times I've forgotten I had documents or digital pictures tucked away somewhere and lost them for good. It's harder to get myself to apply due diligence on my own stuff, but I'll learn eventually.
I've made two major blunders on the job.
The first time was in '97 when I was sent to a vendor site to fix a PC application. I talked to the supervisor there before I got started and was told something to the effect of "do whatever you need to - just get it running". I went to work on it and determined the OS (Win95) had some serious issues and decided a reinstall was most expedient. I reformatted, reinstalled, and put the application on. When I was done I told the supervisor what I had done and that everything was honky dory. That's when he tells me other customers application data was on there and 'I had no business doing that'. They had no backup. My company was charged for the rebuild work, and I ate crow.
The other big mistake was when I was doing a hardware upgrade on a database server. I was new at this division of the company, having transferred only a few weeks before. IIRC I was repartioning a RAID array. I started around 8pm. I made my backup of the database, added disks, and went to restore. The SQL database backup was corrupted. I panicked hard. Why hadn't I tested the backup?! I called Microsoft support but a full restore was not possible. At 4 am, I ended up going back to the previous nights backup. It actually gets worse, but it's too long to document here and it depresses me to think about it.
On my own machines at home, I'm always switching hard disks, reinstalling OS's, etc., and many times I've forgotten I had documents or digital pictures tucked away somewhere and lost them for good. It's harder to get myself to apply due diligence on my own stuff, but I'll learn eventually.
This isn't the only corporation that "Jamie Weathersby" threatened... yet, I don't know of a single threat that was sucessfully carried out.
Uh, yeah... The ones who do pay off blackmailers (and it does happen) don't generally advertise it. When a corporation is successfully extorted, it tends to stop there, unless the bastards ask for a second ransom.
They do put out a separate distribution for the server arena. Sounds like it uses X for the install routine, but after that it's your basic stable Linux server.
But they also seem to blatently ignore all the 'point' releases (which seems really insane in the case of Apple, which makes you pay for the point release upgrades).
t0ny, you're a b00b. Or maybe you're just new to computers.
All commercial OS vendors charge for point releases. It's sad that the Microsoft naming scheme adopted in the summer of '95 would lead you to believe otherwise. Windows XP is just NT v5.1. Windows 2000 was v5.0. And so it goes throughout the product lines...
Don't get me started about all the MS products that skipped directly to version 3 or 4 on their first release.
The guys who created the Expand Accellerator were actually trying to develop a new encryption method when they stumbled across a method to increase virtual bandwidth.
I second that. I have a 600e, and the main battery (on my 3rd now) is completely dead. The ultraslimbay battery, however, seems to be very solid.
I was thinking of replacing the main battery with one made by APC, but now that I understand it is the charge mechanism, I guess I'll get along with what I've got.
Slashdot Mirror
For those who don't know where their hosting ultimately resides, ping your server to get the IP address, then use the IP Whois at DNSStuff.
It just occurred to me that OSDN should really get into hosting. Considering the massive contributions they make to OSS (especially sourceforge), I would be happy to support them.
I'm currently buying shared hosting from an EV1 reseller. My contract isn't up for a couple of months but I'm ready to go as soon as I find a new home.
BSE can be found in Canada as well...
I don't think a bandwidth limitation is going to be effective for this situation. They're still going to consume the same amount of bandwidth, just over a longer term. It's not like people usually sit and wait for the site sucker to do it's thing. Bandwidth limiters like you suggested are usually used to reduce the effects of slashdotting and the like.
What you need is an anti-leech mod to limit the amount of data that can be downloaded from a specific IP. I know they're out there. Just do a bit of googling.
I'll second the nomination for MMORPGs. Star Wars Galaxies has LOTS of couples on it.
Malware author != script kiddie
Agreed.
It would be interesting if there were a way to find out more about motivations of those who filed. I would see them falling into one of three categories.
1) People who agree with the claim and want to hurt MS, even though the settlement causes no changes in their operation.
2) People who don't really understand what this is all about but want the free money (fatwallet types)
3) People who disagree with the whole lawsuit, but whose greed overtakes their principles.
I've made two major blunders on the job.
The first time was in '97 when I was sent to a vendor site to fix a PC application. I talked to the supervisor there before I got started and was told something to the effect of "do whatever you need to - just get it running". I went to work on it and determined the OS (Win95) had some serious issues and decided a reinstall was most expedient. I reformatted, reinstalled, and put the application on. When I was done I told the supervisor what I had done and that everything was honky dory. That's when he tells me other customers application data was on there and 'I had no business doing that'. They had no backup. My company was charged for the rebuild work, and I ate crow.
The other big mistake was when I was doing a hardware upgrade on a database server. I was new at this division of the company, having transferred only a few weeks before. IIRC I was repartioning a RAID array. I started around 8pm. I made my backup of the database, added disks, and went to restore. The SQL database backup was corrupted. I panicked hard. Why hadn't I tested the backup?! I called Microsoft support but a full restore was not possible. At 4 am, I ended up going back to the previous nights backup. It actually gets worse, but it's too long to document here and it depresses me to think about it.
On my own machines at home, I'm always switching hard disks, reinstalling OS's, etc., and many times I've forgotten I had documents or digital pictures tucked away somewhere and lost them for good. It's harder to get myself to apply due diligence on my own stuff, but I'll learn eventually.
I've made two major blunders on the job. The first time was in '97 when I was sent to a vendor site to fix a PC application. I talked to the supervisor there before I got started and was told something to the effect of "do whatever you need to - just get it running". I went to work on it and determined the OS (Win95) had some serious issues and decided a reinstall was most expedient. I reformatted, reinstalled, and put the application on. When I was done I told the supervisor what I had done and that everything was honky dory. That's when he tells me other customers application data was on there and 'I had no business doing that'. They had no backup. My company was charged for the rebuild work, and I ate crow. The other big mistake was when I was doing a hardware upgrade on a database server. I was new at this division of the company, having transferred only a few weeks before. IIRC I was repartioning a RAID array. I started around 8pm. I made my backup of the database, added disks, and went to restore. The SQL database backup was corrupted. I panicked hard. Why hadn't I tested the backup?! I called Microsoft support but a full restore was not possible. At 4 am, I ended up going back to the previous nights backup. It actually gets worse, but it's too long to document here and it depresses me to think about it. On my own machines at home, I'm always switching hard disks, reinstalling OS's, etc., and many times I've forgotten I had documents or digital pictures tucked away somewhere and lost them for good. It's harder to get myself to apply due diligence on my own stuff, but I'll learn eventually.
Holland appears to be the most densely populated western country, unless you count city states or occupied provinces.
Uh, yeah... The ones who do pay off blackmailers (and it does happen) don't generally advertise it. When a corporation is successfully extorted, it tends to stop there, unless the bastards ask for a second ransom.
They do put out a separate distribution for the server arena. Sounds like it uses X for the install routine, but after that it's your basic stable Linux server.
t0ny, you're a b00b. Or maybe you're just new to computers.
All commercial OS vendors charge for point releases. It's sad that the Microsoft naming scheme adopted in the summer of '95 would lead you to believe otherwise. Windows XP is just NT v5.1. Windows 2000 was v5.0. And so it goes throughout the product lines...
Don't get me started about all the MS products that skipped directly to version 3 or 4 on their first release.
The guys who created the Expand Accellerator were actually trying to develop a new encryption method when they stumbled across a method to increase virtual bandwidth.
I second that. I have a 600e, and the main battery (on my 3rd now) is completely dead. The ultraslimbay battery, however, seems to be very solid. I was thinking of replacing the main battery with one made by APC, but now that I understand it is the charge mechanism, I guess I'll get along with what I've got.