📄 592-596.html
字号:
<HTML>
<HEAD>
<TITLE>Using Linux:Managing the Kernel</TITLE>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!--ISBN=0789716232//-->
<!--TITLE=Using Linux//-->
<!--AUTHOR=William Ball//-->
<!--PUBLISHER=Macmillan Computer Publishing//-->
<!--IMPRINT=Que//-->
<!--CHAPTER=32//-->
<!--PAGES=592-596//-->
<!--UNASSIGNED1//-->
<!--UNASSIGNED2//-->
<CENTER>
<TABLE BORDER>
<TR>
<TD><A HREF="589-592.html">Previous</A></TD>
<TD><A HREF="../ewtoc.html">Table of Contents</A></TD>
<TD><A HREF="596-599.html">Next</A></TD>
</TR>
</TABLE>
</CENTER>
<P><BR></P>
<P>The next section deals with floppy and IDE devices:
</P>
<!-- CODE //-->
<PRE>
*
* Floppy, IDE, and other block devices
*
Normal floppy disk support (CONFIG_BLK_DEV_FD)[Y/m/n/?]
Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
(CONFIG_BLK_DEV_IDE)[Y/n/?]
</PRE>
<!-- END CODE //-->
<P>Both questions should be answered with <TT>Y</TT>, unless you don’t want to use either of these devices.</P>
<P>The next section of script assumes you have answered <TT>Y</TT> to IDE device support:</P>
<!-- CODE //-->
<PRE>
*
* Please see Documentation/ide.txt for help/info on IDE drives
*
Use old disk-only driver on primary interface
(CONFIG_BLK_DEV_HD_IDE)[N/y/?]
Include IDE/ATAPI CDROM support
(CONFIG_BLK_DEV_IDECD)[Y/n/?]
Include IDE/ATAPI TAPE support
(CONFIG_BLK_DEV_IDETAPE)[N/y/?]
Include IDE/ATAPI FLOPPY support
(new)(CONFIG_BLK_DEV_IDEFLOPPY)[N/y/?]
SCSI emulation support (CONFIG_BLK_DEV_IDESCSI)[N/y/?]
Support removable IDE interfaces
(PCMCIA)(CONFIG_BLK_DEV_IDE_PCMCIA)[N/y/?]
CMD640 chipset bugfix/support
(CONFIG_BLK_DEV_CMD640)[N/y/?]
RZ1000 chipset bugfix/support
(CONFIG_BLK_DEV_RZ1000)[N/y/?]
Intel 82371 PIIX (Triton I/II)DMA support
(CONFIG_BLK_DEV_TRITON)[Y/n/?]
Other IDE chipset support (CONFIG_IDE_CHIPSETS)[N/y/?]
</PRE>
<!-- END CODE //-->
<P>As stated here, more information on IDE peculiarities can be gleaned from the <TT>Documentation</TT> subdirectory of the <TT>linux</TT> source directory. To summarize, this section of script allows you to enable the new IDE/ATAPI device capabilities. Some IDE CD changers use a protocol similar to the SCSI Logical Units to control the several devices attached, and SCSI emulation support allows the use of regular SCSI tools to exploit this feature. Another option allows the detection of buggy IDE chipsets to be enabled along with their workarounds. Also listed is the option to turn on the Bus Mastering feature of the IDE controller included in Intel’s Triton (430 series) PCI chipsets—under some circumstances the driver will work with the Pentium Pro (440FX) and Pentium II (440LX) chipsets as well.</P>
<P>Other IDE chipsets supported include some chipsets by QDI and others, mostly used on Vesa Local Bus add-on cards shipped with some 486 PC systems. In most cases these drivers enable bus-mastering on the controller for a performance improvement.</P>
<P>The following script is presented next:</P>
<!-- CODE SNIP //-->
<PRE>
*
* Additional Block Devices
*
Loopback device support (CONFIG_BLK_DEV_LOOP)[M/n/y/?]
Multiple devices driver support (CONFIG_BLK_DEV_MD)[N/y/?]
RAM disk support (CONFIG_BLK_DEV_RAM)[N/y/m/?]
XT harddisk support (CONFIG_BLK_DEV_XD)[N/y/m/?]
</PRE>
<!-- END CODE SNIP //-->
<P>These devices are a bit more interesting than those in the run-of-the-mill IDE controller section. The loopback device allows the use of files as “virtual file systems” inside files. This is often used for creating disk images for writing CD-ROMs. There are some other uses for this as well—for example, this device is used by the script that makes a SCSI system’s initial ramdisk. In the preceding case, the makefile recommends this to be a module. It does no harm to leave it this way, and could come in useful.
</P>
<P>The multiple devices driver allows several partitions to be accessed as one. Additional tools and configurations are required to implement this. RAM disk support is important for systems that boot from SCSI disks with modular kernels—answer <TT>Y</TT> to the initial RAM disk support option that is displayed if you have a SCSI system. The last option is for those poor souls who still have hardware that predates the 286.</P>
<TABLE BORDER="2" BORDERCOLOR="#0000" ALIGN="CENTER">
<TR><TD><FONT SIZE="+1"><B>Your initial ramdisk and the loopback adapter</B></FONT>
<BR>If your system requires an initial ramdisk (in other words, your system boots off a SCSI adapter), you need the loopback device to generate that ramdisk in the first place.</TABLE>
<P>On to configuring your kernel’s networking:
</P>
<!-- CODE //-->
<PRE>
*
* Networking options
*
Network firewalls (CONFIG_FIREWALL)[N/y/?]
Network aliasing (CONFIG_NET_ALIAS)[Y/n/?]
TCP/IP networking (CONFIG_INET)[Y/n/?]
IP: forwarding/gatewaying (CONFIG_IP_FORWARD)[N/y/?]
IP: multicasting (CONFIG_IP_MULTICAST)[N/y/?]
IP: syn cookies (CONFIG_SYN_COOKIES)[N/y/?]
IP: rst cookies (CONFIG_RST_COOKIES)[N/y/?]
IP: accounting (CONFIG_IP_ACCT)[N/y/?]
IP: optimize as router not host (CONFIG_IP_ROUTER)[N/y/?]
IP: tunneling (CONFIG_NET_IPIP)[M/n/y/?]
IP: aliasing support (CONFIG_IP_ALIAS)[M/n/y/?]
*
* (it is safe to leave these untouched)
*
IP: PC/TCP compatibility mode (CONFIG_INET_PCTCP)[N/y/?]
IP: Reverse ARP (CONFIG_INET_RARP)[M/n/y/?]
IP: Disable Path MTU Discovery (normally
enabled)(CONFIG_NO_PATH_MTU_DISCOVERY)[N/y/?]
IP: Drop source routed frames (CONFIG_IP_NOSR)[Y/n/?]
IP: Allow large windows (not recommended if <16Mb of mem-
ory)(CONFIG_SKB_LARGE)[Y/n/?]
</PRE>
<!-- END CODE //-->
<P>This section of script details the kernel’s networking options for the base networking tool in Linux: TCP/IP. It’s strongly recommended that you respond with a <TT>Y</TT> here even if you do not have a network card. Your system has a loopback network configured to support local programs whose operation assumes there to be a network. There are many programs (X Window, for instance) on your system that prefer to use network sockets.</P>
<P>The majority of cases do not need either network firewalling or aliasing. (For a more detailed description of how these options work see the Firewall-HOWTO included with your Red Hat Linux CD and available online at <A HREF="http://sunsite.unc.edu/ldp/">http://sunsite.unc.edu/LDP/</A> and on many mirror sites.)</P>
<P>The forwarding/gatewaying option should definitely be set to <TT>N</TT> if you have a system on a LAN and plan to dial the Internet with it. That is, of course, only true if you don’t intend to make your system the gateway. Again, the Net-2-HOWTO should shed a great deal more light on this if you’re interested.</P>
<P>Multicasting is relatively new for the rest of the Internet, and many ISPs’ equipment does not support it. Say <TT>N</TT> here while the rest of the world gets multicasting sorted out.</P>
<P><TT>Syn</TT> and <TT>Rst</TT> cookies are designed to reduce the effectiveness of certain attacks on your system. There has been significant attention paid to “syn flooding” attacks on systems connected to the Internet in recent months, and this change in Linux networking is designed to reduce the effectiveness of the attack significantly.</P>
<P>IP accounting allows you to keep track of network traffic going over your system. It’s really useful only if Linux is being used as a network router, a topic, unfortunately, beyond the scope of this book.</P>
<P>Optimizing as router not host makes some changes to the networking in Linux. It’s recommended to be left off unless you’re setting up a router.</P><P><BR></P>
<CENTER>
<TABLE BORDER>
<TR>
<TD><A HREF="589-592.html">Previous</A></TD>
<TD><A HREF="../ewtoc.html">Table of Contents</A></TD>
<TD><A HREF="596-599.html">Next</A></TD>
</TR>
</TABLE>
</CENTER>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -