Group: Hardware/FSDG distributions
(→General information: Update status for non-technical users) |
(→General information: parabola: graphical install: Add info about installed packages) |
||
Line 38: | Line 38: | ||
| Everybody? | | Everybody? | ||
* The installation can be done graphically | * The installation can be done graphically | ||
− | * | + | * A graphical package manager ([https://www.parabola.nu/packages/pcr/x86_64/octopi/ octopi]) is [https://git.parabola.nu/calamares.git/tree/src/modules/pacstrap-gui/pacstrap-gui.conf?h=merge-2019-05 installed during the graphical installation] |
* Does the user needs to mess up with configuration files? | * Does the user needs to mess up with configuration files? | ||
| Rolling releases | | Rolling releases |
Revision as of 22:01, 6 October 2019
Contents
Introduction
Having FSDG compliant distributions that support many architecture is interesting for several reasons:
- To get the RYF certification for a computer, being able to use all the components of that computer with free software is not enough as that computer also needs run an FSDG compliant distribution on that computer. See the RYF endorsement criteria for more details on that certification.
- Users that want fully free system can also build systems similar to the ones that got the RYF certification themselves and/or get some help to do it, and here they also need FSDG compliant distributions to run on their computers.
- As some computers can run fully free software, with some of the hardware components not working, it's also very interesting to be able to have a distribution to support such hardware. See the article on single-board-computers on the FSF website for more details.
It is also interesting to understand who is able to use the FSDG GNU/Linux distributions. For instance if an architecture is supported only by FSDG compliant distributions that are for technical users with good command line knowledge, it would dramatically limit the amount of people able to use that computers with that architecture with fully free software.
The release type (Rolling release, stable releases) and the release frequency is also important to take into account:
- For users, there are various advantages and disadvantages of using distributions that have rolling releases or stable releases. Less technical users seem to prefer LTS as less (frequent) maintenance is required.
- For adding support for devices in distributions, rolling releases gets the job done faster, but many users might prefer to use stable releases.
General purpose GNU/Linux distributions
General information
Distribution | Audience | Release type |
---|---|---|
GuixSD | Technical users:
|
Rolling release |
Hyperbola | Everybody?
|
Stable releases |
Parabola | Everybody?
|
Rolling releases |
PureOS | Everybody:
|
Rolling release |
Trisquel | Everybody:
|
Stable releases |
Architectures support
Distribution or software | x86 32bit | x86 64bit | ARM 32bit | ARM 64bit | PowerPC 64bit little endian |
---|---|---|---|---|---|
GuixSD | i686 | Yes | armhf | Yes | No |
Hyperbola | i686 | Yes | No | No | No |
Parabola | i686 | Yes | armv7h | No | Unfinished |
PureOS | No | Yes | No | can be installed with debootstrap | No |
Trisquel | i686 | Yes | No | No | No |
Small distributions
Distribution or software | Usage | Audience | Release type |
---|---|---|---|
libreCMC |
|
? | Stable releases |
ProteanOS | ? | ? | ? |
Replicant |
|
Users with extremely basic command line knowledge | Stable releases |
Architectures support
Distribution or software | x86 32bit | x86 64bit | ARM 32bit | ARM 64bit | MIPS |
---|---|---|---|---|---|
libreCMC | Requires to build from source | Requires to build from source | Requires to build from source | No | Yes |
ProteanOS | ? | ? | ? | ? | ? |
Replicant | No | No | Yes | No | No |
Adding support for a device
Distribution or software | Adding support for a device |
---|---|
General purpose GNU/Linux distributions |
|
libreCMC | |
ProteanOS | |
Replicant |
|