Package: vblade-persist Version: 0.6-2 Severity: grave After calling
# vblade-persist setup 1 1 lo /path/to/file # vblade-persist start 1 1 a symlink (/dev/etherd/e1.1 -> /path/to/file) is created from the script /usr/share/vblade-persist/vblade-run. This is problematic: /dev/etherd is the directory in which the Linux kernel-based AoE initiator keeps its device nodes. If a machine acts both as AoE initiator and target, the device node created by a kernel driver may be clobbered by vblade-persist starting or stopping a target. After briefly looking at the scripts, I'm not aware of any technical reason for these symlinks. Please remove creation and removal of the symlinks or find another spot (e.g. /var/run/vblade-persist/ ?) for them. Cheers, -Hilko -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vblade-persist depends on: ii runit 2.1.1-6.2 system-wide service supervision ii vblade 20-1 virtual AoE blade emulator Versions of packages vblade-persist recommends: ii iproute 20110107-2 networking and traffic control too ii net-tools 1.60-23 The NET-3 networking toolkit vblade-persist suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org