Summary: | nodns shown in the configuration line for dhcp doesn't seem like a good default option. | ||
---|---|---|---|
Product: | [OLD] Docs on www.gentoo.org | Reporter: | James Allen <s0563583> |
Component: | Installation Handbook | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugs.gentoo.org/enter_bug.cgi?product=Documentation&format=guided | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
James Allen
2007-01-09 17:02:41 UTC
We already have warning after warning after warning in the handbooks to *read conf.d/net.example* so that users can properly setup their own network, and not rely on the example in the handbook which may or may not apply to them. Actually, "nodns nonis nontp" just means that the dhcp client will not overwrite the dns/nis/ntp settings *you have defined elsewhere*. That's taken from net.example -- you really do need to read it. Our setup is more geared to a basic dhcp-only networked system without complicated nis/dns setups. It will work for the majority of the install base, which is the usual single-homed machine that gets is address from a router or ISP direct. Again, I can't stress enough that we already provide plenty of warnings to read net.example -- it can help you with your setup: # Set generic DHCP options like so #dhcp_eth0="release nodns nontp nonis nogateway nosendhost" # This tells the dhcp client to release it's lease when it stops, not to # overwrite dns, ntp and nis settings, not to set a default route and not to # send the current hostname to the dhcp server and when it starts. # You can use any combination of the above options - the default is not to # use any of them. |