#Startx on boot full#

Start an X session with support for multiple displays. Start an X session at 100 dpi (dots per inch) resolution.

Start an X session at 16 bits color depth. Typically a shell script which runs many programs in the background.Ĭlient to run if the user has no. This variable prevents the X server, if not given the - auth argument, from automatically setting up insecure host-based authentication for the local host.Ĭlient to run. This variable, if not already defined, gets set to $(HOME)/.Xauthority. This variable gets set to the name of the connected clients display. The system-wide xinitrc and xserverrc files are found in the /etc/X11/xinit directory. If command line server options are given, they override this behavior and revert to the xinit behavior. If that is not found, it uses the file xserverrc in the xinit library directory. To determine the server to run, startx first looks for a file called. If command line client options are given, they override this behavior and revert to the xinit behavior. If that is not found, it uses the file xinitrc in the xinit library directory. This mobile payments start-up is competing with credit cards and cash. To determine the client to run, startx first looks for a file called. Why entrepreneurs are flocking to Stanford-originated non-profit incubator StartX. You may need to specify server options with startx to change the color depth, dots per inch, or a different server layout, as permitted by the Xorg server and nf. The special argument ' -' marks the end of client arguments and the beginning of server options. It is often run with no arguments.Īrguments immediately following the startx command are used to start a client in the same manner as xinit. Be quiet, print as little as possible, printing on framebuffer is slow and lock everything in IOwait mode.The startx script is a front end to xinit that provides a somewhat nicer user interface for running a single session of the X Window System. The special argument - marks the end of client. Arguments immediately following the startx command are used to start a client in the same manner as xinit (1). Drop runlevel and manage them manualy (no inittab) The startx script is a front end to xinit (1) that provides a somewhat nicer user interface for running a single session of the X Window System. >fork1 start the other services and load the missing modules like wifi. >fork1 wait 10 second to create the getty (CTRL+F1,F2, etc) >create the necessary env vars and create a process shell >Swtich the SUID/GUID to the corect user (auto login) Replace the DM (KDM/GDM) with a C program that: Strip down the kernel to a monolithic binary (no module, drop the router stack and all uneeded stuff enabled by default) Never spend time without IO, start to load Qt and KDElibs as soon as evertthing else is in the cache. Use a faster but still as flexible as KDE WM like the (great) AwesomeWM

Replace startx with sometinng lighter (loop+wait 0.01 until it is ready to start the WM Use scripts until some daemon are fully loaded (like parsing dmesg and use mknod to do udev job until the boot process is over, as udev is the slowest of them all. I start useless services after complete boot, Using xfbdev was a bit faster to boot and Qt performances were good, but GTK apps fail to run at decent speed.

#Startx on boot full#

I can down to 7 second to full boot and 10 to X on a 5400rpm hard drive.