Synonyms for gobolinux or Related words with gobolinux

slackware              busybox              systemd              mingw              illumos              autoconf              opensolaris              openjdk              openindiana              opensuse              amigaos              freedos              cygwin              reactos              icedtea              pkgsrc              yast              morphos              trueos              watcom              xfce              minix              cmake              xulrunner              pyqt              crunchbang              dpkg              gnewsense              webmin              automake              pclinuxos              plone              msvc              unixware              centos              manjaro              ebuilds              lmde              amigados              launchd              openmosix              lxqt              addons              autotools              uclibc              interix              amule              tortoisesvn              manpage              koffice             



Examples of "gobolinux"
The Compile program was introduced in GoboLinux version 011. Before that, there were discussions about porting Gentoo's Portage system to GoboLinux and developing the port as a SourceForge.net project under the name "GoboPortage".
The GoboLinux hierarchy represents a radical departure from the filesystem hierarchy traditionally employed by most UNIX-like operating systems where specific types of files are stored together in common standard subdirectories (such as codice_2 for executables and codice_3 for configuration files) and where package managers are used to keep track of what file belongs to which program. In GoboLinux, files from each program are placed under their respective program's own dedicated subdirectory. The makers of GoboLinux have said that "the filesystem is the package manager", and the GoboLinux package system uses the filesystem itself as a package database. This is said to produce a more straightforward, less cluttered directory tree. GoboLinux uses symlinks and an optional kernel module called "GoboHide" to achieve all this while maintaining full compatibility with the traditional Linux filesystem hierarchy.
GoboLinux is an open source operating system whose most prominent feature is a reorganization of the traditional Linux file system. Rather than following the Filesystem Hierarchy Standard like most Unix-like systems, each program in a GoboLinux system has its own subdirectory tree, where all of its files (including settings specific for that program) may be found. Thus, a program "Foo" has all of its specific files and libraries in codice_1. According to the GoboLinux developers, this results in a cleaner system.
The design of GoboLinux was influenced by earlier systems such as NeXTSTEP, AtheOS, and BeOS, all of which adopted original filesystem structures while still maintaining a considerable degree of compatibility with Unix. At the root of the GoboLinux tree, there are six directories: Programs, Users, System, Files, Mount, and Depot. The contents of each are described below.
The creators of GoboLinux have stated that their design has other "modernisms", such as the removal of some distinctions between similar traditional directories (such as the locations of executables codice_2, codice_5, and codice_6). GoboLinux designers have claimed that this results in shell scripts breaking less often than with other Linux distributions. This change, introduced by GoboLinux in 2003, has only been adopted by other distributions much later: Fedora merged /bin and /usr/bin in 2012; Debian enabled the /usr merge by default in 2016.
Most Linux distributions follow the Filesystem Hierarchy Standard and declare it their own policy to maintain FHS compliance. GoboLinux and NixOS provide examples of intentionally non-compliant filesystem implementations.
In the GoboLinux hierarchy, files are grouped into functional categories in an index-like structure using symbolic links, rooted at codice_11: All executables are accessible under codice_26, all libraries are accessible under codice_27, and so on.
This eliminates many traditional distinctions in the Filesystem Hierarchy Standard, such as the distinction made between non-essential files stored in codice_28 and essential, emergency files stored directly in subdirectories of the root directory. The GoboLinux developers have maintained that, although these distinctions were once very useful, they are no longer necessary under GoboLinux's schema.
The Compile system is somewhat similar to Gentoo's Portage system, which is based on the FreeBSD Ports collection. However, Portage is made for a traditional filesystem hierarchy, compatible with the Filesystem Hierarchy Standard, while Compile extends the capability of GoboLinux's distinctive filesystem hierarchy into the area of package management. Thus, in GoboLinux, the filesystem itself serves naturally as a kind of package manager database.
GoboLinux is currently developed for x86-64. It was officially made for the i686 only until release 015, but at one point an incomplete port to the i386 was made. Ports have also been made to embedded architectures, such as ARM and SuperH; these tasks were achieved with Bootstrap, a tool developed especially to automate making ports.
The traditional directory structure, which is a heritage from Linux's Unix roots in the 1970s, has been criticized as inappropriate for desktop end users. Some Linux distributions like GoboLinux and moonOS have proposed alternative hierarchies that were argued to be easier for end users, though they achieved little acceptance.
The following Linux distributions use Metalink for ISO image distribution: Adios, Bayanihan Linux, BeleniX, Berry Linux, BLAG Linux and GNU, Bluewhite64 Linux, Damn Small Linux, Fedora, GoboLinux, Granular Linux, KateOS, Linux Mint, openSUSE, Pardus Linux, PCLinuxOS, PuppyLinux, Sabayon Linux, StartCom Enterprise Linux, SUSE Linux, Ubuntu.
GoboLinux also allows the user to have different versions of the same program installed concurrently (and even run them concurrently). Furthermore, it has been claimed that the package management index could never become unsynchronized with the filesystem, because references to nonexistent files simply become broken links, and thus become inactive. GoboLinux's filesystem changes also allow other innovations, such as an entirely new boot system that does not use System V or BSD style init systems.
The following package management systems distribute the source code of their apps. Either the user must know how to compile the packages or they come with a script that automates the compilation process. In both cases, the user must provide the computing power and time needed to compile the app. For example, a recipe file contains information on how to download, unpack, compile and install a package in GoboLinux using its Compile tool. Also, in both cases, the user is legally responsible for the consequences of compiling the package.
There are symbolic links relating most of the usual Unix directories to the GoboLinux tree. Therefore, one can find directories such as codice_3, codice_30, and codice_5 in the expected places. These symbolic links point to the functional equivalent in the codice_11 tree; thus, traditionally crucial path names (such as codice_33 and codice_34) are resolved correctly. These compatibility directories are concealed from view using a custom kernel modification called "GoboHide", which implements support for hidden files in Linux; it is used for aesthetic reasons only and is thus an optional feature.
Releases have been numbered using the octal base system. According to the authors, this scheme was chosen because it keeps the typical leading zero that is present in many free software version numbers (since a leading zero often indicates that a number is octal), and it is a play on the "version numbers race" that happened among Linux distributions around 1999. When read as decimal numbers, using octal numbers causes a deterministic "version bump" each eight releases. Up to version 013, GoboLinux made no "point releases", in order to avoid the implication that some releases were more stable than others. This tradition was broken with version 014.01, an update of 014 focused on bug fixes.
GoboLinux uses its own initialization procedure, unlike most Linux distributions which use a BSD or a System V procedure. At codice_35 are a few files that command the entire boot procedure: codice_36 and codice_37 run at system boot and shutdown, respectively; additionally, it is possible to define "runlevel" scripts to specify different ways the system may be initialized (for example, codice_38 for single-user, codice_39 for multi-user, codice_40 for boot into graphic mode, and so on); this can be controlled from the boot loader menu. The codice_41 file separates site-specific settings from the rest of the scripts. Application-specific tasks can be found at codice_42; they can be called by the boot scripts.