>>106984613
Because I only bothered to google what distrobox is today.

>>106984621
Docker and podman. Distrobox is just a bunch of bash scripts hiding the complexity. Toolbox is the same thing with less options too.

It seems you did not understand what distro is

>>106984670
Ok, thanks

>>106984675
enlighten me

>>106984909
Distro is the thing which manages kernel and x11 version, not the vice versa.

>>106984675
A new distro can be made by chroot, it basically is the first layer of what containers are.

all I need is arch

>>106984918
the kernel manages everything, the distros are just a bundle of tools (and kernel but you don't have to install the kernel to use the tools)

i'm the sysadmin, not the distro. if i want a kernel from distro 1, i mount /boot on that and let distro 1 upgrade the kernel.
the first setup has to start the distro 2 anyway
i'm sure its possible to symlink the tree with a bit of work to default to one or the other.

yesterday i was experimenting with using the linker from distro 1 or the linker from distro 2 to launch their own stuff in the same environment, (no chroot) but i'm not a pro at it yet so for now, they will stay mostly separated

linux is very flexible and no one implied anything was "vice versa" so i dont know what you're talking about

>>106984613
>can you even do this on wayland?
usecase?

>>106984995
So you a moron who manage kernel and its updates by hand, not by using distro which was created to do that for you.

>>106984927
You still need to have "host" distro. Chroot and containers just reuse packages from distro, not distro itself.

>>106985177
The kernel updates itself dumbass

>>106985241
It seems you forgot your meds today

>>106985177
again, i dont know what you're talking about.
if you didn't understand, i use the tools of distro 1 to manage the kernel.
thats not managing by hand.
all i'm doing is prefer tools of one vs the other for different things

>>106984613
>why are you not running multiple distros on the same kernel with separate x11 instances?

Qubes OS? I'm not Edward Snowden

>>106985281
just do it on whatever distro you're on.

>>106985281
break free from distroism

>>106985267
If you have "host" distro which manage your kernel then it is the distro you are using. When you try to use packages from other distro it is not "using distro". Tools from other distro will only work when they are compatible with your kernel and libc. You can not easily mix glibc-based and musl-based tools, for example.

>>106985333
i know.
thats where the linker comes in.
and thats why i'm not mixing them yet. they each have their own root.

someone more experienced with linkers can probably pull it off

>>106985358
In short - you can't
Read this - https://jangafx.com/insights/linux-binary-compatibility

>>106985388
except i just did it with mpv.
i found some post on stackoverflow or something yesterday that talked about calling the linker directly and specifying library path when running the binary like this:

$ /distro2root/lib64/ld-linux-x86-64.so.2 --library-path /distro2root/usr/lib64 /distro2root/usr/bin/mpv

/usr/lib64/ld-linux-x86-64.so.2 is a script.

this works at least for mpv. i checked with lsof what libraries it had opened and lo and behold it had opened the right libraries!

it seems to work for for simpler program like mpv. i have yet to see how it works on more complicated stuff making sure it can load libraries from multiple locations etc.

>>106985651
ignore this:
>/usr/lib64/ld-linux-x86-64.so.2 is a script.

i confused it with libc.so

>>106984613
For what purpose?

>>106985388
but i dont know how to make it load everything yet. judging from lsof output
at least the libraries are opened from distro2 which is mostly what i wanted anyway.

i tried it with gnumeric and it works like mpv.
also, opens the libraries from distro2.

not everything however, it still opens stuff from /var from distro1 and some locale files from /usr/lib also, the fonts but this is irrelevant.

the libraries are loaded from distro2 thats all i need to know for now.

File: vim.png (23 KB, 1362x639)

23 KB PNG

>>106985388

File: vim23421.png (59 KB, 1077x918)

59 KB PNG

>>106985651

File: vim23406.png (73 KB, 1078x1203)

73 KB PNG

>>106985388
2

>>106984613
I don't have a use case that would require that.

>>106984613
No need. I'm already running Qubes
>>106985281
It was annoying at first but now that I'm used to it, it's comfy as fuck. I'm never switching to anything else