[arch-dev-public] [signoff] util-linux-ng-2.16.2-1
Hi guys, finally found the correct patch for loop aes support so here we go: ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.17/v2.17-ReleaseNotes Have fun greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am Freitag 22 Januar 2010 schrieb Tobias Powalowski:
Hi guys, finally found the correct patch for loop aes support so here we go: ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.17/v2.17-ReleaseNotes
Have fun greetings tpowa
anyone? -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 24/01/10 20:34, Tobias Powalowski wrote:
Am Freitag 22 Januar 2010 schrieb Tobias Powalowski:
Hi guys, finally found the correct patch for loop aes support so here we go: ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.17/v2.17-ReleaseNotes
Have fun greetings tpowa
anyone?
Have not tested loop aes support but other stuff seems good. Signoff i686. Allan
On Sun, 24 Jan 2010 20:57:22 +1000, Allan McRae <allan@archlinux.org> wrote:
On 24/01/10 20:34, Tobias Powalowski wrote:
Am Freitag 22 Januar 2010 schrieb Tobias Powalowski:
Hi guys, finally found the correct patch for loop aes support so here we go:
ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.17/v2.17-ReleaseNotes
Have fun greetings tpowa
anyone?
Have not tested loop aes support but other stuff seems good.
Signoff i686. Allan
One thing I noticed that doing a read-only bind mount does no longer work in one step. Instead of mount -o bind,ro foo bar you have to use mount -o bind foo bar mount -o remount,ro bar That bad thing is that this first command does not fail but simply mounts read-write and issues a warning. -- Pierre Schmitz, https://users.archlinux.de/~pierre
Am 24.01.2010 13:24, schrieb Pierre Schmitz:
One thing I noticed that doing a read-only bind mount does no longer work in one step. Instead of
mount -o bind,ro foo bar
you have to use
mount -o bind foo bar mount -o remount,ro bar
That bad thing is that this first command does not fail but simply mounts read-write and issues a warning.
Same here, otherwise /arch/signoff64
Am Sonntag 24 Januar 2010 schrieb Thomas Bächler:
Am 24.01.2010 13:24, schrieb Pierre Schmitz:
One thing I noticed that doing a read-only bind mount does no longer work in one step. Instead of
mount -o bind,ro foo bar
you have to use
mount -o bind foo bar mount -o remount,ro bar
That bad thing is that this first command does not fail but simply mounts read-write and issues a warning.
Same here, otherwise /arch/signoff64
Is this a showstopper? -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Sun, 24 Jan 2010 15:07:16 +0100, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Sonntag 24 Januar 2010 schrieb Thomas Bächler:
Am 24.01.2010 13:24, schrieb Pierre Schmitz:
One thing I noticed that doing a read-only bind mount does no longer work in one step. Instead of
mount -o bind,ro foo bar
you have to use
mount -o bind foo bar mount -o remount,ro bar
That bad thing is that this first command does not fail but simply mounts read-write and issues a warning.
Same here, otherwise /arch/signoff64
Is this a showstopper?
No, its just annoying. :-) It is documented in the man page so I guess its intentional and no bug. -- Pierre Schmitz, https://users.archlinux.de/~pierre
On Sun, 2010-01-24 at 15:19 +0100, Pierre Schmitz wrote:
No, its just annoying. :-) It is documented in the man page so I guess its intentional and no bug.
The manpage says that options are taken from the original filesystem and can't be changed when using --bind. Are you sure that it's mounted readonly after the remount, and if so, are you sure the old release did that also?
participants (5)
-
Allan McRae
-
Jan de Groot
-
Pierre Schmitz
-
Thomas Bächler
-
Tobias Powalowski