Package: initscripts Version: 2.88dsf-13.5 Severity: important Hi,
I think Debian policy 10.5 is pretty clear: Only symlinks *within* a toplevel directory should be relative, symlinks spanning multiple directories should be absolute, i.e. /var/lock should point to /run/lock, /var/run to /run and /dev/shm to /run/shm. It was pointed out, that this makes it harder to inspect those directories in a chroot. On the other hand, relative symlinks make it harder to see where they are pointing to and you can more easily hit the maximum symlink depth. I don't think it makes sense to special case /var/run and it should follow policy. If the reasons for 10.5 no longer hold true, then this section needs a review. But we should avoid inconsistencies when possible. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initscripts depends on: ii coreutils 8.5-1 GNU core utilities ii debianutils 3.4.4 Miscellaneous utilities specific t ii libc6 2.13-2 Embedded GNU C Library: Shared lib ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii mount 2.17.2-9.1 Tools for mounting and manipulatin ii sysv-rc 2.88dsf-13.5 System-V-like runlevel change mech ii sysvinit-utils 2.88dsf-13.5 System-V-like utilities Versions of packages initscripts recommends: ii e2fsprogs 1.41.12-4 ext2/ext3/ext4 file system utiliti ii psmisc 22.13-1 utilities that use the proc file s initscripts suggests no packages. -- Configuration Files: /etc/init.d/mountall.sh changed [not included] -- no debconf information _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
