Novell Doubts Microsoft Latest "Linux Facts"
Robert writes "Microsoft Corp's "Get the Facts" campaign comparing Windows with Linux
continues to prove controversial, with Novell Inc describing the latest set of facts
offered up by Microsoft as "misdirection." The latest report offered up by
Microsoft as evidence that Windows is a better bet than Linux is a white paper from
Security Innovation Inc that compares maintenance, patch application, and system failures
related to a migration from Windows Server 2000 to 2003, and Novell's SUSE Linux
Enterprise Server 8 to SLES 9. The report found that there were more system failures
experienced by Linux systems administrators, and that more patches needed to be applied to
the
Linux systems, while more time was required to complete the Linux migration."
As an 'expert' system administrator (albeit unpaid) I have four servers. One is running Microsoft Windows Small Business Server 2003, one is running Microsoft Window Server 2003, one is running Ubuntu Linux 5.10 (Server), and the other is running Apple OS X Server (10.4).
I can tell you now that when I first started my company, although I was a major advocate of Linux, I soon found that I did not have the time to maintain a then Gentoo or custom LFS distribution, Debian was far too heavy to pick up, and Slackware felt a little dated. So I took a look at Microsoft Windows Small Business Server 2003, liked what I saw, and bought a Dell PowerEdge 400SC with an OEM install.
At first Small Business Server was a breath of fresh air. It was easy to maintain, with a full complement of features, having been bundled with Microsoft Exchange, Microsoft SQL Server, and Window Sharepoint Services. I actually enjoyed - yes, enjoyed - using it.
Until backup stated to fail. Until my tape drive disappeared. Until the sharepoint website database got corrupted. Until exchange monitoring failed. Until the POP connector started to thrash the CPU. Until the Windows Update website failed to check for updates.
These things happened. I'm not saying that they wouldn't happed with another system, but that is not the point, since they happened to me, and that caused me grief, and time, and money to resolve. I ended up trying to build a new system based on Microsoft Windows Server 2003, since I already had Microsoft specific data (files and tables), but this proved even more difficult to maintain.
I struggled for eighteen months, and then decided to build an Ubuntu 5.10 server. I use Ubuntu on one of my laptop, and had gently learnt the apt- way, and liked it. I set up a server with similar features to the Small Business Server, using Postfix, MySQL, and Plone, and even went some ways to transferring my sharepoint data. It works. It hasn't failed yet.
I bet the guys who took part in the survey only set up a server, installed some applications, and patched it. I bet they didn't try running a business for 18-months, just to see what it was really like.
I must say that we recently purchased an Apple PowerMac, and were so impressed we are now looking at completely switching, hence the OS X Server. It is a dream to install and configure, but we are going to run it for several months until we are satisfied that it can do the job.
Any fool can talk, but it takes a wise man to listen.
I would love to know what I should post to show what we have done. I wrote the majority of the code, and it works so well, and deploys in minutes (I have a BDC generation script that will take a blank computer and create a working LDAP enabled BDC and join it to the Samba Domain in less than 15 minutes.)
We use Via EPIA Eden chipset motherboards with dual nics (the Router uses the dual nics, and I also use it on the file servers for hardware consistency). The motherboard only pulls 10 watts of power.
Our company has 9000 employees on payroll, but only 600 actual computer users. Everyone in the company logs into a SAMBA domain. We have done some really, great things with SAMBA deployment, and router deployment. I have a script that generates a router as well (just generates ipsec.conf, ipsec.secrets, rules, policies, and init in the shorewall directory, dhcpd.conf, ipcfg_eth0, ipcfg_eth1, and network in the sysconfig directory, it generates). I can demonstrate everything that I have done and written, and *ahem* never signed an intellectual property agreement of any kind with my employer.
In other words, I own it all, and would love to give it back to the open source community, as I think it would make SAMBA a seriously competitive alternative to Microsoft. windows file servers
I use GoSA as a web based interface to all users and group memberships of the users. EVERYONE should check out GoSA who intendes on using SAMBA over a large group of users (if implementing with LDAP).
https://gosa.gonicus.de/
The coolest thing is the auto login script generation -- you simply add a user to a group in gosa, and it automatically (if you are logging on to that server) create you a login script based on group membership. I will try to paste up the script that calls the scripts that generates (ran from a rootpreexec in smb.conf)
I cannot post, throws a lameness filter, so I cant paste code... oh well.
anyway, if I get a decent response from this, and it seems appropriate, I would be glad to demonstrate some things/code. I am just too busy holding this company together as head/only sysadmin/level 3 support guy.