#16500: app_server: Option to operate Haiku without app_server
---------------------------------+----------------------------
Reporter: CodeforEvolution | Owner: axeld
Type: enhancement | Status: new
Priority: low | Milestone: Unscheduled
Component: Servers/app_server | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
---------------------------------+----------------------------
Comment (by pulkomandy):
Hi,
Well consoled is still here and still works.
Let's check your suggestions:
When app_server crashes, all applications using BApplication will run into
major problems. Dropping to a bash shell isn't better than dropping to the
Debugger CLI. Really recovering from an app_server crash would be managing
to restart the app_server and reconnect all apps to the new one. Or,
ideally, app_server should not crash.
For black screen problems, the failsafe video driver (VESA or framebuffer)
will work fine.
For debugging graphics drivers, consoled is useless because it needs a
working display. If app_server put you in a "black screen" state, consoled
will not know how to fix that. Like KDL, it uses the already set up
framebuffer.
For debugging app_server and graphics card drivers, you can just ssh into
Haiku from another computer. This way you can debug without a working
display. Likewise for architectures without graphics output: your problem
is not app_server there (you could use it in remote mode for example). And
consoled will not help since its job is to have a console on screen, and
you have no screen.
So, just use ssh and bash, it will be more helpful.
Moreover, Haiku is a desktop operating system meant to be easy to use.
That is not what consoled achieves. It's OK as a debugging tool in some
rare cases (ssh makes more sense in 90% of cases), but that's about it. So
I don't see the point in making this supported.
--
Ticket URL: <https://dev.haiku-os.org/ticket/16500#comment:1>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
