45 lines
3.0 KiB
HTML
Executable File
45 lines
3.0 KiB
HTML
Executable File
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>Everest Linux - About</title>
|
|
<link type="text/css" rel="stylesheet" href="css/everest.css"/>
|
|
</head>
|
|
<body>
|
|
<ul>
|
|
<li><a href="index.html">Home</a></li>
|
|
<li><a href="about.html">About</a></li>
|
|
<li><a href="install.html">Handbook</a></li>
|
|
<li><a href="https://git.everestlinux.org/EverestLinux/glacier-pkgs">Packages</a></li>
|
|
<li><a href="download.html">Downloads</a></li>
|
|
<li><a href="https://git.everestlinux.org">Git</a></li>
|
|
</ul>
|
|
<img src="img/banner-ab.jpg" alt="Everest Logo"/>
|
|
<h1>About Everest</h1>
|
|
<p>Everest Linux is a source based Linux meta-distribution.</p>
|
|
<p></p>
|
|
<h3>History of Everest</h3>
|
|
<p>2021 - The idea of a system that combines the simplicity of binary packaging with the flexibility of source based packaging was born</p>
|
|
<p>Early 2022 - Early prototypes of Glacier were created. These versions came with no multi-repository support, caching, or logging of any kind</p>
|
|
<p>Mid 2022 - Glacier reaches a stable release point</p>
|
|
<p>Late June 2022 - everestlinux.org is registered and git.everestlinux.org goes online</p>
|
|
<p>September 2022 - Early prototypes of the ELIF (Everest Linux Installation Framework) are completed</p>
|
|
<p>October 2022 - Glacier v3 enters testing</p>
|
|
<p></p>
|
|
<h3>Design Principles</h3>
|
|
<p>Our design principles guide the development of Everest. You may notice we share most of these with Arch (because Arch is very cool).</p>
|
|
<p><strong>Simplicity</strong> - We provide packages with almost zero modifications from upstream, except when necessary.</p>
|
|
<p>The base Everest system only includes what you need to start building your system - UNIX tools, a C library, a C compiler, and Glacier.</p>
|
|
<p>The base Everest system also weighs in at around 100 MB (may vary with different images, such as GNU or systemd).</p>
|
|
<p><strong>Flexibility</strong> - Everest is designed with flexibility in mind. Any modification can be achieved if the user has enough knowledge</p>
|
|
<p>For example, it is possible to replace Busybox with sbase, or use runit as your init system, all without breaking the system.</p>
|
|
<p><strong>Functionality vs Ideology</strong> - The developers of Everest are strong advocates of free software, but understand that</p>
|
|
<p>it cannot be implemented 100% of the time, such as in the form of drivers. We also understand that some users may prefer proprietary</p>
|
|
<p>software over libre counterparts. We do not take steps to prevent proprietary software in our repositories,</p>
|
|
<p>only requiring it to be under the <strong>multiverse</strong> repository.</p>
|
|
<p>This is very different from heavily ideological distributions, such as Hyperbola, some of which don't even support many packages people may find useful,</p>
|
|
<p>such as systemd, dbus, rust, java, and most recently, sudo.</p>
|
|
<p><strong>User Centrality</strong> - We believe that instead of trying to make Everest beginner friendly, and work out of the box,</p>
|
|
<p>we should instead focus on users with a willingness to learn how to install and use Everest.</p>
|
|
</body>
|
|
</html>
|