Package: selinux-basics Version: 0.2.4 Severity: normal User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency
With dependency based boot sequencing, I discovered what I believe is a bug in the init.d script. The init.d script dependency information state that it should run after checkfs, but not what it should run before: ### BEGIN INIT INFO # Provides: selinux-basics # Required-Start: checkfs # Required-Stop: # Default-Start: S # Default-Stop: # Short-Description: Basic SELinux management # Description: Prepare system for SELinux usage, e.g. relabeling the fs. ### END INIT INFO Does it matter? In #537394 I discovered that it is placed in parallel with mountall.sh and just after checkfs and before mountall-bootclean.sh. This seemed rather strange do me. Then there is this changelog entry in version 0.2.4: * Move initscript to S 36, just after all filesystems have been mounted First of all, S36 was after mountall.sh, while all file systems are only guaranteed to be mounted after mountnfs.sh. I must admit I do not understand what the script is doing, so I am not sure if it should run before any file system related operations or not. If it should run after all file systems are available, it might be better to let it depend on $remote_fs. If it need to run before some other scripts in rcS.d/, these should be listed in an X-Start-Before header. Just thought it best to ask, now that dependency based boot sequencing is the default. <URL: http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html > documents the LSB header format. Some debian notes are available from <URL: http://wiki.debian.org/LSBInitScripts >. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
