Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 75270 Details for
Bug 116267
hb-net-*: adding <c>s, <path>s, proper capitalization,...
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
hb-net-modules.patch
hb-net-modules.patch (text/plain), 7.52 KB, created by
Jan Kundrát (RETIRED)
on 2005-12-21 05:11:36 UTC
(
hide
)
Description:
hb-net-modules.patch
Filename:
MIME Type:
Creator:
Jan Kundrát (RETIRED)
Created:
2005-12-21 05:11:36 UTC
Size:
7.52 KB
patch
obsolete
>Index: doc/en/handbook/hb-net-modules.xml >=================================================================== >RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v >retrieving revision 1.9 >diff -u -b -B -r1.9 hb-net-modules.xml >--- doc/en/handbook/hb-net-modules.xml 21 Dec 2005 13:01:38 -0000 1.9 >+++ doc/en/handbook/hb-net-modules.xml 21 Dec 2005 13:10:44 -0000 >@@ -8,8 +8,8 @@ > > <sections> > >-<version>1.4</version> >-<date>2005-09-07</date> >+<version>1.5</version> >+<date>2005-12-21</date> > > <section> > <title>Network Modules</title> >@@ -50,14 +50,14 @@ > <body> > > <p> >-We provide two interface handlers presently: ifconfig and iproute2. You need one >-of these to do any kind of network configuration. >+We provide two interface handlers presently: <c>ifconfig</c> and >+<c>iproute2</c>. You need one of these to do any kind of network configuration. > </p> > > <p> >-ifconfig is the current Gentoo default and it's included in the system profile. >-iproute2 is a more powerful and flexible package, but it's not included by >-default. >+<c>ifconfig</c> is the current Gentoo default and it's included in the system >+profile. <c>iproute2</c> is a more powerful and flexible package, but it's not >+included by default. > </p> > > <pre caption="To install iproute2"> >@@ -68,9 +68,9 @@ > </pre> > > <p> >-As both ifconfig and iproute2 do very similar things we allow their basic >-configuration to work with each other. For example both the below code snippets >-work regardless of which module you are using. >+As both <c>ifconfig</c> and <c>iproute2</c> do very similar things we allow >+their basic configuration to work with each other. For example both the below >+code snippet work regardless of which module you are using. > </p> > > <pre caption="ifconfig and iproute2 examples"> >@@ -93,13 +93,13 @@ > Gateway, etc) from a DHCP server. This means that if there is a DHCP server > running on the network, you just have to tell each client to use DHCP and it > sets up the network all by itself. Of course, you will have to configure for >-other things like wireless, ppp or other things if required before you can use >+other things like wireless, PPP or other things if required before you can use > DHCP. > </p> > > <p> >-DHCP can be provided by dhclient, dhcpcd, pump or udhcpc. Each DHCP module has >-its pros and cons - here's a quick run down. >+DHCP can be provided by <c>dhclient</c>, <c>dhcpcd</c>, <c>pump</c> or >+<c>udhcpc</c>. Each DHCP module has its pros and cons - here's a quick run down. > </p> > > <table> >@@ -110,8 +110,8 @@ > <th>Cons</th> > </tr> > <tr> >- <ti>dhclient</ti> >- <ti>net-misc/dhcp</ti> >+ <ti><c>dhclient</c></ti> >+ <ti><c>net-misc/dhcp</c></ti> > <ti> > Made by ISC, the same people who make the BIND DNS software. Very > configurable >@@ -122,8 +122,8 @@ > </ti> > </tr> > <tr> >- <ti>dhcpcd</ti> >- <ti>net-misc/dhcpcd</ti> >+ <ti><c>dhcpcd</c></ti> >+ <ti><c>net-misc/dhcpcd</c></ti> > <ti> > Long time Gentoo default, no reliance on outside tools > </ti> >@@ -133,8 +133,8 @@ > </ti> > </tr> > <tr> >- <ti>pump</ti> >- <ti>net-misc/pump</ti> >+ <ti><c>pump</c></ti> >+ <ti><c>net-misc/pump</c></ti> > <ti> > Lightweight, no reliance on outside tools > </ti> >@@ -144,10 +144,10 @@ > </ti> > </tr> > <tr> >- <ti>udhcpc</ti> >- <ti>net-misc/udhcp</ti> >+ <ti><c>udhcpc</c></ti> >+ <ti><c>net-misc/udhcp</c></ti> > <ti> >- Lightweight - smallest dhcp client around, made for embedded systems >+ Lightweight - smallest DHCP client around, made for embedded systems > </ti> > <ti> > Unproven - no distro uses it by default, cannot define a timeout beyond 3 >@@ -158,24 +158,25 @@ > > <p> > If you have more than one DHCP client installed, you need to specify which one >-to use - otherwise we default to dhcpcd if available. >+to use - otherwise we default to <c>dhcpcd</c> if available. > </p> > > <p> >-To send specific options to the dhcp module, use module_eth0="..." >-<e>(change module to the DHCP module you're using - ie dhcpcd_eth0)</e> >+To send specific options to the DHCP module, use <c>module_eth0="..."</c> >+<e>(change module to the DHCP module you're using - ie <c>dhcpcd_eth0</c>)</e> > </p> > > <p> > We try and make DHCP relatively agnostic - as such we support the following >-commands using the dhcp_eth0 variable. The default is not to set any of them >+commands using the <c>dhcp_eth0</c> variable. The default is not to set any of >+them: > </p> > > <ul> >- <li>release - releases the IP address for re-use</li> >- <li>nodns - don't overwrite /etc/resolv.conf</li> >- <li>nontp - don't overwrite /etc/ntp.conf</li> >- <li>nonis - don't overwrite /etc/yp.conf</li> >+ <li><c>release</c> - releases the IP address for re-use</li> >+ <li><c>nodns</c> - don't overwrite /etc/resolv.conf</li> >+ <li><c>nontp</c> - don't overwrite /etc/ntp.conf</li> >+ <li><c>nonis</c> - don't overwrite /etc/yp.conf</li> > </ul> > > <pre caption="Sample DHCP configuration in /etc/conf.d/net"> >@@ -188,8 +189,8 @@ > </pre> > > <note> >-dhcpcd, udhcpc and pump send the current hostname to the DHCP server by default >-so you don't need to specify this anymore. >+<c>dhcpcd</c>, <c>udhcpc</c> and <c>pump</c> send the current hostname to the >+DHCP server by default so you don't need to specify this anymore. > </note> > > </body> >@@ -207,13 +208,13 @@ > </pre> > > <warn> >-baselayout-1.11.x supports PPPOE only. Hopefully future versions will support >-PPPOA. >+<c>baselayout-1.11.x</c> supports PPPOE only. Hopefully future versions will >+support PPPOA. > </warn> > > <p> >-Now we need to instruct configure eth0 to be an ADSL interface and enter our >-username. >+Now we need to instruct configure <c>eth0</c> to be an ADSL interface and enter >+our username. > </p> > > <pre caption="Configure eth0 for ADSL"> >@@ -223,7 +224,7 @@ > > <p> > Finally you need to define your username and password in >-<path>/etc/ppp/pap-secrets</path> >+<path>/etc/ppp/pap-secrets</path>. > </p> > > <pre caption="sample /etc/ppp/pap-secrets"> >@@ -249,7 +250,7 @@ > </p> > > <p> >-For APIPA support, emerge net-misc/iputils or net-analyzer/arping >+For APIPA support, emerge <c>net-misc/iputils</c> or <c>net-analyzer/arping</c>. > </p> > > <pre caption="APIPA configuration in /etc/conf.d/net"> >@@ -268,7 +269,7 @@ > <body> > > <p> >-For link bonding/trunking emerge net-misc/ifenslave >+For link bonding/trunking emerge <c>net-misc/ifenslave</c>. > </p> > > <p> >@@ -297,7 +298,7 @@ > <body> > > <p> >-For bridging support emerge net-misc/bridge-utils >+For bridging support emerge <c>net-misc/bridge-utils</c>. > </p> > > <p> >@@ -328,9 +329,8 @@ > </pre> > > <impo> >-For using some bridge setups, you may need to consult the >-<uri link="?part=4&chap=2#variable_name">variable name</uri> >-documentation. >+For using some bridge setups, you may need to consult the <uri >+link="?part=4&chap=2#variable_name">variable name</uri> documentation. > </impo> > > </body> >@@ -343,7 +343,7 @@ > You don't need to emerge anything for changing the MAC address of your interface > if you change to a specific address. However, if you need to change to a random > address or a random address of a given type then you need to emerge >-net-analyzer/macchanger. >+<c>net-analyzer/macchanger</c>. > </p> > > <pre caption="MAC Address change example"> >@@ -395,7 +395,7 @@ > <body> > > <p> >-For VLAN support, emerge net-misc/vconfig >+For VLAN support, emerge <c>net-misc/vconfig</c>. > </p> > > <p> >@@ -421,9 +421,8 @@ > </pre> > > <impo> >-For using some VLAN setups, you may need to consult the >-<uri link="?part=4&chap=2#variable_name">variable name</uri> >-documentation. >+For using some VLAN setups, you may need to consult the <uri >+link="?part=4&chap=2#variable_name">variable name</uri> documentation. > </impo> > > </body>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 116267
:
75265
|
75266
|
75267
|
75270
|
75271
|
75272
|
75273
|
76467
|
76483