Here is the output from apt-cache:
> LC_ALL=c apt-cache policy cryptsetup
cryptsetup:
Installed: 2:1.0.4+svn29-1ubuntu4
Candidate: 2:1.0.4+svn29-1ubuntu4
Version table:
*** 2:1.0.4+svn29-1ubuntu4 0
500 http://archive.ubuntu.com gutsy/universe Packages
100 /var/lib/dpkg/status
This is the relevant line from /etc/crypttab:
tmp /dev/vg0/ub_tmp_c /dev/urandom tmp
To create the volume I log in as root (as requested during the bootup)
and do the following:
cryptsetup create -d /dev/urandom tmp /dev/mapper/vg0-ub_tmp_c
mkfs.ext2 /dev/mapper/tmp
and then I do CTRL-D to continue the bootup process.
Or to use a more variable-ly looking notation:
cryptsetup create -d $KEYFILE_FROM_CRYPTTAB $DEVICENAME_FROM_CRYPTTAB
$PARTITION_FROM_CRYPTTAB
mkfs.ext2 /dev/mapper/$DEVICENAME_FROM_CRYPTTAB
The latter line is supposed to be triggered by the "tmp" option in
crypttab.
--
no longer creates non-LUKS partitions.
https://bugs.launchpad.net/bugs/119848
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
