1/9/2024 0 Comments Startx vs xinit![]() You can probably already guess where this is going. It’s a one liner which just runs /usr/bin/X with a couple of flags. You’ll find the default file in /etc/X11/xinit/xserverrc. xserverrc, which a user can drop in $ HOME to describe the server startup behavior. xinitrc exists to describe the client side setup, there’s another file. It launches 2 programs - a server (generally X), and a client (or many clients, as described by your. It’s a glorified compiled shell script with some extra signal handling. So how can convince startx to do this for us? startx itself is a wrapper around xinit and performs some modicum of useful setup. All we have to run is our little helper script. #!/bin/bash TTY = $ if ] then printf '=> ERROR: invalid TTY\n' >&2 What if I’m on tty2? Passing vt01 is going to break this - we should pass vt02 in this case. How do we do that? By merely passing the VT we’re current on to xinit.Īnd this just works - you’ll keep your authenticated session, and X is started up according to the contents of $ HOME/.xinitrc. According to upstream, it’s just a matter of convincing xinit (the underlying mechanism in startx) to not allocate a new TTY. If you want to start Xorg at login, please see Start X at login. To start Plasma with xinit/startx, append export DESKTOPSESSIONplasma and exec startplasma-x11 to your. Select Plasma (Wayland) to launch a new session in Wayland. However, if you run startx without parameters, you’ll find that a new terminal is allocated - one where you aren’t authenticated. Select Plasma (X11) to launch a new session in Xorg. When you login on at a getty, you already have an authenticated session. There’s no “ck-session-launch” equivalent, sure, but it isn’t needed. This is for everyone who says that systemd doesn’t work well with startx as far as maintaining an authenticated session. Therefore, if you’re using Arch, stop reading here and update to at least xorg-xinit 1.3.2-3. etc/X11/xinit/xserverrc will start your X session on XDG_VTNR, if the environment variable is set. As Daffy Duck might say to me, "You're despicable.2 Update: Arch Linux now provides this by default. Often they grow quite silent, unsure what to say or think. I also mischievously enjoy watching other people watch me boot my computers. For me that means one less layer of complexity. I'm an old fart and I like booting to console. About 90% of the time that is what I want but 10% of the time I don't want to do that immediately. I wrote my own /usr/local/bin/bash_login script that is sourced by $HOME/.bash_profile and my script prompts if I want to boot into the desktop with startx. I've long grown comfortable with that and to this day still boot all of my Slackware systems to console. Way back then display/login managers were available, but the default was booting to console. There also is a cosmetic reason in that the users would be fully WTF bewildered by logging in at the console and then manually typing startx.Īt home I have been using Slackware for more than 15 years. I'll let others pipe in to help.Īt work I configure the Debian workstations and laptops to use a display/login manager because outside very specific tasks, the users are not command line users. There is much more to distinguish the differences. The common way to do that these days is storing *.desktop files in /etc/xdg/autostart or $HOME/.config/autostart. automatically launching apps at login is a common desire. Whether the desktop is launched from the console or a display/login manager. Some display/login managers support sourcing those files but consult the documentation. Generally, the system and user xinitrc files are used when launching the desktop from the console. Users may override many of those options through a local $HOME/.xinitrc file. The file is sourced from the startx launch sequence. Usually the system /etc/X11/xinit/xinitrc file contains global instructions for creating the graphical environment. With this traditional boot, launching a graphical desktop and X is done through the /usr/bin/startx shell script. In systemd parlance this is called multi-user.target. In traditional parlance, depending on the distro and init system, this was called runlevel 3. In systemd parlance this is called graphical.target.īefore booting into a graphical environment became popular, traditionally Linux systems booted to the console. In traditional parlance, depending on the distro and init system, this was called runlevel 4 or 5. Generally, display/login managers are used when booting into a graphical user environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |