Slashdot Mirror
"Get the Facts" Campaign Working
brontus3927 writes "According to a Reseller Advocate Magazine write-up, Microsoft seems to be winning its war against Linux. Info-Tech Research Group recently ran a survey that is now being used on Microsoft's Get The Facts campaign. In it were some surprising results. 'After polling 1,400 IT managers and CIOs in SMB corporations, his group found that 48% were not interested in Linux, 15% were not sure about Linux, and only 10% plan to evaluate Linux." Despite this, two-thirds of all webservers run Linux. The disparity in these numbers comes from the fact that most smaller companies' websites are hosted by service providers running Linux servers even if the company itself isn't."
Despite this, two-thirds of all webservers run Linux.
No. Two-thirds of all publicly visible web servers found by netcraft run Apache, but this includes many other operating systems.
Tarsnap: Online backups for the truly paranoid
This is the same old same old story for so long, I wonder why these keep ending up on the main page.
Unix rules the server room. Windows rules the desktop. Linux is solidly taking over the server room from proprietary Unices. The Linux revolution is not taking over the desktop. If your business sees computers from the desktop app perspective, MS is the winning vendor. If you are running network services and high availability dbs, you are running Unix (now Linux). Most companies of any size are running a polyglot of op-sys and apps which trends towards windows on the desktop and trends towards Unix/Linux on the back end.
http://linux.slashdot.org/article.pl?sid=05/04/08/ 224225&tid=163
This same group came out with the story '"Mid-Sized Companies Not Interested in Linux - Microsoft Still Dominates, Study Says" - April 5, 2005'.
It looks like the same "study".
Thanks, Slashdot, for giving the lame "study" more legs and contributing to Linux FUD.
Raise your children as if you were teaching them to raise your grandchildren, because you are.
Stripping down Linux is pretty easy. There are many distros that are already stripped down, and every distro I've ever tried has a "server" package, which includes only what you need to run a webserver.
But even if you do the stripping yourself it's not that bad. Whenever you do something mainstream that lots of people do, you can do it the way everyone else does.
The dependencies for apache are clearly known by pretty much every distribution. There's even a project to build everything you need from scratch if you just want to start with nothing and build up. In short, if you have dependency problems when you're dealing with apache, you're using a pretty messed up distro to start with, since virtually all of them solve that problem first.
As far as kernel bloat...I don't know where you're getting this. Even a big kernel is tiny compared to any Windows kernel 95 or higher. Recompile the kernel, or download one of the many, many already created tiny kernels. It takes four minutes to configure and half an hour to recompile and install.
*Note: Poster may be someone looking to Slashdot to do his research for him, and I didn't want to do so. I will, however, say that the links for all the things I mentioned are available at freshmeat.
Mod me down and I will become more powerful than you can possibly imagine!
You fired someone for making a suggestion that turned out bad and in the end was a decision *YOU* were responsible for?!?
That guy is *A LOT* better off now than he was working for you, that much is clear. You are a terrible leader in the worst sense, someone who will cover their own ass at the expense of others.
You are lucky I am not *YOUR* boss... you'd be on the unemployment line right behind that guy... no, actually, only *YOU* would be on the unemployment line... I'd hire him back and get him a better boss too.
If a pion (n-) collides with a proton in the woods & noone is there to hear it, does lamdba decay into the source pa
So you are still running Windows NT 3.51 systems or are you talking about early release NT 4.0 systems?
There has been so many changes with Windows products over the past ten years, that each iteration, while built upon the last, is sufficiently different from the previous release so as to make it virtually impossible to use the exact same skill set from one revision of the OS to another.
So, at most, if you are running Windows 2000 Pro and Server across your network, you have roughly 5 years experience and expertise. If you switched up to Windows Server 2003, and WinXP Pro workstations, you have even less. (Although, from my limited reading the 2000 to 2003 Server changes aren't quite as drastic as the Windows 2000 Pro to Windows XP Pro changes...)
If you ignore the other uses of a tool, does that make the tool less useful, or you less useful?
Some movement right here.
All that for under $500.
Bunk. 2/3 might run Apache, but that runs on any flavor of Unix, BSD/OSX, even Windows.
http://www.linuxquestions.org/
Very helpful community, and very active for a lot of distros. I have never, ever, seen an answer that was only "RTFM". I've seen answers like "Here's how you do it, and here's the section of the manual where this fix comes from", but never only "read the !@#$@#$ manual."
Most of those people probably already have Linux boxes. Their staff has likely snuck some in as firewalls and servers. Furthermore, lots of their embedded devices (access points, network storage, routers, etc.) run on Linux.
:-)
The nice thing is that these people don't have to "investigate" Linux, Linux is coming to them, piece by piece. In Capitalist America, you don't adopt Linux, Linux adopts you
Wrong. 2000/XP PRO does not install IIS unless you dig around in the add/remove programs post installation.
OTOH, all versions of 2000 SERVER dumbly run IIS automatically, and a lot of "hobbyists" want to be l335 and run this in their homes. Note how most of the Code Red worm problems came from cable/DSL subnets.
You're missing his point - it's a good idea to reboot machines now and then just to make sure they reboot cleanly, with all necessary services running. Better to find out something is broken in a maintenance window than after a power failure at 3am Saturday morning or smack bang in the middle of production time.
Well 'running servers' doesn't just mean that we make sure the fans are spinning, and the little green lights stay on.
I spend 90% of my time programming...and about 10% maintaining the 4 servers that I use. That includes keeping users FTP accounts up to date.
We have thousands of users, and one of the people maintains the filesharing/e-mail servers, while supporting those users in using them.
We sell products, and use a webserver/database server/firewall for that system. Maintaining the servers is a small part- keeping the site with shopping cart running/secure/up-to-date is more important.
Actually for only 4 people, we get a ton of work done- and our administrative overhead is very low. That's why we wouldn't be switching anytime soon- I would have to re-write a lot of what I've done. We would have to switch tons of user accounts, get a new e-mail system, etc. etc. We do real stuff...not just some stupid administrative tasks that could be automated...those are the people who will soon see the unemployment line.
No reason to lie.
In our environment, what we notice the most is that Windows patches tend to require reboots. With the number of servers we have, a reboot for every set of patches (and some patches which force reboots themselves) is pretty significant. Linux/UNIX ones tend not to require a reboot unless it's a kernel update. Even with an automated patching system in place, the Windows servers require more maintenence and cause more issues than all the Linux and UNIX systems combined.
Indeed, Kerberos V and OpenLDAP give us across the board authentication and policy control over all of the Linux, UNIX (and Windows systems via an AD trust). No scripting involved on the UNIX systems, just a few configuration changes that are now part of the install image. The fact that we only need to reboot our non-Windows servers when there's a kernel update is priceless, as it helps us maintain our service availability requirements.