TeX

TeXFinally, after considerable thought, I have chosen, not without the help of others, to use TeX for writing documentation. After two days of using it, I must admit that I enjoy it really much. There are few helpful online resource like TeX User Group, UK List of TeX FAQ, LaTex and BibTeX course notes (with lots of examples). For those who can read and understand Russian, TeX FAQ and TeX section of opensource.ru might be of some help.

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.

Slay – user process killer and CVS

Came over a nice program called Slay which does the following:

Slay sends given signal (KILL by default) to all processes belonging to user(s) given on the command line.

I was also playing a bit with CVS GUIs today. There are some programs out there. WinCVS.org was particularly helpful. For CVS itself, I found www.cvshome.org to be the most helpful resource.

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.