Sponsored Content
Full Discussion: Questions on CLI and xwindow
Top Forums UNIX for Dummies Questions & Answers Questions on CLI and xwindow Post 302953493 by bakunin on Friday 28th of August 2015 02:18:20 PM
Old 08-28-2015
Quote:
Originally Posted by jamie_123
Hi,

I was not sure about the terminology of the thing that I am about to explain, so it was very difficult to find relevant search results.

I want to use my computer using the ctrl+alt+f1 CLI without using a graphical system. However, at the same time, I would also like to do basic tasks like reading a PDF or open a browser. Switching back to a GUI for these tasks are quite distracting. Is there a way that I can launch windows under the CLI interface and somehow overlay them over the CLI?

Any pointers would be much appreciated.
It is much easier than you are thinking: a UNIX system (your Linux, as i can tell you use, is no exception) has a (theoretically) unlimited amount of possible terminals attached via "serial lines" (see "RS232" about what a serial line is). This is the basic way you connect to a UNIX system.

Your Linux has a graphically-enabled terminal, which you use to connect with locally and which runs an X-Window-system: a so-called "X-Server" (picture it as a driver for your graphic card plus a library with some function calls programs can use, providing graphic primitives like "draw line", "draw rectangle" and so on), a Window Manager on top of it and on top of this are some programs running (like Firefox, Open Office, etc.) which use the services these underlying programs provide. This is what you perceive as "your desktp".

At the same time you can connect to your system also at a more basic level, via classical serial terminals. Your system initially creates 7 of these (virtual) terrminals, between which you can switch with CTRL-ALT-F1 through CTRL-ALT-F7. In the seventh one (reachable by CRTL-ALT-F7) your graphical environment runs.

But terminals can be created on the fly and there are programs running under the X-Window-System (just like our Firefox) which provide such terminals. These programs are called "terminal emulators" (because they emulate a piece of hardware which is out of use today for most people, but still sets the standard of how things work). The most common one is called "XTerm" and they all operate more or less the same way: they create a window, start a shell inside it and when you leave the shell the window closes. You can run several instances of these emulators side by side and this way have several windows with open shells at the same time.

I hope this helps and you got some general knowledge and terminology out of it too. If you still have questions just feel free to ask.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO os5 xwindow

I acciedentaly terminated the x window session on my sco os5 machine. Can somone help me get it going again with out rebooting? Another ? Does anyone know where I can get the VNC version for SCO or can some one help me make changes to the RH version to work for SCO OS5. Thanks. (2 Replies)
Discussion started by: ruizf
2 Replies

2. UNIX for Dummies Questions & Answers

xwindow on old computer

hello at first sorry for my english... i know it isn't good but i hope you can understand me i want to install xwindow on my old pentium133MHz, 49MB ram memory, graphic card - stb horizon64 1MB (with old monochromatic monitor - horizontal 30.6-36.0, vertical 50-90) all this under redhat6.1...... (1 Reply)
Discussion started by: pgas
1 Replies

3. UNIX for Dummies Questions & Answers

XWindow problems

ok, i've got a FreeBSD box, and it doesn't like my monitor. At all. The first time i installed BSD, it wouldn't write the changes. I reformated and reinstalled, and this time it would write, but when i went to load the x server with startx it would go through the load process, but say "no screens"... (4 Replies)
Discussion started by: GirlsHackBetter
4 Replies

4. UNIX for Dummies Questions & Answers

Xwindow display

I am installing Oracle 10g on UNIX. I have prepared the server in various fields. Then when I started installation, one error message came out like this: Could not execute auto check for display colors using command /usr/openwin/bin/xdpyinfo. Check if the DISPLAY variable is set. So I check... (3 Replies)
Discussion started by: duke0001
3 Replies

5. UNIX for Dummies Questions & Answers

Some CLI questions

I use Ubuntu Linux, and I'd like to become more familiar with the CLI. I have these questions: 1) How to remove a directory that is not empty? The only option in man rmdir is -p and that does not do what I need. rm -R needs sudo for some reason. 2) What is a CLI command to make all the files... (3 Replies)
Discussion started by: dotancohen
3 Replies

6. UNIX Desktop Questions & Answers

Where is xwindow start script

I am using a Mandrake spinoff (PCLinux) and would like to have a yakuake terminal started when I launch xwin. Where is the start up script? Thanks JZ (2 Replies)
Discussion started by: jwzumwalt
2 Replies

7. Shell Programming and Scripting

command to exit xwindow

What is the command to exit xwindow when i am in xwindow's terminal. Thanks in advance. (3 Replies)
Discussion started by: uativan
3 Replies

8. UNIX for Dummies Questions & Answers

Help with Xwindow on Linux

Hi, On my PC which is a XP, I have installed SSH client from www.ssh.com company. Linux server is a CentOS version 5. Before using my application, I want to test it and I am trying to get the xclock display back to my window and it's not working. Any idea. #... (4 Replies)
Discussion started by: samnyc
4 Replies

