On Tuesday, February 22, 2011 09:51:27 AM Bill Nottingham wrote: > A.J. Werkman (AJ.Werkman@xxxxxxxxxxxx) said: > > >1.http://0pointer.de/blog/projects/systemd-for-admins-1.html > > >2.http://0pointer.de/blog/projects/systemd-for-admins-2.html > > >3.http://0pointer.de/blog/projects/systemd-for-admins-3.html > > >4.http://0pointer.de/blog/projects/systemd-for-admins-3.html > > > > Yes I know. But is the old network startup script not ported to the > > new systemd? That would mean I am forced to use NetworkManager to > > start up networking? > > The network script will call NM to control interfaces if NM > happens to be running. There are some discussions on how NM gets > autostarted under some conditions where it perhaps shouldn't be > that are still being resolved. I remember in the past that nmcli was called when starting network to check on something. the result was that NetworkManager had to be running since systemd opens the socket so without a running NetworkManager you got no network as nmcli would hang waiting for a response. this was back when F14 was in development so it could have been resolved. ive not tried lately. Dennis
Attachment:
signature.asc
Description: This is a digitally signed message part.
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
