Bringing Linux to Work – Portal Part 3

Ubuntu just doesn’t want to be chosen for me. I’ve had nothing but problems with it since I started going on it. I decided that it would be easier to use Ubuntu (1 disk install, apt-get abilities) to house the in house Intranet portal page here where I work. However, I didn’t count on Ubuntu having so many problems.

The first of many problems was mod_ntlm. This Apache module WILL NOT compile on my server. I emailed someone who actually got this to compile in Ubuntu and asked for how they got it to work, implemented their changes in the .c file, yet still couldn’t get it to compile. This reason alone is enough for me to not use it. But there are more reasons still that Ubuntu doesn’t do it for me.

The second reason is going cold. What I mean by going cold is that it almost froze up. For example, it would take over an hour to run apt-get update, about the same to run apt-get upgrade (depending on downloads) and even 20 minutes to do a standard ls -al | grep keyword command. After a reboot everything was fine. This led me to believe that some sort of power saving module was kicking in. So I removed all power saving modules, recompiled a kernel from scratch, turned off all BIOS power saving items, crossed my fingers and rebooted. Even with all of these actions, Ubuntu still went cold after a day of uptime. This is on an IBM NetVista P4 with 1 GB RAM. Ubuntu however will not be staying on any PC at my job due to the previous problems experienced.

I’ve got an exact match of this machine to provide backup for it so I’ve simulataneously been using CentOS to experiment around with it. There’s a reason that Red Hat is the leader in the server arena…because they get it done and provide a fantastically stable Linux environment. CentOS is repackaged Red Hat Enterprise Linux and it is fantastic. So from this point on, Ubuntu will not be actively developed on by myself…I’ll be using CentOS from this point on. Which leads me to the decisions I’ve been trying to come to.

I’ve been trying to find a good portal CMS that can house documents and provide news announcements for my department. No chat is needed…no forums…just a repository for docs. With all of this being said, I need to provide a flexible solution to house these documents as well because who knows what the director will come back and say. Perhaps tomorrow he’ll change his mind and want to have all documentation developed and worked on in Sharepoint and all reports to go on our intranet page. So I need flexibility if I’m going to get a CMS running on Linux and I need it to be stable so I can show tangible results to upper managment. Otherwise, they’ll continue to go with what has been working for them…and that is Windows.

Some of you are probably saying, “just use OpenLDAP any distro”. Well, that would be just fine if my requirements were to use the LDAP database for user authentication making the user sign on one time only…however, stipulations for me were ZERO sign in…hence single sign on…they login to our domain here and then never have to login again. So, ntlm is the only way currently. Finding a CMS is up next.

I’ve looked at midgard but am thinking it is way to complicated. I just want a simple page that can act as a document repository. I’ve looked at and installed knowledgetree but there currently is no single sign on support at all so it is out of the question. I’ve looked at Zope and Plone and found it to be right along the lines of what I need. The problem I hit is that I have to use Apache to pass the ntlm to the Zope server…so it’s going to take some configuring (this is the #1 candidate right now though).

So does anyone out there have any idea of a CMS that can use SSO (Single Sign On) in a Win2k Active directory environment with minimal configuration (as this needs to go up in about 2 weeks)? I’m all ears. The next update should be my attempt to use CentOS with ntlm and apache/zope/plone.

Wish me Luck,

Devnet

This content is published under the Attribution-Noncommercial-Share Alike 3.0 Unported license.