Do we really need to keep this in the menu? Does anyone need System->Administration->Network or Network Device Control now that we have NetworkManager?
As a casual, but interested user, I do find the network configuration confusing... I use fedora 10 (gnome) most of the time, and I can never remember which submenu to go to in order to set the hostname...
Every once in a while, Network Manager behaves flaky and stops or won't start (I've seen this mainly in Ubuntu 8, 9.x) and then you can be stuck.
Sent from my iPhone
On Feb 19, 2010, at 7:49 PM, Chuck Anderson cra@WPI.EDU wrote:
Do we really need to keep this in the menu? Does anyone need System->Administration->Network or Network Device Control now that we have NetworkManager? -- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
On Fri, 2010-02-19 at 21:12 -0500, Brad Banko wrote:
As a casual, but interested user, I do find the network configuration confusing... I use fedora 10 (gnome) most of the time, and I can never remember which submenu to go to in order to set the hostname...
Every once in a while, Network Manager behaves flaky and stops or won't start (I've seen this mainly in Ubuntu 8, 9.x) and then you can be stuck.
Ubuntu 8 and 9.04 ship pretty old versions of NetworkManager that we haven't shipped in Fedora since F7/F8/F9. They aren't a good read of the state of NetworkManager for the past year or two.
Dan
Sent from my iPhone
On Feb 19, 2010, at 7:49 PM, Chuck Anderson cra@WPI.EDU wrote:
Do we really need to keep this in the menu? Does anyone need System->Administration->Network or Network Device Control now that we have NetworkManager? -- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
On 02/20/2010 02:49 AM, Chuck Anderson wrote:
Do we really need to keep this in the menu? Does anyone need System->Administration->Network or Network Device Control now that we have NetworkManager?
I, for one, do not use N-M unless on a laptop (wired and wireless interfaces). I prefer the old-fashioned way to connect and set up my Ethernet interfaces. And I bet there are others.
On Sat, Feb 20, 2010 at 02:41:25PM +0200, Aioanei Rares wrote:
On 02/20/2010 02:49 AM, Chuck Anderson wrote:
Do we really need to keep this in the menu? Does anyone need System->Administration->Network or Network Device Control now that we have NetworkManager?
I, for one, do not use N-M unless on a laptop (wired and wireless interfaces). I prefer the old-fashioned way to connect and set up my Ethernet interfaces. And I bet there are others.
Yes, but it is confusing to new users. We can still keep the command line system-config-network, I'm just advocating to hide/remove it from the menu of the Desktop spin for F13. NM has matured enough that I think it is about time to accept it as the "one default" in the menu.
On Sat, 2010-02-20 at 09:15 -0500, Chuck Anderson wrote:
On Sat, Feb 20, 2010 at 02:41:25PM +0200, Aioanei Rares wrote:
On 02/20/2010 02:49 AM, Chuck Anderson wrote:
Do we really need to keep this in the menu? Does anyone need System->Administration->Network or Network Device Control now that we have NetworkManager?
I, for one, do not use N-M unless on a laptop (wired and wireless interfaces). I prefer the old-fashioned way to connect and set up my Ethernet interfaces. And I bet there are others.
Yes, but it is confusing to new users. We can still keep the command line system-config-network, I'm just advocating to hide/remove it from the menu of the Desktop spin for F13. NM has matured enough that I think it is about time to accept it as the "one default" in the menu.
+1, I think having both network config utilities in the menus is a bad idea. Of course, it'd be best to have whichever one is actually appropriate to the current configuration present, but I don't think that's possible unless we adopt some messy wrapper approach?
Adam Williamson (awilliam@redhat.com) said:
+1, I think having both network config utilities in the menus is a bad idea. Of course, it'd be best to have whichever one is actually appropriate to the current configuration present, but I don't think that's possible unless we adopt some messy wrapper approach?
nm-connection-editor, when checking 'make connection available to all users', writes the same configuration files that s-c-network does.
Bill
On Mon, Feb 22, 2010 at 02:13:34PM -0500, Bill Nottingham wrote:
Adam Williamson (awilliam@redhat.com) said:
+1, I think having both network config utilities in the menus is a bad idea. Of course, it'd be best to have whichever one is actually appropriate to the current configuration present, but I don't think that's possible unless we adopt some messy wrapper approach?
nm-connection-editor, when checking 'make connection available to all users', writes the same configuration files that s-c-network does.
Yup, and it is already in the menu:
System->Preferences->Network Connections
desktop@lists.fedoraproject.org
-
Adam Williamson -
Bill Nottingham -
Brad B -
Chuck Anderson -
Dan Williams -
Rares Aioanei