Gobolinux – SpeedyLook encyclopedia

before-content-x4

GoboLinux It is a GNU/Linux distribution that has a remarkable feature in its reorganization of the hierarchy of the file system. In GoboLinux , each program has its own subdirectory tree, where all its files are located.

after-content-x4

The hierarchy of GoboLinux It is radically different compared to the archive system hierarchy traditionally used by most Linux and Clones distributions (UNIX), where specific types of files are stored together in standard subdirectory common ones (such as P.EJ. bin and man ), And the package managers are used to maintain a track towards the file that belongs to some program.

In Gobolinux, the different programs archives are separated into different deputy directors. While in the Gobolinux type files they are also separated in subdirectory, although these are aligned within the subdirectory of their programs.

The manufacturers of GoboLinux They say that “the file system is the package manager”, and the package management system of GoboLinux It uses itself as a package database. This produces a simpler and less messy director of directories. Gobolinux uses symlinks and an (optional and cosmetic ) Core called “Gobohide” To achieve all this maintaining high compatibility with the traditional Linux file system hierarchy.

The hierarchy of Gobolinux It has additional benefits, for example, this removes some distinctions between the traditional directories (such as the Locations of the Executables /bin , /USR/BIN , and /usr/local/bin ). The designers of GoboLinux They claim that this causes them Scripts or Guions de shell se deciphe in codes , often, less frequently than in other Linux distributions.

GoboLinux It also allows the user to have different versions of the same program simultaneously (and still control them simultaneously). In addition, the package management index can never get out of synchronization, such as references for non -existing files, which are simply broken, and thus inactive links. Changes of the file system of GoboLinux They have also allowed other innovations, such as a new Self -Arranque system that does not use those used in System V or BSD as systems styles heat .

The Gobolinux archive system hierarchy [ To edit ]

The design of GoboLinux It is influenced by the first systems such as Nextstep, Atheos and Beos, which adopted original structures of file systems, while still maintained a considerable degree of compatbility with UNIX.
In the root / ( root In English) of the tree, there are six main directories:

after-content-x4
  • Software ( Programs )
  • Users ( Users )
  • System ( System )
  • Files ( Files )
  • Mounting ( Mount )
  • Deposit ( Depot )

Description of each directory [ To edit ]

directory Description
/ Main hierarchy , root directory ( root in English) of the hierarchy of the file system.
/Programs/
(Software)
This directory contains a directory for each program installed on the computer. Each program of the program, in turn, contains one or more versions directories, and optionally, subdirectories of “Settings” and “Variables” .

Examples of this directory, deputy director and programs are: /Programs/bash/3.0/bin/bash and /Programs/xorg-server/Settings/x11/xorg.conf .

/Users/
(Users)
This directory contains the directories “home” of the users. In this way a User identity ( userid ) call “user” could have a directory home : /Users/usuario .
/System/
(System)
Contains system files Enstentials Most are administered by system applications (for example: /System/Settings/passwd ) and Scripts of GoboLinux (For example, /System/Links ).
/Links/
(Links)
Contains directories of “Links” that the files related to /Programs
/Environment/
(Around)
Links to environment files. These are compiled in a file Cache and loads by the Shell, allowing the programs to register their own environments.
/Executables/
(Executable)
Contains links to files coming from programs directories /bin and /sbin
/Headers/
(Headers)
This directory contains links to files from the programs, includes directories.
/Libraries/
(Bookstores)
Links to files from directories programs / lib .
/Manuals/
(Manuals)
Manual contents and information information.
/Shared/
(Compadetidos)
Links to files from shared directories programs.
/Tasks/
(Tasks)
Links to programs, starting tasks of its directories of Resources/Tasks (resources/tasks).
/Settings/
(Settings)
File and link configuration to the programs files, directories “Settings” (of configurations).
/BootScripts/
(Arrante scripts)
Used during the starter system (booting). This is a symbolic link to /Settings/BootScrips/ low /Programs/BootScripts .
/Variable/
(Variable)
Multi-proposal record, temporary-transitory file.
/tmp/
Temporary files.
/Kernel/
(Núcleo Linux)
Core -related directories (Linux nucleus).
/Boot/
(Start)
Programs and configuration of files used during the process of Bootstrapping of the operating system. This is where the image of the nucleus (Linux nucleus) and the configuration files of the starter loader (bootloader) is located.
/Devices/
(Devices)
Device files (managed by Udev ).
/Modules/
(Modules)
It contains several modules of the nucleus, organized by launching the nucleus.
/Objects/
(Objects)
Provides a vision of the nucleus device tree (introduced with file systems sysfs In the series of kernel 2.6 )
/Status/
(State)
Core status files (managed by the file system proc ).
/Files/
(Files)
Archives maintains structured data that are used by programs, but are not part of the programs themselves. Those files are usually entities, in general, independent, such as: text sources (FONTS), CODECS and PLUGINS (and as such, do not require packages administrator).

In addition, applications can define their own deputy director to store specific data sites – Compile , the border tool for compilation of packages of GoboLinux , use it.

/Mount/
(Mounting) on arranged
And Assembly point For local or remote additional file system. Common directories are CD-ROM, Dysque and Zip
/Depot/
(Deposit)
Repository for user files. This repository is

This deposit is proposed to be organized as the user deems it convenient. No deputy director of /Depot (Deposit) is considered part of the GDE Jearchia standard GoboLinux

Compile (Gobolinux compilation system) [ To edit ]

