On Tue, Oct 02, 2012 at 02:52:30AM +0200, Cyril Brulebois wrote:
Philipp Kern pk...@debian.org (01/10/2012):
It worked with on/off, on/on, just not off/on. Rev 762daa6[1] should
fix that. I did not have time to test it in all circumstances,
though. I uploaded the mini.iso to [2].
Is that
On Mon, Oct 01, 2012 at 07:24:33PM +0200, Karsten Merker wrote:
I have just run a test with today's daily netinst
(http://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso,
dated 01-Oct-2012 00:11) with the same setup (IPv6-only network,
radvd announces prefix and RDNSS,
Philipp Kern pk...@debian.org (01/10/2012):
It worked with on/off, on/on, just not off/on. Rev 762daa6[1] should
fix that. I did not have time to test it in all circumstances,
though. I uploaded the mini.iso to [2].
Is that worth a new netcfg/debian-installer upload? From where I
stand, it
Re: Philipp Kern 2012-09-18 20120918090525.ga...@spike.0x539.de
On Tue, Sep 18, 2012 at 10:59:04AM +0200, Bjørn Mork wrote:
No, I didn't get any wiser. Except that I now am pretty convinced that
no service should listen to localhost. They should explictly choose
127.0.0.1 and/or ::1
On Mon, Sep 24, 2012 at 10:08:08AM +0200, Christoph Berg wrote:
Given that DNS seems to tend to resolve localhost to both 127.0.0.1
and ::1, I guess the proper solution would be to put the same in to
/etc/hosts.
DNS does not resolve localhost in most instances I tried (or to just
127.0.0.1).
On Tue, Sep 18, 2012 at 10:25:06AM +0200, Bjørn Mork wrote:
For example:
bjorn@canardo:~$ grep localhost /etc/hosts
127.0.0.1 localhost
::1 ip6-localhost ip6-loopback
bjorn@canardo:~$ host localhost
localhost has address 127.0.0.1
localhost has IPv6
Philipp Kern pk...@debian.org writes:
On Mon, Sep 17, 2012 at 11:30:58PM +0200, Marco d'Itri wrote:
On Sep 17, Philipp Kern pk...@debian.org wrote:
True, but somehow I feel that freeze time is not the time to change this.
I disagree, netcfg should be fixed. There is plenty of time to look at
Philipp Kern pk...@debian.org writes:
On Tue, Sep 18, 2012 at 10:25:06AM +0200, Bjørn Mork wrote:
For example:
bjorn@canardo:~$ grep localhost /etc/hosts
127.0.0.1 localhost
::1 ip6-localhost ip6-loopback
bjorn@canardo:~$ host localhost
localhost has
On Tue, Sep 18, 2012 at 10:59:04AM +0200, Bjørn Mork wrote:
No, I didn't get any wiser. Except that I now am pretty convinced that
no service should listen to localhost. They should explictly choose
127.0.0.1 and/or ::1
AIUI the point is to listen to both and hence the (or a?) record should
On Fri, Sep 07, 2012 at 09:44:12PM +0200, Christoph Berg wrote:
From my point of view, localhost should be handled like any other
multi-homed host, that is, it should have both addresses. It might
have been different in 2010, wenn netcfg 1.57 was uploaded, but
nowadays applications really need
On Sep 17, Philipp Kern pk...@debian.org wrote:
True, but somehow I feel that freeze time is not the time to change this.
I disagree, netcfg should be fixed. There is plenty of time to look at
any fallback, and even reverting the change if needed.
This is 2012, Europe and Asia are out of IPv4
On Mon, Sep 17, 2012 at 11:30:58PM +0200, Marco d'Itri wrote:
On Sep 17, Philipp Kern pk...@debian.org wrote:
True, but somehow I feel that freeze time is not the time to change this.
I disagree, netcfg should be fixed. There is plenty of time to look at
any fallback, and even reverting the
Package: netbase,netcfg
Severity: normal
Tags: d-i ipv6
In #685362, a user complains that PostgreSQL doesn't listen on ipv6
localhost, unless he has ::1 localhost in his /etc/hosts. I can
confirm that adding this fixes the problem for postgresql-9.1. Looking
through my systems, I'm seeing
13 matches
Mail list logo
