Re: Design Questions

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

 



John Summerfield wrote:
David Cantrell wrote:
John Summerfield wrote:

David Cantrell wrote:

Daniel F de Araujo wrote:

Hello list,

I have a couple of questions regarding the design of the network gui/text screen. Before I ask, it maybe helpful to explain my setup and situation:

I have a network adapter with two ports. The first port (eth0, static IP) is connected to the public network and the other port (eth1, dhcp) is connected to my private network (same subnet as the NFS installation and DHCP servers). After I grab a dynamic IP for eth1 and setup the partitions, I end up in the network gui. Here, I enter the static IP address of eth0. I cannot, however, edit the gateway or DNS settings (which are different than eth1) for this port (eth0). So:

1) Is Anaconda designed to simply configure the adapter/port that accesses the install data? I assume the responsibility would then fall on the user to configure the other adapters during the firstboot process or setup agent screen.

2) If #1 is true, then I am curious as to why Anaconda allows the user to configure the IP, but the not the gateway/DNS information, for other adapters since it relies on firstboot, etc.

Thanks in advance for the help/explanations.



Anaconda collects enough information to write out files in /etc/sysconfig/network-scripts. We write out ifcfg-ethX files. The gateway and DNS settings are not stored per-interface. The gateway is written to /etc/sysconfig/network since you can only have one default gateway. DNS settings are written to /etc/resolv.conf and are also system-wide rather than per interface.


Flawed logic there. I have a laptop. Which network device should provide the default route depends.... One is 11b wireless, sometimes I connect to wire for increased speed. So does my boss.

It would be reasonable for which ever is more-recently activated to prevail, and for removing wire to restore wireless (if it's still present).


The answer to this situation is NetworkManager, not the installer. Enable it post-install:

    chkconfig NetworkManagerDispatcher on
    chkconfig NetworkManager on

Use it.  Never futz with the ifcfg-ethX scripts again.

Then the installer should set this up.

Agreed. I'd like the network configuration stage of anaconda to be supplemented with a screen before it that asks "Would you like to enable NetworkManager?" accompanied by a description of network manager and the benefits and such. If the user selects yes, it skips of the network configuration screen. If they select no, we go to the network configuration screen. I have it on a to do list somewhere.

David, I don't like off-list replies. They don't filter well (I use the list-id header), and they break threads.

Do you think you could coax the list manager to change this list's settings so that its default is for replies to go to the list, as is appropriate for a discussion list?

Also agreed. I'll see what I can do. No promises and no guarantees that I won't forget about this 5 seconds after sending the email.

--
David Cantrell
Red Hat / Westford, MA


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux