Il giorno Wed, 4 Jan 2017 12:24:40 +0000
KatolaZ <katolaz@???> ha scritto:

> On Wed, Jan 04, 2017 at 01:10:31PM +0100, Alessandro Selli wrote:
>
> [cut]
>
> > > I'm kind of envisioning this as part of the initial system setup, so a
> > > little more like this.
> > > Though I fully admit caffeine hasn't kicked in yet, so I may be
> > > spouting more crazy than normal :).
> > >

> > > [*] No DNS config (warning - may limit ability to install optional
> > > components) [ ] Pick geographically closest
> > > [ ] Pick Random
> > > [ ] Custom
> > >      DNS1 [_________________] (required if 'custom')
> > >      DNS2 [_________________] (optional)

> > >
> > > (Buttons / options at the bottom)
> > >
> > > [BACK] [List Public DNS Servers] [OK]
> >
> > Cool. Functional, simple and transparent. Just what Devuan is all
> > about.
> >
>
> This is misleading, and useless. IMHO. If you specify "No DNS config
> (warning - may limit....)" it does not mean that you will not have a
> DNS configured anywhere (as the wording seems to suggest here). It
> just means that Devuan will not provide any fallback DNS configuration
> if your dhclient fails, or if your AP does not give you a decent DNS,
> or if you don't know which DNS to use with in a manual network config.
>
> I would rather like having an option saying:
>
> "[ ] Configure *fallback* DNS"

This is exactly what has been discussed so far. The Debian bug report is
indeed about the fallback DNS configuration:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658

| From a cursory look over the sources, I am led to believe that
| resolved defaults to using Google nameservers.
|
| I would like to propose that we either provide no default fallback,
| or chose to support OpenNIC that way.


> which makes clear that this is meant to be a fallback, to be used only
> if dhclient has failed, if you AP sucks, if you suck, and in general
> when there is nothing useful in /etc/resolv.conf during the
> installation.

I always gave it for granted that the proposed DNS selection menu would pop
up only in the event that DHCP did not work (at least for DNS configuration)
or was expressly skipped by the user at installation time (in favour of a
manual interface configuration, for instance).

> I am strongly convinced that we don't want to (and we should not, by
> any means) be responsible for DNS configuration, mainly because we
> don't want to have users complaining because they "..have set up the
> fallback DNS during Devuan installation, but then it got removed when
> I restarted my laptop...".
>
> No automatism should take care of policy. No automatism can cure
> ignorance.

This is precisely the reason we're giving the user a chance to perform their
choice of DNS setting, unlike what they decided to do at Debian (silently
configure Goggle DNS servers as a fallback with no possible user interaction).



--
Alessandro Selli http://alessandro.route-add.net
VOIP SIP: dhatarattha@???
Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9