CVS and bugtracking with Mantis

All the small things to close working week. Rest of the day I’ve spent education myself on CVS again. :) I’ve came across CVS book at red-bean.com which I now want to order hardcopy. All my today CVS practise was around a wonderful piece of software called Mantis. It is simple yet powerfull bugtracking system, which I have adopted as technical support tool for our company. All of my changes were based on version 0.16.0, while mantis went to version 0.17.0. So, I’ve been porting all my changes to the new version. Tried both ways with traditional diff-edit-patch-repeat and cvs ways. So far, I enjoy the cvs way of doing things, and I haven’t yet tried branching and merging. Oh, I sound like a developer, don’t I? :)

Java, CVS, and documentation

Last few days were pretty active. First of all, I was playing with apache, JBoss and resin setup. I managed to get them to work together, although failed to make resin handle web apps from the /.

I also spent a fair amount of time on CVS, mutt+gnupg, CA with openssl and some other stuff. CVS makes me happy. I’ve read about some BSD application called arch, which is supposed to be even better then CVS, though the port for Linux is not complete yet, so be it :) Mutt was pretty easy to set up with gnupg. Actually, it happened so, that I had pgp support compiled in for ages, and gpg.rc configuration file was kindly provided with the distribution of mutt package.

Now I am about to write several technical documents for our company internal use, so I was looking for the right way to do it. Office suits were not even thought of, after I remembered my Final Year Project preparation in MS Office. Yuck, that was a pain in the … Hmm.. Mkay. So, I went off to the direction of XML and SGML, but that land is a bit confusing. DocBook followed with recomendations from Linux Documentaion Project (aka LDP). All roads lead to Rome, though and I ended up with TeX idea in my head. I will live it through over the weekend and I will decide finally what to use.

OpenOffice.org

OpenOffice.orgPlayed with OpenOffice.org most of the day. Funny, after a lot of trying and braking, I have read about /net (or -n) option, which is used for OpenOffice.org installations for multiuser environments. Otherwise, .sversion file is not created in the proper place and nasty things happen :)
OpenOffice.org has nice configuration scheme through xml files. Easy to use for scripting and automative user setups. Bravo.

First LDAP encounter

I have started to learn LDAP today. Here is how I did it:

  • Install new Red Hat Linux 7.2 server.
  • During install
    • Specify to authenticate through LDAP which is located at 127.0.0.1
    • I forgot to permit SSH connection during firewall configuration
    • In boot manager configuration, I have specified to use GRUB with which I don’t have any experience yet.

When I did all this, I have found myself in situation where machine refused any connections via secure shell, refused any logins locally, Result:

  1. Unusable machine
  2. Frozen butt (a/c in the server room)
  3. Complete reinstall
  4. Linux LDAP Tutorial