Fix `grml2ram` when booted via `loopback.cfg`

When booted from a multiboot USB stick via loopback.cfg (or when using
`findiso=` kernel option manually), `/dev/loop0` is used for the ISO file and
`/dev/loop1` for the squashfs image.

Therefore, changing backing file descriptor of `/dev/loop0` will fail. Call `losetup` to find the name of
the loop device associaed to the squashfs image instead.

diff --git a/usr_sbin/grml2ram b/usr_sbin/grml2ram
index a4e119e..0806383 100755 (executable)
--- a/usr_sbin/grml2ram
+++ b/usr_sbin/grml2ram
@@ -65,6 +65,7 @@ fi
 
 GRMLSIZE="$(du $IMAGE | awk '{print $1}')"
 RAM=$(/usr/bin/gawk '/MemFree/{print $2}' /proc/meminfo)
+LOOPDEV=$(/sbin/losetup -j "${IMAGE}" -n -O NAME)
 
 case "$*" in -f|--force)
   ewarn "Forcing copy process for grml-image (${GRMLSIZE}kB) as requested via force option." ; eend 0
@@ -80,7 +81,7 @@ esac
 einfo "Copying $IMAGE to RAM, this might take a while."
 rsync -a --progress $IMAGE /tmp/GRML
 LANGUAGE=C LANG=C LC_ALL=C perl << EOF
-open LOOP, '</dev/loop0' or die $!;
+open LOOP, '<${LOOPDEV}' or die $!;
 open DEST, '</tmp/GRML' or die $!;
 ioctl(LOOP, 0x4C06, fileno(DEST)) or die $!;
 close LOOP;