> Date: Tue, 05 Apr 2016 15:41:16 +0100 > From: [email protected] (akhiezer) > > > From: "Gerhard Gedigk" <[email protected]> > > Date: Tue, 5 Apr 2016 13:27:33 +0200 > > . . > > I need initrd to launch udev so early so I can use the symlinks > > in /etc/fstab . With init and 10udev it is too late. > > > > Alarm bells - in-the-mix are initrd, earlier-than-usual(?) udev, > symlinks in fstab, .... . Keep it simple first? > > > Assume for now that your devices beyond sd{a,b} _are_ ~randomly > assigned device-names. > > > Then how are you going to specify the new-disk lfs79 ? > . . > > (If necessary, since you currently can't boot lfs79, then boot lfs77 > (or mint/whatever), temp-mount the relevant lfs79 partition(s), > and get the materials that way - usual stuff.) > > > Can you try doing: > == > * copy the lfs79 kernel+initrd to the lfs77 boot area. > * add a menu entry to the grub.cfg that you posted earlier, that > refers to the lfs79 kernel+initrd in the lfs77 boot area; but for > 'root=', specify the relevant lfs79 uuid. . . >
For debugging/testing here, ideally if possible, at some point it may be a good idea to compile an lfs79 kernel that does not use an initrd. Boot e.g. lfs77, mount the relevant lfs79 partns, bind-mount /dev &c (into the lfs79 tmp-mnt area) as nec from lfs77, chroot into the lfs79 area, compile a 'huge' kernel (ie as much built-in as possible - cf e.g. 'allyesconfig' ), copy it to lfs77 boot area, and add an entry to same grub area that is used for lfs77 . akh -- -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
