saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: cloud-initramfs-tools (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bug
** Branch linked: lp:~smoser/ubuntu/saucy/cloud-initramfs-
tools/lp-1267225
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267225
Title:
initramfs in cloud-images does not contain crypt modules
To
Latest daily build for 14.04 has fix and resolves this issue. (Verified
on 20120206 daily build)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267225
Title:
initramfs in cloud-images does not conta
** No longer affects: cryptsetup (Ubuntu)
** Also affects: cloud-initramfs-tools (Ubuntu Saucy)
Importance: Undecided
Status: New
** Changed in: cloud-initramfs-tools (Ubuntu Saucy)
Status: New => Confirmed
** Changed in: cloud-initramfs-tools (Ubuntu Saucy)
Importance: Undec
** Branch linked: lp:cloud-initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267225
Title:
initramfs in cloud-images does not contain crypt modules
To manage notifications about this b
This bug was fixed in the package cloud-initramfs-tools - 0.22ubuntu1
---
cloud-initramfs-tools (0.22ubuntu1) trusty; urgency=medium
* correctly identify partition and block device for devices named
like devnameXpN, such as mmcblk0p1 (LP: #1236380).
* always include aesni_inte
** Branch linked: lp:ubuntu/trusty-proposed/cloud-initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267225
Title:
initramfs in cloud-images does not contain crypt modules
To manage not
On Wed, Jan 08, 2014 at 10:04:31PM -, Scott Moser wrote:
> Seems that sometime in saucy we got:
> * debian/initramfs/cryptroot-hook:
> - Do not unconditionally include cryptsetup utils in the initramfs.
> - Do not include any modules or utils in the initramfs, unless
> rootfs/r
@xnox,
Could you explain why you did this? Generally debian/ubuntu initramfs policy
is to build a "large generic" initramfs instead of a customized one per
configuration of the system. Ie, lsinitramfs shows me some net/ppp/ drivers
that i'm a lot less likely to use in my initramfs than crypt
Seems that sometime in saucy we got:
* debian/initramfs/cryptroot-hook:
- Do not unconditionally include cryptsetup utils in the initramfs.
- Do not include any modules or utils in the initramfs, unless
rootfs/resume devices are encrypted or CRYPTSETUP is set to 'y' in
the in
This looks like a build-time bug in both overlayroot and crypt-setup.
overlayroot/hooks/overlayroot does:
egrep -qswo "aes" /proc/cpuinfo && manual_add_modules aesni_intel || true
And cryptsetup's /usr/share/initramfs-tools/hooks/cryptroot does:
# Load hardware aes module
11 matches
Mail list logo
