By analyzing the content of the startx command file, it is known that startx mainly sets the location of the X client and X server, and processes the relevant parameters, and finally hands it to xinit for processing. So how can I enter Desktop Environment? Let us analyze the operation of the startx command.

If $HOME/.xinitrc does not exist, it is equivalent to execute: xinit xterm -/usr/bin/X will not enter the Desktop Environment (desktop environment, such as GNOME, KDE, etc.) if $HOME/.xinitrc does not exist or if $HOME/.xinitrc is not set correctly, there is only one xterm and 'X' in front of us Shaped mouse. If $HOME/.xinitrc exists, it is equivalent to execute: xinit $HOME/.xinitrc -/usr/bin/X 2. According to the existence of $HOME/.xinitrc, xinit will run differently. Client program, see later for specific settings. xinitrc file in the directory to be executed as an X client, that is, you can set X to run when you enter X. By default, when we execute the xinit command without any parameters under the CLI, xinit will search for the. They represent the specific path of the program, which must start with/or. The above and are called X client program and X server program respectively. let’s take a look at the usage of xinit command: xinit options] options] It can be seen that xinit initializes X through two levels The X client program and the X server program. The following mainly analyzes the process of xinit to initialize X: 1. The startx command we often use to log in to X also starts X by passing parameters to xinit, that is, xinit is the final start of X. There are two main ways to start X: One is Display Manager, such as XDM, GDM, KDM, this method is to log in through a graphical interface the other is via xinit, which is suitable for character interface login. Search for another thread I made about getting The Ur-quan Masters (Star Control 2) to work for more information on this.Xinit starts the X Window System process. I was able to get past this by adding the argument double dash -nomouse That hid the mouse making it such that I had to move the mouse around until the keyboard worked, but it worked out for me in the end. Which was annoying since the program I was using didn't *use* the mouse. But I had to maneuver the mouse over the window for it to accept keyboard input. Now this worked out fine since that's where the program window was placed anyway. Unfortunately, rather than truly resizing the screen, all this did was limit me to the top left hand portion of the screen (so if I did xres=800 yres=640, it showed the top left 800圆40 area of the screen). My basic solution was to use xinit then specify a path to an xinitrc file in which I set xres and yres to the resolution I needed. Piglet wrote:Please could you write up everything needed to get it working as far as you have? I see lots of information in the thread but it would be good to see enough information about your end-state solution for others to follow. # start my program – when this exits so does X xinitrc in ~mythtv that runs evilwm in the background (apt-get it – it is really minimal) and then starts my program: Those parameters just give it a black root window, turn of vesa screen blanking and make it local only.

Startx -br -nolisten tcp -dpms # the - is two dashes Whatever you are using on the Pi probably has SysV init so you can do something similar in /etc/inittab replacing an existing getty line with mingetty –autologin=mythtv In Ubuntu with upstart that works out to be a file in /etc/init called tty7 with a line in it that readsĮxec /sbin/mingetty –autologin=mythtv tty7 #the - is two dashes Replace mythtv with username of your choice. I have a console autologin using mingetty which you can apt-get. You can set an X display manager to autologin which is point and click easy. My mythtv has been doing that for about 5 years.

Startx vs xinit