Hi On Wednesday 06 June 2012, Matthijs Kooijman wrote: > Hi Stefan, > > > I'm pretty sure this is due to a missing LSB dependency on $local_fs > > for lirc's init script. > I'm not so sure this is really the case: The problem is really that the > udev rule triggers a lirc (re)start too soon on the boot sequence, not > that the normal init script invocation is too soon. > > This would mean that any dependency changes in the init script would not > fix this problem.
In my experience, with several USB/ hotpluggable lirc devices and a
separate /var/ partition, this is the actual problem. What happens is
that the lircd socket gets created underneath the final /var/run/,
/run/ respectively, before it is mounted on its final place, thereby
getting hidden and inaccessible from the clients. On a regular
installed the most common cause for this is mounting /var/ on a
dedicated partition, I assume something similar is the case on
Debian-live with its writeable overlay filesystem(s).
I am considering to force /run/ for wheezy, instead of /var/run/ and
relying on on initscript's transitioning magic though, as this would
make the socket handling a bit more robust, but the actual upgrade a
little more complex than before; due to the symlinks there are no
consequences for userspace ABIs.
> > update-rc.d -f lirc remove
> > update-rc.d lirc defaults 19
> I just tried these, but this did not cause any reordering in the
> scripts. I didn't try booting the system again (I'd have to generate a
> new image first), but I have the entire rootfs under version control so
> I'm sure nothing changed as a result of the above commands.
[…]
If you're trying it on Debian live systems, you better inject a fixed
package[1] into the ISO build - but I'm not familiar with Debian-live
specifics.
Regards
Stefan Lippers-Hollmann
[1] by applying this patch
http://lists.alioth.debian.org/pipermail/pkg-lirc-changes/2011-May/000568.html
to 0.9.0~pre1-1. Tell me, if you need help with creating
those test packages
signature.asc
Description: This is a digitally signed message part.
