How can I quit the OK prompt?
mark
After rebooting, the prompt is still there.
How do I get now out of the prompt?
Thanks.
Mark
Bernd Haug
roman
If you want to boot ...
go RET
If you want to get back where you left
Mr. Johan Andersson
Im not quite sure I follow you here...
You press STOP-A and you get to the ok> prompt
this is just as it should
Then you reboot and the prompt is still there?
HOW do you reboot?
Did you just switch the power off and on?
Did you type boot and hit return?
if you just flicked the power,chances are that your auto-boot? environment
variable is set to false
if it doesnt boot when you type boot and hit return, your boot-device
might be specified wrong...
if a simple boot, i.e.
ok> boot
doesnt run, then what does it return?
give us...
ok> printenv
and
ok> probe-scsi
or
ok> probe-ide
depending on system
/Johan A
mark
>> How do I get now out of the prompt?
>
> boot RET
will this command reboot my workstation *again*?
Mark
jdh13
setenv auto-boot? true
reset-all
Bernd Haug
> will this command reboot my workstation *again*?
Given your question, I assumed that you had not started an OS after the
"reboot" (I think you meant reset) -- if you had actually booted an OS
you should see a login prompt, not the ok prompt.
What I would guess from the symptoms you described is that you went to
initstate 0 (go to firmware), as opposed to 5 (power off) or 6 (reboot).
At that state, boot should reset your hardware, initialize the RAM and
boot. So yes, in a way it will reboot again; as I understand you haven't
booted at all so far in that you haven't started an OS.
I hope I didn't misunderstand you; and I hope I'm not confusing you.
BTW - if you want access for a large and quick collection of man pages
of many systems (including Solaris up to 9, very useful while your
Solaris box is down), you can find it at
http://www.freebsd.org/cgi/man.cgi
E.g., there's a nice description of runlevels in the manpage of
init(1M). If you run Solaris 10 normally, you might also want to search
for the manpage of svcadm and read about milestones, which are in some
senses "the new runlevels".
Oh, and finally, if you meant just turning the system off once you're at
the ok prompt (which is really how you can "quit" it, otherwise it's just
how the box reacts to not having an OS running), just do a "power-off"
(this will only work if you have a keyboard with a power-on button, if you
don't, you'll have to switch the machine off on the case).
lg, Bernd
Richard B. gilbert
What leads you to believe that your workstation rebooted?
Normally, rebooting brings up the GUI desktop. I suppose it's possible
for a system to drop to the ok prompt spontaneously but I can't think
what might do it.
mark
1. Stop-A
2. Ok prompt> boot
3. WS reboots
4. I log in
5. OK prompt still there.
What can I do to turn it off????
Mark
Tony Curtis
How can you login if you're still at the "ok" prompt?
No Solaris is running at this point.
You're sure the shell prompt isn't an "ok" as well?
mark
> How can you login if you're still at the "ok" prompt?
> No Solaris is running at this point.
The ok prompt pops up when I open a terminal window and log in.
su - myuser
password
then on the ok prompt:
"workstation#147: su myuser succeded for xxx on /dev/pts/13"
How do I turn off that damn thing?
Mark
hume.sp...@bofh.ca
> The ok prompt pops up when I open a terminal window and log in.
Someone has changed your shell prompt to "ok" on your workstation... this
strikes me as perhaps a lame joke, or just foolish administration.
What does "echo $SHELL" tell you?
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
hume.sp...@bofh.ca
> then on the ok prompt:
>
> "workstation#147: su myuser succeded for xxx on /dev/pts/13"
Okay, I've re-read this, and now I'm even more confused, and I think the
others are, too.
If you've pressed stop-A to get to the OpenBOOT PROM, then you've STOPPED
the operating system, and it's not possible to 'su' to anything.
When you open this "terminal", what are you running? Are you at the
graphical desktop?
Mr. Johan Andersson
On Tue, 27 Feb 2007, mark wrote:
Oo, I guess he has X up and the console is running behind, I've seen this
happen a long time ago, quite annoying when the whole X scrolls up because
of the console messages being written on the screen at the same time as X
is running... I assume he has his console pointed at the wrong device...
Dont remember how I got around that, belive I just started a console
window :-) and that took the output... it was many years ago...
/Johan A
Bernd Haug
> Normally, rebooting brings up the GUI desktop. I suppose it's possible
> for a system to drop to the ok prompt spontaneously but I can't think
> what might do it.
I think you can set a mode where a panic leaves you at ok after syncing;
but then you see a lot more on the screen except ok. ;-/
lg, Bernd
Rainer Beushausen
xterm -C should capture the console output as a workaround.
Rainer
tew...@gmail.com
This isn't just a case of syslog logging to the screen?
First, the user logs in and gets a prompt. Then syslog logs the
message to logged in users (default behavior in old versions of
solaris?) This gets appended to whatever's on the terminal, in this
case, his prompt. Hitting enter will supply the user with a fresh
prompt.
This behavior (logging to the screen) can be changed in /etc/
syslog.conf :
>From syslog.conf(4)
The action field indicates where to forward the message.
Values for this field can have one of four forms:
o A comma-separated list of usernames, which indicates
that messages specified by the selector are to be writ-
ten to the named users if they are logged in.
o An asterisk, which indicates that messages specified by
the selector are to be written to all logged-in users.