On Thu, Jul 10, 2014 at 10:55 PM, Michael Biebl <bi...@debian.org> wrote: > Am 10.07.2014 22:02, schrieb Peter Poeschl: >> Package: udev >> Version: 204-14 >> Severity: important >> >> Dear Maintainer, >> >> * What led up to the situation? >> udev upgrade from 204-8 to 204-14 removed the file /etc/udev/links.conf. >> >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> Try to loop-mount a file via an existing /etc/fstab entry >> >> * What was the outcome of this action? >> mount failed with >> mount: Could not find any loop device. Maybe this kernel does not know >> about the loop device? (If so, recompile or `modprobe loop'.) >> >> * What outcome did you expect instead? >> mount succeeds >> >> >> Workaround: >> 1) running >> # modprobe loop >> temporarily solves the problem. >> >> 2) # echo 'loop' > /etc/modules-load.d/loop.conf >> persistently solves the problem, but I don't know if this is the proper >> solution. >> > > Kay, is the loop modules supposed to be auto-loaded these days or does > it require and explicit modprobe?
The logic in util-linux, libmount, losetup, ... tries to access /dev/loop-control which will block and trigger a kernel-side module auto-load. All that is needed is that tmpfiles have created the "dead" device node to access from userspace, and the major/minor of that node will resolve to the kernel module providing the requested device. Kay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
