Linux文档：掌握Linux操作系统必备！ (linux documentation)
Linux操作系统正在成为越来越多人的选择，这种免费的、开放源代码的操作系统一方面可以为个人节省一定的开销，另一方面也为企业提供了更安全、更稳定的服务器环境。在掌握Linux操作系统的过程中，Linux文档成为了必不可少的一部分。
什么是Linux文档？
Linux文档是指Linux操作系统中各种指南、手册、教程、参考资料等文件。它们通常是以纯文本形式存在的，也有一些格式化的文档，比如HTML、PDF等。这些文档对于Linux使用者来说非常重要，因为它们可以帮助我们更好地了解Linux操作系统的功能和使用方法，帮助我们解决问题、优化系统等。
Linux文档的种类
Linux文档有很多种类，常见的有以下几种：
1. 用户手册：这些文档包括了Linux的各种使用教程、指南和帮助手册等，帮助用户快速、高效地掌握Linux的操作方法，提供了丰富的命令用法等内容。
2. 系统管理员手册：这些文档主要面向Linux系统管理员，包括了系统管理员优化性能、安全管理、系统备份和还原等方面的指南和手册。这些文档不仅提供了基础知识，还可以帮助管理员快速掌握使用Linux的高级功能。
3. 开发人员手册：这些文档主要是为Linux开发人员提供的，它们包括了Linux的程序接口、开发工具、编程技巧、调试技术等方面的指南。这些手册对于Linux开发人员来说是非常重要的，可以使他们更快速更高效地开发出代码。
4. 参考手册：这些文档主要是提供参考信息和技巧，包括了Linux的命令和系统调用、文件格式规范、网络协议、硬件配置等方面的文档。这些文档的目的是为Linux用户和开发人员提供一种方便的查询资料。
Linux文档的重要性
Linux文档对于掌握Linux操作系统非常重要，它们为Linux用户和开发人员提供了参考和指导。下面列举了一些重要的原因：
1. 帮助解决问题
在使用Linux操作系统时，遇到问题是不可避免的。Linux文档提供了很多解决问题的方法，可以帮助我们找到问题的根源并寻找更佳的解决方案。通过前人的经验和可以使我们更快速地解决问题，从而提高工作效率。
2. 提供操作指南和命令用法
Linux文档提供丰富的操作指南和命令用法，可以使我们更快速地掌握Linux操作技巧。通过阅读文档中的操作指南和命令用法，我们可以更快速地使用Linux系统，提高我们的效率。
3. 优化系统
Linux文档提供了丰富的系统管理和优化指南，可以帮助我们更好地管理和优化我们的Linux系统。这些指南包括了调整参数、优化文件系统、优化内存和磁盘使用等方面的方法，可以使我们的系统更加安全、稳定和高效。
4. 开发指南
Linux文档为开发人员提供了丰富的开发指南，可以帮助开发人员更好地开发Linux应用程序。这些指南包括了开发工具、编程知识和调试方法等方面的内容，可以使开发人员更有效地完成开发工作。
Linux文档对于掌握Linux操作系统非常重要，为用户和开发人员提供了参考和指导。通过阅读和理解Linux文档，可以帮助我们更快速地解决问题、掌握操作技巧、优化系统和完成开发工作。因此，在学习和使用Linux操作系统时，我们必须充分利用并学习Linux文档。
相关问题拓展阅读：
在LINUX中如何加载驱动网卡
实现是通过虚拟网卡实现的。
若想加载USB无启盯线网卡，只需要把这个USB设备和host切断联系，虚歼旁闷拟机的Linux可以自氏弯动的接管这个USB设备。
就在虚拟机下面的状态栏上可以控制设备归谁管理。
直接找好对应的驱动 一般都会有readme 或者install 之类的说明文兄岩毁档来告诉你如何去安装这个网羡备卡驱动的
Linux* Base Driver for the Atheros(R) AR8121/AR8113 PCI-E Ethernet Adapter
==========================================================================
Contents
========
– In This Release
– Building and Installation
– Command Line Parameters
– Additional Configurations
– Known Issues
– Support
In This Release
===============
This file describes the Linux* Base Driver for the Atheros(R) AR8121/AR8113 PCI-E
Ethernet Adapter, version 1.0.0.5 This driver supports the 2.4.x and 2.6.x kernels.
This driver is only supported as a loadable module at this time. Atheros is not
supplying patches against the kernel source to allow for static linking of
the driver. For questions related to hardware requirements, refer to the
documentation supplied with your Atheros(R) adapter. All hardware
requirements listed apply to use with Linux.
Building and Installation
=========================
To build a binary RPM* package of this driver, run ‘rpmbuild -tb
‘. Replace with the specific filename of
the driver.
NOTE: For the build to work properly, the currently running kernel MUST match
the version and configuration of the installed kernel sources. If you
have just recompiled the kernel reboot the system now.
RPM functionality has only been tested in Red Hat distributions.
1. Move the base driver tar file to the directory of your choice. For example,
use /home/username/arl1e or /usr/local/src/枣唯arl1e.
2. Untar/unzip archive:
tar zxf arl1e-x.x.x.x.tar.gz
3. Change to the driver src directory:
cd arl1e-x.x.x.x/src/
4. Compile the driver module:
make install
The binary will be installed as:
/lib/modules//kernel/drivers/net/arl1e.o
The install locations listed above are the default locations. They might
not be correct for certain Linux distributions. For more information,
see the ldistrib.txt file included in the driver tar.
5. Install the module:
inod arl1e =
6. Assign an IP address to the interface by entering the following, where
x is the interface number:
ifconfig ethx
7. Verify that the interface works. Enter the following, where
is the IP address for another machine on the same subnet as the interface
that is being tested:
ping
Command Line Parameters
=======================
If the driver is built as a module, the following optional parameters are
used by entering them on the command line with the modprobe or inod command
using this syntax:
modprobe arl1e
inod arl1e
For example, with two L001 PCIE adapters, entering:
inod arl1e TxMemSize=80,128
loads the arl1e driver with 8KB TX memory for the first adapter and 10KB TX memory
for the second adapter.
The default value for each parameter is generally the recommended setting,
unless otherwise noted.
NOTES: A descriptor describes a data buffer and attributes related to the
data buffer. This information is accessed by the hardware.
media_type
Valid Range: 0-4
auto-negotiate at all supported speeds
only link at 1000Mbps Full Duplex
only link at 100Mbps Full Duplex
only link at 100Mbps Half Duplex
only link at 10Mbps Full Duplex
only link at 10Mbps Half Duplex
Default Value: 0
media_type forces the line speed/duplex to the specified value in
megabits per second(Mbps). If this parameter is not specified or is set
to 0 and the link partner is set to auto-negotiate, the board will
auto-detect the correct speed.
int_mod_timer
Valid Range:
Default Value: 100
This value represents the minmum interval between interrupts controller
generated.
RxMemBlock
Valid Range:
Default Value: 64
This value is the number of receice memory block allocated by the driver.
Increasing this value allows the driver to buffer more incoming packets.
Each memory block is 1536 bytes.
NOTE: Depending on the available system resources, the request for a
higher number of receive descriptors may be denied. In this case,
use a lower number.
TxMemSize
Valid Range: 4-64
Default Value: 8
This value is the number KB of tranit memory allocated by the driver.
Increasing this value allows the driver to queue more tranits.
NOTE: Depending on the available system resources, the request for a
higher number of tranit descriptors may be denied. In this case,
use a lower number.
FlashVendor
Valid Range: 0-2
Default Value: 0
This value standards on vendor of spi flash used by the adapter.
0 for Atmel, 1 for SST, 2 for ST
Additional Configurations
=========================
Configuring the Driver on Different Distributions
Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding
an alias line to /etc/modules.conf as well as editing other system startup
scripts and/or configuration files. Many popular Linux distributions ship
with tools to make these changes for you. To learn the proper way to
configure a network device for your system, refer to your distribution
documentation. If during this process you are asked for the driver or module
name, the name for the Linux Base Driver for the Atheros AR8121/AR8113 is arl1e
As an example, if you install the arl1e driver for two AR8121/AR8113 adapters
(eth0 and eth1) and set the speed and duplex to 10full and 100half, add the
following to modules.conf:
alias eth0 arl1e
alias eth1 arl1e
options arl1e Speed=10,100 Duplex=2,1
Viewing Link Messages
Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages
on your console, set dmesg to eight by entering the following:
dmesg -n 8
NOTE: This setting is not saved across reboots.
Known Issues
============
NOTE: For distribution-specific information, see the ldistrib.txt file
included in the driver tar.
Driver Compilation
——
When trying to compile the driver by running make install, the following
error may occur:
“Linux kernel source not configured – missing version.h”
To solve this issue, create the version.h file by going to the Linux source
tree and entering:
make include/linux/version.h.
Support
=======
For general information, go to the Atheros support website at:
If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to
the issue to
License
=======
This software program is released under the terms of a license agreement
between you (‘Licensee’) and Atheros. Do not use or load this software or any
associated materials (collectively, the ‘Software’) until you have carefully
read the full terms and conditions of the LICENSE located in this software
package. By loading or using the Software, you agree to the terms of this
Agreement. If you do not agree with the terms of this Agreement, do not
install or use the Software.
* Other names and brands may be claimed as the property of others.
下载驱动，解压，然后进入驱动所在目录 运行make install
驱动就是内核模块。加载内核模块就是加载网卡驱动！
如何开始学习Linux内核
首先，你需要知道一个linux的论坛，在这里所有对内核有兴趣的人都会在这里讨论跟内核代码有关的东西，这里我介绍的网站叫：
， 通过网页上的链接，你可以了解很多跟linux有关的东西。注意，网页是英文的，如果英文不好的就只能怪自己没有好好的念书了。
接着，你需要有人指点你如何进行linux内核的学习，在上面论坛的最下面卜返如有一个FAQ的链接，里面详细的给出了linux内核学习的一些资料，后面，我将会把全部的内容翻译出来，给需要的人使用。
网页的原址：
linux内核邮件列表FAQ
在你考虑发送邮件到linux内核邮型启件列表前，请至少阅读第三节。
频繁被问到的问题被划分为若干目录中。如果你觉得有必要也请对这些菜单和Q/A指出不足之处。如果你有额外的信息需要提供，你世握也可以对于任何问题增加你自己的回答。
网站的官方网址为：
（位于美国东海岸）。非常感谢Sam Chesan和David Niemi为FAQ提供了高带宽和高管理质量的linux服务器。下列镜像同样可以使用：
in Sydney, Australia
in Calgary, Canada
in the west coast of the U.S.A
在开始抱怨linux内核的编译问题前，请阅读下面的章节，来确认是否已经有很多人已经注意到同样的问题或者是已经发布了修复的补丁。
目录：
Basic Linux kernel documentation
Contributors and some special expressions
Related mailing lists
Question Index
General questions
Driver specific questions
Mailing list questions
“How do I” questions
“Who’s who” questions
CPU questions
OS questions
Compiler/binutils questions
Feature specific questions
“What’s changed between kernels 2.0.x and 2.2.x” questions
Primer documents
Kernel Programming Questions
Mysterious kernel messages
Odd kernel behaviour
Programming Religion
User-space Programming Questions
Answers
Contributing
基本linux内核文档（稍后，我会将文档进一步翻译，并放在博客上）
下面列出linux内核相关文档，在你发送邮件到linux内核邮件列表前应该进行阅读：
The Linux Kernel Hackers’ Guide, compiled by Michael K. Johnson of Red Hat fame. Includes among other documents selected Q/As from the linux-kernel mailing list.
The Linux Kernel book, by David A. Rusling, available in various formats from the Linux Documentation Project and mirrors. Still being worked on, but explains clearly the main structure of the Linux kernel.
The Linux FAQ by Robert Kiesling has many high quality Q/As.
The Linux Kernel HOWTO by Brian Ward. Fundamental reading for anybody wanting to post to the linux-kernel mailing list.
Various Linux HOWTOs on specific questions, such as the BogoMips mini-HOWTO by Wim van Dorst. These are all by definition LDP documents.
The Linux kernel source code for any particular kernel version that you may be using. Note that there is a /Documentation directory which holds some very useful text files about drivers, etc. Also check the MAINTAINERS file in the kernel source root directory.
Some drivers even have Web pages, with additional up to date information e.g. the network drivers by Donald Becker, etc. Check the Hardware section in the LDP site.
Similarly, Linux implementations for some CPU architectures have dedicated Web pages, mailing lists, and sometimes even a HOWTO e.g. the Linux Alpha HOWTO by Neal Crook. Check the LDP site and its mirrors for Web links to the various architecture specific sites.
Linux device drivers, a book written by Alessandro Rubini. C. Scott Ananian reviewed it for Amazon.com.
Linux kernel internals, a book by Michael Beck (Editor) et al. Also reviewed for Amazon.com.
Another useful site is:
Here is a general guide on how to ask questions in a way that greatly improves your chances of getting a reply:
If you have a bug to report, you should also read
Extra instructions, specific to the Linux kernel are available here.
贡献者与特殊的说明
This is the list of contributors to this FAQ. They are listed in alphabetic order of their abbreviations, used in the Answers sections below to identify the author(s) of each answer.
AC : Alan Cox
AV : Alexander Viro
ADB: Andrew D. Balsa
CP : Colin Plumb
DBE: Daniel Bergstrom
D: David S. Miller (co-postmaster)
DW : David Woodhouse
JBG: Jan-Benedict Glaw
KGB: Krzysztof G. Baranowski
KO : Keith Owens
MEA: Matti E. Aarnio (co-postmaster)
MRW: Matthew Wilcox
PG : Paul Gortmaker
RC : Ralph Corderoy
REG: Richard E. Gooch (FAQ maintainer)
REW: Roger E. Wolff
RML: Robert M. Love
RRR: Rafael R. Reilova
TAC: Thomas A. Cort
TJ : Trevor Johnson
TYT: Theodore Y. Ts’o
VKh: Vassilii Khachaturov
关于linux documentation的介绍到此就结束了，不知道你从中找到你需要的信息了吗 ？如果你还想了解更多这方面的信息，记得收藏关注本站。
