We now have comments!

I probably should have used an already existing Blog system that includes a comment facility. However, I decided to roll my own, with inferior features, lax security, poor scaleability etc. All I need to do now is to write something that is worth someone making a comment about 🙂

Modules Madness

Ok, I am about to rant a little. I hate modules! Or maybe it is just the modules on my machine.

I recently installed Debian Unstable onto my machine. I used the stock 2.6 kernel, and the only thing I needed to do to get my USB TV adaptor to work was to copy the firmware file to the correct location.

That got me up and running with xine. Now, today I wanted to use dvbstream to record the GP. It failed. I remembered reading on Hugo’s website (www.carfax.org.uk) about adding an option to one of the dvb modules that stopped it from being automatically unloaded, or something. I found the details quite easily, but then I need to find exactly where to stick this information. It was by now about five minutes to go before the start of the GP.

It would appear that Debian is in the process of upgrading how modules are configured as there seems to be two places holding configuration files. Frankly, I don’t care how they are handled, as long as it works. With minutes to go, I was not in the mood to learn. Naturally, with sods law in motion, the first place I tried failed to work. I finally managed to get it to work by adding a file called dvb in /etc/modprobe.d. The file contained the single line

options dvb_core dvb_shutdown_timeout=0

I hope I remember this for the next time I re-install!

Multisite Gallery

I had installed Gallery v2 on my Debian testing server. It works very well. Now I had a problem where I wanted to have some images available publicly, while the majority I wanted to keep for viewing on my internal network only. I know that Gallery has permissions, but I decided that a multisite install would do what I wanted.

I started with Gallery installed from the default Debian testing package. This is a standard single instance installation. On the Gallery website there is some information on setting up a multisite installation. The main thing to remember is to make sure that the database and directories for the new instance are created beforehand. Then it is a simple matter of selecting the multisite option during the install. The install is initiated by going to

http://sitename/gallery2/install

The only additional thing I had to do was make a copy of the Apache config file for gallery in

/etc/apache2/conf.d

I then repeated the operation to make a private gallery.

Once the private gallery was completed, I needed to move the contents of the original gallery yo it. This section was missing from the gallery documentation mentioned above, so I had to wing it on my own. Using phpmyadmin I created a backup of the original gallery database. Then I imported that into the new private gallery database. All the actual albums are then copied from the file system to the new albums location. I would not try this if there were any pictures already in the destination gallery.

I now have two picture galleries that are totally independent, and I can easily secure one from being publicly viewable. If you want to test that claim then the public gallery is here and the private one is here.