![]() ![]() So do not use gnome-shell or unity or modern things when doing this experiments, or you could mess up your configuration. Notice: modern desktop environments are not designed to run simultaneously, for the same user, in two different consoles. and if you feel really adventurous, you can start a native session on another virtual console (read the other answers) by going to one of them with Ctrl-Alt-F1, loggin in, and startx ~/test (You can have the menu by clicking on the "Xnest" desktop). and you have a 80ies workstation screen: Startx ~/test - /usr/bin/Xnest -ac :1 -geometry 800圆00 As I said, most new systems do not have sensible defaults for startx alone.). Sudo apt-get install xfonts-100dpi xfonts-100dpi-transcoded xfonts-75dpi-transcoded xfonts-75dpiī) write this file somewhere, for example in you home dir, and call it ~/test: #!/bin/bashĬ) Run (notice: startx is normally run with first the client command, then a double dash, and then a server command. Fvwm is a very simple window manager which was very popular back then. Xnest is a graphic server-within-a-server, a kind of server that will open as a window in your normal system. If you want to experiment and the feel the good old times, the best thing is doing the following:Ī) install Xnest and fvwm. Modern systems are thought from the bottom up to have a graphical system running all the time, so no one has probably checked the working of startx for ages - that explains a lot of strange behavior you can have. By default the commands that are run are in ~/.xinitrc file in your home directory, or some generic system file otherwise. Startx basically runs an Xserver (the graphical "driver") and a command which run on it, which is typically a window manager. So when you needed a graphical interface you just started it with startx (2). Most Unix computers were used for scientific computations and simulation in multi-user environments, and the graphic interface running on them would reduce the memory and CPU power available to them. This means that the sshd daemon is pretending to be an X server with display #10, whereas in reality it is forwarding all connections through to your local PC where they reach the real X server.Once upon a time(1), when the memory of the computers was measured in kilobytes and the disks in megabytes, running the graphic interface all the time was considered harmful. It will automatically be set on login, to a value such as localhost:10.0. Note that when using SSH X11 Forwarding, you do not need to set the DISPLAY variable. After this, as soon as the connection is open, just type xterm &, or any other X command. Under Connection->SSH->X11, tick 'enable X11 forwarding' before you start your session. Since you are using PuTTY, an even easier way is to use it's built in X11 forwarding. ![]() I recommend putting the '&' on the end, as that starts xterm in the background and returns your original shell so you can enter more commands if desired. In short, all you had to type was this: $ export DISPLAY=":0.0 It is interpreting the word DISPLAY as the name of the shell you want to use - thus the error message No absolute path found for shell: DISPLAY. It is enough to have the environment variable DISPLAY set and exported (as you have in your first command). You do not need to put the argument DISPLAY after xterm like that.
0 Comments
Leave a Reply. |