Fedora/RHEL/Centos Won't Init

In the event that a Fedora/RHEL/CentOS box won't perform the init (which comes right after the initial kernel load), don't fret - it can be fixed. Make a note of the missing libraries or executables. Simply boot onto a livecd or rescuecd and chroot into your main installation. Once you're chrooted, just forcefully install any RPM's which might contain files that are missing when the init is loaded.

Forcing the installation of an RPM:

rpm -ivh --force filename.rpm

Listing the files that an installed RPM contains:

rpm -ql rpmname

Listing the files that an RPM file contains:

rpm -qpl filename.rpm

Finding the RPM that contains a certain file/executable:

rpm -qf /usr/bin/filename

Figuring out what might be wrong with files already installed from an RPM:

rpm -V rpmname

Printed from: http://rackerhacker.com/2006/12/28/fedorarhelcentos-wont-init/ .
© Major Hayden 2012.

Leave a Reply

 

  • Welcome! I started this blog as a way to give back to all of the other system administrators who have taught me something in the past. Writing these posts brings me a lot of enjoyment and I hope you find the information useful. If you spot something that's incorrect or confusing, please write a comment and let me know. Drop me a line if there's something you want to know more about and I'll do my best to write a post on the topic.
    -- Major Hayden

    Flattr this