LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   initrd.gz multilib vs pure 64 : 5.8 MB vs 4.8 MB (http://www.linuxquestions.org/questions/slackware-14/initrd-gz-multilib-vs-pure-64-5-8-mb-vs-4-8-mb-4175456678/)

burdi01 04-03-2013 06:59 AM

initrd.gz multilib vs pure 64 : 5.8 MB vs 4.8 MB
 
1 Attachment(s)
An initrd.gz generated under current64 with multilib is much bigger (5.8 MB vs 4.8 MB) than one generated under current64 without multilib. Some research shows that the "with" /lib contains some 32-bit libraries, whereas the "without" /lib does not. For the remainder "with" and "without" are identical. The 32-bit libraries have no meaning in the initrd.

/sbin/mkinitrd contains 2 "find /lib /lib64 ... | cp ... $SOURCE_TREE/" constructs. As i?86 and s390 have their libraries in /lib and x86_64 in /lib64 this is a clever way to not have to sense the machine type. But with x86_64/multilib things turn out to be too clever. The attached patch resolves the problem.
:D

T3slider 04-03-2013 01:56 PM

I noticed this as well and have a nearly identical patch working for me. My /boot partition is only so big and will hold 3 kernels+initrds, so when /boot became full (thus creating an incomplete initrd) after going multilib I had to patch it as well. Since multilib is unsupported though I don't know if it's considered a Slackware bug.


All times are GMT -5. The time now is 03:18 AM.