In: Categories » Computers and technology » Linux Commands » X offers the ability to display content on other hosts
In Linux tutorial 1, I said that X offers the ability to display content on other hosts’ screens. This makes it possible to log in to a server that has a special program on it and have the display redirected to the screen in front of you. Allowing this to happen is a two-step process. The first step is telling your machine that it should allow connections from another host for X displays. This is done with the xhost command:
[michael@workbox michael]$ xhost +ungerer
where ungerer is the name of the host you want to allow X displays to come from in addition to your own host. Now that you have allowed ungerer to display to your host, log in to ungerer, and set your DISPLAY environment variable like so:
[michael@ungerer michael]$ DISPLAY="workbox:0"; export DISPLAY
This will redirect all X displays to the host workbox. If you have two hosts to try this with, an easy test to see if it worked is to start a web browser on the remote host and watch it display its content on your host. Neat trick, isn’t it? Once you are done with whatever work is required to allow other hosts to display to your screen, you need to explicitly disallow future connections like so:
[michael@workbox michael]$ xhost -ungerer
If you want to disallow everyone, you can use the following shortcut:
[michael@workbox michael]$ xhost -
CAUTION
Issuing the command xhost + is dangerous because it allows anyone to connect to your machine and display things on it. While this most often leads only to practical jokes, the potential for something more serious to happen is there. Be sure to specify from which hosts you allow X connections, and remember to undo it when you are done.
Mail Preferences: mail, pine, and mutt
Like everyone else, Linux folk need to read their e-mail. And as you can imagine, you have plenty of choices as to how. Although there are many GUI-based POP mail readers, this module covers command-line tools.
The one tool that you will always be able to find is called—you guessed it—mail. Simply run mail from the command line like so:
[michael@workbox michael]$ mail
and you’ll see what mail you have available to read. Because this tool does not require any screen formatting, it is well suited for those instances where you are troubleshooting a host so broken it has no terminal control. To exit the mail program, type q and press ENTER. If you want more information about mail, check out its man page. As you’ll see, for a tool that looks very simple, it actually offers quite a bit of capability. Another popular tool is pine, which actually takes control of your terminal window and makes the display look much nicer. Being a fully menu-driven program where all of your options are always listed on a menu in front of you, pine tends to be a very popular choice for people new to UNIX. From a practical point of view, pine is ideal for communicating with people who use all sorts of other mail tools, since it understands all of the popular standards in use today (such as MIME attachments). The pine program also offers a very powerful filing system with which you can archive your mail easily and find it again at a later date. My personal favorite mail tool is mutt. To quote mutt’s author, “All mail clients suck. This one just sucks less.” mutt is another tool that looks simple on the outside but offers a wealth of capability. Unlike pine, mutt is much less menu-oriented. For folks who are used to the UNIX environment, this is a very welcome feature because it allows for very efficient use. Doubly useful is that mutt offers excellent memory management and can therefore handle extremely large mailboxes. More than once, I’ve used mutt to clean up someone’s mailbox that Outlook choked on. ftp Linux offers a very handy command-line version of the FTP client. Anyone used to theWindows version of the FTP client that runs under command.com will feel right at home with this, since theWindows version adopted the standard commands in use by the UNIX community since the late 70s. To start the FTP client, simply run ftp at the command line like so:
[michael@workbox michael]$ ftp remotehostname
where remotehostname is the name of the host that you would like to FTP to/from.
legal notice
Our website is not responsible for the information contained by this article. Web-articles is a free articles resource.
Suggestion: If you need fresh, daily updated content for your website, feel free to use our service. Click here for more information.
Useful tools and features
If you like this article (tutorial), please link to it from your web page using the information above.
related articles
Reviewing Linux File System Standards One argument you hear regularly against Linux is that there are too many different distributions, and that multiple distributions lead to fragmentation. This fragmentation will eventuate in different, incompatible Linux versions. This is, without a doubt, complete nonsense that plays on “FUD” (Fear, Uncertainty, and Doubt). These types of arguments usually stem from a misunderstanding of the kernel and distributions. However, the Linux community has realized that it h...
2. Linux is built upon the foundation of file systems
File Systems Linux is built upon the foundation of file systems. They are the mechanisms by which the disk gets organized, providing all of the abstraction layers above sectors and cylinders. In this module, you’ll learn about the composition and management of these abstraction layers supported by the default Linux file system, ext2, and its more robust counterpart, ext3. This module covers the many aspects of managing disks. This includes creating partitions, establishing file systems, automating the process ...
3. Mounting and Unmounting Local Disks
Linux’s strong points include its flexibility and the way it lends itself to seamless management of file locations. Partitions are mounted so that they appear as just another subdirectory. Even a substantial number of file systems look, to the user, like one large directory tree. This characteristic is especially helpful to the administrator, who can relocate partitions to various servers but can have the partitions still mounted to the same location in the directory tree; users of the file system need not know abou...
4. The fsck tool short for File System ChecK
Using fsck The fsck tool, short for File System ChecK, is used to diagnose and repair file systems that may have become damaged in the course of daily operations. Such repairs are usually necessary after a system crash in which the system did not get a chance to fully flush all of its internal buffers to disk. (Although this tool’s name bears a striking resemblance to one of the expressions often uttered after a system crash, that this tool is part of the recovery process is strictly coincidence.) Us...
5. The process of adding a disk under Linux on the Intel
Adding and Partitioning a Disk The process of adding a disk under Linux on the Intel (x86) platform is relatively easy. Assuming you are adding a disk that is of similar type to your existing disks (e.g., adding an IDE disk to a system that already has IDE drives or adding a SCSI disk to a system that already has SCSI drives), the system should automatically detect the new disk at boot time, and all that is left is partitioning it and creating a file system on it. If you are adding a new type of disk (...
6. With the partitions created you need to put file systems on them
Syncing disks. WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information. [root@tedford /root]# If you needed to write an /etc/fstab file yourself for this configuration, it would look something like this: /dev/hdb1 / ext3 defaults 1 1 /dev/hdb2 swap swap defaults 0 0 /dev/hdb3 /usr ext3 defaults 1 2 /dev/hdb5 /home ext3 defaults 1 2 /dev/hdb6 /var ext3 defaults 1 2 /dev/hdb...
7. Mounting NFS partitions works much the same way as mounting local partitions
Mounting NFS Partitions Mounting NFS partitions works much the same way as mounting local partitions. The only difference is in how the partition is addressed. On local disks, partitions are addressed by their device name, such as /dev/hda1. In NFS mounts, partitions are referenced by their hostnames and export directories. Thus, if the server named ungerer is allowing your host to mount the directory /export/SL1200/MK2 and you want to mount this to /projects/topsecret1, you would use this command:...
8. Using autofs to mount partitions across the network
Starting the autofs Service Because the way you’re using autofs to mount partitions across the network relies on NFS, before using it you’ll need to be sure you can do normal NFS mounts. Once you have this working, just make a simple change to your startup scripts to deploy the autofs service. The easiest way to do this is to run the redhat-config-services utility to enable the daemon. Simply start the configuration tool and mark the autofs check box as shown. If you need to start autofs by hand...
9. Configuring Individual Partitions on Linux machines
Managing Quotas In any multiuser environment, you’re bound to run across users who—either refusing to play fair or because they’re oblivious to common courtesy—practice the fine art of disk hogging, taking up more than a reasonable amount of disk space. This problem can be managed in several ways. The first and most obvious solution is to beg and plead. This rarely works. The second approach is peer pressure: You regularly and publicly post the amounts of disk space being hogged by these users. If peop...