On Thu, Oct 24, 2002 at 10:53:43PM +0200, Tzafrir Cohen wrote:
> On Thu, 24 Oct 2002 [EMAIL PROTECTED] wrote:
>
> > Indeed, what were the results of appending init=/bin/sh?
> > Similarily, one can try booting into single user mode and then reconnect
> > the modem.
>
> No point in booting to single-user mode, as the sysetm hangs somewhere in
> the rc.sysinit script.
>
> OTOH, this specific part of the rc.sysinit part could be safely patched
> away, right?
>
This should be answered by who ever has this file. I don't have it.
Maybe you are right. Maybe it can be safely patched away. What does it
do anyway?
Yet being able to point the offending script is a good place to start
looking for the real problem. Just run the commands manually one after
the other. Which brings me to the original poster `what do I do after
booting with init=/bin/sh' question: you start running manually
the scripts that the system runs automatically, until you have reached
the rc.sysinit script. At that point you start running the commands,
rather then the scripts, manually. Of course the whole process should
be done while the modem is attached to the USB bus. If I didn't miss
something essential, one of these commands will make the machine hang,
and then we can start searching why.
However this looks to me too simple. I must have missed something.
--
Shaul Karl, [EMAIL PROTECTED] e t
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
