Neal Becker wrote:
sean darcy wrote:
NM sets my nameserver based on the isp, which is _very_ slow. I've set
up a local caching nameserver which works well. But how do I tell NM to
use 127.0.0.1??
I've set up dhclient.conf with a prepend statement. If I just run
dhclient that works, i.e.
On Mon, 2008-07-14 at 10:33 +0930, Tim wrote:
On Sun, 2008-07-13 at 15:08 +0100, Timothy Murphy wrote:
Just to be a bit more precise, what I would like from NM
is error messages along the lines: The AP you specify
does not accept your WEP code, or There is no response
from the AP you
Matthew Saltzman wrote:
Meanwhile, I use it when it works, and I when it doesn't, I try to
troubleshoot it and file bugs or turn it off and use the individual
tools that it tries to tie together. And I try very hard to be
patient...
The basic problem with NM is not so much bugs
as the lack
On Sun, 2008-07-13 at 15:08 +0100, Timothy Murphy wrote:
Just to be a bit more precise, what I would like from NM
is error messages along the lines: The AP you specify
does not accept your WEP code, or There is no response
from the AP you specify, etc.
In the Good Old Days when memory and
Hello,
On Fri, 2008-07-11 at 15:34 -0400, Matthew Saltzman wrote:
On Fri, 2008-07-11 at 09:48 -0700, Rick Stevens wrote:
Michael H. Warfield wrote:
I have a longer rant that I'm strongly tempted to send.
I'd wouldn't necessarily post your rant here, as most of us here agree
On Sat, 2008-07-12 at 15:56 -0400, Michael H. Warfield wrote:
Hello,
On Fri, 2008-07-11 at 15:34 -0400, Matthew Saltzman wrote:
On Fri, 2008-07-11 at 09:48 -0700, Rick Stevens wrote:
Michael H. Warfield wrote:
I have a longer rant that I'm strongly tempted to send.
Michael H. Warfield wrote:
On Thu, 2008-07-10 at 13:10 -0400, sean darcy wrote:
sean darcy wrote:
NM sets my nameserver based on the isp, which is _very_ slow. I've set
up a local caching nameserver which works well. But how do I tell NM to
use 127.0.0.1??
I've set up dhclient.conf with a
On Fri, 2008-07-11 at 09:48 -0700, Rick Stevens wrote:
Michael H. Warfield wrote:
I have a longer rant that I'm strongly tempted to send.
I'd wouldn't necessarily post your rant here, as most of us here agree
that NM is a bad idea gone wrong.
Speak for yourself (unless you have
Matthew Saltzman wrote:
On Fri, 2008-07-11 at 09:48 -0700, Rick Stevens wrote:
Michael H. Warfield wrote:
I have a longer rant that I'm strongly tempted to send.
I'd wouldn't necessarily post your rant here, as most of us here agree
that NM is a bad idea gone wrong.
Speak for
sean darcy wrote:
NM sets my nameserver based on the isp, which is _very_ slow. I've set
up a local caching nameserver which works well. But how do I tell NM to
use 127.0.0.1??
I've set up dhclient.conf with a prepend statement. If I just run
dhclient that works, i.e. /etc/resolv.conf has
On Thu, 2008-07-10 at 13:10 -0400, sean darcy wrote:
sean darcy wrote:
NM sets my nameserver based on the isp, which is _very_ slow. I've set
up a local caching nameserver which works well. But how do I tell NM to
use 127.0.0.1??
I've set up dhclient.conf with a prepend statement. If
Michael H. Warfield wrote:
-snip-
My solution, at this point, is yum erase NetworkManger and then go
back to the older scripts which WORK and work reliably.
Unless you're having problems with wireless (and there are better
solutions to that problem) NetworkManager has no
sean darcy wrote:
NM sets my nameserver based on the isp, which is _very_ slow. I've set
up a local caching nameserver which works well. But how do I tell NM to
use 127.0.0.1??
I've set up dhclient.conf with a prepend statement. If I just run
dhclient that works, i.e. /etc/resolv.conf has
On Thu, 2008-07-10 at 14:54 -0700, stan wrote:
Michael H. Warfield wrote:
-snip-
My solution, at this point, is yum erase NetworkManger and then go
back to the older scripts which WORK and work reliably.
Unless you're having problems with wireless (and there are better
14 matches
Mail list logo
