On Sat, 2011-08-06 at 16:54 -0400, Felix Miata wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=727381 stops me from doing a > fresh F16 install, so I converted an F15 to F16. After finishing, I did some > culling of packages I'll never use with yum. In the process, something > eradicated Network Manager. This I don't mind, because under this roof there > is only ethernet. Now I can't figure out what it takes to make systemd start > the network in appropriate runlevels. I created a symlink from > /lib/systemd/system/network.target to > /etc/systemd/system/multi-user.target.wants/network.target, but that didn't > help. Is there some other package needed to make traditional networking auto > start? If not, what is required? Try 'systemctl enable network.service' . As network.service is really still the SysV 'network' service, it'll redirect to 'chkconfig network on'. systemd's network.target is something different; it's a sort of systemd built-in. See 'man systemd.special': network.target systemd automatically adds dependencies of type After for this target unit to all SysV init script service units with an LSB header referring to the $network facility. i.e. it's used as part of handling the LSB dependency standard stuff, it's used to ensure services that need networking get started after the network comes up. It's not a service that actually starts networking. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
