On Sat, Aug 27, 2011 at 1:01 AM, Jona Joachim j...@hcl-club.lu wrote:
On 2011-08-26, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote:
Supersede gives me what I want. It just felt weird those entries
ended up on resolv.conf when I had not requested them.
Thanks and sorry for the
On 2011-08-27, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote:
On Sat, Aug 27, 2011 at 1:01 AM, Jona Joachim j...@hcl-club.lu wrote:
On 2011-08-26, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote:
Supersede gives me what I want. It just felt weird those entries
ended up on
Hi all users and developers
I simply noticed what I would call a weird behaviour on my 32 bit 4.9
GENERIC#671 box's dhclient, which I hope is not the expected behavior.
While reading RFC2131, I didnt find any sentence stating or implying
that is the desired behavior, as in a server MUST
Say
On 2011-08-26, I?igo Ortiz de Urbina tarom...@gmail.com wrote:
Hi all users and developers
I simply noticed what I would call a weird behaviour on my 32 bit 4.9
GENERIC#671 box's dhclient, which I hope is not the expected behavior.
While reading RFC2131, I didnt find any sentence stating or
Supersede gives me what I want. It just felt weird those entries
ended up on resolv.conf when I had not requested them.
Thanks and sorry for the noise.
2011/8/27 IC1igo Ortiz de Urbina tarom...@gmail.com:
Hi all users and developers
I simply noticed what I would call a weird behaviour on my
On 2011-08-26, I??igo Ortiz de Urbina inigoortizdeurb...@gmail.com wrote:
Supersede gives me what I want. It just felt weird those entries
ended up on resolv.conf when I had not requested them.
Thanks and sorry for the noise.
This is expected behaviour for the prepend option, it does just
6 matches
Mail list logo