Joel Liu's Library tagged Linux →  View Popular, Search in Google

Figures 1 through 5 picture the features and operation of Screen. Looking at Figure 1,   assume that you have used SSH to log in to a remote host. Initially, you have your   original shell on your local host (say, your laptop or desktop) and a remote shell. As   usual, you can use the remote shell to run commands on the remote host; output is   encrypted and sent over the SSH connection to your local shell. (In the figures, blue   highlights the shell output that is currently visible.) As lamented above, if your local   shell or the remote shell or the connection between the two is terminated, the   remote shell is terminated, taking your work to the big bit bucket in the sky.

Hard links are created with the ln command. For example, the following would create a hard link named hlink1 to a file named file1, both in the current directory (i.e., the directory in which the user is currently working): 

  

 

 ln file1 hlink1 

 

  

 When a hard link is created, there is no obvious indication that it is any different from any other file. That is, hard links appear to be files of the same type as their target files (i.e., the files to which they are linked) when they are viewed with commands such as ls (i.e., list) and file (which is used to determine the type of any specified files). Likewise, when viewed in a GUI (graphical user interface), the icons for hard links are identical to those for their target files. 

  

 That the initial name of a file and all hard links to that file all share the same inode can be clearly seen by using the ls command with its -i (i.e., inode) option. Thus, for example, the following would show that the inode numbers of file1 and hlink1 from the above example are identical: 

  

 

 ls -i file1 hlink1

The rest of this section covers the scope of the kernel development process

and the kinds of frustrations that developers and their employers can

encounter there.  There are a great many reasons why kernel code should be

merged into the official ("mainline") kernel, including automatic

availability to users, community support in many forms, and the ability to

influence the direction of kernel development.  Code contributed to the

Linux kernel must be made available under a GPL-compatible license.

Section 5 talks about the process of posting patches for review.  To be

taken seriously by the development community, patches must be properly

formatted and described, and they must be sent to the right place.

Following the advice in this section should help to ensure the best

possible reception for your work.

Linux 2.6.0 has made significant improvements in the processor scheduler in the 2.6.0 release. Not only are processes scheduled more efficiently, but the scheduler has been redesigned to be more scalable when the number of processes in a machine are increased. In 2.4, the  scaling is not as prominent.

The hackbench test is a benchmark for measuring the performance, overhead, and scalability of the Linux scheduler. Created by Rusty Russell, it uses client and server processes grouped to send and receive data in order to simulate the connections established for a chat room. Each client sends a message to each server in the group.

With all the buzz, it shouldn’t come as a surprise that Ubuntu is king, and  while the other distributions are experiencing a downward trend, Ubuntu keeps  growing. It’s also interesting to see that Red Hat is firmly at the bottom when  comparing these five distributions.

One of the greatest features of the Linux® operating system is its networking  stack. It was initially a derivative of the BSD stack and is well organized with  a clean set of interfaces. Its interfaces range from the protocol agnostics,  such as the common sockets layer interface or the device layer, to the specific  interfaces of the individual networking protocols. This article explores the  structure of the Linux networking stack from the perspective of its layers and  also examines some of its major structures.

It can be a little expensive to read analog signals, for example temperature readings or light levels, into your computer. In this article we will show you (1) how Linux can use a computer parallel port and a $10 integrated circuit to read 8 analog channels at 12 bit accuracy, and (2) how we used this to build the Extreme Comfort System (ECS.) 

Interfacing an Analog-to-Digital Converter (ADC) with Linux via the parallel port is fairly simple. There two major areas that need to be addressed - hardware and software. The hardware consists of the parallel port, an ADC, and an analog signal source. The software we programmed in 'C' language.