Package: zeroconf Version: 0.8-1 Severity: normal Installing zeroconf in a chroot causes the daemon to be started there, disregarding policy.d settings. This causes the temporarily mounted /dev within the chroot to be unmountable until the daemon is located and killed.
That's bad for lessdisks :-( I interpret policy as mandating daemons to always use invoke-rc.d and thus respect policy.d - but I am unsure about this interpretation, so lowering severity. Please raise it if you agree with my interpretation. - Jonas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-powerpc Locale: LANG=da_DK, LC_CTYPE=da_DK (charmap=ISO-8859-1) Versions of packages zeroconf depends on: ii ifupdown 0.6.7 high level tools to configure netw ii iproute 20051007-4 Professional tools to control the ii libc6 2.3.6-5 GNU C Library: Shared libraries an zeroconf recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
