On 16/11/12 13:47, Bob Goodwin - Zuni, Virginia, USA wrote:
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. I shut down at night and if I
   only reboot once it's a minor annoyance but if I do something that
   requires a reboot it becomes a major pain! That's probably the real
reason I still use NM, the removal is messy.

   I decided to disable NetworkManager on another F17/64 bit computer,
   did "yum install system-config-network." There was no problem with
   long boot times, 45 seconds on a slower computer, the boot process
   goes smoothly with no hitches where it stops and waits for something
   to time out.

   I find Yumex convenient at times, mainly for it's list of available
   app's.  Yumex would not connect until I yum removed NetworkManager?
   I don't know what else it may have caused problems with.

   Systemctl status network.service still works but that is the only
   one of those, start, restart, etc. Fail. It is convenient to have
   the NetworkManager icon where the connection can be controlled,
   sometimes I want to disconnect from the internet. Now all there is
   is the Network Control gui for that, inconvenient to use

   Just my observations at this point.

--
http://www.qrz.com/db/W2BOD

box7

--
users mailing list
users@lists.fedoraproject.org
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

Reply via email to