You are not logged in.
Hi everyone,
I don't know about you all, but as I dig deeper into the murky jungles of the inner operating system, I think (for me) more questions arise than are answered. But some of the questions that I storm up I really hate to create multiple threads for, just for the mods to have to clean up, monitor and soon it'll just be forgotten. So I leave this idea up to the mods, but could this thread be kept around to post sort of quick, random questions, that really probably warrant a quick answer or just in general, not worth creating a completely new topic around. Anyway I (obviously) have a few quick picks lined up, so I can get this started:
1. In regards to the display/login manager, why is it up to this piece of software to kickstart everything else in the graphic env? Why is it responsible for starting x11? Isn't X responsible for doing the major foundational graphic creation? Shouldn't it be the very first gui application that's run? The display or login manager, to me, should be just a quick process that's started at boot, to authenticate and pass the user along. I was really surprised to find that ALL graphical processes orignate from the display manager... It just seems to me like Xorg is the bigger fish here, and that it should be the first and 'parent' of all the rest.
Last edited by Horizon_Brave (2015-11-13 19:57:12)
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Xorg, XFree86 and X11 are display servers, which create the graphical environment. This is where "ALL graphical processes originate".
The display manager (= login manager) is the first X program run by the system if the system (not the user) is starting X and allows you to log on to the local system, or network system. It doesn't "kickstart" the graphical environment - that has already happened.
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
I don't know about you all, but as I dig deeper into the murky jungles of the inner operating system, I think (for me) more questions arise than are answered. But some of the questions that I storm up I really hate to create multiple threads for, just for the mods to have to clean up, monitor and soon it'll just be forgotten. So I leave this idea up to the mods, but could this thread be kept around to post sort of quick, random questions, that really probably warrant a quick answer or just in general, not worth creating a completely new topic around.
I disagree.
To quote the great Carl Sagan:
There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand the world. There is no such thing as a dumb question.
Please restrict yourself to a single thread per query.
This allows users with the same question to easily find the answer rather than it being buried away in a random thread.
Also, you don't need a display manager to start X.
Offline
you don't need a display manager to start X.
https://wiki.archlinux.org/index.php/Xi … X_at_login
works on any distro (after you disable the login/display manager).
Offline
https://wiki.archlinux.org/index.php/Xi … X_at_login
works on any distro (after you disable the login/display manager).
...as long as it uses systemd
The $XDG_VTNR variable is not set by sysvinit -- use this instead under sysvinit:
[[ -z "$DISPLAY" && $(tty) == /dev/tty1 ]] && startx
This will `startx` automatically after login to TTY1
Offline
Yeh I think I agree with Head_on_a_Stick on this one. One-issue-per-thread makes it much easier for people who come afterwards to find the help they need.
OTOH I think sometimes there's a case for long megathreads when people are posting hints, links or short bits of code that won't trigger a discussion. Then you can just scroll down looking for the interesting stuff.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
The $XDG_VTNR variable is not set by sysvinit -- use this instead under sysvinit:
[[ -z "$DISPLAY" && $(tty) == /dev/tty1 ]] && startx
thanks for pointing this out.
there was even a bug in systemd recently (but long fixed now) that made me use the latter method...
Offline
Yeh I think I agree with Head_on_a_Stick on this one. One-issue-per-thread makes it much easier for people who come afterwards to find the help they need.
+1
Offline
It is also important to consider the forum search capability, which works far better if there is something relating to your question in the thread title. I use search quite a bit when looking for something specific.
Offline
Ok OK! I concede! Remove this thread then! 8.(
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
LOL no it wil get it's own special place :-)
Offline
Remove this thread then! 8.(
No need for us to delete resolved problems
Please add "[SOLVED]" to the thread title for the benefit of others.
Offline
Ya! All was not lost!
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline