A good friend Johan Sölve was having some difficulty getting the two versions of Lasso to play together when working with images. It was published a few months back that on CentOS 6.7 that, they changed the default builds of ImageMagick from 6.5 to 6.7 and all binaries built against the older IM libs needed to be rebuilt against the newer. LP8.6 uses the 6.6 libs. Therein comes the question. How do you do that considering L9 uses IM6.7 and LP8.6 uses 6.6? It turns out it’s not too bad. I took all of the sweat out of it. From a high level perspective, you build the older IM in /usr/local and tell the OS to look there for the older binaries/libs. L9.3.x will continue looking at the default in /usr and then LP8.6.x picks up the new location upon restart and viola! Both work side by side using two different versions of IM.
Since the default location is in /usr, you can do yum update all day long and it won’t hurt the custom build you do in /usr/local.
From here out, this assumes you already have installed and initialized LP8.6 and L9.3.
I did this all as root but others may suggest differently. This works just fine as long as you are comfortable working as root. Let the fun begin!
# yum groupinstall "Development Tools" # yum install bzip2-devel freetype-devel libjpeg-devel libpng-devel libtiff-devel giflib-devel zlib-devel perl-devel ghostscript ghostscript-devel djvulibre-devel libwmf-devel jasper-devel libtool-ltdl-devel libX11-devel libXext-devel libXt-devel lcms-devel libxml2-devel librsvg2-devel # mkdir -p /usr/local/src # cd /usr/local/src # wget https://sourceforge.net/projects/imagemagick/files/old-sources/6.x/6.6/ImageMagick-6.6.5-10.tar.gz # tar xzf ImageMagick-6.6.5-10.tar.gz # cd ImageMagick-6.6.5-10 # ./configure --prefix=/usr/local --enable-shared=yes --enable-static=yes # make install # nano /etc/ld.so.conf
At the bottom add the line, if not already there, for
/usr/local/lib and save the file (ctrl -o and ctrl-x).
# ldconfig # lasso8ctl restart
This should work as-is. If you see any compilation errors, you may want to
make clean; make install again. You can try other versions of 6.6 but this one worked fine. I believe it contains the first iteration of the libMagickCore.so.4 and libMagickWand.so.4 which LP8.6.x requires. You may also want to use the ~lasso/Tools/consoleLassoService.sh to restart Lasso in console mode so you can make sure the ImageTag.so library was loaded. If so, you’re golden.
Now, for Apache, I keep it simple. Since there are two different versions of Lasso connectors, you need to implicitly tell Apache which one to use for each site.
/etc/httpd/conf.d I create a file named
"all_lasso.conf" which contains:
# Include the config for the site you want into each vhost declaration from the /etc/httpd/other # directory to load the set handlers <IfModule !lasso8_module> LoadModule lasso8_module modules/Lasso8ConnectorforApache2.2.so </IfModule> <IfModule !lasso9_module> LoadModule lasso9_module modules/mod_lasso9.so </IfModule>
/etc/httpd/conf.d delete the
mod_lasso9.conf files. Create the folder in
/etc/httpd/other. In this location you will create the following:
<Location ~ "^.*\.[Ll][Aa][Ss][Ss][Oo]$"> SetHandler lasso8-handler </Location> <Location ~ "^.*\.[Ll][Aa][Ss][Ss][Oo][Aa][Pp][Pp]$"> SetHandler lasso8-handler </Location>
<Location /lasso9> SetHandler lasso9-handler Order allow,deny Allow from all </Location> # instance management requests are redirected to lassospitfire <Location /lasso9/lux> SetHandler lasso9-instancemanager Order allow,deny Allow from all </Location> Redirect 303 /lasso9/instancemanager /lasso9/lux # requests ending with .lasso or .lasso9 are processed by lassoserver <LocationMatch \.(?i:lasso9?)$> SetHandler lasso9-handler </LocationMatch>
This loads all the lasso modules when Apache starts and then uses the correct module for each site as it is implicitly selected. In each
<VirtualHost ...></VirtualHost> you will use either:
Include /etc/httpd/other/lasso8.conf OR
Again, this tells Apache which Lasso connector to use for each site. Within these files you can globally set the file handlers such as
.html if you want or you can set it within each vhost to be processed by Lasso.
I had a client who wanted AFP services to work on CentOS 5.5 since he was moving from MacOS X. I was saddened to see that it was not already in the CentOS, EPEL or Remi’s repos. So, I set out on a journey to get it included in the Remi or EPEL repos. I contacted Jiri Skala, the Fedora package maintainer, to get it moved into EPEL 5 & 6. You can see the requests here and here. Unfortunately the latest version that could be installed is 2.0.x via EPEL. That did not do it for me so I took the time to research how to build it for CentOS 5 and make it all work.
I downloaded the Webmin module .9b4 and tried to use it but it is lacking of a semi-finished product. I spent the better portion of a day going through and fixing up the code. I emailed it to the package maintainer directly because I do not yet use GIT or DIFF to send him the differences. I’ve posted it here for anyone to test and build on. If you do revise it, send it to me so I can add it to what I have and I’ll keep track of the changes until the original author has time to post it.
I tried to follow instructions on this page but found them slightly off. Here is what worked for me.
# yum install openssl.x86_64 libssl-dev gcc automake autoconf GSSAPI libgssapi-devel libgssapi libgssapi-devel krb5-devel pam-devel shadow-devel openssl-devel cracklib wget
# mkdir /downloads
# cd /downloads
Now to begin downloading and manually building the packages. The following will build the berkeley db binaries, libs etc into /usr/local by default. I recommend not changing this since it just works.
# wget http://download.oracle.com/berkeley-db/db-4.8.30.tar.gz
# tar xzfp db-4.8.30.tar.gz
# cd db-4.8.30/build_unix/
# make install
Now to begin building the netatalk package.
When I did the make install, it created the directories for me and copied all the config files over except afp_ldap.conf. I copied that one manually.
# cp config/afp_ldap.conf /etc/netatalk/
From there all you have to do is either manually start the services or use the Webmin module to do it.
# chkconfig netatalk on
# service netatalk start
After that its only a matter of going in and configuring things. The webmin module does only a basic job but will save some time. Custom tweaks can be done by the Edit Config Files link I added rather than having to use the terminal to do it.