From 1eda26a9c8acc793a9d204392ef2307bcb447267 Mon Sep 17 00:00:00 2001 From: Liam Waldron Date: Thu, 7 Dec 2023 12:06:00 -0500 Subject: [PATCH] 12/7/23 --- css/nord.css | 44 +++++++++++++ docs/home.html | 1 + docs/intro-to-glacier.html | 66 ++++++++++---------- docs/meta-reading.html | 83 ++++++++++++++++++++++++ docs/recovery.html | 62 ++++++++++++++++++ install.html | 125 ++++++++++++++++++++++--------------- 6 files changed, 298 insertions(+), 83 deletions(-) create mode 100644 docs/meta-reading.html create mode 100644 docs/recovery.html diff --git a/css/nord.css b/css/nord.css index 6662ed5..39a4113 100644 --- a/css/nord.css +++ b/css/nord.css @@ -70,6 +70,28 @@ html { color: #ECEFF4; } +.note { + background-color: #88C0D0; + border-left-style: solid; + border-left-color: #88C0D0; + border-width: 4px; + border-radius: 2px; + padding: 4px; + width: 50%; + color: #2E3440; +} + +.caution { + background-color: #EBCB8B; + border-left-style: solid; + border-left-color: #EBCB8B; + border-width: 4px; + border-radius: 2px; + padding: 4px; + width: 50%; + color: #2E3440; +} + .warning { background-color: #BF616A; border-left-style: solid; @@ -107,6 +129,17 @@ th { border-color: #ECEFF4; } +notehead { + background-color: #88C0D0; + border-left-style: solid; + border-left-color: #88C0D0; + border-width: 4px; + border-radius: 2px; + padding: 6px; + width: 50%; + color: #2E3440; +} + fhead { background-color: #2E3440; border-left-style: solid; @@ -129,6 +162,17 @@ khead { color: #B48EAD; } +cautionhead { + background-color: #EBCB8B; + border-left-style: solid; + border-left-color: #EBCB8B; + border-width: 4px; + border-radius: 2px; + padding: 6px; + width: 50%; + color: #2E3440; +} + warnhead { background-color: #BF616A; border-left-style: solid; diff --git a/docs/home.html b/docs/home.html index b5235ee..a9ac679 100644 --- a/docs/home.html +++ b/docs/home.html @@ -55,6 +55,7 @@
  • Developer Documentation
  • General Recommendations
  • Introduction to Glacier
    • +
  • Meta: Reading Guide
  • musl or glibc?
    • diff --git a/docs/intro-to-glacier.html b/docs/intro-to-glacier.html index 670d084..00d6e73 100644 --- a/docs/intro-to-glacier.html +++ b/docs/intro-to-glacier.html @@ -26,15 +26,15 @@ -

    Introduction

    +

    1 - Introduction

    Glacier is the package management system for Glacier. All users should be familiar with how it works.

    -

    Terminology

    +

    2 - Terminology

    In this case, the word 'merge' and 'install' mean the same thing.

    A package index is a list of all installed packages on any given Everest system.

    The local index is managed by all users on the system, and is located in /usr/glacier/index.

    The global index is managed by Git, and is located in /glacier/index.

    A system profile describes your base system, including C library, architecture, SELinux support, multilib support, etc.

    -

    Included programs

    +

    3 - Included programs

    3.1 gpkg

    'gpkg' is the program most users will be interacting with. It handles the downloading, installation, and logging of packages.

    3.2 syspkg

    @@ -45,30 +45,30 @@

    'gquery' queries information on a package.

    3.5 glacier-mkprofile

    'glacier-mkprofile' makes changes to the system-wide profile. Users should not interact with this unless needed.

    -

    Frontends

    +

    4 - Frontends

    Frontends, or wrappers, may provide additional functionality to Glacier.

    WARNING:

    Third party frontends and wrapper scripts are not supported. Use them at your own risk.

    -

    Merging packages

    -

    4.1 Using gpkg

    +

    5 - Merging packages

    +

    5.1 Using gpkg

    To merge a package from a repository:

    (root)# gpkg -f repo/pkg

    For instance, to install 'vim' in the 'world' repository:

    (root)# gpkg -f world/vim -

    4.2 Using syspkg

    +

    5.2 Using syspkg

    Using 'syspkg' is not recommended for end users because all changes to the global package index will be overwritten when pulling a new update.

    If you understand these risks, and wish to use 'syspkg' anyways, you are acknowledging that things may break.

    To merge a package from a repository:

    (root)# syspkg -f repo/pkg -

    Updating packages

    -

    5.1 Introduction

    +

    6 - Updating packages

    +

    6.1 Introduction

    When merging a package into any index, the package file is retained in said index. This provides most information needed to keep track of the package, however, when updating, an updated package file will need to be downloaded. Old package files will be retained as 'pkgname.old'.

    -

    5.2 Using gpkg

    +

    6.2 Using gpkg

    To update a package:

    (root)# gpkg -u repo/pkg -

    5.3 Using syspkg

    +

    6.3 Using syspkg

    As mentioned above, 'syspkg' is intended for system development, and NOT for end users.

    However, 'syspkg -u' has some use cases for end users. These include:

    To update a package:

    (root)# syspkg -u repo/pkg -

    Removing packages

    -

    6.1 Introduction

    +

    7 - Removing packages

    +

    7.1 Introduction

    When removing a package, the package info file is moved from the appropriate index to /tmp, and saved as 'pkgname.rm'. This means it will be wiped after the next reboot.

    -

    6.2 Using gpkg

    +

    7.2 Using gpkg

    To remove a package:

    (root)# gpkg -x pkg

    Note that no repository name was provided. It is not required, as no files will be downloaded during the removal process.

    If a package is a dependency for another, you will be shown the following error:

    [x] Could not remove (package_name): is a dependency for (package_name) -

    6.3 Using syspkg

    +

    7.3 Using syspkg

    WARNING:

    Removing packages that shipped with the system images WILL cause catastrophic damage. You have been warned.

    If you wish to proceed anyways, you can remove a package with:

    (root)# syspkg -x pkg -

    Advanced usage

    -

    7.1 Patching packages

    +

    8 - Advanced usage

    +

    8.1 Patching packages

    Patching packages is the act of editing a package file to change compile options, optimizations, etc. It is very useful if used correctly.

    The officially tested and verified method for patching is as follows:

    -

    7.2 Custom package repository

    +

    8.2 Custom package repository

    If Glacier's standard package repository is not sufficient, you can use a custom one.

    WARNING:
    @@ -116,21 +116,21 @@

    export GREPO="https://some-repo.org

    -

    7.3 Compile flags

    +

    8.3 Compile flags

    When an operation is performed on a package, 'gpkg' invokes the system's C compiler, which can take flags for compilation.

    'MAKEFLAGS', 'CFLAGS', 'CXXFLAGS', and 'LDFLAGS' can be set in '/etc/make.conf'.

    It is highly recommended to keep '-static' in 'CFLAGS' and 'LDFLAGS'.

    -

    7.4 Using syspkg

    +

    8.4 Using syspkg

    'syspkg' is intended for development use and not for end users. That being said, 'syspkg' can be used for fixing security vulnerabilities without pulling in a new release from git.

    Note that all changes to the global package index ('/glacier/index') will be overwritten during an update, where the user invokes 'git pull' on '/'.

    -

    7.5 Whitelisting licenses

    +

    8.5 Whitelisting licenses

    Certain license types can be whitelisted or blacklisted. This is useful for controlling which software is installed on your system.

    This setting is stored in /etc/glacier.conf, in a simple Bash array. By default, it should look something like this:

    FILE: /etc/glacier.conf

    export GLACIER_ALLOWED_LICENSES=("GPL v3" "GPL v2" "GPL" "MIT" "BSD" "APACHE")

    -

    7.6 Services

    +

    8.6 Services

    Glacier services are small programs that can do certain tasks within Glacier, such as updating the local package database.

    Services must be enabled in /etc/glacier.conf before they can be used.

    FILE: /etc/glacier.conf @@ -151,25 +151,25 @@ FILE: /etc/glacier/end-srv

    #!/bin/bash

    -

     

    +

     

    GLACIER_SRV_DIR="/etc/glacier/services"

    $GLACIER_SRV_DIR/update-pkgdb.hook

    -

    Querying packages

    -

    8.1 Introduction

    +

    9 - Querying packages

    +

    9.1 Introduction

    Glacier packages, in ther simplest form, are text files, containing instructions on how the package is built, who made it, what it's called, and what files it includes.

    -

    8.2 Querying files

    +

    9.2 Querying files

    All files belonging to a package can be listed with:

    (user)$ gquery -f pkg -

    8.3 Querying info

    +

    9.3 Querying info

    Package info can be listed with:

    (user)$ gquery -i pkg -

    Writing packages

    -

    9.1 Introduction

    +

    10 - Writing packages

    +

    10.1 Introduction

    As mentioned before, Glacier packages are simply text files. This makes them very easy to write and maintain.

    If you have previous experience writing PKGBUILDs for the AUR, writing Glacier packages should feel very similar.

    In this page, 'nano' will be used as an example.

    -

    9.2 Metadata

    +

    10.2 Metadata

    Package files start with metadata, which tells Glacier who made the package, what its called, as well as other information.

    Double check that all of this information is correct before submitting a package.

    FILE: $(pwd)/nano @@ -184,7 +184,7 @@

    Hopefully, most of these options are self explanatory.

    For INCLUDED_FILES, ensure you DON'T include documentation (manpages, etc).

    -

    9.3 Integrity information

    +

    10.3 Integrity information

    FILE: $(pwd)/nano

    SHA256SUMS="86f3442768bd2873cec693f83cdf80b4b444ad3cc14760b74361474fc87a4526"

    @@ -192,7 +192,7 @@

    All packages must include their checksums. When merging a package, 'gpkg' will check the provided checksum against the actual checksum of the package, and if they don't match, the operation will be cancelled.

    To get the checksum of a package:

    (user)$ sha256sum package -

    9.4 Dependency information

    +

    10.4 Dependency information

    FILE: $(pwd)/nano

    DEPENDS=("")

    @@ -200,7 +200,7 @@

    Dependency information is extremely important. It allows 'gpkg' to install any dependencies. It also warns the user when a package conflicts with another.

    This should be fairly easy to figure out. Most projects will have this listed in their README. If you're the developer, you'll probably already know the dependencies your package requires.

    -

    9.5 Source information

    +

    10.5 Source information

    FILE: $(pwd)/nano

    PACKAGE_SRC="https://nano-editor.org/dist/v7/nano-7.2.tar.xz

    diff --git a/docs/meta-reading.html b/docs/meta-reading.html new file mode 100644 index 0000000..964d780 --- /dev/null +++ b/docs/meta-reading.html @@ -0,0 +1,83 @@ + + + + + + Everest Linux - Docs + + + + +
    + everest-logo + Home + About + Install + Packages + Downloads + Docs + Errata + Git ↗ +
    + + +
    + +

    1 - Introduction

    +

    Documentation for Everest is formatted in a specific way. This page explains how a page is formatted, and what certain things mean, in as much detail as possible.

    +

    2 - Cards

    +

    2.1 Introduction

    +

    Most Everest documentation pages will contain some type of a "card". Put simply, these are small sections that contain file contents, kernel configurations, warnings, notes, etc. There are 6 types of cards:

    +

    2.2 Note

    +

    This card is the most simple. It contains a note on a certain section. They are usually not required to read, but contain important information.

    + NOTE: +
    +

    This is an example of a note card.

    +
    +

    2.3 Caution

    +

    This card is one step up from a note. It contains important information, and should be read. However, it usually isn't urgent, or if it is, it contains things that most would consider common knowledge.

    + CAUTION: +
    +

    This is an example of a caution card.

    +
    +

    2.4 Warning

    +

    This card is one of the most important. It contains extremely important information that, if not understood, could lead to system breakage, data loss, etc.

    + WARNING: +
    +

    This is an example of a warning card.

    +
    +

    2.5 File

    +

    This card contains the contents of a text file. It is usually used to show configuration files.

    + FILE: example.txt +
    +

    This is an example of a file card.

    +
    +

    2.6 Kernel

    +

    This card contains a kernel configuration as seen in make menuconfig.

    + KERNEL: Enable module "example +
    +

    This is an example of a kernel card.

    +
    +

    2.7 Bigcode

    +

    The code tag is typically used to denote commands the user should run. The bigcode card is meant for showing programs, usually Bash or Python scripts, or C programs.

    + CODE: example.c +
    +

    This is an example of a bigcode card.

    +
    +

    2.8 News

    +

    This card is meant for sharing news about the distribution. It is only found on the homepage.

    + 1/1/70 - Example +
    +

    This is an example of a news card.

    +
    +
    +
    +

    Page last updated MM/DD/YY @ HH:MM

    +

    Page licensed under GNU Free Documentation License 1.3 or later

    +

    --------------------

    +

    Copyright (C) 2021-2023 Everest Linux

    +

    Linux (R) is a registered trademark of Linus Torvalds.

    +

    Everest Linux is provided AS IS, WITHOUT WARRANTY.

    +
    diff --git a/docs/recovery.html b/docs/recovery.html new file mode 100644 index 0000000..ea437dd --- /dev/null +++ b/docs/recovery.html @@ -0,0 +1,62 @@ + + + + + + Everest Linux - Docs + + + + +
    + everest-logo + Home + About + Install + Packages + Downloads + Docs + Errata + Git ↗ +
    + + +
    + +

    Recovery

    +

    System security is very important, however there are time that a system becomes so secure that the owner of the system becomes locked out of their own computer. There are a couple different methods for recovering a locked system.

    +

    1 - Issues

    +

    1.1 Issues resulting in a locked system

    +

    There are many things which may lock someone out of their system. The most notable ones are:

    +
      +
    • Forgotten root password
      • +
    • Problematic PAM configuration
      • +
    +

    There are two methods for recovering a system locked out by these issues, one of which should be set up by default.

    +

    2 - Rescue Partition

    +

    2.1 Introduction

    +

    Everest includes a small rescue partition in its system images, which contains only what is necessary to recover a system. Using this partition, system recovery is a relatively easy task.

    +

    2.2 Booting

    +

    While installing, either GRUB automatically created a boot entry for the rescue partition, or you did it yourself. If not, the rescue partition is unusable for recovery.

    +

    To boot into the rescue partition, power off your system, and select Everest Linux (rescue) in the GRUB boot menu.

    +

    3 - Using BASH as init

    +

    3.1 Introduction

    +

    The Linux kernel supports setting a custom init using kernel parameters. In this instance, we will use bash as our init to recover a locked system.

    +

    3.2 Booting

    +

    Power off your system. While booting, edit your boot entry's kernel parameters. On GRUB, this can be done with the e key.

    +

    Add the following to your kernel parameters:

    + KERNEL: Required kernel parameters to use BASH as init +
    +

    init="/bin/bash"

    +
    +
    +
    +

    Page last updated MM/DD/YY @ HH:MM

    +

    Page licensed under GNU Free Documentation License 1.3 or later

    +

    --------------------

    +

    Copyright (C) 2021-2023 Everest Linux

    +

    Linux (R) is a registered trademark of Linus Torvalds.

    +

    Everest Linux is provided AS IS, WITHOUT WARRANTY.

    +
    diff --git a/install.html b/install.html index 380f8af..c820c1f 100644 --- a/install.html +++ b/install.html @@ -30,24 +30,12 @@

    Installation Handbook

    This guide is the official installation handbook for Everest Linux.

    - WARNING: + PRELIMINARY WARNINGS:
    -

    Using unofficial guides is not recommended, as they may be outdated, or unreliable. The official guide is located at https://www.everestlinux.org/install.

    -
    -

    - WARNING: -
    -

    Simply copy and pasting commands from this guide won't cut it, and you'll most likely end up with a broken installation. Ensure you know what each command does, and how to tailor it to your system, if necessary.

    -
    -

    - WARNING: -
    -

    Everest is not for the faint of heart. If you have never touched Linux in your life, Everest is most certainly not for you. Linux Mint is a great distribution that works out of the box, and is a great entry point into Linux.

    -
    -

    - WARNING: -
    -

    Everest at its current state is highly experimental. Install at your own risk.

    +

    WARNING 1: Using unofficial guides is not recommended, as they may be outdated, or unreliable. The official guide is located at https://www.everestlinux.org/install.

    +

    WARNING 2: Simply copy and pasting commands from this guide won't cut it, and you'll likely end up with a broken installation. Ensure you know what each command does, and how to tailor it to your system, if necessary.

    +

    WARNING 3: Everest is not for the faint of heart. There is absolutely no hand holding provided, you are on your own. If you have never touched Linux in your life, Everest is most certainly not for you. There are many distributions which provide a much better user experience for those new to Linux, we personally recommend Linux Mint.

    +

    WARNING 4: Everest in its current state is highly experimental. Install at your own risk.

    If you need assistance, reach out to us on IRC (libera.chat, #everestlinux) or Discord.

    Prerequisites

    @@ -57,6 +45,7 @@
  • Download a system image
  • Unpack the system image
  • Change root into the new system
    • +
  • Set up the Glacier system profile and package index
  • Install programs
  • Install the Linux kernel
  • Set up init scripts and services
    • @@ -68,8 +57,8 @@

    Run commands prefixed with (root)# as the root user.

    Run commands prefixed with (chroot)# inside the chroot environment.

    Set up the environment

    -

    Everest needs a proper environment set up in order to install correctly.

    -

    A system mountpoint is where the new system's root (/) will be. Where you put this doesn't matter, as the host system used to build the system won't be included in the final installation. In this example, we will use /mnt/everest.

    +

    On the host system being used to install Everest, a properly set up environment containing certain programs and directories must be set up to ensure the installation can take place. This section will go into detail on how to set up this environment.

    +

    A system mountpoint is where the new system's root (/) will be. Where you put this doesn't matter, as the host system used to build the system won't be included in the final installation. In this example, we will use /mnt/everest.

    Create a system mountpoint:

    (root)# mkdir -pv /mnt/everest

    A variable pointing to the system mountpoint may be useful in the future, as it will save you a bit of typing.

    @@ -86,12 +75,12 @@ /mnt/everest/boot EFI system partition (esp) - No smaller than 256 MB, no larger than 1 GB + No smaller than 256 MB, no larger than 1 GB (minimum 1 GB if installing multiple kernels) /mnt/everest/usr /usr - No smaller than 25 GB + No smaller than 25 GB, recommended size varies. /mnt/everest @@ -104,11 +93,12 @@

    A valid filesystem is required on the drive.

    Most filesystems should work, however ensure the system has the corresponding package for whatever filesystem you choose.

    For example, if XFS is used, when installing the system:

    - (chroot)# gpkg -f world/xfsprogs + (chroot)# gpkg -f xfsprogs

    - WARNING: -
    + CAUTION: +

    Zfs is not officially supported by Everest, and requires a lot of configuration to work properly. Use Zfs at your own risk.

    +

    This stance may change at a later date, however currently there is no official Everest documentation for setting up Zfs.

    In this example, Ext4 will be used.

    Create a filesystem:

    @@ -131,7 +121,7 @@

    Create remaining directories on /usr with mkusrskel:

    (root)# mkusrskel -d /mnt/everest/usr

    Downloading a system image

    -

    An Everest system image provides an incomplete root filesystem which users can build a system off of. Users should be careful of which image they choose, as switching in the future is arduous, time consuming, and requires rebuilding a lot of packages.

    +

    An Everest system image provides an incomplete root filesystem which users can build a system off of. This includes system programs, libraries, Glacier, among others. Users should be careful of which image they choose, as switching in the future is arduous, time consuming, and requires rebuilding a lot of packages.

    It's a lot better to get it right the first time, rather than trying to get it right later.

    Do some thorough planning to ensure you get the right system image. For instance, ask yourself a few questions, such as:

      @@ -141,9 +131,9 @@
    1. Do I want to set up NSA Security Enhanced Linux (SELinux)
    2. Do I want an init system other than Busybox's built in init configured out of the box?
    - WARNING: -
    -

    Make sure you're happy with the system image you choose. While migrating in the future is possible, it requires rebuilding the majority of the system.

    + NOTE: +
    +

    Make sure you're happy with the system image you choose. While migrating in the future is possible, it requires rebuilding the majority of the system, takes a substantial amount of time, and may present other issues.

    Downloading a system image that is severely out of date is not recommended. Many programs, such as the kernel or SSL library will be vulnerable to attacks.

    Download a system image with wget:

    @@ -151,30 +141,32 @@

    Unpacking the system image

    Now that a system image has been downloaded, we can unpack it.

    Ensure the system image is inside the system mountpoint, otherwise you may run into trouble.

    -

    Since a Linux root filesystem is complex, and many different files need to be owned by certain users, or have certain permissions, simply running `tar xf` will result in a broken image. A couple extra flags are needed to preserve these permissions in the unpacked image.

    +

    Since a Linux root filesystem is complex, and many different files need to be owned by certain users, or have certain permissions, simply running tar xf will result in a broken image, as the proper permissions are not carried over. A couple extra flags are needed to preserve these permissions in the unpacked image.

    Unpack the system image:

    (root)# tar -xpvf SYSTEM_IMAGE --xattrs-include='*.*' --numeric-owner

    If this command was run correctly, you shouldn't need to edit any permissions manually.

    -

    In case permissions were changed, you can use the 'prep' command from everest-build-tools.

    +

    In case permissions were changed, you can use the prep command from everest-build-tools.

    Chrooting into the system mountpoint

    -

    Although we have a relatively complete root filesystem at this point, many essential programs are still missing. These include the kernel and bootloader. Without these, the system is unable to boot. At this point, we must chroot into the new system. This will allow us to complete the system without booting.

    +

    Although we have a relatively complete root filesystem at this point, many essential programs are still missing. These include the kernel and bootloader. Without these, the system is unable to boot. At this point, we must chroot into the new system. This will allow us to complete the system's build process without booting into it.

    Chroot into the new system:

    (root)# everest-chroot /mnt/everest

    Change the shell prompt to differentiate the two environments:

    - (chroot)# echo "export PS1='(chroot) ${PS1}'" >> /etc/profile && source /etc/profile + (chroot)# echo "export PS1='(chroot) ${PS1}'" >> /etc/profile && source /etc/profile

    Install packages

    Any programs you wish to install, such as display servers, login managers, and desktop environments, should be installed now. The kernel can take multiple hours to compile on some hardware.

    Glacier manages packages on the system, and it allows users to install, or 'merge' their own. It is recommended to get familiar with this system.

    WIKI: Introduction to Glacier +

    Glacier may not function correctly if the package database has not been downloaded. If gpkg outputs the following error: [x] Local package database does not exist., run:

    +

    (chroot)# glacier-update-pkgdb

    Install the Linux kernel

    The most important part of the system, the kernel, which allows hardware to communicate with software, is ready to be installed.

    If needed, merge the linux-firmware package, which provides device firmware:

    - (chroot)# gpkg -f world/linux-firmware + (chroot)# gpkg -f linux-firmware

    At this stage, you can decide which kernel you want to install. In Everest's package repository, many prebuilt kernels are available, as well as the source code, should you wish to compile your own.

    Option 1: Custom kernel

    -

    Compiling a custom kernel is the recommended option for most users, as it allows the most control.

    +

    Compiling a custom kernel is the recommended option for most users, as it allows the most control over what exactly is installed on your system.

    Download the kernel's source tree:

    - (chroot)# gpkg -f world/linux + (chroot)# gpkg -f linux

    The source tree will be located under /usr/src/linux.

    Inside /usr/src/linux, ensure the source tree is completely clean by running the following:

    (chroot)# make mrproper @@ -183,8 +175,8 @@ KERNEL: Enbable support for IPv6

    Networking support --->

    -

          Networking options --->

    -

                <*> The IPv6 protocol [CONFIG_IPV6]

    +

          Networking options --->

    +

                <*> The IPv6 protocol [CONFIG_IPV6]

    Recommended options are not provided - it is up to you to configure the kernel for your setup.

    Configure the kernel:

    @@ -222,9 +214,9 @@

    For example, on a system with a root, /usr, and boot partition, /etc/fstab will look like this:

    FILE: /etc/fstab
    -

    /dev/sda1      /      ext4      noatime      0 1

    -

    /dev/sda2      /usr      ext4      noatime      0 1

    -

    /dev/sda3      /boot      vfat      defaults,noatime      0 2

    +

    /dev/sda1      /      ext4      noatime      0 1

    +

    /dev/sda2      /usr      ext4      noatime      0 1

    +

    /dev/sda3      /boot      vfat      defaults,noatime      0 2

    System services that some may find helpful, such as a cron daemon or logging daemon, should be set up now.

    On systems using systemd:

    @@ -241,8 +233,8 @@

    Or, on systemd:

    (chroot)# hostnamectl hostname hostname

    A network connection is very important, and there are multiple ways to set one up.

    - WARNING: -
    + CAUTION: +

    Ensure your network is fully set up before proceeding with any other steps. It's better to get it right the first time, rather than trying to fix it later.

    First, ensure the desired network interface is not blocked by rfkill:

    @@ -272,9 +264,9 @@

    The /etc/hosts file is used to resolve IP addresses not resolved by the DHCP server.

    FILE: /etc/hosts
    -

    127.0.0.1      localhost

    -

    ::1      localhost

    -

    127.0.1.1      localdomain hostname

    +

    127.0.0.1      localhost

    +

    ::1            localhost

    +

    127.0.1.1      localdomain hostname

    The root password is extremely important, as it controls access to the root user, the most powerful user on the system.

    Ensure your chosen root password is strong enough where it cannot be guessed easily.

    @@ -295,12 +287,45 @@

    Configure the bootloader

    Now that the system is correctly configured and the kernel is installed, the final step can proceed - installing the bootloader. Without a bootloader, the system will be unable to load the Linux kernel upon boot.

    This guide only mentions GRUB, however note that other bootloaders are supported.

    -

    Merge GRUB for BIOS:

    - (chroot)# gpkg -f world/grub-bios -

    Merge GRUB for UEFI:

    - (chroot)# gpkg -f world/grub-efi +

    The GRUB package for certain system profiles compiles BIOS AND UEFI support. If you wish to remove UEFI support, you will have to manually patch the package file.

    +

    Unless you are using some obscure system profile, or simply want to make your system as small as possible, you definitely will not have to worry about this.

    + WIKI: Introduction to Glacier +

    Merge grub:

    + (chroot)# gpkg -f grub

    Install GRUB for BIOS:

    (chroot)# grub-install /dev/sda +

    If configuring GRUB to boot with UEFI, a few extra things need to be configured.

    +

    The following kernel options need to be configured in order to support UEFI:

    + KERNEL: Enable UEFI support +
    +

    Processor type and features --->

    +

          [*] EFI runtime service support

    +

    +

    -*- Enable the block layer --->

    +

          Partition Types --->

    +

                [ /*] Advanced partition selection

    +

                [*] EFI GUID Partition support

    +

    +

    Device Drivers --->

    +

          Firmware Drivers --->

    +

                [*] Mark VGA/VBE/EFI FB as generic system framebuffer

    +

          Graphics Support --->

    +

                <*> Direct Rendering Manager (Xfree86 4.1.0 and higher DRI support) --->

    +

                [*] Enable legacy fbdev support for your modsetting driver

    +

                <*> Simple framebuffer driver

    +

                Frame buffer Devices --->

    +

                      <*> Support for frame buffer devices --->

    +

                Console display driver support --->

    +

                      -*- Framebuffer Console support

    +

    File systems --->

    +

          DOS/FAT/EXFAT/NT Filesystems --->

    +

                <*/M> VFAT (Windows-95) fs support

    +

          Psuedo filesystems --->

    +

                <*/M> EFI Variable filesystem

    +

          -*- Native language support --->

    +

                <*/M> Codepage 437 (United States, Canada)

    +

                <*/M> NLS ISO 8859-1 (Latin 1; Western European Languages)

    +

    Install GRUB for UEFI:

    (chroot)# grub-install --target=x86_64-efi --efi-directory=/boot

    For GRUB to work correctly, a configuration file must be created. Create one now:

    @@ -314,7 +339,7 @@ (root)# umount -R /mnt/everest

    Reboot the system:

    (root)# reboot -

    Ensure the installation medium is removed, or else you will not boot into the new system, rather back into the installation medium.

    +

    Ensure the newly installed bootloader is first to boot, otherwise you will end up in your old system again. If you used a live USB to install Everest, make sure you remove it before rebooting.

    Conclusion

    If all went well, Everest should boot up with no problems.

    Remove the system image from /: