> On Wed, 2005-03-09 at 09:22 -0500, Kwan Lowe wrote:
>> The troubleshooting approach can depend on your distro. You have the right
>> idea in hunting down a bad or missing library. On an RPM distro you could do
>> something like:
>>
>>
>> 1) rpm -qif /sbin/getty
>
> Thanks for your help Kwan. I don't think getty is the culprit here.
> Init says it can't start getty, but only because getty can't start
> (disabled because respawning too fast) because it waiting on another
> broken library. So how do I see what library that is? If I could see
> the full boot message that scrolls past super quickly (not dmesg, and
> not /var/log/messages) I think it might name the problem library. -Eric
Which distro are you running?
Some will have the option to interrupt the boot process (similar to the
Windows confirm mode). You can try pressing "I" when the message pops up, then
confirming each init script. IIRC, this should occur before the rc's start
initializing.
Look in /var/log/boot.log for boot messages. It should get everything after
the kernel initialization.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:25:08 EDT