1, file system
No matter how many partitions, the entire file system is a complete tree structure. The most common catalogs are:
(1) / usr: Store various application files. Where use of / usr / local to store software installed
(2) / var: Used to store all data files
(3) / proc: The file inside is used to represent various configurations and status of the system kernel. This piece is not a real file system, but various data in memory. Some common system information can be obtained from here. For example, what is memory memory.
(4) / etc: Here is to place all system configuration files. Under normal circumstances, the post-installed software configuration file will not be placed here. Unless you are installing software or deliberately doing this with RPM. I don't like to mix together different software files, so I usually make different software configuration files in their respective directories.
2, common command
Here I list some of the frequently used commands, and the specific usage can be found in the relevant manus page (I hope your English is not as bad).
Vi (must use this very annoying thing, if you succumb, you can choose another editor called Pico, it has a little icon Edit)
HEAD (used to see a long file)
Tail (ibid)
NetStat (see network status)
TAR (unlock .tar.gz compression package)
PS (see process)
Kill (Dry Process)
TOP (see system conditions)
Shutdown (shut down system)
CAT (see file content)
Ping (see network communication conditions)
FTP (transfer file)
MAN (manual)
The above commands are most common, and the basic usage is sure to remember. In fact, each person can remember all the parameters of all commands or commands, remember that several commonly used. Other books.
3, kernel upgrade
If you don't want to adventure, you can skip this part. However, according to my actual experience, the 2.4.x version of the kernel performance is at least 40% of the performance of 2.2.x, or it is worth a try. Now the latest distribution kits have almost a new 2.4 core, but the version number wants to be conservative. Here, my suggestion is when deciding to upgrade any part, you must first look at the so-called "Currect Version Release Note" information, tell you what changes in this version upgrade. If the contents of the change do not involve your current environment or demand, just add some evil door equipment, you must not have to upgrade. In addition: One of Linux's kernel version number is an odd number of non-stable versions, such as 2.3, is an even number of stable versions.
The steps to upgrade the kernel are as follows:
(1) First find the kernel file you intend to upgrade online, the general name is: Linux-2.x.xx.tar.gz, copy this file to / usr / src. (I don't know where to find it? Take a look: http://www.kernel.org, it is best to find .tar.gz format, such as here: http://www.kernel.org/pub/linux/kernel/v2 .x /). The following upgrade example is upgraded from 2.2.18 to 2.5.7 (this is the latest kernel, you don't forget to change the version number using other versions)
(2) Decompression: TAR ZXVF Linux-2.5.7.tar.gz generated a directory: Linux-2.5.7.
(3) Enter / usr / src, use the ls -l command to see there is a connection in the SRC, similar to: Linux -> Linux-2.2.18 / (connection pointing to your current kernel version). First remove this connection (RM Linux), rebuild the connection with the ln -s linux-2.5.7 linux command. I think you will not even have the version number here. (4) Enter Linux-2.5.7 directory, if not the first time to compile this core, it is best to use the command: make mrproperty to delete the .o file, etc., of course, the previously saved configuration is also lost.
(5) Use the command: make menuconfig command to adjust the kernel configuration to accommodate your current environment, remember, do not understand the configuration. The primary task is to adjust the environment of various hardware, such as the SCSI card: SCSI Support / SCSI Low-Level Drivers, don't know the current SCSI card model? It can be found in / proc / scsi. There is also a network card, in the Network Device Support. Don't know the current network card model? Write in this file: /Proc/net/pro_lan_adapters/th0.info or / proc / pci file can also be found. Use the space bar to change the option status in MenuConfig, the previous <*> indicates that the function is compiled in the kernel, mainly running fast. <> Indicates that this feature is not required. Indicates that the function is compiled into a module, which is usually compiled into a module to reduce the size, and the convenience of replacement.
(6) The following things are compared to the program, do: make dep (check the integrity of the file, the process is very complicated)
(7) Make Bzimage accounts cases (really start compiling yeah! I feel this is the most addicted, the screen "", this time you will feel that how many unknown programmers contribute in this complex system What kind of power is
(8) Make Modules (Compiling those marked functional modules or drivers)
(9) Make MODULES_INSTALL (copy the compiled module to the specified location, generally: / lib / modules /. Note: The module of the different version numbers is completely separated in different directories, because Modules is closely related to the kernel, Mixing is easy to cause system crash)
(10) CD /USR/SRC/LINUX-2.5.7/Arch/i386/boot, use commands: cp /usr/src/linux2.5.7/Arch/i386/boot/bzimage /boot/vmlinuz-2.5.7 File BZIMAGE file is changed to VMLinuz-2.5.7 copy to / boot /
(11) cp /usr/src/linux-2.5.7/system.map /boot/system.map-2.5.7
(12) Enter / boot directory, RM system.map
(13) Running the LN System.map-2.5.7 System.map 10-13 in the / boot directory. Two steps must be done each time you recompile.
(14) I started reminding, I hope that you have installed Lilo (otherwise you sing: "God, save me!"), Editorial file: /etc/lilo.conf, do the following editing:
Boot = / dev / sda
MAP = / boot / map
INSTALL = / boot / boot.bprompt
TIMEOUT = 50
LBA32
Default = linux-2.5.7
Image = / boot / vmlinuz
Label = Linux
INitrd = / boot / initrd
Read-only
root = / dev / sda5
Image = / boot / vmlinuz-2.5.7
Label = linux-2.5.7
INitrd = / boot / initrd
Read-only
root = / dev / sda5
The black body part is a followed and modified. In case you don't have LILO, you can only modify the / boot below to point to your new System.map and VMLinuz without modifying LILO. This can also be started, but once problems have, your machine can't start.
(15) Execute the command: LILO (used to update LILO data), pay attention to the result of the output: With the star number is default.
(16) Pray, then the Reboot system is restarted, and the new kernel can be seen with uname -a. If any problems cannot be booted, you need to select the original kernel start in LILO's boot interface, re-change the kernel parameters, adjust the hardware or other configuration after entering the system. Then repeat all the procedures.
