[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: mkinitrd cleanup questions
- From: Warren Togami <wtogami redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: mkinitrd cleanup questions
- Date: Sat, 01 Dec 2007 12:38:37 -0500
3)
<...>
Adding module dm-mod
Adding module dm-mirror
Adding module dm-zero
Adding module dm-snapshot
Adding module libiscsi
Adding module ata_piix
This initrd uses dynamic shared objects.
Adding dynamic linker configuration files.
/etc/ld.so.conf -> /tmp/initrd.sa4630/etc/ld.so.conf
/etc/ld.so.conf.d/wine-32.conf ->
/tmp/initrd.sa4630/etc/ld.so.conf.d/wine-32.conf
/etc/ld.so.conf.d/qt-x86_64.conf ->
/tmp/initrd.sa4630/etc/ld.so.conf.d/qt-x86_64.conf
/etc/ld.so.conf.d/qt-i386.conf ->
/tmp/initrd.sa4630/etc/ld.so.conf.d/qt-i386.conf
/etc/ld.so.conf.d/mysql-x86_64.conf ->
/tmp/initrd.sa4630/etc/ld.so.conf.d/mysql-x86_64.conf
Running ldconfig
mkinitrd -v of both bash-branch and upstream copies these irrelevant
ld.so.conf.d files into the initrd. These particular files don't seem
to be causing harm, but should we avoid copying this stuff just in case
some arbitrary file might cause unexpected behavior?
Warren Togami
wtogami redhat com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]