[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: What to do with lamentable "Network Configuration" button?

On Thu, 2010-08-05 at 14:42 +0200, Radek Vykydal wrote:
> These lines are about activating network devices automatically after reboot.
> It is a follow-up of James Laska's suggestion on IRC. I wanted to add some
> context and ask for your suggestions.
> Our present policy is to activate automatically only device used to enable
> networking during installation.  To change this default behaviour user 
> action
> is required - using kickstart network command, or "Configure Network" button
> (nm-c-e) in stage 2.
> There are bugs for rhel 6.1 and Fedora to reverse the policy (automatically
> activate all network devices by defalt after reboot) - the use case 
> behind is
> media install without using network. (In rhel 5, in this case network was
> enabled after install without any user intervention because there were 
> network
> configuration screen with "active on boot" setting prechecked for the first
> device). The change of policy has its issues (see [*] for details).
> But apart from changing the policy, we can do at least something to 
> improve the
> experience in the before-mentioned case - James Laska came with an idea 
> to make
> "Configure Network" option more visible, enhanced with a suggestion. Here is
> what mduffy proposed:
> http://jlaska.fedorapeople.org/Screenshot.png
> I am all for a comment above the button, only the wording is not 
> suitable for
> the situation when the network has already been enabled. So I'd propose 
> to have
> two wordings, depending on the state of the network. If it is not 
> enabled, the
> suggested wording is ok (maybe hint to check "Connect Automatically" in 
> nm-c-e
> can be added).  If it is enabled, I'd  suggest something like:
> After booting the installed system, network will be activated with the same
> configuration that is used now.  You can change the configuration by 
> visiting
> "Network Connections" dialog on installed system, or immediately by 
> clicking on
> "Configure Network" button.

With two wordings, I just worry about having to validate that the
expected wording shows up depending on your boot method (w/ or w/o
networking).  To clarify, when using the 'Configure Network' button,
this configures the network for the install environment *and* the
post-installed system, right?

What about phrasing the text to note that this is for Advanced Network
Configuration?  The text wouldn't changed based on whether networking
was enabled or disabled.  A proposed wording ...

        Some systems may require additional network configuration.  To
        enable or configure networking on your system, please click
        'Configure Network' button below.  You may also configure
        networking after completing the installation by visiting the
        'Network Connections' dialog.

> [*]
> Devices activated automatically after boot have to have ONBOOT="yes" set in
> ifcfg file. In nm-c-e - ONBOOT is controlled by "Connect Automatically"
> checkbox.
> We preset ONBOOT to "no" in loader for all devices. When we enable 
> networking,
> we change the value to "yes". In stage 2 it is done by changing the value in
> ifcfg file before running nm-c-e.
> The problem with setting ONBOOT to "yes" by default is that the setting also
> immediately activates the device during install which we probably don't 
> want.
> To prevent this we could set it only in ifcfg files of installed system
> (in /mnt/sysimage) after package installation - but then we might override
> what user had set in "Configure Network".  So this can't be done completely
> correctly because configuration of networking for system is done in nm-c-e
> operating on ifcfg files of install environment which we then copy to 
> the system
> (/mnt/sysimage). (Well I consider additional set of checkboxes for 
> system ifcfg
> files ONBOOT setting as out of question after we got rid of the similar for
> nm-controlled-ness). 

> Maybe moving "Configure Network" to firstboot would be
> the best solution.
> (IRC: "* jlaska wonders if the nm-connection-editor button would be better
> suited as a firstboot plugin")

I'm not sure that's the best solution either ... but just threw that out
there for feedback.  I could certainly see this working, just don't know
if this is what others would expect.

        Your system is not configured to access the internet.  To
        configure networking for this system, click on the 'Configure
        Network' button below.  You may also enable networking after
        logging into the desktop and visiting the 'Network Connections'

    [Configure Network]


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]