-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 25 Nov 2005 17:57:35 +0000 Martin Michlmayr <[EMAIL PROTECTED]> 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. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh2mmn7DbMsAkQLgRAgLsAKCigGe/vXrPJhDmJUXUZ5mYqa+32wCdF7if ajycsZYL9uieqXObbOPccPU= =yRAQ -----END PGP SIGNATURE-----
