> From: Paul D. DeRocco > > My build is an Intel Cedartrail system based on Dylan, using > systemd. It > appears to have udhcp available from busybox, but it's not > running. systemd > reports that it is "masked", because > /etc/systemd/system/busybox-udhcpc.service is linked to > /dev/null. What > creates this link, and how do I get the DHCP client enabled > in my build? Is > there something else I need to include?
It appears this is masked by a post-install script in meta/recipes-core/systemd/system-compat-units.bb. The comment says "Units to make systemd work better with existing sysvinit scripts." Doesn't seem like it's doing that in this case. However, if I tweak the recipe so that the systemd service unit for busybox-udhcpc isn't masked, it doesn't reveal a valid service unit, I wind up with nothing. That suggests that there should be a sysvinit script somewhere else for starting udhcpc, but I can't find anything under /etc that contains the string "udhcpc" other than the script that udhcpc calls when an interface changes state. I also find that I can manually run udhcpc with the appropriate interface parameter, and it works fine; my Samba server from OE becomes accessible from a Windows machine, and everything seems happy. So how is udhcpc normally supposed to be launched? I could hack it in any number of ways, but I'd like to know the right way, because I'd like it to be able to assign an address if someone plugs in a USB WiFi dongle, too, and that's beyond my ability. Or is this just something that works with sysvinit, but no one's gotten around to figuring out how to integrate it into systemd, and I'm on my own? -- Ciao, Paul D. DeRocco Paul mailto:[email protected] _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
