I think it would help to at least take this through a-full so we have a higher degree of knowledge in what breaks and what doesn’t.
I didn’t look at the patch in detail and won’t be able to for a few more days. We definitely need to understand how it affects other init systems, but it is totally doable, there is only a limited number of them and how they handle tmp directories and what they expect from them is tractable research. As long as no one expects RP to do that. Alex On Fri 17. Mar 2023 at 17.31, Markus Volk <[email protected]> wrote: > Am Fr, 17. Mär 2023 um 11:53:17 +0000 schrieb Richard Purdie < > [email protected]>: > > It would help me if adverse effects are mentioned in commit messages. In > this case I can spot it easily enough but I don't always know/spot all the > issues. > > > It would be too harsh to say that I don't care about sysvinit. Of course, > if something breaks as a result of this commit, I'm willing to take care of > it if I can help. It's just that I don't personally use it, so I haven't > identified any other issues that might be relevant to sysvinit. Other than > the obvious that anything that would write directly to '/var/volatile/tmp' > would break. > At least I checked that sysvinit images could still boot. I have > successfully run core-image-ptest-glib-2.0 with this patch applied. If I > knew of any problems with sysvinit I would have pointed them out, but > unfortunately I have no further findings yet > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#178759): https://lists.openembedded.org/g/openembedded-core/message/178759 Mute This Topic: https://lists.openembedded.org/mt/97667591/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
