|
Lines 179-187
Link Here
|
| 179 |
</pre> |
179 |
</pre> |
| 180 |
|
180 |
|
| 181 |
<p> |
181 |
<p> |
| 182 |
For a more detailed discussion about dependency, |
182 |
For a more detailed discussion about dependency, consult the section |
| 183 |
<uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=4#doc_chap4"> |
183 |
<uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=4#doc_chap4"> |
| 184 |
consult the Gentoo Handbook</uri> |
184 |
"Writing Init Scripts"</uri> in the Gentoo Handbook. |
| 185 |
</p> |
185 |
</p> |
| 186 |
|
186 |
|
| 187 |
</body> |
187 |
</body> |
|
Lines 192-198
Link Here
|
| 192 |
<body> |
192 |
<body> |
| 193 |
|
193 |
|
| 194 |
<p> |
194 |
<p> |
| 195 |
Variable names are dynamic. They are normally follow the structure of |
195 |
Variable names are dynamic. They normally follow the structure of |
| 196 |
<c>variable_${interface|mac|essid|apmac}</c>. For example, the variable |
196 |
<c>variable_${interface|mac|essid|apmac}</c>. For example, the variable |
| 197 |
<c>dhcpcd_eth0</c> holds the value for dhcpcd options for eth0 and |
197 |
<c>dhcpcd_eth0</c> holds the value for dhcpcd options for eth0 and |
| 198 |
<c>dhcpcd_essid</c> holds the value for dhcpcd options when any interface |
198 |
<c>dhcpcd_essid</c> holds the value for dhcpcd options when any interface |
|
Lines 201-210
Link Here
|
| 201 |
|
201 |
|
| 202 |
<p> |
202 |
<p> |
| 203 |
However, there is no hard and fast rule that states interface names must be |
203 |
However, there is no hard and fast rule that states interface names must be |
| 204 |
ethx. Infact, many wireless interfaces have names wlanx, rax as well as ethx. |
204 |
ethx. In fact, many wireless interfaces have names like wlanx, rax as well as ethx. |
| 205 |
Also, some user defined interfaces such as bridges can be given any name, such |
205 |
Also, some user defined interfaces such as bridges can be given any name, such |
| 206 |
has foo. To life more interesting, wireless Access Points can have names with |
206 |
as foo. To make life more interesting, wireless Access Points can have names with |
| 207 |
non alpha-numeric characters in - this is important because you can configure |
207 |
non alpha-numeric characters in them - this is important because you can configure |
| 208 |
networking parameters per ESSID. |
208 |
networking parameters per ESSID. |
| 209 |
</p> |
209 |
</p> |
| 210 |
|
210 |
|
|
Lines 216-222
Link Here
|
| 216 |
</p> |
216 |
</p> |
| 217 |
|
217 |
|
| 218 |
<p> |
218 |
<p> |
| 219 |
Another downside of bash is the content of variables - some character need to |
219 |
Another downside of bash is the content of variables - some characters need to |
| 220 |
be escaped. This can be achived by placing the \ character in front of the |
220 |
be escaped. This can be achived by placing the \ character in front of the |
| 221 |
character that needs to be escaped. Below is a list of characters that need |
221 |
character that needs to be escaped. Below is a list of characters that need |
| 222 |
to be escaped in this way. |
222 |
to be escaped in this way. |
|
Lines 239-246
Link Here
|
| 239 |
<comment># This does work, but the domain is invalid</comment> |
239 |
<comment># This does work, but the domain is invalid</comment> |
| 240 |
dns_domain_My____NET="My \"\\ NET" |
240 |
dns_domain_My____NET="My \"\\ NET" |
| 241 |
|
241 |
|
| 242 |
<comment># The above sets the dns domain to My \" NET when a wireless card |
242 |
<comment># The above sets the dns domain to My "\ NET when a wireless card |
| 243 |
# connects to an AP whose ESSID is My \" NET</comment> |
243 |
# connects to an AP whose ESSID is My "\ NET</comment> |
| 244 |
</pre> |
244 |
</pre> |
| 245 |
|
245 |
|
| 246 |
</body> |
246 |
</body> |
