On Sat, Jun 01, 2019 at 09:38:38AM +0000, Fungi4All via artix-general wrote:
> On Saturday, June 1, 2019 7:23 AM, Javier via artix-general <artix-general at artixlinux.org> wrote:
> > Thak you all. I made my mind I really don't need autologin. It's enough if the init always finishes on VT1, and I can auto-start X there. I have no clue if openRC always start on VT1, but it seems systemd on Arch does, though not sure if because of this available by default on Arch, but I bet there might be a way to ensure that if not.
> In general most distributions activate tty1 at least, most have many others.
> Ctrl-Alt-F(1,2,3,4,5,6) switches between ttys
> For reasons I've never cared to find out (probably Ruben knows, he is the X-man :) X starts (it is directed to) at a different tty than the one starting it. So you can be at tty4 and type startx (if setup to start this way and not already running) and X will start at tty7, in other systems it may be setup to start on tty3, etc.
> I don't know if this is the reason or not, but let's say X freezes up, no keyboard no mouse working or anything. You may still flip back to tty1 and either Ctrl-Z if it is where X was started and diagnose it or kill it all together. This is where htop is handy instead of a gui-task manager that is frozen.
> > Thanks !
X opens on a display which is usually assinged to tty09? or 12 or
The tty need open permisions if you chose to start X on the command
there is a built in networking component to this as well
XINIT(1) General Commands Manual XINIT(1)
xinit - X Window System initializer
xinit [ [ client ] options ... ] [ -- [ server ] [ display ] options
The xinit program is used to start the X Window System server and a
first client program on systems that are not using a display manager
such as xdm(1) or in environments that use multiple window systems.
When this first client exits, xinit will kill the X server and then
If no specific client program is given on the command line, xinit will
look for a file in the user's home directory called .xinitrc to run as
a shell script to start up client programs. If no such file exists,
xinit will use the following as a default:
xterm -geometry +1+1 -n login -display :0
If no specific server program is given on the command line, xinit will
look for a file in the user's home directory called .xserverrc to run
as a shell script to start up the server. If no such file exists,
xinit will use the following as a default:
Note that this assumes that there is a program named X in the current
search path. The site administrator should, therefore, make a link to
the appropriate type of server on the machine, or create a shell script
that runs xinit with the appropriate server.
Note, when using a .xserverrc script be sure to ``exec'' the real X
server. Failing to do this can make the X server slow to start and
exit. For example:
An important point is that programs which are run by .xinitrc should be
run in the background if they do not exit right away, so that they
don't prevent other programs from starting up. However, the last long-
lived program started (usually a window manager or terminal emulator)
should be left in the foreground so that the script won't exit (which
indicates that the user is done and that xinit should exit).
An alternate client and/or server may be specified on the command line.
The desired client program and its arguments should be given as the
first command line arguments to xinit. To specify a particular server
command line, append a double dash (--) to the xinit command line
(after any client and arguments) followed by the desired server com-
Both the client program name and the server program name must begin
with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines. This makes
it possible to add arguments (for example, foreground and background
colors) without having to retype the whole command line.
If an explicit server name is not given and the first argument follow-
ing the double dash (--) is a colon followed by a digit, xinit will use
that number as the display number instead of zero. All remaining argu-
ments are appended to the server command line.
Below are several examples of how command line arguments in xinit are
xinit This will start up a server named X and run the user's .xini-
trc, if it exists, or else start an xterm.
xinit -- /usr/bin/Xvnc :1
This is how one could start a specific type of server on an
xinit -geometry =80x65+10+10 -fn 8x13 -j -fg white -bg navy
This will start up a server named X, and will append the given
arguments to the default xterm command. It will ignore .xini-
xinit -e widgets -- ./Xorg -l -c
This will use the command .Xorg -l -c to start the server and
will append the arguments -e widgets to the default xterm com-
xinit /usr/ucb/rsh fasthost cpupig -display ws:1 -- :1 -a 2 -t 5
This will start a server named X on display 1 with the argu-
ments -a 2 -t 5. It will then start a remote shell on the
machine fasthost in which it will run the command cpupig,
telling it to display back on the local workstation.
Below is a sample .xinitrc that starts a clock, several terminals, and
leaves the window manager running as the ``last'' application. Assum-
ing that the window manager has been configured properly, the user then
chooses the ``Exit'' menu item to shut down X.
xrdb -load $HOME/.Xresources
xsetroot -solid gray &
xclock -g 50x50-0+0 -bw 0 &
xload -g 50x50-50+0 -bw 0 &
xterm -g 80x24+0+0 &
xterm -g 80x24+0-0 &
Sites that want to create a common startup environment could simply
create a default .xinitrc that references a site-wide startup file:
Another approach is to write a script that starts xinit with a specific
shell script. Such scripts are usually named x11, xstart, or startx
and are a convenient way to provide a simple interface for novice
xinit /etc/X11/xinit/site.xinitrc -- /usr/bin/X -br
DISPLAY This variable gets set to the name of the display to
which clients should connect.
XINITRC This variable specifies an init file containing shell
commands to start up the initial windows. By default,
.xinitrc in the home directory will be used.
.xinitrc default client script
xterm client to run if .xinitrc does not exist
.xserverrc default server script
X server to run if .xserverrc does not exist
X(7), startx(1), Xserver(1), Xorg(1), xorg.conf(5), xterm(1)
Bob Scheifler, MIT Laboratory for Computer Science
X Version 11 xinit 1.3.3 XINIT(1)
> We are learning, different pace, different paths, different start points, nobody can possibly know it all. I encourage you to use the forum more, more people active around the globe there that you can get advise most likely sooner than here on the list.
> Fungalnet (sysdfree.wordpress.com)
> artix-general mailing list
> artix-general at artixlinux.org
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
Being so tracked is for FARM ANIMALS and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013
More information about the artix-general mailing list