Comment 10 for bug 325059

Hello again. Glad to see that somebody is trying to resolve this :)

This is just to let you know that I strongly suggest using spacenavd 0.4 as it fixed a lot of the problems of previous versions.

Specifically, it now detects automatically when a supported device is plugged in by monitoring kernel hotplugging events, and it also detects when the X server is started without having to rely on the user to call spnavd_ctl to signal that it's OK to connect to the X server as I mentioned in my first message.

Now as for the setup_init script that comes with spacenavd, that's meant more like an example, and an attempt to help users trying to install the driver from source on a typical GNU/Linux system without assuming anything distribution-specific. I assumed that it wouldn't be used in distribution packages where the packager would be able to set everything up according to each distribution's conventions and idiosyncrasies.

So, feel free to start the daemon using whatever init system ubuntu uses. In this case that would be upstart. I don't think it's a good idea to make a udev rule, because then you'd have to maintain a list of USB devices which are supported by spacenavd, thus duplicating the work done in spacenavd.

Cheers