On Mon, Dec 6, 2010 at 1:52 PM, Thomas Bächler wrote:

Thanks. The initscripts patch won't work though:

[[ $USELVM =~ yes|YES && -x /sbin/lvm && -d /sys/block ]] || return "return" is a statement that will only work inside a function. I don't know what it will do on the top level, but certainly not what you'd expect.

D'oh! Copy-paste error, sorry about that. Updated commit: https://github.com/teg/initscripts-arch/commit/feef447b8368244525dd98582b662.... Thanks for testing, Tom

On Tue, Dec 7, 2010 at 1:10 AM, Thomas Bächler wrote:

I pushed everything to the official git tree.

Great!

There's one more thing about the check in the SWAP area of the crypttab code: Instead of using isLuks to check for a LUKS device, check with blkid whether there is any valid file system signature on it.

The problem is: If blkid finds more than one valid signature, it will not return anything, and we will mistakenly believe that there is no file system (and happily overwrite the drive). This part of initscripts is giving me a headache everytime I touch it.

Hmmm... Interesting... I'll put this on my mental TODO list and have a look next time I have time. Cheers, Tom

Am 07.12.2010 14:30, schrieb Dieter Plaetinck:

...

The problem is: If blkid finds more than one valid signature, it will not return anything, and we will mistakenly believe that there is no file system (and happily overwrite the drive). This part of initscripts is giving me a headache everytime I touch it.

what do the util-linux-ng maintainers say about that? Isn't this something that should be fixed in the blkid source code?

No, that won't be fixed - at least not the way you think. Older blkid-like tools used to report the first matched signature. That resulted in (for example) using an ext3 file system that also happened to have a valid swap header as swapspace, destroying the ext3 file system. (There are tons of other examples like this, in particular, old versions of cryptsetup and mkswap didn't wipe old existing file system headers.) It was decided that blkid will refuse to report any ambiguous match as a match. I'm thinking about requesting a feature that allows to report any match, ambiguous or not.

Am 08.12.2010 00:47, schrieb Alexander Duscheleit:

Do you think, you can have a look at https://bugs.archlinux.org/task/16625

It's a constant annoyance if you use something like qemu/kvm/etc and have to wait ~20 seconds on every boot just for your dhcp-assigned IP-Address.

Thanks, Jinks

Please oh please can that be implemented that in netcfg (basic bridging is there, but no advanced options), so we can drop bridging support from initscripts entirely?