i set up different minimal templates cloned from the debian minimal for example, why /usr/bin/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11/X11 exists? Im buffled how and why
i see in ls -l X*
1 Jan 24 2025 X11 → .
$ ls -l /usr/bin/X*
lrwxrwxrwx 1 root root 4 Sep 5 07:52 /usr/bin/X -> Xorg
lrwxrwxrwx 1 root root 1 Jan 24 2025 /usr/bin/X11 -> .
-rwxr-xr-x 1 root root 274 Sep 5 07:52 /usr/bin/Xorg
There indeed looks to be an X11 linked to ., it makes it so that doing cd /usr/bin/X11 places you in /usr/bin. Why that is I have no idea, probably some weird quirk for backwards compatibility.
thanks Atrate for confirming that its from the base template and not something i messed up here. What backwards compatibility would need an inception of X11 folders. Does not make sense somewhat
I have the same, so it’s not cause you messed something up.
My hunch is that some weird utility could hardcode a path like /usr/bin/X11/X and this would be needed to keep it from falling over.
And it is not minimal only, same in xfce
ye as far i understood and also Atrate explained, if old applications refer to something in /usr/bin/X11/xcalc for example, this path is in new derivates not existing anymore, and to not break the apps or have to correct all of them it substitutes /usr/bin/X11 via the symlink . into /usr/bin where all the needed references live