Re: Contents of /etc/hosts

2016-10-11 Thread Ludovic Courtès
Hello! John Darrington skribis: > On Wed, Oct 05, 2016 at 10:17:14PM +0200, Ludovic Court??s wrote: > Hi! > > John Darrington skribis: > > > So ... my recommendations: > > > > 1. We change /etc/hosts to read > > > > > > 127.0.0.1 localhost.lo

Re: Contents of /etc/hosts

2016-10-09 Thread Hartmut Goebel
Am 09.10.2016 um 11:56 schrieb John Darrington: > But for IPv6 the loopback interface has ::1/128, this ::2 would not got > there. > > So if we follow your proposal adding "127.0.0.2 gambrius" to /etc/hosts, > we could not contently doe this for IPv6. > > IPv6 is som

Re: Contents of /etc/hosts

2016-10-09 Thread John Darrington
On Sun, Oct 09, 2016 at 11:12:58AM +0200, Hartmut Goebel wrote: Am 08.10.2016 um 16:08 schrieb John Darrington: > > 127.0.0.2 gambrinus > Now what happens if you "ping gambrinus"? > > ICMP packets will be sent to the local host. Me fool. of cours

Re: Contents of /etc/hosts

2016-10-09 Thread Hartmut Goebel
Am 08.10.2016 um 16:08 schrieb John Darrington: > > 127.0.0.2 gambrinus > Now what happens if you "ping gambrinus"? > > ICMP packets will be sent to the local host. Me fool. of course it does: the loopback interface has netmask /8 )defined in RFC 990 https://tools.ietf.org/html/rf

Re: Contents of /etc/hosts

2016-10-08 Thread John Darrington
On Thu, Oct 06, 2016 at 12:07:37PM +0200, Hartmut Goebel wrote: Am 06.10.2016 um 02:57 schrieb John Darrington: >127.0.0.1 localhost >::1 localhost >127.0.0.1 gambrinus >::1 gambrinus > > Or am I missing somet

Re: Contents of /etc/hosts

2016-10-08 Thread John Darrington
On Thu, Oct 06, 2016 at 11:24:57AM +0200, Hartmut Goebel wrote: Am 05.10.2016 um 20:31 schrieb John Darrington: > (shepherd-service-type >'host-name >(lambda (name) > (shepherd-service I suggest adding a comment here whether this is the bare hostna

Re: Contents of /etc/hosts

2016-10-06 Thread Hartmut Goebel
Am 06.10.2016 um 02:57 schrieb John Darrington: >127.0.0.1 localhost >::1 localhost >127.0.0.1 gambrinus >::1 gambrinus > > Or am I missing something? > > Hmm. I have never seen it done this way elsewhere, and I really wonder how > some > ser

Re: Contents of /etc/hosts

2016-10-06 Thread Hartmut Goebel
Am 05.10.2016 um 20:31 schrieb John Darrington: > (shepherd-service-type >'host-name >(lambda (name) > (shepherd-service I suggest adding a comment here whether this is the bare hostname or the FQDN. > 127.0.0.2 gambrinus Now what happens if you "ping gambrinus"? -- Schönen Gruß

Re: Contents of /etc/hosts

2016-10-05 Thread John Darrington
On Wed, Oct 05, 2016 at 10:17:14PM +0200, Ludovic Court??s wrote: Hi! John Darrington skribis: > So ... my recommendations: > > 1. We change /etc/hosts to read > > > 127.0.0.1 localhost.localdomain localhost > ::1 localhost.localdom

Re: Contents of /etc/hosts

2016-10-05 Thread Ludovic Courtès
Hi! John Darrington skribis: > So ... my recommendations: > > 1. We change /etc/hosts to read > > > 127.0.0.1 localhost.localdomain localhost > ::1 localhost.localdomain localhost > > 127.0.0.2 gambrinus It’s not very useful to have “localhost.localdomain”, is it? Also, shouldn’t we

Contents of /etc/hosts

2016-10-05 Thread John Darrington
Further to discussions on #guix earlier this week ... Some of us are concerned about what we currently have in /etc/hosts viz: 127.0.0.1 localhost gambrinus ::1 localhost gambrinus (my machine is called "gambrinus") This is a problem becuase it means that "hostname -f" returns the wrong