Control-d key sequence ignored when booting 5.0.7
When booting SCO 5.0.7 and the process reaches the following prompt.
Type CONTROL-d to proceed with normal startup,
(or give root password for system maintenance):
The key sequence control-d is ignored. I have swapped keyboards and the
problem still exists. It used to work but has stopped after installing
an updated EFS from HP. The server is a HP dl380/g4. The EFS currently
installed is 5.64a. Have tried 5.66a and 5.68a. You can key in the
password for root and go into system maintenance mode. Control-d will
work here to exit maintenance mode. If I let the system boot into
multi-user mode the control-d key sequence works here as well.
Has anyone any idea as to what is causing this?
Re: Control-d key sequence ignored when booting 5.0.7
Craig Green wrote:[color=blue]
> When booting SCO 5.0.7 and the process reaches the following prompt.
>
> Type CONTROL-d to proceed with normal startup,
> (or give root password for system maintenance):
>
> The key sequence control-d is ignored. I have swapped keyboards and the
> problem still exists. It used to work but has stopped after installing
> an updated EFS from HP. The server is a HP dl380/g4. The EFS currently
> installed is 5.64a. Have tried 5.66a and 5.68a. You can key in the
> password for root and go into system maintenance mode. Control-d will
> work here to exit maintenance mode. If I let the system boot into
> multi-user mode the control-d key sequence works here as well.
>
> Has anyone any idea as to what is causing this?[/color]
Probably ioctl.syscom
See [url]http://aplawrence.com/SCOFAQ/FAQ_scotec3ioctl_syscon.html[/url]
--
Tony Lawrence
Unix/Linux/Mac OS X resources: [url]http://aplawrence.com[/url]
Re: Control-d key sequence ignored when booting 5.0.7
Tony Lawrence wrote:[color=blue]
> Craig Green wrote:
>[color=green]
>> When booting SCO 5.0.7 and the process reaches the following prompt.
>>
>> Type CONTROL-d to proceed with normal startup,
>> (or give root password for system maintenance):
>>
>> The key sequence control-d is ignored. I have swapped keyboards and
>> the problem still exists. It used to work but has stopped after
>> installing an updated EFS from HP. The server is a HP dl380/g4. The
>> EFS currently installed is 5.64a. Have tried 5.66a and 5.68a. You can
>> key in the password for root and go into system maintenance mode.
>> Control-d will work here to exit maintenance mode. If I let the system
>> boot into multi-user mode the control-d key sequence works here as well.
>>
>> Has anyone any idea as to what is causing this?[/color]
>
>
> Probably ioctl.syscom
>
> See [url]http://aplawrence.com/SCOFAQ/FAQ_scotec3ioctl_syscon.html[/url]
>[/color]
Thank you for the response. I have checked out the link. I will
arrange to test the fix over the weekend.
Re: Control-d key sequence ignored when booting 5.0.7
"Craig Green" <cmgreen@deltalink.com.au> wrote in message
news:%agDe.118$ka6.546@nnrp1.ozemail.com.au...[color=blue]
> Tony Lawrence wrote:[color=green]
>> Craig Green wrote:
>>[color=darkred]
>>> When booting SCO 5.0.7 and the process reaches the following prompt.
>>>
>>> Type CONTROL-d to proceed with normal startup,
>>> (or give root password for system maintenance):
>>>
>>> The key sequence control-d is ignored. I have swapped keyboards and the
>>> problem still exists. It used to work but has stopped after installing
>>> an updated EFS from HP. The server is a HP dl380/g4. The EFS currently
>>> installed is 5.64a. Have tried 5.66a and 5.68a. You can key in the
>>> password for root and go into system maintenance mode. Control-d will
>>> work here to exit maintenance mode. If I let the system boot into
>>> multi-user mode the control-d key sequence works here as well.
>>>
>>> Has anyone any idea as to what is causing this?[/color]
>>
>>
>> Probably ioctl.syscom
>>
>> See [url]http://aplawrence.com/SCOFAQ/FAQ_scotec3ioctl_syscon.html[/url]
>>[/color]
> Thank you for the response. I have checked out the link. I will arrange
> to test the fix over the weekend.[/color]
I had the problem on 5.0.6 as you described it. The removal of the file did
the trick.
Ron