tomb

commit aa35441d696cfdeb9af8506c6bf5cc003e42c522
parent d4c4a82d7359fc14ffc39a636c587afbeb76e018
Author: Jaromil <jaromil@dyne.org>
Date:   Sun, 16 Nov 2014 11:09:43 +0100

this should fix lo_mount() as reported in #154

Diffstat:
M
tomb
 | 
6
++----

1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/tomb b/tomb
@@ -480,7 +480,7 @@ lo_mount() {
     tpath="$1"
 
     # check if we have support for loop mounting
-    losetup -f >& -
+    _nstloop=`losetup -f`
     [[ $? = 0 ]] || {
         _warning "Loop mount of volumes is not possible on this machine, this error"
         _warning "often occurs on VPS and kernels that don't provide the loop module."
@@ -488,9 +488,7 @@ lo_mount() {
         _failure "Operation aborted."
     }
 
-    _nstloop=`losetup -f` # get the number for next loopback device
-
-    losetup -f "$tpath" >& - # allocates the next loopback for our file
+    losetup -f "$tpath" # allocates the next loopback for our file
 
     TOMBLOOPDEVS+=("$_nstloop") # add to array of lodevs used