[systemd-devel] udevd creates unwanted loop devices, and too early

Jan Engelhardt jengelh at inai.de
Fri Oct 12 15:01:47 PDT 2012


On Friday 2012-10-12 23:50, Jan Engelhardt wrote:

>Hi,
>
>on openSUSE 12.2, which has udev-182 and systemd-44, I found that 
>starting udevd creates some loop devices in /dev (which is a devtmpfs).
>
>* boot linux using "-b" to make systemd go into emergency
># ls /dev/loop*
>ls: cannot access /dev/loop*: No such file or directory
># systemctl start udev.service
># ls /dev/loop*
>/dev/loop0  /dev/loop2  /dev/loop4  /dev/loop6  /dev/loop-control
>/dev/loop1  /dev/loop3  /dev/loop5  /dev/loop7

Well it seems openSUSE had the idea of placing some static devices in 
/lib/udev/devices. So as far as upstream systemd is concerned, this has 
already resolved itself, thanks to the capable members in IRC.


More information about the systemd-devel mailing list