On Tue, Feb 21, 2012 at 06:50:21PM +0100, Thomas Bächler wrote:

Am 21.02.2012 18:43, schrieb Tom Gundersen:

...

fstab should be fine, but people who don't use the filesystem hook in mkinitcpio, but rather include the ext2 or ext3 module manually (and not ext4) might get in trouble.

mkinitcpio should resolve aliases in all those cases, I think (at least 'modinfo' resolves implicitly).

You can all go to hell for making fun of kmod -- while mit's modinfo doesn't resolve aliases, kmod's does. suck on that. EXCELSIOR! SAVED BY KMOD!!! </snarky> Yeah, we should be fine, since ext4 gains ext{2,3} as aliases with this option set. d

On Tue, Feb 21, 2012 at 2:57 PM, Ionut Biru wrote:

On 02/21/2012 07:38 PM, Tobias Powalowski wrote:

...

https://bugs.archlinux.org/task/25341 - ext4 manages now ext2/ext3 and ext4

Please report if any issues happen, here all went fine on all machines. I had not to change any config file like fstab or mkinitcpio.conf.

greetings tpowa

Why do we do config changes in bug fix releases? Can't this change be delayed until 3.3?

Please revert this change. Thomas explicitly said to try this in 3.3, and you went ahead with it in 3.2.7 and broke boot on at least one user's system because this hadn't been tested with mkinitcpio yet [1]. -Dan [1] https://bugs.archlinux.org/task/28569