Re: mkinitcpio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Fri, Mar 2, 2012 at 9:45 AM, Simon Perry <arch@xxxxxxxxxxx> wrote:
> On 02/03/12, Thomas Bächler wrote:
>
> | Actually no. But you can make a backup copy of your old
> | initramfs-linux.img and compare lsinitcpio -a output for the old and new
> | one.
>
> It's a lot of output to parse and diff accurately.

comm -3 <(lsinitcpio /boot/initramfs-linux.img) <(lsinitcpio
/boot/initramfs-linux.img.orig)

(note: `.orig` ;-)

... diff would work too.

> Nevertheless, be glad you didn't bet (even though I provided no counter
> reward).
>
> I've just spent 20 minutes netbooting, mount raid / lvm / luks volumes,
> and getting ext4 back into my initrd.

:-(

i guess you missed the "make a backup copy of your old
initramfs-linux.img" part?  you should have been able to simply edit
you bootloader on the fly, and use the old copy.

> Filesystems hook is necessary if you want to leave MODULES bare.

indeed -- will include all FS modules if used before autodetect, or
only your root device if used after.  if not used at all ... well,
then it won't include squat.

-- 

C Anthony


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux