[arch-dev-public] [signoff] cryptsetup 1.0.6-2
This changes the "udevsettle" command in cryptsetup to "udevadm settle" to work with udev from testing. This still breaks in klibc, but the udevsettle call is not that important there as it causes problems only when too many devices are being opened/closed. The udevsettle call will be gone from the next cryptsetup version, so I hope this fix is temporary. Tested here on x86_64, please sign off.
On Fri, Sep 12, 2008 at 11:39 AM, Thomas Bächler <thomas@archlinux.org> wrote:
This changes the "udevsettle" command in cryptsetup to "udevadm settle" to work with udev from testing. This still breaks in klibc, but the udevsettle call is not that important there as it causes problems only when too many devices are being opened/closed.
The udevsettle call will be gone from the next cryptsetup version, so I hope this fix is temporary.
Tested here on x86_64, please sign off.
Ping. Anyone use cryptsetup?
2008/9/14 Aaron Griffin <aaronmgriffin@gmail.com>:
On Fri, Sep 12, 2008 at 11:39 AM, Thomas Bächler <thomas@archlinux.org> wrote:
This changes the "udevsettle" command in cryptsetup to "udevadm settle" to work with udev from testing. This still breaks in klibc, but the udevsettle call is not that important there as it causes problems only when too many devices are being opened/closed.
The udevsettle call will be gone from the next cryptsetup version, so I hope this fix is temporary.
Tested here on x86_64, please sign off.
Ping. Anyone use cryptsetup?
Me, me! All HDD except /boot partition is encyphered. Nothing got broken, so here's my signoff (x86_64). -- Roman Kyrylych (Роман Кирилич)
On Mon, 2008-09-15 at 22:00 +0300, Roman Kyrylych wrote:
2008/9/14 Aaron Griffin <aaronmgriffin@gmail.com>:
On Fri, Sep 12, 2008 at 11:39 AM, Thomas Bächler <thomas@archlinux.org> wrote:
This changes the "udevsettle" command in cryptsetup to "udevadm settle" to work with udev from testing. This still breaks in klibc, but the udevsettle call is not that important there as it causes problems only when too many devices are being opened/closed.
The udevsettle call will be gone from the next cryptsetup version, so I hope this fix is temporary.
Tested here on x86_64, please sign off.
Ping. Anyone use cryptsetup?
Me, me! All HDD except /boot partition is encyphered. Nothing got broken, so here's my signoff (x86_64).
Was able to create and use an encrypted ext2 filesystem in a container file. Signoff for i686. -- K. Piche <kpiche@rogers.com>
2008/9/20 K. Piche <kpiche@rogers.com>:
On Mon, 2008-09-15 at 22:00 +0300, Roman Kyrylych wrote:
2008/9/14 Aaron Griffin <aaronmgriffin@gmail.com>:
On Fri, Sep 12, 2008 at 11:39 AM, Thomas Bächler <thomas@archlinux.org> wrote:
This changes the "udevsettle" command in cryptsetup to "udevadm settle" to work with udev from testing. This still breaks in klibc, but the udevsettle call is not that important there as it causes problems only when too many devices are being opened/closed.
The udevsettle call will be gone from the next cryptsetup version, so I hope this fix is temporary.
Tested here on x86_64, please sign off.
Ping. Anyone use cryptsetup?
Me, me! All HDD except /boot partition is encyphered. Nothing got broken, so here's my signoff (x86_64).
Was able to create and use an encrypted ext2 filesystem in a container file. Signoff for i686.
Still in Testing! ;-) -- Roman Kyrylych (Роман Кирилич)
participants (4)
-
Aaron Griffin
-
K. Piche
-
Roman Kyrylych
-
Thomas Bächler