Your message dated Sun, 3 May 2020 21:59:56 +0200
with message-id <[email protected]>
and subject line Re: Bug#282144: cryptsetup: allow to mount devices
automagically
has caused the Debian Bug report #282144,
regarding cryptsetup: allow to mount devices automagically
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
282144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282144
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptsetup
Version: 0.1-6
Severity: minor
Tags: patch
Hi,
I usually don't start cryptsetup on system boot since I:
a) don't want an additional stop on unattended boots
b) dont' need the data on the encrypted partition all the time
So when starting up cryptsetup later via:
/etc/init.d/cryptsetup start
I have to mount devices after that. To save some typing I added a
"mount" option to crypttab that allows for "automounting" of devices. It
relies on having an fstab entry for that device with the noauto option
set. Please apply.
Cheers,
-- Guido
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9-albook12
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.00.19-4 The Linux Kernel Device Mapper use
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libdevmapper1.00 2:1.00.19-4 The Linux Kernel Device Mapper use
ii libpopt0 1.7-5 lib for parsing cmdline parameters
-- no debconf information
--- cryptdisks.orig 2004-11-20 00:08:28.543412192 +0100
+++ cryptdisks 2004-11-20 00:19:29.612914352 +0100
@@ -60,6 +60,7 @@
PARAMS=""
MAKESWAP=""
SKIP=""
+ MOUNT=""
# Parse the options field, convert to cryptsetup
parameters
# and contruct the command line
@@ -100,6 +101,11 @@
MAKESWAP=yes
PARAM=""
VALUE=""
+ ;;
+ mount)
+ MOUNT=$dst
+ PARAM=""
+ VALUE=""
esac
PARAMS="$PARAMS $PARAM $VALUE"
done
@@ -135,6 +141,9 @@
if test "x$MAKESWAP" = "xyes" && test -b $MAPPER/$dst;
then
mkswap $MAPPER/$dst 2>/dev/null >/dev/null
fi
+ if test "x$MOUNT" != "x"; then
+ mount $MAPPER/$dst
+ fi
fi
done
echo "."
--- End Message ---
--- Begin Message ---
* Guido Guenther <[email protected]> [200503 19:58]:
> I usually don't start cryptsetup on system boot since I:
> a) don't want an additional stop on unattended boots
> b) dont' need the data on the encrypted partition all the time
> So when starting up cryptsetup later via:
> /etc/init.d/cryptsetup start
> I have to mount devices after that. To save some typing I added a
> "mount" option to crypttab that allows for "automounting" of devices. It
> relies on having an fstab entry for that device with the noauto option
> set. Please apply.
Thanks for the report. I understand that this feature is available
with udev/systemd. Certainly there's nothing to be done on the
util-linux side (tbf, I don't quite understand why this ended up as
a bug against util-linux).
Stay safe,
Chris
--- End Message ---
