using latest genkernel >= 3.11.1, blkid in initramfs don't support LABEL or UUID anymore Reproducible: Always Steps to Reproduce: 1.emerge genkernel >= 3.11.1 2. build initramfs with it : genkernel --disklabel initramfs 3. try blkid inside linuxrc Actual Results: all partitions listed Expected Results: one partition matching LABEL=... or UUID=...
(In reply to comment #0) > Actual Results: > all partitions listed What do you mean by that? Also, please paste - your kernel boot options / grub entry - genkernel call - genkernel.conf used
1. emerge genkernel 2. build initramfs with genkernel --disklabel initramfs 3. append "debug" on the grub entrie 4. boot 5. in busybox (from debug) try blkid LABEL=... (ROOT for me) 6. output is all the partitions :( this is the blkid of busybox and not the stand alone one, i don't know why ... Loux
(In reply to comment #2) > 5. in busybox (from debug) try blkid LABEL=... (ROOT for me) > 6. output is all the partitions :( > > this is the blkid of busybox and not the stand alone one, i don't know why ... Excellent report - I was now able to re-produce the problem: In the initramfs currently /sbin/blkid is a symlink to busybox, whereas blkid of e2fsprogs resides in /bin/. As /sbin is coming before /bin in $PATH, you always get busybox's blkid when running "blkid". I have modified genkernel to copy the blkid binary into /sbin/ now: http://git.overlays.gentoo.org/gitweb/?p=proj/genkernel.git;a=commitdiff;h=81e41d541d2d9acbf8b3f9ab1c51fbe6a6d19942 The command blikd -t LABEL=swap now works for me from the debug shell. Please emerge genkernel-99999 (five nines) to test this patch and report back. If it works for you too, you can have a release 3.4.12.5 in no time.
hello, sounds good for me, you copy blkid (stand-alone) on blkid (busybox) so i works, why don't we remove the config busybox one ? (so no more blkid from busybox if disklabel is set) see you loux
(In reply to comment #4) > why don't we remove the config busybox one ? (so no more blkid from busybox if > disklabel is set) I worry breaking other things, that we may not have thought of. Release 3.4.12.5 just hit the main tree. If you run into problems again, please open a new bug.
