Bug#336567: postinst fails runnng modprobe on 'ext3,ext2'

[Sven Luther <sven.luther@wanadoo.fr>]

On Tue, Nov 01, 2005 at 04:11:19PM +0100, Jonas Smedegaard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> severity 336567 important
> thanks
> 
> On Mon, 31 Oct 2005 09:03:23 +0000
> Alastair McKinstry <mckinstry@debian.org> wrote:
> 
> > Package: yaird
> > Version: 0.0.11-10
> > Severity: serious
>             ^^^^^^^
> 
> I dare lower this to "important", as I believe it does not violate
> policy, and even if annoying the error is not fatal.
> 
> 
> > I have an /etc/fstab with lines of the form:
> > /dev/hda2	/	ext3,ext2	errors=remount-ro
> > 0	1
> > 
> > ie. for filesystem, try ext3 first, if this cannot be done, use ext2. 
> > Recent versions of mount understand this syntax, but yairds' postinst
> > barfs on it:
> 
> Indeed, yaird is too stupid in parsing this.
> 
> Erik, upstream maintainer, is listening here as well, and I hope he can
> quickly extend the parser to handle this and "auto" which fails
> similarly.
> 
> Until fixed, the obvious workaround is to change to only use one of the
> options.
> 
> Alternatively you can try using initramfs-tools instead of yaird:
> Install initramfs-tools, and either uninstall yaird or change priority
> of ramdisk tools by adding the following to /etc/kernel-img.conf (in a
> single line):
> 
> ramdisk
> = /usr/sbin/mkinitrd /usr/sbin/mkinitramfs /usr/sbin/mkinitrd.yaird

Jonas, Erik,

Is there a way to bypass this check by providing the info about the root
filesystem directly ?

In general, it could be a solution for this and other cases like the moving
raid array of Dan to be able to bypass all checks with hand-written options
written to a configuration file.

Friendly,

Sven Luther