First of all, about Linux
1, what is the use of Linux?
First of all, few people use Linux as a desktop system, because the Windows desktop system is good enough. We mainly use Linux as the operating system of the network server. If you and your application meet the following requirements, then you are suitable for using Linux:
* Unwilling to spend money on operating systems and network applications.
* Being condemned by conscience or afraid of taking responsibility for using version D system.
* Want performance similar to that of an expensive system.
* Present a high level in front of users.
* Know a few masters of Linux, or know where to find the answer to the question.
2. Are there many differences between each Linux distribution?
If you used a lot of PCs from the late 1980s to 1995, you should have a good understanding of Linux: it is like a 32-bit preemptive multitasking kernel DOS, but the difference is that it looks like a UNIX. Linux is piled up by many people with wisdom. Novices often ask, "RedHat or Slackware?" . This person also faces hundreds of choices at the same time, which is really a headache. Most Linux distribution packages are actually very simple, almost all of them are the same kernel (possibly different versions), and the difference between external commands and data files is only limited to the storage location in the file system (which leads to some compatibility problems, because specific files cannot be found in some places). In addition, some distribution packages add their own utilities to show their Excellence. In fact, there are not many manufacturers who modify the kernel, because this will keep the official version of the kernel updated. Of course, some embedded system developers have made their own systems based on Linux.
Having a large number of distribution packages is a very annoying problem for Linux. In this respect, I prefer FreeBSD, because it has only one official release version and runs relatively stably. There are too many programmers who can do software for Linux, and there is more information about Linux. Remember: when a person tells you that it doesn't matter which distribution you use, he is an expert.
3. Is it the stuff of Linux amateurs?
Such propaganda has given many people such an impression. In fact, Linux is a serious operating system, which has all the characteristics of all operating systems. Can be used in many serious occasions.
4. Is 4.Linux better than Windows?
The answer here will disappoint you. According to my previous actual test, the performance of version 2.2 Linux kernel is lower than that of windows2000. Fortunately, the core performance of version 2.4 has been greatly improved, which is basically close to Windows2000. However, the complex graphical interface of Windows2000 occupies a lot of system resources.
5. Is 5.Linux more complicated and professional than Windows?
In terms of complexity, Windows2000 is much more complicated than Linux. On the core technology, Windows is also more advanced.
6. Is 6.Linux more reliable?
The reliability of the system should be evaluated from two angles. (1) The reliability of the system itself is similar. The impression that Windwos is not as reliable as Linux is generally believed to come from countless good and bad software in Windows. Of course, the structure of Linux is simpler than that of Windows, and it can also improve the reliability to some extent. (2) From the security point of view, Linux is much higher than Windows for a simple reason: a big tree attracts the wind. In addition, the open source mechanism of Linux makes the discovery and elimination of vulnerabilities very fast. Windows is more bureaucratic. To add here, the most reliable system I have ever used is BSD-like OS, with remarkable reliability and security.
7. Is 7.Linux really free?
Most distribution packages cost very little money to buy. Of course, you can also download it from the Internet. In fact, these distributions may not conform to your application, and usually require some changes and customization to run well. Of course, it costs less than Windows.
Second, Linux installation considerations
Most of the current distribution packages are easy to install and are basically graphical guides. Each distribution package is different and cannot be described one by one. Don't use Linux if you don't know how to install it. The following are just a few points for attention.
1. If you want to mix with Windows, you must install Windows first and then Linux.
2. When partitioning, flexibly decide the partition according to the software to be installed. Generally, there are:/,/root, /usr, /var and swap partitions, among which the types of swap partitions need to be specially selected, and their space is generally twice that of physical memory. The /root partition is used for emergency root, and 64 megabytes is enough.
Of course, for convenience, you can install the distribution package to make software for you. But my habit of installing Linux is to install a minimum system at first, and then install all the compilation tools. The method of installing compilation tools is generally realized through the package management tools you use to distribute packages, which is the most convenient. For example, in TurboLinux, just run /usr/sbin/Turbopkg. Select all options related to development person or gcc in the management tool, which is generally acceptable.
4. lilo must be installed. Otherwise, once there is a partition problem, it will be difficult.
5. If it is mixed with Windows, the system will not get up after installation. You can start with the 98 startup disk and then use FDISK.
/MBR reverts to the primary boot partition to preserve the Windows partition.
After installing the minimum system and a complete compiler, we should get a relatively clean system. On this system, you can download and install various applications.
Third, the basic use
1, file system
No matter how many partitions there are, the whole file system is a complete tree structure. Commonly used directories are:
(1)/usr: used to store various application files. /usr/local is used to store the installed software.
(2)/var: used to store all data files.
(3)/proc: The files in it are used to represent various configurations and states of the system kernel. This block is not a real file system, but all kinds of data in memory. You can get some common system information from here. Such as CPU memory or something.
(4)/etc: This is where all system configuration files are placed. Under normal circumstances, the configuration files of post-installed software will not be placed here. Unless you installed the software with the RPM distribution package, or did it on purpose. I don't like mixing files of different softwares, so I usually put the configuration files of different softwares in their own directories.
2. Common commands
Here I have listed some common commands. Please refer to the relevant manual page for specific usage (I hope your English is not as bad as mine).
Be sure to use this thing you hate. If you give in, you can choose another editor called pico, which is a bit like DOS edit.
Title (for reading long documents)
Tail (same as above)
Netstat (see network status)
Tar (Open tar.gz's compressed package)
Ps (view process)
Kill (delete process)
Top (depending on system status)
Shut down (shut down the system)
Cat (see file content)
thump
(depending on network connection)
Ftp (Transfer File)
Manual (manual)
These commands are the most commonly used, so you must remember the basic usage. In fact, everyone can remember all the commands or all the parameters of a command, just remember a few commonly used ones. Other books.
3. Kernel upgrade
If you are not willing to take risks, you can skip this part. However, according to my practical experience, the kernel performance of version 2.4.x is at least 40% higher than that of version 2.2.x, which is still worth a try. Almost all the latest distributions now have a new 2.4 kernel, but the version number wants to be conservative. Here, my suggestion is that when you decide to upgrade any part, you must first look at the so-called "currect"
Version release
Attention "information, which tells you what changes have been made in this version upgrade. If the change doesn't involve your current environment or needs, but just adds some devilish device drivers, you don't need to rush to upgrade. Add: The middle bit of the Linux kernel version number is an odd unstable version, such as 2.3, and the even version is a stable version.
The steps to upgrade the kernel are as follows:
(1) First, find the kernel file you intend to upgrade on the Internet, with the common name of linux-2.x.xx.tar.gz, and copy it to /usr/src. I don't know where to look. Look: /PRO_LAN_Adapters/eth0.info or /proc/pci files can also be found.
. In menuconfig, use the space bar to change the option status, as well as the previous
& gt indicates that this function is not required. Is to compile this function into modules, usually some drivers are compiled into modules, in order to reduce the size and facilitate replacement.
(6) The following things are more procedural, so do it: make.
Dep (checking the integrity of the file, the process is very complicated)
(7) making bzImage
Pay attention to case (compilation has really started! I think this is the most enjoyable, and the screen "crashes". At this time, you will feel that there are many unknown programmers in this complex system.
(8) Manufacturing
Module (compile function module or driver marked as)
(9) Manufacturing
Modules_install (copy the compiled module to the specified location, generally: /lib/modules/
. Note: Modules with different version numbers are completely separated in different directories, because modules are closely related to the kernel, and mixing them together will easily lead to system crash.)
(10) CD
/usr/src/Linux-2.5.7/arch/i386/boot, the command is: cp.
/usr/src/Linux 2 . 5 . 7/arch/i386/boot/bzi mage/boot/vmlinuz-2 . 5 . 7
Rename the file bzImage to vmlinuz-2.5.7 and copy it to /boot/
( 1 1)cp
/usr/src/Linux-2 . 5 . 7/system . map/boot/system . map-2 . 5 . 7
(12) Enter the /boot directory rm.
System.map
(13) run ln System.map-2.5.7 System.map in the /boot directory.
10- 13 Every time you recompile, you have to do two steps.
(14) I began to remind you. I hope you have installed lilo.
Otherwise, you can sing: "God, help me!" " ), edit the file:/etc/lilo.conf.
, make the following edits:
Boot =/dev/sda
map=/boot/map
Install =/boot/boot.b
point out
Timeout =50
lba32
Default value =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
Bold parts have been added and modified. If you don't have lilo installed, you can only modify the connection under /boot to point to your new System.map and vmlinuz.
Without modifying lilo. This can also be started, but once something goes wrong, your machine won't start.
(15) execute the command lilo.
(used to update lilo data), pay attention to the output results: those with asterisks are the default.
(16) Pray, then restart the system and use uname–a.
You can see that the new kernel is working. If there is any problem that can't be booted, you need to select the original kernel boot in lilo's boot interface, change the kernel parameters again after entering the system, and adjust the hardware or other configurations. Then repeat all the previous processes.