About users of comcast on their home servers (note, dynamic) are crying about no longer being able to host their mail servers.
And?
You are using the services of comcast as an ISP and thus are subject to their TOS. If comcast says "no, we don't want you to host a server" then quite simply, you can not host a server. However, as it may be, they have a yes/no look upon servers.
As many comcast users who run a httpd, I'm sure we've all noticed the massive script checking logs that probe how well our servers are secured. No, it isn't a million script kiddies, because comcast higher-up's comfirmed their security scanning. (gave them a call and spent a few good hours cutting heads off). Their primary concern isn't about pissing off the companies, as Comcast is primarily a dynamic IP home userbase. This means that they are more worried about the security of the home user's network as well as Comcast's network, and thus why they run security scans on the users servers.
If your server is secure, isn't spamming, or using an unusual amount of bandwidth, they won't lift a finger or say a word. If you are running an ancient server version, spamming, or using a ton of unusual bandwidth on incoming, they are going to notify you.
See, I'm fine with that. But let's not (parent) go into a hypnotic state in which people can chant "linux is free kthx 4eva" when there are obvious costs to any migration from one distro to another.
Just the small fact that Linux is FREE and what you really pay for wheny buying a Linux distro such as RedHat or SuSe is support.
No, that doesn't make any sense, especially in a buisness model. Sure, the OS itself can be free, the installation, free, but you have extra costs:
1. Paying to teach the administrators the new distro that they are not used to administrating on
2. Paying to teach the employees how to use the new distro that they are not used to working on
3. Payment for code conversion (if not already cross compatible) to switch from windows to linux, so the employess can use the company programs.
4. Payment for rollover and backups, so that they can be implimented properly and without a laspe of time between OS switches.
5. Payment for the entire time spent on computers/terminals that will be out of the loop during the time it takes the OS switch to occur. This is a statement of fact, even if done one computer at a time or entire sections.
Right, because all the apps and kernel releases on a nix/BSD distrobution NEVER receive patches or upgrades at a similar speed, if notso in more quantity than Windows patches.
security systems, air quality controls,
I can see it now.. someone logs in trying to use an unencrypted signal.
HAL: "What are you doing Dave? How do you feel?"
Moron: -gasping for breath-
Slashdot Mirror
About users of comcast on their home servers (note, dynamic) are crying about no longer being able to host their mail servers.
And?
You are using the services of comcast as an ISP and thus are subject to their TOS. If comcast says "no, we don't want you to host a server" then quite simply, you can not host a server. However, as it may be, they have a yes/no look upon servers.
As many comcast users who run a httpd, I'm sure we've all noticed the massive script checking logs that probe how well our servers are secured. No, it isn't a million script kiddies, because comcast higher-up's comfirmed their security scanning. (gave them a call and spent a few good hours cutting heads off). Their primary concern isn't about pissing off the companies, as Comcast is primarily a dynamic IP home userbase. This means that they are more worried about the security of the home user's network as well as Comcast's network, and thus why they run security scans on the users servers.
If your server is secure, isn't spamming, or using an unusual amount of bandwidth, they won't lift a finger or say a word. If you are running an ancient server version, spamming, or using a ton of unusual bandwidth on incoming, they are going to notify you.
It's that simple guys.
If Xfree was cross platformable, then I don't see why x.org wouldn't be. Remember, it's a fork. Think Xfree86 + improvements + future updates
From ICANN to ICAN'T
-dodges the incoming flames-
It's early..
See, I'm fine with that. But let's not (parent) go into a hypnotic state in which people can chant "linux is free kthx 4eva" when there are obvious costs to any migration from one distro to another.
Just the small fact that Linux is FREE and what you really pay for wheny buying a Linux distro such as RedHat or SuSe is support.
No, that doesn't make any sense, especially in a buisness model. Sure, the OS itself can be free, the installation, free, but you have extra costs:
1. Paying to teach the administrators the new distro that they are not used to administrating on
2. Paying to teach the employees how to use the new distro that they are not used to working on
3. Payment for code conversion (if not already cross compatible) to switch from windows to linux, so the employess can use the company programs.
4. Payment for rollover and backups, so that they can be implimented properly and without a laspe of time between OS switches.
5. Payment for the entire time spent on computers/terminals that will be out of the loop during the time it takes the OS switch to occur. This is a statement of fact, even if done one computer at a time or entire sections.
Right, because all the apps and kernel releases on a nix/BSD distrobution NEVER receive patches or upgrades at a similar speed, if notso in more quantity than Windows patches.
It must be true. I mean, after all pigs fly, fat lady has sung, and the cows have come home.
security systems, air quality controls, I can see it now.. someone logs in trying to use an unencrypted signal. HAL: "What are you doing Dave? How do you feel?" Moron: -gasping for breath-
Cross-seeding eh? I say it is merely a good old fashion, interstellar splunking competition.