how can i emulate sysvipc init?

[dontknowhy]

i notice proot has "--sysvipc" option
but i can launch it and it doesn't works???
when i try to tun "init 3",it allways says:Couldn't find an alternative telinit implementation to spawn.
how can i fix it?
and can i use systemd in Proot?

[michalbednarski]

sysvipc stands for System V IPC (Inter Process Communication) and is unrelated to init (--sysvipc switch allows using for example fakeroot)

SystemD cannot work inside proot (due to not being pid 1, although I'd expect further issues (haven't tried so I don't know if it'd be cgroups/namespaces/mounts or something else) if that one would be emulated)

Usually proot is used without init inside guest and launching necessary services manually from shell

[dontknowhy]

I think you want last line to be exec $command /bin/sh -c "init -i & ; login"

/usr/bin/sh: 1: Syntax error: ";" unexpected
…

[dontknowhy]

I think you want last line to be exec $command /bin/sh -c "init -i & ; login"

/usr/bin/sh: 1: Syntax error: ";" unexpected
…

i started the container…
but…

my termux IS BROKEN!!!
how to disable this selinux… or how can i disable this output…(tried >>/dev/null)

[dontknowhy]

I think you want last line to be exec $command /bin/sh -c "init -i & ; login"

now it's working
and terminal working fine…
but the selinux mount failed text still can't fix it(i need to login twice because login will think this mesage is my password)
i tried to disable selinux by creating a fake config file in /etc/selinux/config
but dpkg will crash because its connection to the information channel is disconnected (translated from Chinese)
how can i clear this mesage?(it will make terminal run into a problem)

[michalbednarski]

I guess it'd be
exec $command /bin/sh -c "init -i < /dev/null > /dev/null 2> /dev/null & ; login"

Though I think you're going too far and need to step back and answer what you need init for in first place

[dontknowhy]

I guess it'd be
exec $command /bin/sh -c "init -i < /dev/null > /dev/null 2> /dev/null & ; login"

Though I think you're going too far and need to step back and answer what you need init for in first place

i only want a working service manager and it's working like a normal computer…
also this command doesn't work:

i tried bash but it doesn't work too…

[JanuszChmiel]

Some important remarks related to services.
Some services depend on real Linux kernel so it is impossible to use them from Proot.
Some services can depend on standard Linux.
So before loading some services from Bash shell or from other shell.
It is necessary to contact The specific service author and ask him, if his service depend on some specific Linux kernel system call or kernel module, which is not Thepart of Android kernel.
I personally do not start services in Chroot enviroinment on Android device.
I simply run apps, desktop environments, I can build and compile apps.
I would like to have dbus-broker functioning on Fedora37. Not standard dbus, but really dbus-broker. It is preconfigured professionally when user use The official Fedora Linux installer.
But The question is, if dbus-broker do not depend on some specific Linux kernel system calls.
Some apps such as various modern Linux repositoryes containers refuse to run on non rooted Android devices.
For example Flatpak.
So it is impossible to anticipate, that chrooted Linux container which are being executed by Android non rooted devices by using Proot will work as a Linux distros which ou are boot on virtual machine or directly from some bootable arbitrary media.

From my personal experience.
Proot work The best on devices, where Proot do not have to use too much work arounds to overcome issues with some Android kernels and system configurations.
Some devices have wrongly implemented Pokedata system call, some devices are having troubles with other file system features or system calls.

Some devices have encryption enabled by default, so performance is also slower.
It is complex problematic.