----- Original Message ----- > From: "Colin Walters" <walt...@verbum.org> > To: networkmanager-list@gnome.org > Sent: Wednesday, June 26, 2013 4:25:31 PM > Subject: discuss: NM server defaults > > So I filed this downstream: > > https://bugzilla.redhat.com/show_bug.cgi?id=978081
I think it might be useful to consider this upstream as well. > But it seems like something worth talking about here. We could easily > maintain nm-server-defaults.conf in the upstream git repo, at least. +1 for maintaining a universal server.conf that can be further tweaked by the distributors and/or administrators. > We > could also add --enable-server-defaults as a build time option, I don't think it has any real value as a ./configure option. The server config is just one file that can be easily copied over by a specfile command line (or similar). It might be useful to install the file, though. It might be disabled by file name (e.g. .sample suffix) or by location (e.g. documentation directory). > for > OS builders that do servers and clients as separate builds from source > instead of packages. Although it's possible to build seprate server/client packabes, it doesn't seem to be overly useful. On the other hand, separate packages with just the configuration files/defaults might be handy and a distribution that would like to do that will just copy *all* such configuration files and put them in subpackages. > Collecting some comments from IRC: > > <danw> we'll probably want ignore-carrier=* too Sounds like a useful default for specific class of usage. I, personally, would prefer the server to react on carrier at least when using DHCP. So this might actually be an area where we as developers don't know yet whether it is preferable and by which groups of people. Cheers, Pavel _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
