Bug#340759: doesn't honour root=, fails when disk changes from /dev/hda to /dev/hdc

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

On Fri, Nov 25, 2005 at 08:44:38PM +0100, Jonas Smedegaard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Fri, 25 Nov 2005 17:57:35 +0000
> Martin Michlmayr <tbm@cyrius.com> wrote:
> 
> > I installed Debian on /dev/hda2, then moved this disk to the 2nd IDE
> > channel (/dev/hdc), put in another disk as /dev/hda and installed
> > Debian on /dev/hda3 (/dev/hda2 is swap now).  I mounted /dev/hdc2 and
> > fixed /etc/fstab, then I booted from hdc2 but yaird still tried to
> > mount hd_a_2 - and obviously failed.  Booting 2.4 with an initrd
> > generated by initrd-tools works.  yaird should really take the root=
> > parameter into account.
> 
> Yaird is different by design than initrd-tools. By default it generates
> initial ramdisks working only for your current setup.
> 
> I agree that this could be made more flexible, but imagine you moved to
> hde2 instead: Then it would not only be a matter of passing the root
> argument but also to include whatever additional kernel modules needed
> for that other IDE controller.
> 
> The approach working with the yaird logic is to regenerate the ramdisk
> when things change (which is sometimes tricky, I know...)
> 
> 
> So, all in all: I agree this is not great, but disagree that the goal
> of yaird must be to behave exactly like initrd-tools.

Well, i kind of disagree, if the user provides a root= argument, then he
probably knows what he does, and if he is wrong, then too bad for him, but
chances are good that he knows what he was doing :)

Friendly,

Sven Luther