[Dann Frazier]
> Thanks for the report.
> I suspect you've seen this issue with other packages? If so, you
> have one you'd suggest looking at for a good postinst example?
There is the supported way and the ugly way. :)
The supported way is to remove all the symlinks and reinsert them
again using something like this from nfs-common:
case "$1" in
configure)
...
if [ "$2" != "" ] && dpkg --compare-versions "$2" lt 1:1.1.0-10; then
update-rc.d -f nfs-common remove >/dev/null
fi
update-rc.d nfs-common start 20 2 3 4 5 . stop 20 0 1 6 . start 44 S .
>/dev/null
...
;;
esac
This might loose user changes to the set of enabled runlevels, but is
the only supported option working with both sysv-rc and file-rc.
On the other hand, there is the ugly option, only working with
sysv-rc, which is to work directly on the symlinks, for example like
this from quota:
elif dpkg --compare-versions "$2" lt 3.17-4
then
rm -f /etc/rcS.d/S*quotarpc
fi
Of course sysv-rc with insserv is the only configuration with the
problem, so this might be OK in this case. On the other hand, if
file-rc gain support for dependency based boot sequencing, that might
not hold true in the future.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
