Question

这发生在命令apt-get dist-upgrade升级到debian jessie之后，之后我试图移除保险丝，然后重新安装。同样的错误：

root@msgapp:/dev# apt-get install fuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  fuse
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/69.9 kB of archives.
After this operation, 191 kB of additional disk space will be used.
Selecting previously unselected package fuse.
(Reading database ... 39354 files and directories currently installed.)
Preparing to unpack .../fuse_2.9.3-10_amd64.deb ...
Unpacking fuse (2.9.3-10) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up fuse (2.9.3-10) ...
MAKEDEV not installed, skipping device node creation.
device node not found
dpkg: error processing package fuse (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 fuse
E: Sub-process /usr/bin/dpkg returned an error code (1)

更新

重新安装makedev会产生另一个问题：

root@msgapp:/dev# apt-get install makedev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  makedev
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/42.6 kB of archives.
After this operation, 129 kB of additional disk space will be used.
Selecting previously unselected package makedev.
(Reading database ... 39347 files and directories currently installed.)
Preparing to unpack .../makedev_2.3.1-93_all.deb ...
Unpacking makedev (2.3.1-93) ...
Processing triggers for man-db (2.6.7.1-1) ...
ySetting up makedev (2.3.1-93) ...
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.

有ticket提出，他们的修复不会给出任何结果：

root@msgapp:/dev#  cd /dev && ./MAKEDEV fuse
/run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.

Answer 1

这更多是评论而不是答案，但我不允许发表评论。

根据http://ubuntuforums.org/showthread.php?t=1324257：＆＃34;检查udev并在发现makedev时使用makedev是正常的事情。＆＃34;

另外https://lists.debian.org/debian-user/2009/10/msg00434.html ＆＃34;据我了解，如果udev处于活动状态，则不需要调用MAKEDEV。因此，这不是警告，只是通知。＆＃34;

＆＃34; apt-get install fuse＆＃34;既然你已经安装了makedev？

Answer 2

我建议，这可能是在OpenVZ虚拟专用服务器（VPS）容器中使用udev，makedev和融合时的问题。尝试将debian wheezy vps升级到debian jessie vps时遇到了相同的问题。也许无法说出解决方案吗？

“这是OpenVZ VPS吗？” – cantsay '16 Feb 22在0:16

也许，这只能由vps主机上的ISP解决。 https://virtuozzosupport.force.com/s/article/000017479

我猜这也适用于OpenVZ：
debian bug #550334

此错误基本上导致该软件包无法在任何chroot中安装   安装了udev的环境（包括ltsp，pbuilder和piuparts），   因为udev在检测到chroot环境时不会启动（默认情况下）。

将udev优先于makedev（在fuse-utils 2.8.1-1中引入）会导致此错误   默认在chroots中被触发。

创建设备节点的解决方案应该不是这样

root @ msgapp：/ dev＃cd / dev && ./MAKEDEV保险丝

但是像这样

root @ msgapp：/ dev＃cd / dev && MAKEDEV保险丝

因为MAKEDEV位于/ sbin / MAKEDEV而不是/ dev / MAKEDEV

作为一种解决方法，我删除了/ dev / fuse以避免/var/lib/dpkg/info/fuse.postinst运行udevadm info -q path -n / dev / fuse，这在现有的特殊设备上也失败了

crw-rw ---- 1根root 10，229 Jan 23 01:38保险丝。

然后我将/ run / udev重命名为/ run / _udev，以绕过MAKEDEV的可怕抱怨

/ run / udev或.udevdb或.udev存在表示活动的udev。中止MAKEDEV调用。

最后，我可以通过apt install fuse安装保险丝，或者继续使用apt upgrade并重命名/ run / _udev。

mv / run / _udev / run / udev

apt-get install fuse - 未安装MAKEDEV，跳过设备节点创建

2 个答案: