Bob Goodwin: > The old system-config-network was better for my purposes but > attempts to remove NM have caused extremely long "boot" times each > time I've tried that. It would increase from the present thirty > seconds or so to several minutes Seemingly network-related prolonged bootup times could be down to several issues. Just to mention some of them: Name resolution - something is trying to resolve a name (e.g. the machine's own hostname), but can't because name resolution isn't working, or the network isn't up for it to access the name server. Or, for systems where the name resolution will be done on the same machine, the network isn't up, yet, and things are waiting for the network to come up before they start working, even if they don't need to make external access. They're just waiting for the network to come up. And those waiting things hold up the boot process. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
