Is antiX going to get s6 init manager?

[Anonymous]

Helpful

Up

0

::

I did it says
strace: Can't stat '/usr/66-scandir': No such file or directory

[Member eric]

Helpful

Up

0

::

not /usr but /usr/bin/66-scandir 🙂

[Anonymous]

Helpful

Up

0

::

ok that correction spit out a bunch of info.
on this when I rebooted is mounted ro like normal and
verbosity=4 on kernel line.

[Anonymous]

Helpful

Up

0

::

htop also shows 66-boot -m as pid 1 running
also this is a fresh install and hasn’t been updated at all from the
19.3-runit-32-bit full iso and is on a p-4 hp zv-5000 laptop.

[Anonymous]

Helpful

Up

0

::

sorry for typo and quick misread. been hectic lately.

[Anonymous]

Helpful

Up

0

::

want to switch test to bullseye and build documentation for this? or
stick to buster.

[Member eric]

Helpful

Up

0

::

To be honest i don’t know what happens here. I expected a crash at the 66-scandir call and it’s not the case. The 66-scandir finish correctly. So nothing wrong on the 66-scandir code itself.

I don’t understand why the call by 66-boot to the 66-scandir tool sent an error.
Need reflexion….
What is puzzled me it’s that Void do not have the trouble.

[Anonymous]

Helpful

Up

0

::

? I don’t use void and no idea just trying to help on a clean test machine.

[Member fungalnet]

Helpful

Up

0

::

301 openat(AT_FDCWD, “/lib/i386-linux-gnu/i686/sse2/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/lib/i386-linux-gnu/i686/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/lib/i386-linux-gnu/sse2/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/lib/i386-linux-gnu/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/usr/lib/i386-linux-gnu/i686/sse2/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/usr/lib/i386-linux-gnu/i686/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/usr/lib/i386-linux-gnu/sse2/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/usr/lib/i386-linux-gnu/liboblibs.so.0.1”, O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
301 openat(AT_FDCWD, “/lib/liboblibs.so.0.1”

Maybe some linking or different configuration path would help?
And what is calling for liboblibs.so.0.1?

• This reply was modified 2 years, 2 months ago by fungalnet.

anti-X - Adélie - obarun - systemd Free Space

[Member eric]

Helpful

Up

0

::

@linuxdaddy
I really appreciated your contributions :).

@fungalnet
Good catch. Maybe @anticapitalista can try to build it in static mode instead of shared to see what happens.

[Member mobinmob]

Helpful

Up

0

::

eric wrote:

@linuxdaddy
I really appreciated your contributions :).

@fungalnet
Good catch. Maybe @anticapitalista can try to build it in static mode instead of shared to see what happens.

I have --libdir=/usr/lib in my oblibs packaging template and --with-lib=${XBPS_CROSS_BASE}/usr/lib in the 66 and 66-tools templates. I am aware that these have to do with static libs, but maybe it makes sense using something like --with-dynlib=/usr/lib in the build script or indeed make a static build. /usr/lib/i386-linux-gnu/liboblibs.so.0.1 seems something that has do with cross-building.

• This reply was modified 2 years, 2 months ago by mobinmob.

[Anonymous]

Helpful

Up

0

::

@eric : you’re welcome hopefully it helps pinpoint the problem

[Member oops]

Helpful

Up

0

::

anticapitalista wrote:

antiX-21-a1 running s6/66 with sysvinit removed.

After few tests here too (AMD64), s6/66 init seems promising for antiX.

• This reply was modified 2 years, 2 months ago by oops.
• This reply was modified 2 years, 2 months ago by oops.

[Member fungalnet]

Helpful

Up

0

::

When I looked for i386 image to test with all I found was 19, is there a link to this 21-beta?
I assume that if you switch repos to next level you get 21 after dist-upgrade.

anti-X - Adélie - obarun - systemd Free Space

[Member userzero]

Helpful

Up

0

::

Not available for i386.

https://sourceforge.net/projects/antix-linux/files/Testing/

“I assume that if you switch repos to next level you get 21 after dist-upgrade”

antiX-FAQ:

If you have a very old desktop/laptop with less than 256MB RAM (PII, PIII), or you want a desktop with “the basics”, it is probably best to use antiX-base.

If you want complete control over what applications to install and know the Debian system fairly well, then use antiX-core or antiX-net since both these do not include X.

[Author]

Posts