Re: [yocto] Changing over to systemd (no dhcp)

On 20-01-17 14:59, colin.helliw...@ln-systems.com wrote: Thanks for all the pointers everyone. I’ve now got (in my distro conf): DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_remove = " sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" PREFERRED_PROVIDER_udev = "systemd"

Re: [yocto] Changing over to systemd (no dhcp)

On Mon, 2017-01-23 at 07:47 +, colin.helliw...@ln-systems.com wrote: > Looking at one which does seem to switch over cleanly - dropbear - I'm > puzzled how the recipe [dropbear.inc, in poky/meta/recipes-core] > appears to install both init.d script and .service in its do_install, > yet only

Re: [yocto] Changing over to systemd (no dhcp)

On 21-01-17 13:41, Leon Woestenberg wrote: Hello Mike, On Fri, Jan 20, 2017 at 3:27 PM, Mike Looijmans > wrote: An no one (except one of the systemd folks) has come up with a program that just waits for the the processes to

Re: [yocto] Changing over to systemd (no dhcp)

oestenberg [mailto:l...@sidebranch.com] Sent: 21 January 2017 13:09 To: colin.helliw...@ln-systems.com Cc: Yocto discussion list <yocto@yoctoproject.org> Subject: Re: [yocto] Changing over to systemd (no dhcp) Hi Colin, On Fri, Jan 20, 2017 at 2:59 PM, <colin.helliw...@ln

Re: [yocto] Changing over to systemd (no dhcp)

<yocto@yoctoproject.org> Subject: Re: [yocto] Changing over to systemd (no dhcp) Hi Colin, On Fri, Jan 20, 2017 at 2:59 PM, <colin.helliw...@ln-systems.com> wrote: > > DISTRO_FEATURES_remove = " sysvinit" > > I suspect there’s also some de-cluttering needed e.g. init.

Re: [yocto] Changing over to systemd (no dhcp)

Hi Colin, On Fri, Jan 20, 2017 at 2:59 PM, wrote: > > DISTRO_FEATURES_remove = " sysvinit" > > I suspect there’s also some de-cluttering needed e.g. init.d scripts still > being installed as well as a .service. > I wouldn't expect these to be installed. Which

Re: [yocto] Changing over to systemd (no dhcp)

Hello Mike, On Fri, Jan 20, 2017 at 3:27 PM, Mike Looijmans wrote: > An no one (except one of the systemd folks) has come up with a program > that just waits for the the processes to finish (with a timeout) and only > uses the "-9" double barrel shotgun to finish only

Re: [yocto] Changing over to systemd (no dhcp)

On 20-01-17 07:15, Michael Gloff wrote: Mike, On Thu, Jan 19, 2017 at 3:18 AM, Mike Looijmans > wrote: On 18-01-17 16:10, colin.helliw...@ln-systems.com wrote: We have a

Re: [yocto] Changing over to systemd (no dhcp)

Thanks for all the pointers everyone. I've now got (in my distro conf): DISTRO_FEATURES_append = " systemd" DISTRO_FEATURES_remove = " sysvinit" VIRTUAL-RUNTIME_init_manager = "systemd" PREFERRED_PROVIDER_udev = "systemd" PACKAGECONFIG_append_pn-systemd = " resolved networkd" It's booting

Re: [yocto] Changing over to systemd (no dhcp)

On Wed, Jan 18, 2017 at 7:10 AM, wrote: > We have a configuration for our embedded system which is working via SysV, > but we’re investigating moving over to systemd. > > Not sure if this is ‘wise’ – if anyone has technological arguments > for/against then I’d be

Re: [yocto] Changing over to systemd (no dhcp)

Mike, On Thu, Jan 19, 2017 at 3:18 AM, Mike Looijmans wrote: > On 18-01-17 16:10, colin.helliw...@ln-systems.com wrote: > >> We have a configuration for our embedded system which is working via >> SysV, but >> we’re investigating moving over to systemd. >> >> Not sure

Re: [yocto] Changing over to systemd (no dhcp)

lth...@google.com>; 'Andre McCurdy' <armccu...@gmail.com> *Cc:* 'Yocto discussion list' <yocto@yoctoproject.org> *Subject:* Re: [yocto] Changing over to systemd (no dhcp) Hi Colin, For the dhcp problem, what you need is a network manager. Any network manager that supports dhcp would d

Re: [yocto] Changing over to systemd (no dhcp)

iscussion list' <yocto@yoctoproject.org> Subject: Re: [yocto] Changing over to systemd (no dhcp) Hi Colin, For the dhcp problem, what you need is a network manager. Any network manager that supports dhcp would do the job. systemd-networkd might be sufficient in your case. For the local.conf pr

Re: [yocto] Changing over to systemd (no dhcp)

On 18-01-17 16:10, colin.helliw...@ln-systems.com wrote: We have a configuration for our embedded system which is working via SysV, but we’re investigating moving over to systemd. Not sure if this is ‘wise’ – if anyone has technological arguments for/against then I’d be interested – but I

Re: [yocto] Changing over to systemd (no dhcp)

com> *Cc:* colin.helliw...@ln-systems.com; Yocto discussion list <yocto@yoctoproject.org> *Subject:* Re: [yocto] Changing over to systemd (no dhcp) I was wondering about this recently. Why are these snippets put in local.conf.sample.extended instead of separate, well-named .inc fil

Re: [yocto] Changing over to systemd (no dhcp)

...@ln-systems.com; Yocto discussion list <yocto@yoctoproject.org> Subject: Re: [yocto] Changing over to systemd (no dhcp) I was wondering about this recently. Why are these snippets put in local.conf.sample.extended instead of separate, well-named .inc files that can be shared by mult

Re: [yocto] Changing over to systemd (no dhcp)

On 18/01/17 16:10, colin.helliw...@ln-systems.com wrote: > We have a configuration for our embedded system which is working via > SysV, but we’re investigating moving over to systemd. > > Not sure if this is ‘wise’ – if anyone has technological arguments > for/against then I’d be interested – but

Re: [yocto] Changing over to systemd (no dhcp)

On Wed, Jan 18, 2017 at 7:10 AM, wrote: > We have a configuration for our embedded system which is working via SysV, > but we’re investigating moving over to systemd. > > Not sure if this is ‘wise’ – if anyone has technological arguments > for/against then I’d be

[yocto] Changing over to systemd (no dhcp)

We have a configuration for our embedded system which is working via SysV, but we're investigating moving over to systemd. Not sure if this is 'wise' - if anyone has technological arguments for/against then I'd be interested - but I wanted to investigate it anyway. I've modified local.conf