GetRidOfEtcResolvConf

Differences between revisions 1 and 2
Revision 1 as of 2006-11-07 19:04:56
Size: 849
Editor: 207
Comment: initial rationale
Revision 2 as of 2006-11-07 20:14:07
Size: 1330
Editor: 66
Comment: Current system doesn't work well for chroot environments anyway
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
 * Whatever approach is taken it needs to allow chroot environments to get online. Copying /etc/resolv.conf into the chroot used to work, but since the /etc/resolvconf stuff this has been difficult in situations such as automatically setting up a chroot system on a non-root partition, since linking (hard or soft) the file doesn't work and it must be done manually (which therefore is not "automatically setting up") I hope this is the right place to air my concerns. -- Warbo

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Rationale

DNS configuration in /etc/resolv.conf gets clobbered by automatic network management tools (dhclient, network-manger, etc). There needs to be a mechanism to handle DNS updates that does not destroy custom changes in /etc/resolv.conf.

Use cases

Scope

Design

Implementation

Code

Data preservation and migration

Unresolved issues

  • Whatever approach is taken it needs to allow chroot environments to get online. Copying /etc/resolv.conf into the chroot used to work, but since the /etc/resolvconf stuff this has been difficult in situations such as automatically setting up a chroot system on a non-root partition, since linking (hard or soft) the file doesn't work and it must be done manually (which therefore is not "automatically setting up") I hope this is the right place to air my concerns. -- Warbo

BoF agenda and discussion


CategorySpec

GetRidOfEtcResolvConf (last edited 2008-08-06 16:32:42 by localhost)