* is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
@ 2022-07-06 16:38 Robert P. J. Day
2022-07-06 16:40 ` [OE-core] " Khem Raj
0 siblings, 1 reply; 8+ messages in thread
From: Robert P. J. Day @ 2022-07-06 16:38 UTC (permalink / raw)
To: OE Core mailing list
not sure why i never noticed this before, but i started a new
project from the poky layer (not OE), and realized that poky.conf
explicitly sets:
INIT_MANAGER = "sysvinit"
which can't be overridden in my local.conf. if i want systemd, i guess
i can initialize my project from the OE layer, and i also notice that
i could use poky-altcfg.conf.
but is there a reason that the default poky-based project fixes
INIT_MANAGER to "sysvinit". perhaps just for simplicity?
rday
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
2022-07-06 16:38 is "poky" distro defined to use "sysvinit" as INIT_MANAGER? Robert P. J. Day
@ 2022-07-06 16:40 ` Khem Raj
2023-01-03 14:41 ` Michael Opdenacker
[not found] ` <1736D38C7177CA6A.6604@lists.openembedded.org>
0 siblings, 2 replies; 8+ messages in thread
From: Khem Raj @ 2022-07-06 16:40 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: OE Core mailing list
On Wed, Jul 6, 2022 at 12:38 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
>
> not sure why i never noticed this before, but i started a new
> project from the poky layer (not OE), and realized that poky.conf
> explicitly sets:
>
> INIT_MANAGER = "sysvinit"
>
> which can't be overridden in my local.conf. if i want systemd, i guess
> i can initialize my project from the OE layer, and i also notice that
> i could use poky-altcfg.conf.
>
> but is there a reason that the default poky-based project fixes
> INIT_MANAGER to "sysvinit". perhaps just for simplicity?
>
poky defaults to sysvinit.
poky has poky-alt distro fi you want to use say systemd
> rday
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167735): https://lists.openembedded.org/g/openembedded-core/message/167735
> Mute This Topic: https://lists.openembedded.org/mt/92210454/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
2022-07-06 16:40 ` [OE-core] " Khem Raj
@ 2023-01-03 14:41 ` Michael Opdenacker
[not found] ` <1736D38C7177CA6A.6604@lists.openembedded.org>
1 sibling, 0 replies; 8+ messages in thread
From: Michael Opdenacker @ 2023-01-03 14:41 UTC (permalink / raw)
To: Richard Purdie; +Cc: OE Core mailing list, Khem Raj, Robert P. J. Day
Hello Richard,
Trying to improve the documentation about the selection of the init
system, I'm jumping back to this old conversation, following a change
that you made (https://lists.yoctoproject.org/g/poky/message/12760).
Am 06.07.22 um 18:40 schrieb Khem Raj:
> On Wed, Jul 6, 2022 at 12:38 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>>
>> not sure why i never noticed this before, but i started a new
>> project from the poky layer (not OE), and realized that poky.conf
>> explicitly sets:
>>
>> INIT_MANAGER = "sysvinit"
>>
>> which can't be overridden in my local.conf. if i want systemd, i guess
>> i can initialize my project from the OE layer, and i also notice that
>> i could use poky-altcfg.conf.
>>
>> but is there a reason that the default poky-based project fixes
>> INIT_MANAGER to "sysvinit". perhaps just for simplicity?
>>
> poky defaults to sysvinit.
> poky has poky-alt distro fi you want to use say systemd
But why not setting INIT_MANAGER with "?=" instead of "=" in poky.conf?
This way, we could just override INIT_MANAGER from local.conf.
I checked that the generated system works. This would make things easier
to document, unless I'm missing other reasons.
Thanks in advance,
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
[not found] ` <1736D38C7177CA6A.6604@lists.openembedded.org>
@ 2023-01-05 14:23 ` Michael Opdenacker
2023-01-05 14:57 ` Richard Purdie
0 siblings, 1 reply; 8+ messages in thread
From: Michael Opdenacker @ 2023-01-05 14:23 UTC (permalink / raw)
To: Richard Purdie
Cc: OE Core mailing list, Khem Raj, Robert P. J. Day, YP docs mailing list
Am 03.01.23 um 15:41 schrieb Michael Opdenacker via lists.openembedded.org:
> Hello Richard,
>
> Trying to improve the documentation about the selection of the init
> system, I'm jumping back to this old conversation, following a change
> that you made (https://lists.yoctoproject.org/g/poky/message/12760).
>
> Am 06.07.22 um 18:40 schrieb Khem Raj:
>> On Wed, Jul 6, 2022 at 12:38 PM Robert P. J. Day
>> <rpjday@crashcourse.ca> wrote:
>>>
>>> not sure why i never noticed this before, but i started a new
>>> project from the poky layer (not OE), and realized that poky.conf
>>> explicitly sets:
>>>
>>> INIT_MANAGER = "sysvinit"
>>>
>>> which can't be overridden in my local.conf. if i want systemd, i guess
>>> i can initialize my project from the OE layer, and i also notice that
>>> i could use poky-altcfg.conf.
>>>
>>> but is there a reason that the default poky-based project fixes
>>> INIT_MANAGER to "sysvinit". perhaps just for simplicity?
>>>
>> poky defaults to sysvinit.
>> poky has poky-alt distro fi you want to use say systemd
>
> But why not setting INIT_MANAGER with "?=" instead of "=" in poky.conf?
>
> This way, we could just override INIT_MANAGER from local.conf.
>
> I checked that the generated system works. This would make things
> easier to document, unless I'm missing other reasons.
Richard told me on IRC that, from memory, this was set because of
interference poky-altcfg (if I understood correctly).
I understand one recommended way to have systemd instead of sysvinit in
Poky is to use "poky-altcfg" instead of "poky" as distro.
Similarly, I guess I should use "poky-tiny" if I want to use
"mdev-busybox" as INIT_MANAGER.
Then, I guess I'll document something like this:
* With the OpenEmbedded build system, you can choose your init system
by setting INIT_MANAGER to "sysvinit", "systemd", "busybox-mdev" or
"none"
* BUT if you're using Poky, that won't work, so your options will be
to use either "poky" (sysvinit), "poky-altcfg" (systemd) or
"poky-tiny" (mdev-busybox).
Does this sound like the right way to document this?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
2023-01-05 14:23 ` Michael Opdenacker
@ 2023-01-05 14:57 ` Richard Purdie
2023-01-05 15:02 ` Michael Opdenacker
2023-01-05 21:46 ` Peter Kjellerstedt
0 siblings, 2 replies; 8+ messages in thread
From: Richard Purdie @ 2023-01-05 14:57 UTC (permalink / raw)
To: Michael Opdenacker
Cc: OE Core mailing list, Khem Raj, Robert P. J. Day, YP docs mailing list
On Thu, 2023-01-05 at 15:23 +0100, Michael Opdenacker wrote:
> Am 03.01.23 um 15:41 schrieb Michael Opdenacker via lists.openembedded.org:
> > Hello Richard,
> >
> > Trying to improve the documentation about the selection of the init
> > system, I'm jumping back to this old conversation, following a change
> > that you made (https://lists.yoctoproject.org/g/poky/message/12760).
> >
> > Am 06.07.22 um 18:40 schrieb Khem Raj:
> > > On Wed, Jul 6, 2022 at 12:38 PM Robert P. J. Day
> > > <rpjday@crashcourse.ca> wrote:
> > > >
> > > > not sure why i never noticed this before, but i started a new
> > > > project from the poky layer (not OE), and realized that poky.conf
> > > > explicitly sets:
> > > >
> > > > INIT_MANAGER = "sysvinit"
> > > >
> > > > which can't be overridden in my local.conf. if i want systemd, i guess
> > > > i can initialize my project from the OE layer, and i also notice that
> > > > i could use poky-altcfg.conf.
> > > >
> > > > but is there a reason that the default poky-based project fixes
> > > > INIT_MANAGER to "sysvinit". perhaps just for simplicity?
> > > >
> > > poky defaults to sysvinit.
> > > poky has poky-alt distro fi you want to use say systemd
> >
> > But why not setting INIT_MANAGER with "?=" instead of "=" in poky.conf?
> >
> > This way, we could just override INIT_MANAGER from local.conf.
> >
> > I checked that the generated system works. This would make things
> > easier to document, unless I'm missing other reasons.
>
>
> Richard told me on IRC that, from memory, this was set because of
> interference poky-altcfg (if I understood correctly).
>
> I understand one recommended way to have systemd instead of sysvinit in
> Poky is to use "poky-altcfg" instead of "poky" as distro.
>
> Similarly, I guess I should use "poky-tiny" if I want to use
> "mdev-busybox" as INIT_MANAGER.
>
> Then, I guess I'll document something like this:
>
> * With the OpenEmbedded build system, you can choose your init system
> by setting INIT_MANAGER to "sysvinit", "systemd", "busybox-mdev" or
> "none"
> * BUT if you're using Poky, that won't work, so your options will be
> to use either "poky" (sysvinit), "poky-altcfg" (systemd) or
> "poky-tiny" (mdev-busybox).
>
> Does this sound like the right way to document this?
We should really fix poky so this works correctly. I just have a memory
of trying to fix it and it not being as straightforward it first
appears. I'd then have got distracted by the next problem :/
Cheers,
Richard
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
2023-01-05 14:57 ` Richard Purdie
@ 2023-01-05 15:02 ` Michael Opdenacker
2023-01-05 15:09 ` [docs] " Alexander Kanavin
2023-01-05 21:46 ` Peter Kjellerstedt
1 sibling, 1 reply; 8+ messages in thread
From: Michael Opdenacker @ 2023-01-05 15:02 UTC (permalink / raw)
To: Richard Purdie
Cc: michael.opdenacker, OE Core mailing list, Khem Raj,
Robert P. J. Day, YP docs mailing list
Am 05.01.23 um 15:57 schrieb Richard Purdie:
> On Thu, 2023-01-05 at 15:23 +0100, Michael Opdenacker wrote:
>>
>> Richard told me on IRC that, from memory, this was set because of
>> interference poky-altcfg (if I understood correctly).
>>
>> I understand one recommended way to have systemd instead of sysvinit in
>> Poky is to use "poky-altcfg" instead of "poky" as distro.
>>
>> Similarly, I guess I should use "poky-tiny" if I want to use
>> "mdev-busybox" as INIT_MANAGER.
>>
>> Then, I guess I'll document something like this:
>>
>> * With the OpenEmbedded build system, you can choose your init system
>> by setting INIT_MANAGER to "sysvinit", "systemd", "busybox-mdev" or
>> "none"
>> * BUT if you're using Poky, that won't work, so your options will be
>> to use either "poky" (sysvinit), "poky-altcfg" (systemd) or
>> "poky-tiny" (mdev-busybox).
>>
>> Does this sound like the right way to document this?
> We should really fix poky so this works correctly. I just have a memory
> of trying to fix it and it not being as straightforward it first
> appears. I'd then have got distracted by the next problem :/
As far as I am concerned, I tried to set INIT_MANAGER with "?=" in
poky.conf and the set INIT_MANAGER = "systemd" in local.conf and the
resulting system was booting fine.
Shall we make the change in master and see if autobuilders catch any
issue? Unless your remember was the complexity was about.
Or shall I file a bug so that one of us addresses this when (s)he has time?
Thanks for your help on this!
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [docs] [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
2023-01-05 15:02 ` Michael Opdenacker
@ 2023-01-05 15:09 ` Alexander Kanavin
0 siblings, 0 replies; 8+ messages in thread
From: Alexander Kanavin @ 2023-01-05 15:09 UTC (permalink / raw)
To: michael.opdenacker
Cc: Richard Purdie, OE Core mailing list, Khem Raj, Robert P. J. Day,
YP docs mailing list
On Thu, 5 Jan 2023 at 16:02, Michael Opdenacker via
lists.yoctoproject.org
<michael.opdenacker=bootlin.com@lists.yoctoproject.org> wrote:
> As far as I am concerned, I tried to set INIT_MANAGER with "?=" in
> poky.conf and the set INIT_MANAGER = "systemd" in local.conf and the
> resulting system was booting fine.
> Shall we make the change in master and see if autobuilders catch any
> issue? Unless your remember was the complexity was about.
I think you have the privilege of running things directly on the AB
without having to ask anyone, so I'd say just make a commit and toss
it into one of the master-next builds that bootlin runs :)
Alex
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: [docs] [OE-core] is "poky" distro defined to use "sysvinit" as INIT_MANAGER?
2023-01-05 14:57 ` Richard Purdie
2023-01-05 15:02 ` Michael Opdenacker
@ 2023-01-05 21:46 ` Peter Kjellerstedt
1 sibling, 0 replies; 8+ messages in thread
From: Peter Kjellerstedt @ 2023-01-05 21:46 UTC (permalink / raw)
To: Richard Purdie, Michael Opdenacker
Cc: OE Core mailing list, Khem Raj, Robert P. J. Day, YP docs mailing list
> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf
> Of Richard Purdie
> Sent: den 5 januari 2023 15:57
> To: Michael Opdenacker <michael.opdenacker@bootlin.com>
> Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>; Khem
> Raj <raj.khem@gmail.com>; Robert P. J. Day <rpjday@crashcourse.ca>; YP
> docs mailing list <docs@lists.yoctoproject.org>
> Subject: Re: [docs] [OE-core] is "poky" distro defined to use "sysvinit"
> as INIT_MANAGER?
>
> On Thu, 2023-01-05 at 15:23 +0100, Michael Opdenacker wrote:
> > Am 03.01.23 um 15:41 schrieb Michael Opdenacker via
> lists.openembedded.org:
> > > Hello Richard,
> > >
> > > Trying to improve the documentation about the selection of the init
> > > system, I'm jumping back to this old conversation, following a change
> > > that you made (https://lists.yoctoproject.org/g/poky/message/12760).
> > >
> > > Am 06.07.22 um 18:40 schrieb Khem Raj:
> > > > On Wed, Jul 6, 2022 at 12:38 PM Robert P. J. Day
> > > > <rpjday@crashcourse.ca> wrote:
> > > > >
> > > > > not sure why i never noticed this before, but i started a new
> > > > > project from the poky layer (not OE), and realized that poky.conf
> > > > > explicitly sets:
> > > > >
> > > > > INIT_MANAGER = "sysvinit"
> > > > >
> > > > > which can't be overridden in my local.conf. if i want systemd, i guess
> > > > > i can initialize my project from the OE layer, and i also notice that
> > > > > i could use poky-altcfg.conf.
> > > > >
> > > > > but is there a reason that the default poky-based project fixes
> > > > > INIT_MANAGER to "sysvinit". perhaps just for simplicity?
> > > > >
> > > > poky defaults to sysvinit.
> > > > poky has poky-alt distro fi you want to use say systemd
> > >
> > > But why not setting INIT_MANAGER with "?=" instead of "=" in poky.conf?
> > >
> > > This way, we could just override INIT_MANAGER from local.conf.
> > >
> > > I checked that the generated system works. This would make things
> > > easier to document, unless I'm missing other reasons.
> >
> >
> > Richard told me on IRC that, from memory, this was set because of
> > interference poky-altcfg (if I understood correctly).
> >
> > I understand one recommended way to have systemd instead of sysvinit in
> > Poky is to use "poky-altcfg" instead of "poky" as distro.
I am not sure using poky-altcfg as an alternative to using poky + systemd
is a good suggestion since poky-altcfg changes a couple of other settings as
well (see meta-poky/conf/distro/include/poky-distro-alt-test-config.inc).
> >
> > Similarly, I guess I should use "poky-tiny" if I want to use
> > "mdev-busybox" as INIT_MANAGER.
> >
> > Then, I guess I'll document something like this:
> >
> > * With the OpenEmbedded build system, you can choose your init system
> > by setting INIT_MANAGER to "sysvinit", "systemd", "busybox-mdev" or
> > "none"
> > * BUT if you're using Poky, that won't work, so your options will be
> > to use either "poky" (sysvinit), "poky-altcfg" (systemd) or
> > "poky-tiny" (mdev-busybox).
> >
> > Does this sound like the right way to document this?
>
> We should really fix poky so this works correctly. I just have a memory
> of trying to fix it and it not being as straightforward it first
> appears. I'd then have got distracted by the next problem :/
>
> Cheers,
>
> Richard
You can of course override it in your local.conf, but it requires to use an
override, e.g., INIT_MANAGER:poky = "systemd" should work if you are in fact
using the poky distro.
However, since the recommendation typically is to use your own distro if you
are doing more serious changes (like, e.g., using another init manager than
the default one), this should normally not be a problem. In the simplest case
you can create a distro like:
require conf/distro/poky.conf
INIT_MANAGER = "systemd"
and you are then better off than doing this kind of changes in your
local.conf.
//Peter
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2023-01-05 21:46 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-06 16:38 is "poky" distro defined to use "sysvinit" as INIT_MANAGER? Robert P. J. Day
2022-07-06 16:40 ` [OE-core] " Khem Raj
2023-01-03 14:41 ` Michael Opdenacker
[not found] ` <1736D38C7177CA6A.6604@lists.openembedded.org>
2023-01-05 14:23 ` Michael Opdenacker
2023-01-05 14:57 ` Richard Purdie
2023-01-05 15:02 ` Michael Opdenacker
2023-01-05 15:09 ` [docs] " Alexander Kanavin
2023-01-05 21:46 ` Peter Kjellerstedt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.