9. Red Hat

XWindow is not enabling !!!

Dear Experts, Our system admin is struggling over a month with an issue regarding xwindow. RHEL 5.4 is our server OS. whenever I export Display with my machine IP and run xclock. It is not working. We are using DHCP. Please tell me what checks and actions should be taken from our sys admin point... (8 Replies)
Discussion started by: saifurshaon
8 Replies

10. UNIX for Dummies Questions & Answers

XWindow Tool

Hi Guys can any one help me in this regard .. I'm using Reflaction and xManager but I want list of another xWindow tools between Unix and Windows .. Pls advice .. (1 Reply)
Discussion started by: top.level
1 Replies
SHUTDOWN(8)						Linux System Administrator's Manual					       SHUTDOWN(8)

NAME
shutdown - bring the system down SYNOPSIS
/sbin/shutdown [-t sec] [-arkhncfF] time [warning-message] DESCRIPTION
shutdown brings the system down in a secure way. All logged-in users are notified that the system is going down, and login(1) is blocked. It is possible to shut the system down immediately or after a specified delay. All processes are first notified that the system is going down by the signal SIGTERM. This gives programs like vi(1) the time to save the file being edited, mail and news processing programs a chance to exit cleanly, etc. shutdown does its job by signalling the init process, asking it to change the runlevel. Runlevel 0 is used to halt the system, runlevel 6 is used to reboot the system, and runlevel 1 is used to put to system into a state where administrative tasks can be performed; this is the default if neither the -h or -r flag is given to shutdown. To see which actions are taken on halt or reboot see the appropriate entries for these runlevels in the file /etc/inittab. OPTIONS
-a Use /etc/shutdown.allow. -t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel. -k Don't really shutdown; only send the warning messages to everybody. -r Reboot after shutdown. -h Halt after shutdown. -n [DEPRECATED] Don't call init(8) to do the shutdown but do it ourself. The use of this option is discouraged, and its results are not always what you'd expect. -f Skip fsck on reboot. -F Force fsck on reboot. -c Cancel an already running shutdown. With this option it is of course not possible to give the time argument, but you can enter a explanatory message on the command line that will be sent to all users. time When to shutdown. warning-message Message to send to all users. The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 dig- its) and mm is the minute of the hour (in two digits). Second, it can be in the format +m, in which m is the number of minutes to wait. The word now is an alias for +0. If shutdown is called with a delay, it creates the advisory file /etc/nologin which causes programs such as login(1) to not allow new user logins. Shutdown removes this file if it is stopped before it can signal init (i.e. it is cancelled or something goes wrong). It also removes it before calling init to change the runlevel. The -f flag means `reboot fast'. This only creates an advisory file /fastboot which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide not to run fsck(1) since the system has been shut down in the proper way. After that, the boot process should remove /fastboot. The -F flag means `force fsck'. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide to run fsck(1) with a special `force' flag so that even properly unmounted filesystems get checked. After that, the boot process should remove /forcefsck. The -n flag causes shutdown not to call init, but to kill all running processes itself. shutdown will then turn off quota, accounting, and swapping and unmount all filesystems. ACCESS CONTROL
shutdown can be called from init(8) when the magic keys CTRL-ALT-DEL are pressed, by creating an appropriate entry in /etc/inittab. This means that everyone who has physical access to the console keyboard can shut the system down. To prevent this, shutdown can check to see if an authorized user is logged in on one of the virtual consoles. If shutdown is called with the -a argument (add this to the invocation of shutdown in /etc/inittab), it checks to see if the file /etc/shutdown.allow is present. It then compares the login names in that file with the list of people that are logged in on a virtual console (from /var/run/utmp). Only if one of those authorized users or root is logged in, it will proceed. Otherwise it will write the message shutdown: no authorized users logged in to the (physical) system console. The format of /etc/shutdown.allow is one user name per line. Empty lines and comment lines (prefixed by a #) are allowed. Currently there is a limit of 32 users in this file. Note that if /etc/shutdown.allow is not present, the -a argument is ignored. FILES
/fastboot /etc/inittab /etc/init.d/halt /etc/init.d/reboot /etc/shutdown.allow NOTES
A lot of users forget to give the time argument and are then puzzled by the error message shutdown produces. The time argument is manda- tory; in 90 percent of all cases this argument will be the word now. Init can only capture CTRL-ALT-DEL and start shutdown in console mode. If the system is running the X window System, the X server pro- cesses all key strokes. Some X11 environments make it possible to capture CTRL-ALT-DEL, but what exactly is done with that event depends on that environment. Shutdown wasn't designed to be run setuid. /etc/shutdown.allow is not used to find out who is executing shutdown, it ONLY checks who is currently logged in on (one of the) console(s). AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
fsck(8), init(8), halt(8), poweroff(8), reboot(8) Juli 31, 2001 SHUTDOWN(8)
All times are GMT -4. The time now is 07:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy