Killing Aqua, the GUI, for a while

Question

Level 1

85 points

Killing Aqua, the GUI, for a while

Sorry if this is not the right forum to ask this...

I want to know if it is possible to kill Aqua, the GUI, at will, and use the system running only the CLI.

If possible, can I still use the AirPort card, (or the NIC for that matter) to browse internet using links, for instance? Or killing Aqua drops you on single user mode with no networking at all.

I know there was an option to pass the ">console" user at the login graphical display, but I'm not sure if that is still valid on Tiger.

As usual TIA 😀

PS: to get back to Aqua I type exit, right?

PB 15" @ 1.67 Ghz Mac OS X (10.4.5) Also a (Logic Board) dead 12" dual USB @700 MHz 20 GB HDD

Posted on Mar 27, 2006 9:52 PM

Reply

Answer 1

Camelot

Level 9

58,527 points

Mar 27, 2006 11:01 PM in response to hictio

If you login to the console via the LoginWindow, all normal system services are already up and running by this point, so anything network-wise is already set.

From a command-line perspective, though, you'll be limited to something like Lynx as a browser, unless you're into reading HTML directly.

Reply

Answer 2

hictio Author

Level 1

85 points

Mar 27, 2006 11:20 PM in response to Camelot

Thanks a lot Camelot, but how do I drop to the CLI from Aqua? Is there a command that I have to type on the Terminal, or is there a Ctrl + Alt + Backspace equivalent for Os X?

Reply

Answer 3

hictio Author

Level 1

85 points

Mar 27, 2006 11:26 PM in response to Camelot

[quote]
If you login to the console via the LoginWindow
[/quote]

How do I do this?

[quote]
From a command-line perspective, though, you'll be limited to something like Lynx as a browser, unless you're into reading HTML directly.
[/quote]

I have always prefered elinks

Reply

Answer 4

Mar 28, 2006 2:20 AM in response to hictio

Hi,

To go to the LoginWindow just log out from the Apple Menu...

SiR G.

Reply

Answer 5

Dale Ranta

Level 4

1,660 points

Mar 28, 2006 5:52 AM in response to hictio

At the login window

console

will put you into command line mode

Reply

Answer 6

hictio Author

Level 1

85 points

Mar 28, 2006 6:45 AM in response to SiRGadaBout

Ja ja, thanks, yes I know how to go there, the question was how to go from there to the CLI.

Reply

Answer 7

hictio Author

Level 1

85 points

Mar 28, 2006 6:48 AM in response to Dale Ranta

At the login window

console

will put you into command line mode

I have tried that before, and it did not work... I'll give it another shot, one question, tho, the ">console" is the username? What password do I have to use?
I remember I have tried using my password, using ">console" once again, etc, and nothing worked.

Reply

Answer 8

Bill Scott

Level 6

11,465 points

Mar 28, 2006 7:26 AM in response to hictio

It is incompatable with fast user switching, so log everyone out first.

Then, in the login slot, simply type

<pre>

console

</pre>

and then it switches you to a full-screen console where you are prompted for your own username and password. Your default shell startup files are run. Everything works for networking (I just tried it.) Just no gui.

Reply

Answer 9

hictio Author

Level 1

85 points

Mar 28, 2006 3:05 PM in response to Bill Scott

It is incompatable with fast user switching, so log
everyone out first.

Then, in the login slot, simply type

<pre>

console

</pre>

and then it switches you to a full-screen console
where you are prompted for your own username and
password. Your default shell startup files are run.
Everything works for networking (I just tried it.)
Just no gui.

I'm afraid it is not working... After I type '>console' as my user name (without the single quote marks!), the Aqua Login display vanishes, and it shows a black screen, showing this on the top of the screen:

Mar 28 19:20:24 osiris getty: /dev/console: Operation not supported by device

Then, after a few seconds I get back to the graphical login window.

This is the entry from the log:

Mar 28 19:19:57 osiris loginwindow[7199]: Login Window Started Security Agent Mar 28 19:20:24 osiris getty: /dev/console: Operation not supported by device Mar 28 19:20:24 osiris launchd: getty repeating too quickly on port /dev/console, sleeping Mar 28 19:20:54 osiris /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started

PB 15" @ 1.67 Ghz Mac OS X (10.4.5) Also a (Logic Board) dead 12" dual USB @700 MHz 20 GB HDD

Reply

Answer 10

hictio Author

Level 1

85 points

Mar 28, 2006 8:48 PM in response to hictio

Googling a bit with the error message, I found this recent (March 2 2006) blog entry: Getting >console to work in 10.4

So, it looks like it is no longer working as-is on Tiger.

Reply

Answer 11

reese_

Level 4

1,735 points

Mar 28, 2006 9:18 PM in response to hictio

I was getting the blue screen, and this article said that was due to ARD. After turning off ARD '>console' worked for me (10.4.5 with all current updates).

Reese

Reply

Answer 12

biovizier

Level 5

7,931 points

Mar 29, 2006 11:51 AM in response to reese_

Another thing to try - if your firewall is on, try turning it off then on again.

Reply