Hello everyone, One of the packages I maintain, OpenAFS, is a network file system. As such, one generally wants it to start before things like gdm that need to read the user's home directory. However, in Ubuntu, gdm is started by upstart instead of an init script, and all init scripts are run after the native upstart jobs are run.
The best way to address this for Ubuntu would be to introduce an upstart job for OpenAFS. However, the package is in universe and hence preferrably shared between Ubuntu and Debian. Is there any reason why it would cause problems for me to add an upstart job to the Debian package, even though Debian doesn't currently use upstart? (I realize that the logic around deactivating the init script if upstart is present may be a bit complex, but I suspect we can find ways of dealing with that.) I assume the job just sit there quiescent until Debian switches to upstart. (Separately, I'm going to look at upstream changes required so that I can have the openafs init script provide $remote_fs instead of depend on it as it does now so that it will move earlier in Debian's boot process as well.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
