Netbook a little small for an IDE

Eclipse eating CPU
Eclipse was filtering the list of installable add-ons

After I installed Linux Mint 10 to get away from Unity bugs, I went to reinstall Eclipse.

First from Synaptic, but the version was a bit old. I did not manage to install Maven.

Next a download and manual install of Helios. Filtering the list of available add-ons seems to launch an enormous job. Type one letter and wait 2 minutes.

Hope I can get it all running before lunch. :-{

EPUBReader for Firefox

EPUBReader blog masthead

Head down working yesterday. I was too tired to write to you by the time I quit at 11 pm.

Still busy today, but I took a few minutes out to look at how to read the .epub files I have been generating with help from Docbkx Tools.

I don’t have an appliance to read EPUB, but there’s an EPUBReader add-on for Firefox that seems to work fairly well. At least well enough for me to figure out what I am doing wrong or right.

Why EPUB? My hope is that the content will be even easier to read than PDF, and still available so you can read the docs during a system crash combined with a network outtage. 😉 Seriously, I’m more curious than anything else at this point.

LDAP Account Manager and OpenDJ

LAM logoFrom Freshmeat.net, I saw an announcement that LDAP Account Manager had reached version 3.4.0. Congratulations to Roland Gruber and all the other contributors. A quick summary from the project site:

LDAP Account Manager (LAM) is a web frontend for managing entries (e.g. users, groups, DHCP settings) stored in an LDAP directory. LAM was designed to make LDAP management as easy as possible for the user. It abstracts from the technical details of LDAP and allows persons without technical background to manage LDAP entries. If needed, power users may still directly edit LDAP entries via the integrated LDAP browser.

This morning I tried out the older version of LDAP Account Manager with OpenDJ, version 3.1 I believe, that has gone into Linux Mint 10.

Setup works through the PHP-based web GUI. Yet I managed to put a typo in my ldap URL and could not contact OpenDJ, which is running on another system. Looking around, I found that the config info entered through the PHP pages goes not under /etc/ldap-account-manager, but into /usr/share/ldap-account-manager/config/lam.conf. So sudo vi /usr/share/ldap-account-manager/config/lam.conf and I was back in the saddle again after fixing ldap://192.168.0.11:1/1389 to read ldap://192.168.0.11:1389.

The lam.conf file seems approximately self-explanatory. It says, “Please do not modify this file manually.” I admit to having been impolite therefore. But what I did seemed to work.

  • Could not figure out how to get LAM to login with cn=Directory Manager — note: probably a good thing — so to the list of Admins I added uid=mark,ou=people,dc=example,dc=com, which is one of the users in my OpenDJ setup. mark appeared in the drop-down lists of LAM admins after I saved.
  • Changed a number of base DNs in the file to reflect that my main suffix is dc=example,dc=com.
  • Changed ou=group,dc=example,dc=com to ou=Groups,dc=example,dc=com.
Also, one of the organizationalUnit entries was missing. I added ou=Machines,dc=example,dc=com on the OpenDJ server.
I’m just discovering LAM, so I haven’t scratched the surface, yet. My guess is that a number of standard schema definitions are missing in OpenDJ to handle the accounts, because I could not even create a new UNIX group, let alone a Samba 3 group. Instead I got an object class violation.
Nevertheless the GUI is quite nice. Will have to give LAM a longer look later.

JSPWiki/Tomcat using LDAP auth

JSPWiki logo

An interesting thread came up Easter Sunday on the jspwiki-user list. Brian Burch explains how to set up LDAP authentication behind JSPWiki running on Apache Tomcat.

I have only gotten so far as to update the LDAP schema for OpenDJ (here’s what I used), add the tomcatRole to my users, create my groups, activate Tomcat container authentication through to LDAP, and tell JSPWiki to use container auth.

Now I see that SSL is needed, which makes sense if anyone’s going to start typing passwords to authenticate.

The procedure is not exactly quick and easy, but I am glad to see that the overall steps have been written up.

OpenDJ 2.4.2 available

OpenDJ logoGlad to relay that OpenDJ 2.4.2 has just released. 🙂

OpenDJ 2.4.2 is an update release that fixes a number of issues. See Ludo’s blog entry for more.

To perform an evaluation install if you already have Sun Java 6 on your system, try the Java WebStart version.

You are welcome to join the community, and also to sign up for the mailing list.

Notepad and \n

Billgates.JPG
Source: http://en.wikipedia.org/

Notepad still does not recognize UNIX newlines. But you already knew that.

Every time an intern looks at the problem and says, “Shucks, I could commit this one line fix for that,” a Windows product manager springs out from behind the desk to say, “Never! Not in a million years!”

I saw the issue first while trying Slackware, probably in 1996-7. Latest workaround noticed: On Windows 7 when you run the edit command in a Power Shell to open a UNIX file, you can just save it again. It’s like running unix2dos. Then you can edit the file in Notepad. YMMV, but it seemed to work for me.

dn: o=北京大学

g11n testing
Testing non-European locales, source: http://server.lunq.net

I told Gary I would run some manual functional tests of OpenDJ on Windows. At home the kids’ Windows 7 PC is in locale fr-FR.

Testing with European language characters seems to be pretty easy. Copy a suffix DN from a web page, paste it into the Control Panel, and then import an LDIF file. No problem.

But when I try creating a suffix with Chinese, o=北京大学, or Japanese, o=東京大学, all the entries are ignored on import. It is as if the text I copy/paste is not the same as the text I copy/paste then save in Notepad in UTF-8.

How does all that work, anyway? (Will the copy/paste steps I’m doing between a Terminal and Chrome on the Mac show up right in your view of this entry?)