**** BEGIN LOGGING AT Sat Feb 02 02:59:56 2019 Feb 02 17:45:58 Here's a fun one. With thud, nodistro, systemd and a USB eth adapter (that works if I tell udhcpc to use it by hand) should I expect networking to come up? Feb 02 17:54:40 afaik networking won't come up automatically by default with systemd at all unless you enable systemd-networkd, install and use a manager like connman, or systemctl enable dhcpcd@ or similar Feb 02 17:54:45 not ideal :\ Feb 02 17:56:31 perhaps that last part is it then. I have some examples sitting around of bbappending in a unit Feb 02 17:56:36 But that seems less than ideal Feb 02 17:57:26 connman or networkmanager would probably bring it up by default being regular ethernet.. *shrugs* Feb 02 17:57:35 not sure about systemd-networkd, but that can be enabled via packageconfig Feb 02 17:57:45 Yeah, networkd is there Feb 02 17:58:01 but doesn't dhcp them by default as I guess I need to enable that service Feb 02 17:58:06 ah Feb 02 17:58:11 brb Feb 02 18:03:04 Alright, thanks. Looks like I really will need to go the unit way or similar Feb 02 18:04:01 np. lots of options, it's irritating we don't have a clean automatic setup out of the box without needing a heavier network manager or providing more config to systemd.. we used to have something for it with ifupdown/interfaces + hotplug scripts.. Feb 02 18:04:56 networkd definitely seems rather manual — https://wiki.archlinux.org/index.php/Systemd-networkd#Required_services_and_setup Feb 02 18:08:45 I _think_ and will be testing shortly, pulling in dhcp-client and then enabling it by default rather than not, will solve this use case of mine Feb 02 18:10:21 and as arch notes you can use wildcards, which is what the other example (that I didn't trust to be the best example) does Feb 02 18:10:30 ah, interesting Feb 02 18:10:35 connman isn't bad, really, but a little heavier than a systemctl approach, and manual and wifi config isn't exactly pretty Feb 02 18:11:19 Yeah, and I'm setting aside my wifi problems for later Feb 02 18:12:18 iwd seems interesting in that area, haven't tried it yet though. - https://wiki.archlinux.org/index.php/Iwd Feb 02 18:13:10 Isn't "-c devshell" supposed to put you in ${B} initially ? Feb 02 18:20:18 I mean ${S}.. Feb 02 18:25:33 There is DEVSHELL_STARTDIR but I don't see it being used Feb 02 19:11:55 so last entry in do_*[dirs] is the tasks working directory Feb 02 19:26:48 Sigh, nope dhcp-client and systemd and read-only-rootfs have a silly hiccup too wrt /etc/resolv.conf and perhaps lack of real integration Feb 02 19:30:11 Tartarus: ro-rfs+systemd is a PITA Feb 02 19:31:11 I have made it work to a certain extent for Yoe distro but it still keeps coming up with new kinks Feb 02 19:31:27 khem: seems to be working, but what should I be on the lookout for? Feb 02 19:32:44 VOLATILE_BINDS help in making files r/w Feb 02 19:33:24 things like /etc/hostname /var/lib /var/log being RO upsets systemd Feb 02 19:34:57 Ah Feb 02 19:36:25 I need to go whack meta-virtualization to append that for docker at least Feb 02 19:38:01 systemd-machine-id-commit.service needs /etc to be rw Feb 02 19:38:14 so you need to delete that check Feb 02 19:41:00 What's broken without it tho? Feb 02 19:41:23 Part of why I'm doing read-only-rootfs atm is I'm also doing mender on top of this for updates, so transient data needs to be transient, really Feb 02 19:46:23 well it generates machine_id on boot Feb 02 19:48:54 khem: OK. But that can change or otherwise be re-created at will on boot without harm? Feb 02 19:49:20 read-only is a good way to catch stuff that will possibly fail or be otherwise unhappy when moving from A to B Feb 02 20:25:00 yes everything can be donw Feb 02 20:25:23 as I mentioned road is filled with potholes so brace **** ENDING LOGGING AT Sun Feb 03 02:59:56 2019