Dear Diary: The Eternal Ramblings of Trevor Watson

Inspired by my success in getting Squid into the Service Management Framework for Solaris 10, I have also now managed to hack something together for Samba.

The script used to kick off and kill the samba daemons is here. This should be copied to a suitable system location - I chose the default service methods directory: /lib/svc/method/.

The service bundle file is here. You could save this to the system services directory: /var/svc/manifest/network, but I chose just to keep it in my homedir as I am only experimenting with it. I guess if you plan to use LiveUpgrade in the future, it might be worthwhile copying this file over as I'm not sure how or whether the services database is rebuilt during Live Upgrade.

The service bundle is loaded into the SMF using the command:

# svccfg validate samba.xml
# svccfg import samba.xml

Note that I have marked it as disabled by default. To enable it, run:

# svcadm enable network/samba

That was easy, wasn't it ?

You may recall that I've been having some problems getting my iPod and Sony camcorder to work over the IEEE1394 link to my PC (or any other computer for that matter).

Things haven't really moved forward much. However, I did take the iPod back to the retailer a couple of weeks ago and told them it was faulty. It apparently went off to Apple to be repaired and should be back "soon".

I tried my camcorder in the 1394 port of my SunBlade 2000, and it too failed to recognise that anything was plugged in. Normally, in Solaris 10, the system will detect the connection and then attempt to locate a suitable device driver. If it can't find a driver, it then reports that using syslog. No message at all in syslog, so obviously the system doesn't actually see the camcorder. So, this morning the camcorder went off to the local Sony repair centre in the hope that they can find and fix the fault.

Given that both devices appear to be faulty, I'm leaning towards the possibility that the 1394 port on my PC into which I first plugged the devices was faulty and has somehow damaged them. Either that or it's a very strange coincidence.

More news will follow when the iPod returns from Apple.