https://wiki.gobolinux.org/Concepts/index.htmlThis is an important chapter in your GoboLinux journey. Before you begin fiddling around with the GoboLinux operating system, we highly advice thoroughly studying the following chapters. Once you have familiarized yousrelf with the GoboLinux theory and concept, you may commence onto the the Usage chapter. The GoboLinux Way GoboLinux Filesystem Hierarchy System Index Understanding system indices Alien Packaging Subsystem RunnerHugoen-ushttps://wiki.gobolinux.org/Concepts/The-GoboLinux-Way/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://wiki.gobolinux.org/Concepts/The-GoboLinux-Way/index.htmlWelcome to the world of GoboLinux The main task of a Linux distribution is to keep track of and organize the programs in your computer, so that they work properly. GoboLinux is no different from the others in this goal, but it adopts a fundamentally different approach in solving this problem. Instead of scattering the files of programs around, following the decades-old conventions of ancient UNIX systems, and then adding a layer of control (a “package manager”) to try to give order to chaos, in GoboLinux we organize the files that comprise the programs in an ordered way in the first place.https://wiki.gobolinux.org/Concepts/GoboLinux-Filesystem-Hierarchy/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://wiki.gobolinux.org/Concepts/GoboLinux-Filesystem-Hierarchy/index.htmlHere is an overview of the GoboLinux filesystem tree. The legacy folders (on the “:” part of the tree) are links to the corresponding GoboLinux folders. The legacy folders are excluded from default directory view by GoboHide. / |-- Data - for resources belonging to the system and to individual programs | |-- Compile - sources, recipes and other files used by the Compile tool | | |-- Archives | | |-- LocalRecipes | | |-- PackedRecipes | | |-- Recipes | | `-- Sources | `-- Variable - for spool files, log files, temporary files, etc. | |-- cache | |-- empty | |-- lib | |-- lock | |-- log | |-- run | |-- spool | `-- tmp |-- Mount - mountpoints for filesystems |-- Programs - where programs (with all their files) are installed |-- System | |-- Aliens - files managed by programming language package managers | |-- Environment - links to program files declaring environment variables | |-- Index - links to files in each program's | | |-- bin + bin/ and sbin/ directories | | |-- include + include/ directory | | |-- lib + lib/ directory | | |-- libexec + libexec/ directory | | `-- share + share/ directory | | |-- consolefonts | | |-- fonts | | `-- man | | |-- info + info/ directory | | `-- man{1-9} + man{1-9}/ directories | |-- Kernel | | |-- Boot - kernel images, config files and programs needed to boot | | |-- Devices - device files (managed by Udev). | | |-- Modules - loadable kernel modules (device drivers) | | |-- Objects - a view of the kernel's device tree | | `-- Status - kernel status files (belonging to the /proc filesystem) | |-- Settings - system config files and links to files in program's Settings/ directories. | | `-- BootScripts - scripts used for boot, symlink to /Programs/BootScripts/Settings/BootScripts/ | `-- Tasks - links to programs' boot tasks (from their Resources/Tasks/ directory) |-- Users - contains users' home directories : : :-- etc -> System/Settings :-- dev -> System/Kernel/Devices :-- sys -> System/Kernel/Objects :-- proc -> System/Kernel/Status :-- var -> System/Variable :-- tmp -> System/Variable/tmp :-- sbin -> System/Index/bin :-- bin -> System/Index/bin :-- lib -> System/Index/lib :-- lib64 -> System/Index/lib `-- usr |-- X11R6 -> . |-- local -> . |-- bin -> ../System/Index/bin |-- sbin -> ../System/Index/bin |-- include -> ../System/Index/include |-- lib -> ../System/Index/lib |-- lib64 -> ../System/Index/lib |-- libexec -> ../System/Index/libexec `-- share -> ../System/Index/sharehttps://wiki.gobolinux.org/Concepts/System-Index/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://wiki.gobolinux.org/Concepts/System-Index/index.htmlSystem Index Compiled programs in C and C++ typically have a lib/ directory and often also a bin/ directory. On GoboLinux, these will be symlinked into /System/Index such as for ping: /System/Index/bin/ping /System/Index/lib/libpng.so.3 Traditional Unix paths are also symlinks to the /System/Index directory structure: /bin -> /System/Index/bin /usr/bin -> /System/Index/bin /usr/lib -> /System/Index/lib /etc -> /System/Settingshttps://wiki.gobolinux.org/Concepts/Understanding-and-maintaining-system-indices/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://wiki.gobolinux.org/Concepts/Understanding-and-maintaining-system-indices/index.htmlThe two main parts of GoboLinux are /Programs and /System. If you stick to using InstallPackage and Compile, these two parts will be implicitly kept in sync by SymlinkProgram. But a lot of power lies in the fact that you can tune how these two worlds interact. Program entries under /Programs feature a Current symlink pointing to a specific version that is “active” in the system. This Current version is taken as the default version when you don’t specify a version in scripts, and the link is updated when you install a new version with InstallPackage or Compile.https://wiki.gobolinux.org/Concepts/Alien-Packaging-Subsystem/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://wiki.gobolinux.org/Concepts/Alien-Packaging-Subsystem/index.htmlAlien Packages GoboLinux has a concept of “Alien” packages. These are programs that are usually packaged via external, distro-independant package managers. Common examples are: pip (Python), npm (Javascript), cargo (Rust), LuaRocks (Lua), RubyGems (Ruby), CPAN (Perl). GoboLinux currently supports the following backends: LuaRocks PIP3 RubyGems CPAN How to install and update Alien packages Main article: Managing Alien Packageshttps://wiki.gobolinux.org/Concepts/Runner-Intro/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://wiki.gobolinux.org/Concepts/Runner-Intro/index.htmlRunner is a utility for launching programs under GoboLinux that ensures that the filesystem view of a process will match its dependencies. In other words, Runner eliminates the possibility of library conflicts when running an executable. Runner is a filesystem virtualization tool that sets up a constrained view of /System/Index for a process based on the executable program’s Dependencies file. It is run as a wrapper, e.g. Runner SomeApp. Runner builds a custom mount table for the process, like container tools do, but without duplicating files. It dynamically picks the correct parts of your /Programs tree. This approach is feasible in GoboLinux due to way programs are each confined to their own subdirectories.