Bug#341559: yaird: fails to create initrd

[Maximilian Attems <maks@sternwelten.at>]

On Thu, Dec 01, 2005 at 03:16:04PM +0100, Sven Luther wrote:
> On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote:
> > On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote:
> > > clone 341559 -1
> > > reassign -1 initramfs-tools
> > > stop
> > > 
> > > On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote:
> > > > On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote:
> > > > > just saw your bugreport could you try latest initramfs-tools 
> > > > > from unstable too?  would be cool to get it tested,
> > > > > and report probable boot error (or success)?
> > > > 
> > > > Exactly the same error:
> > > > 
> > > > # dpkg --configure -a
> > > > Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ...
> > > > Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
> > > 
> > > well you are still using yaird.
> > 
> > OK. I thought installing initramfs-tools would suffice, I didn't know
> > that it was an alternativ to yaird, nor that it would not be used by
> > default.
> > 
> > > please try temporarly adding to /etc/kernel-img.conf
> > > ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
> > 
> > OK.
> > 
> > Now it worked! the initrd was created and the boot successful.
> 
> Can you try the same thing also using MODULES=dep (or whatever that option is
> called) in /etc/mkinitramfs/mkinitramfs.conf please ? 

no please dont!!

svenl stop givine bad advices to users.
#341559 is an yaird bug,
the initramfs one was cloned as #341567 and is fixede.

-- 
maks

ps one last time cc 341559, sorry for the noise jonas.