On Thursday, August 26, 2010, 3:17:52 PM, Jeff wrote: > On Thu, Aug 26, 2010 at 10:29 AM, Jon Masters <jonat...@jonmasters.org> wrote: >> Great. It works fine on a laptop, in general. But on a >> desktop/server/workstation that is connected for weeks at a time (like >> mine), I don't want to have to do clicky buttony stuff just to make my >> network work. Nothing has yet proved as simple as the "network" scripts, >> though I'm sure we could shove in a few layers of >> g-whatever-it's-called-now-conf for good measure.
> Just to be clear.. its the clickity nature of the initial system wide > configuration that is the barrier for you? if you had a reasonable > non-clickity way to add a system wide on-boot activated network > controlled networkmanager via cli would that suffice? > -jef Let's not forget that NM is not suitable for someone running a local DNS server (bind with DNSSEC enabled). It also does not work at all when used on a laptop as a caching DNS. There is a F14^H^H^HF15 feature to make NM work with bind and DSNSEC. I look forward to it - my girlfriend's ISP's DNS servers can take up to 10 seconds to resolve an address, and occasionally simply do not resolve legit URLs. Al -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
