On 14 January 2015 at 16:18, Axel Beckert wrote:
>> It's up to the admin to change things in /etc/. Programs that play
>> around with things in /etc/ at runtime are not well behaved by Debian
>> standards.
>
> Depends. I agree for anything in the maintainer scripts, but I
> disagree for anything w
On 2015-01-14 15:24:53 +0100, Thomas Hood wrote:
> It's up to the admin to change things in /etc/. Programs that play
> around with things in /etc/ at runtime are not well behaved by Debian
> standards.
dhclient does this by default.
> > Otherwise the user needs to modify
> > /etc/dhcp/dhclient-e
Hi,
Thomas Hood wrote:
> On 14 January 2015 at 15:08, Vincent Lefevre wrote:
> > On 2015-01-14 14:14:22 +0100, Thomas Hood wrote:
> >> This is an allowed configuration (which is sometimes even useful). [...]
> >
> > OK, but this is a very atypical usage for users of wicd, whose goal
> > is to mak
On 14 January 2015 at 15:08, Vincent Lefevre wrote:
> On 2015-01-14 14:14:22 +0100, Thomas Hood wrote:
>> This is an allowed configuration (which is sometimes even useful). [...]
>
> OK, but this is a very atypical usage for users of wicd, whose goal
> is to make things work without needing to be
On 2015-01-14 14:14:22 +0100, Thomas Hood wrote:
> > The problem is actually a lack of consistency: only
> > /run/resolvconf/resolv.conf is modified *but* it is not used.
>
> This is an allowed configuration (which is sometimes even useful).
> Resolvconf writes /run/resolvconf/resolv.conf and the
Hi Vincent,
Vincent Lefevre wrote:
> and indeed, there is a backup file:
>
> -rw-r--r-- 1 root root 21 2010-05-24 20:28:15 /var/lib/wicd/resolv.conf.orig
Yep, here, too.
> However it is completely obsolete. The above method is obviously
> broken: if ever wicd-daemon or the system crashes, or th
On 2015-01-13 23:32:45 +0100, Axel Beckert wrote:
> Yes, the patch has been removed with the 1.6.0-1 upload with the
> following changelog entry:
>
> * debian/patches/:
> - 01-fix_desktop_file.patch, 07-add_resolvconf_support.patch
> removed, fixed upstream
Anyway I haven't provided a
On 2015-01-13 20:47:56 +0100, Thomas Hood wrote:
> Hi there and thanks for the report.
>
> First I need some info.
>
> 1. When (if ever) does wicd modify dhclient.conf?
In the past, wicd was creating its own dhclient.conf and was
invoking dhclient with this config file:
2011/12/17 03:16:46 :: /
Hi Thomas,
Thomas Hood wrote:
> I just read bug report #514597 entitled "wicd does not work properly
> with resolvconf" which was closed in version 1.5.9-2 with the message
> that "07-add_resolvconf_support.patch added". Although I don't see
> this patch in the current source tree, I do see refere
I just read bug report #514597 entitled "wicd does not work properly
with resolvconf" which was closed in version 1.5.9-2 with the message
that "07-add_resolvconf_support.patch added". Although I don't see
this patch in the current source tree, I do see references to the
resolvconf program which in
Hi,
Thomas Hood wrote:
> 1. When (if ever) does wicd modify dhclient.conf?
I claim that it doesn't touch the one at /etc/dhcp/dhclient.conf at
all.
>From the bug report and the logic (you can set things like search
domains and DNS servers statically per configured connection, e.g. per
WLAN), I w
Hi there and thanks for the report.
First I need some info.
1. When (if ever) does wicd modify dhclient.conf?
2. When the malfunction occurs are the contents
/run/resolvconf/resolv.conf correct (i.e., what one would expect to
find in resolv.conf)? So that the problem is that /etc/resolv.conf is
12 matches
Mail list logo
