touch-packages team mailing list archive

[HeinMueck <1394081@xxxxxxxxxxxxxxxxxx>]

Public bug reported:


Currently - trusty LTS - there is no way to turn off the regeneration of /etc/resolv.conf that would survive a package upgrade. 

- you cannot remove resolvconf as it is needed by minimal
- you cannot disable-upgrades as this flag is removed by reboots
- if you disable the resolvconf job in upstart package upgrade will reset the disable-upgrade flags
- if you hack the scripts - it will only last until the next upgrade

There are two ways to ensure that admins willing to turn it off can do
so:

First solution: add a run=no to /etc/default/resolvconf and bail out if
it is set.

The second solution is more subtile. In /etc/network/if-
up.d/000resolvconf you will find this line:

[ -x /sbin/resolvconf ] || exit 0

While in /etc/dhcp/dhclient-enter-hooks.d/resolvconf it says

if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then

Way more clever! So if you do not want to implement the default option,
why not check if its a link all the way? So at least a conf gets not
overwritten once the admin wrote his own.

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1394081

Title:
  Add manual options for administrators

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  
  Currently - trusty LTS - there is no way to turn off the regeneration of /etc/resolv.conf that would survive a package upgrade. 

  - you cannot remove resolvconf as it is needed by minimal
  - you cannot disable-upgrades as this flag is removed by reboots
  - if you disable the resolvconf job in upstart package upgrade will reset the disable-upgrade flags
  - if you hack the scripts - it will only last until the next upgrade

  There are two ways to ensure that admins willing to turn it off can do
  so:

  First solution: add a run=no to /etc/default/resolvconf and bail out
  if it is set.

  The second solution is more subtile. In /etc/network/if-
  up.d/000resolvconf you will find this line:

  [ -x /sbin/resolvconf ] || exit 0

  While in /etc/dhcp/dhclient-enter-hooks.d/resolvconf it says

  if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then

  Way more clever! So if you do not want to implement the default
  option, why not check if its a link all the way? So at least a conf
  gets not overwritten once the admin wrote his own.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1394081/+subscriptions