I am really just trying to auto bringup eth0 on boot. Christopher, I don't have dhcpcd, so I enabled udhcpc@eth0. No dice. Is dhcpcd@eth0 how you guys bring up on boot? I've been using udhcpc for my wireless connections and I have no complain.
Thank you, Adam On Mon, May 5, 2014 at 5:41 PM, Stephen Arnold <[email protected]> wrote: > Well, none of my rpi or bbb images use systemd/connman/networkmanager and > I'm just fine with that as the baseline. > > Steve > > > On Mon, May 5, 2014 at 5:37 PM, Christopher Larson <[email protected]>wrote: > >> On Mon, May 5, 2014 at 5:31 PM, Adam Lee <[email protected]> wrote: >> >> > I noticed networking.service is masked by default - >> > >> > >> http://cgit.openembedded.org/cgit.cgi/openembedded-core/tree/meta/recipes-core/systemd/systemd-compat-units.bb?h=master >> > . >> > >> > I guess I can use the Network Manager to bring up eth0 on boot, but I >> > rather not. >> > >> > What's the harm in networking.service? >> > >> >> Is it really needed? Does systemctl enable dhcpcd@eth0 not do the job, or >> am I missing something? >> -- >> Christopher Larson >> clarson at kergoth dot com >> Founder - BitBake, OpenEmbedded, OpenZaurus >> Maintainer - Tslib >> Senior Software Engineer, Mentor Graphics >> -- >> _______________________________________________ >> Openembedded-devel mailing list >> [email protected] >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