Compile , he Compilation system in GoboLinux , introduced in the version 0.11 , [ first ] Discharge, tidy, compile and installs since Tarballs with Unique Command ( “Compile foo” ), using simple compilation scripts, known as “recipes” (of English recipes ).

Comparison parameters [ 2 ] Have been established between the compiler GoboLinux’ and the Gentoo Portage System (which is, in turn, based on the FreeBSD ports collection), which carries out its renowned actions with scripts known as “ebuilds” . However, unlike Portage (which is made for a file system hierarchy traditional, compatible with FHS), compile expands the capacity of the file system hierarchy distinctive GoboLinux in the area of ​​packaging administration. Thus, in GoboLinux , the file system is the package management system. To see its characteristics, you can read the article: “The ideas behind Compile” . [ 3 ]

Before it was done Compile , in the official Gentoo forums, the possibility of third parties to carry the Gentoo Portage system that was later developed as a Sourceforge project, under the name of GoboPortage . [ 4 ] [ 5 ]

  • Use the projects discharged from projects : The repository of the distribution (or one of its mirrors) is only used to download recipes . The recipes They may be Downloaded on the march o In lots.
  • Use minimalist compilation scripts in your orientation and declaration : The typical "configure; make; make install" ; Software can be written in two lines, relieving maintenance.
  • Supports style dependencies GoboLinux : Compiled software “A how many” The user is taken into account by the detection mechanism.
  • The design path (route) of design does not interest : It also works in a rootless installation (uprooted) [ 6 ] Of GoboLinux , that is, inside a directory $HOME of any other distribution.

Differences between Gobolinux and traditional distributions [ To edit ]

File system [ To edit ]

In the hierarchy of GoboLinux , the files are grouped by their functional category, in an index structure, using symbolic links, routed to /System/Link : All executables are accessible under /System/Links/Executables , all libraries are accessible under /System/Links/Libraries , etc.

This eliminates traditional distinctions in the standard of file system hierarchy, such as the distinction made between non -essential stored files in /usr and the essentials, emergency files stored directly in subdirectories of the root directory (/).

The developers maintain that, although these distinctions were once very practical, they are not necessary in our radically modern environment.

Symbolic links [ To edit ]

There are symbolic links that relate the most used directories in UNIX to the tree of GoboLinux . Therefore, one can find directories such as /etc , /was/Log and /USR/BIN in certain places. These symbolic link points for low equivalent functionalities /System/Links , so crucial names and routes such as /Bin/SH and /etc/passwd They are resolved correctly. These compatibility directories are hidden from the view using a modification of the core called Gobohide , this modification, which implements support for files hidden in Linux, is used only for aesthetic reasons and is optional

Start System [ To edit ]

Unlike most Linux distributions, GoboLinux does not use an initiation process (init), BSD style or system v, instead using a specific procedure of GoboLinux . In / System / Settings / Bootcripts There are a few files that you command the starting process: the BootUp and the Shutdown They run the boot system and the off , respectively; Additionally, it is possible Single For a session of Unique user , Multi For a session Multi -user , Graphical for a graphic mode start, etc.) and control what comes from the loading menu load. The file /System/Settings/BootOptions Separate the specific configurations from the site from the rest of the scripts. Specific application tasks can be found in /System/Links/Tasks and called by starting scripts.

The versions are numbered using the Octal Base System. The reason for this numbering is given, according to its authors, for three reasons: it maintains the typical zero present in many free software version numbers (since an initial zero is the indicator of Octal numbers in the programming language c); has no points, and therefore there is no “Minor versions” ; And it is a joke about the phenomenon of “Version jumps” , since, when they are read as decimal numbers, Octal numbers They cause a deterministic leap every eight versions.

  • 016 – December 15, 2016: introduced Runner , a tool for virtualization of the file system. First version for X86-64.
  • May 015 – May 7, 2014: introduced the hierarchy /System/Index
  • 014 – April 4, 2008: New stable version, containing updates of packages, bugs repairs and new versions of Gobolinux’s management tools.
  • 013 – November 2, 2006: introduced Listener , a tool to listen to files of the file system and attribute actions to be automatically executed
  • 012 – June 6, 2005: introduced Manager , a graphic tool for system administration.
  • June 011 – 7, 2004: introduced Compile , the Gobolinux packages compilation tool.
  • 010 – January 7, 2004: Added an accessible graphic installer from the LIVECD desktop environment.
  • 007 – October 22, 2003: Added Resources , a metadata directory per package.
  • 006 – May 9, 2003: introduced Gobohide , adopted installation of programs with a sandbox.
  • 005 – 2003: First public version launched online.
  • Versions prior to 005 were used only by the initial developers.

Portability [ To edit ]

As of March 2006, Gobolinux It is only officially available for architecture I686 and the translation into architecture i386 is Specific domain (Thus, incomplete). However, in 2003, Hisham Muhammad, the main project developer GoboLinux , Wrote one «Fast and dirty portability guide» (” Quick-and-Dirty Porting Guide “) [ 7 ] For those who wanted to carry the distribution to the PowerPC platform (among other architectures). He also works for take her the same. [ 8 ] It also behaved to embedded architectures, such as ARM and Superh, which was easily achieved after the launch of Bootstrap, [ 9 ] A tool developed specifically to automate the process of carrying the distribution.

Notes and references [ To edit ]

See also [ To edit ]

external links [ To edit ]

after-content-x4