Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30947 - [initscripts] new crypttab format no longer creates swap with label
Attached to Project:
Arch Linux
Opened by Geert Hendrickx (ghen) - Tuesday, 31 July 2012, 20:21 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 01 August 2012, 23:39 GMT
Opened by Geert Hendrickx (ghen) - Tuesday, 31 July 2012, 20:21 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 01 August 2012, 23:39 GMT
|
DetailsThe old crypttab init code did "mkswap -f -L $1" (requested name), allowing to use LABEL=requested_name in /etc/fstab (instead of the crypted blockdevice's path).
This no longer works with the new (systemd) /etc/crypttab syntax and its associated initscripts code, which ommits the -L label. This made my system boot without any swap. I changed the device reference in fstab to the /dev/mapper path, but being able to use the label instead was nice. Can you please add -L $label there too? |
This task depends upon
Closed by Tom Gundersen (tomegun)
Wednesday, 01 August 2012, 23:39 GMT
Reason for closing: Won't implement
Additional comments about closing: If a usecase exists, I'd be happy to do revisit this.
Wednesday, 01 August 2012, 23:39 GMT
Reason for closing: Won't implement
Additional comments about closing: If a usecase exists, I'd be happy to do revisit this.
I prefer to refer to filesystem/blockdevices by label, because it's absolute.