Forum › Forums › General › Tips and Tricks › antiX Base login to Console/TUI
- This topic has 5 replies, 3 voices, and was last updated Apr 21-6:37 pm by seaken64.
-
AuthorPosts
-
April 19, 2019 at 3:17 pm #20569Member
seaken64
My apologies if this topic shows up twice. I did something wrong and I don’t think I actually entered the topic last time. Here goes again.
I’ve been experimenting with both Core and Base versions of antiX-17.4.1. On the Base version I would like to set the default login to the Text User Interface (TUI) and then, when I want to, launch the GUI desktop from command line. I liked that feature of Vector Linux. I could always choose the TUI and then use “startx” to launch the GUI. But I can’t figure out how to do that in antiX. There does not seem to be a section in the wiki or manual that shows me how to do this type of setup. I always get logged in to the GUI in BASE.
How do I set the default login to the console/TUI in antiX Base? And then what do I type at the command line to start IceWM/Fluxbox/JWM window manager?
Thanks for any tips you can share.
Seaken64
April 19, 2019 at 5:50 pm #20575Memberseaken64
::I’ve made a little headway. I figured out how to launch slim, which launches the window manager. But it was a lot like groping around for the light switch in a strange house, like at a condo. Sometimes you get it right and sometimes you turn on the garbage disposal and wake up the baby.
I looked around the file system using mc and found some references to /usr/bin/slim. So I tried entering /usr/bin/slim at the command line. Nothing. Then I tried it again with sudo. It worked! But I am wondering if I am missing anything by launching this way.
If I login at console/TUI and then enter slim, am I bypassing anything that is normally processed in the normal initialization script? I can’t get SeaMonkey to launch, but I got Firefox launched and am using that to make this post. I also launched and closed LXTerminal. It seems normal. But I don’t really know what I am doing.
Now I have to figure out what config file setting tells the system to start with the console/TUI. If I don’t enter a “3” on the boot line I still go directly to IceWM.
Seaken64
April 19, 2019 at 8:24 pm #20581Anonymous
::what config file setting tells the system to start with the console/TUI
Open this file in an editor
/etc/inittab
and (at or about line 5 or 6) this is where the default runlevel is specified.This wiki page provides additional details: https://debian-administration.org/article/212/An_introduction_to_run-levels
April 21, 2019 at 2:43 am #20613Moderator
caprea
::And then what do I type at the command line to start IceWM/Fluxbox/JWM window manager?
AFAIK, the right command should be something like
startx /usr/local/bin/desktop-session rox-fluxboxApril 21, 2019 at 6:34 pm #20622Memberseaken64
::what config file setting tells the system to start with the console/TUI
Open this file in an editor
/etc/inittab
and (at or about line 5 or 6) this is where the default runlevel is specified.This wiki page provides additional details: https://debian-administration.org/article/212/An_introduction_to_run-levels
Thank you for that. I could not make that connection. I found the setting in /etc/inittab. What does “inittab” stand for? Many file names have some reason but I would never figure out inittab to change the runlevel.
And thanks for the link. I read lot of stuff on that site. Eventually led me to finally figuring out how to login remotely to antiX both with VNC and X, and SSH in text mode. Good stuff.
Seaken64
April 21, 2019 at 6:37 pm #20623Memberseaken64
::And then what do I type at the command line to start IceWM/Fluxbox/JWM window manager?
AFAIK, the right command should be something like
startx /usr/local/bin/desktop-session rox-fluxboxThank you caprea. I was hoping it would be startx as that was what I was used to in Vector. But it doesn’t work for me. It might work if I typed it in as you listed. I haven’t tried that yet. But “slim” works so I will stick with that for now.
Seaken64
-
AuthorPosts
- You must be logged in to reply to this topic.