FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 10-28-2008, 03:38 PM
Jesse Keating
 
Default Default network configuration during installation, NetworkManager and the /etc/sysconfig/network-script's

On Tue, 2008-10-28 at 11:31 +0000, Michael Cutler wrote:
>
> (1). Include NetworkManager in the '@core' group, such that every
> install will include NetworkManager and a minimal install as described
> above will bring the system up with network connectivity.

And here we have another fun argument about how 'minimal' should the
minimal install be! We've chucked yum in @core, might as well chuck
NetworkManager too...

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
identi.ca: http://identi.ca/jkeating
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 10-28-2008, 09:51 PM
Les Mikesell
 
Default Default network configuration during installation, NetworkManager and the /etc/sysconfig/network-script's

David Cantrell wrote:

On Tue, Oct 28, 2008 at 11:31:40AM +0000, Michael Cutler wrote:

(1). Include NetworkManager in the '@core' group, such that every install will include NetworkManager and a minimal install as described above will bring the system up with network connectivity.


I'm not opposed to this, but I'm also not opposed to it staying where it is.


(2). Add some logic to the installer, if NetworkManager isnt to be installed, adjust the /etc/sysconfig/network-scripts appropriately such that network connectivity comes up after install. However this could be more problematic that I first thought, how many interfaces do you enable? If I have 4 NIC's, 3 not connected do I need to wait for the 'network' service to give up on the other three NIC's before bringing the system up etc.


I'm not in favor of this. The situation you're describing is exactly why we
wanted to get rid of the network configuration screen.



Isn't the system already capable of knowing if link is up on an
interface and not waiting for dhcp if it isn't connected?


--
Les Mikesell
lesmikesell@gmail.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 10-28-2008, 09:57 PM
Les Mikesell
 
Default Default network configuration during installation, NetworkManager and the /etc/sysconfig/network-script's

David Cantrell wrote:

On Tue, Oct 28, 2008 at 06:45:44PM -0400, Chuck Anderson wrote:

On Tue, Oct 28, 2008 at 12:39:31PM -1000, David Cantrell wrote:

On Tue, Oct 28, 2008 at 02:18:55PM -0400, Chuck Anderson wrote:
I think it is a perfectly reasonable default to have DHCP enabled by
default for all network interfaces, whether NetworkManager is used or
not.

Seriously?

Yes, why not?


Right away I can think of the user with 185 network interfaces complaining
about boot up taking too long because he's having to wait for each one to time
out.


Assume that only the ones that he wants to use are connected. And that
he wants to do the initial install via NFS.


--
Les Mikesell
lesmikesell@gmail.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 07:07 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org