Documentation issueshttps://git.adelielinux.org/adelie/docs/-/issues2023-11-19T17:55:29Zhttps://git.adelielinux.org/adelie/docs/-/issues/321Improve developer onboarding documentation2023-11-19T17:55:29ZZach van RijnImprove developer onboarding documentationWe need to improve our developer documentation to create a smoother on-ramp for new developers.We need to improve our developer documentation to create a smoother on-ramp for new developers.https://git.adelielinux.org/adelie/docs/-/issues/320Admin Handbook - Configuration - Setup Keyboard2022-01-27T16:16:18ZBjörn StrömbergAdmin Handbook - Configuration - Setup Keyboardthe admin handbook pointed me to setting XKBLAYOUT in /etc/default/keyboard.
which does not work, after some lurking in the issue tracker i found adelie/horizon#323
horizon sets the keyboard layout in /etc/conf.d/keymaps
pretty much e...the admin handbook pointed me to setting XKBLAYOUT in /etc/default/keyboard.
which does not work, after some lurking in the issue tracker i found adelie/horizon#323
horizon sets the keyboard layout in /etc/conf.d/keymaps
pretty much everything is configured via /etc/conf.d on a raw console install it seems so far from the config files, docs should reference this cleanly.https://git.adelielinux.org/adelie/docs/-/issues/319UEFI and Adelie / Alpine2022-05-17T17:03:29ZBjörn StrömbergUEFI and Adelie / Alpineso after a lot of trouble with the 1.0-RC2 image, just to get an installed system i had to revert back to ArchLinux style manual install..
anyway to make a long story short, there [Quick-Start-Guide Bootloader](https://git.adelielinux.o...so after a lot of trouble with the 1.0-RC2 image, just to get an installed system i had to revert back to ArchLinux style manual install..
anyway to make a long story short, there [Quick-Start-Guide Bootloader](https://git.adelielinux.org/adelie/docs/-/wikis/Quick-Start-Guides/Installation#bootloader-non-macintosh) is no Bootloader entry for UEFI Bootloading.
so we need to add a few things to this page..<br>
Add:<br>
**Before Mounts we need to install some stuff on the temporary-live-system**
- apk add efibootmgr grub-efi
- modprobe efivarfs (should been loaded by apk install but just in case..)
- run efibootmgr to check if it can list the EFI Bootlist.. (says 'UEFI variables are not supported on this machine.' if anything is wrong.. or list the info if all is good.)
[Modify Mounts](https://git.adelielinux.org/adelie/docs/-/wikis/Quick-Start-Guides/Installation#mounts)<br>
**Before Chroot into new install, we do the regular stuff, mount needed filesystems..**
- mount -B /dev /target/dev
- mount -t proc none /target/proc
- mount -t sysfs none /target/sys
- mount -t efivarfs none /target/sys/firmware/efi/efivars **[only needed if UEFI]**
In the bootloader cluster of items [Mac, Non-Mac]<br> add BIOS/UEFI to Non-Mac<br>
[Modify Bootloader (non-Macintosh)](https://git.adelielinux.org/adelie/docs/-/wikis/Quick-Start-Guides/Installation#bootloader-non-macintosh)<br>
before:
#### Bootloader (non-Macintosh)
* Set up the bootloader (GRUB), which may be a different partition in your setup. Skip this section for Macintosh hardware.
```shell
apk add grub grub-bios
grub-mkconfig -o /boot/grub/grub.cfg
grub-install --boot-directory=/boot /dev/sda
```
after:
#### Bootloader BIOS (non-Macintosh)
* Set up the BIOS Bootloader (GRUB), which may be a different partition in your setup. Skip this section for Macintosh hardware. or UEFI Hardware
```shell
apk add grub grub-bios
grub-mkconfig -o /boot/grub/grub.cfg
grub-install --boot-directory=/boot /dev/sda
```
#### Bootloader UEFI (non-Macintosh)
* Set up the UEFI Bootloader (GRUB), which may be a different partition in your setup. Skip this section for Macintosh hardware. or BIOS Hardware
```shell
apk add grub grub-efi
grub-mkconfig -o /boot/grub/grub.cfg
mkdir /efi
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB
```
there still might be a few gremlins here, but i add this now so i can remember what i did.
initially got 3 UEFI systems to test UEFI installs on so as time progresses i might have time to create the updates myself.https://git.adelielinux.org/adelie/docs/-/issues/94Administrator's Handbook, chapter 5: "Static addressing" does not cover stati...2021-05-12T03:52:58ZEmilyAdministrator's Handbook, chapter 5: "Static addressing" does not cover static addressing| | |
| --- | --- |
| Bugzilla ID | 94 |
| Reporter | A. Wilcox (awilfox) |
| Assignee | A. Wilcox (awilfox) |
| Reported | 2019-05-21 17:18:47 -0500 |
| Modified | 2019-05-21 17:18:47 -0500 |
| Status | CONFIRMED |
| Version | 1.0-BE...| | |
| --- | --- |
| Bugzilla ID | 94 |
| Reporter | A. Wilcox (awilfox) |
| Assignee | A. Wilcox (awilfox) |
| Reported | 2019-05-21 17:18:47 -0500 |
| Modified | 2019-05-21 17:18:47 -0500 |
| Status | CONFIRMED |
| Version | 1.0-BETA3 |
| Hardware | All / All |
| Importance | --- / major |
## Description
There is no mention of config_*, routes_*, etc. We should cover at least the basics, and reference the netifrc documentation for advanced usage.1.0-BETA3https://git.adelielinux.org/adelie/docs/-/issues/86Admin Handbook, chapter 1: Revise introduction to "The shell environment"?2021-05-12T03:52:56ZEmilyAdmin Handbook, chapter 1: Revise introduction to "The shell environment"?| | |
| --- | --- |
| Bugzilla ID | 86 |
| Reporter | Michael Siegel |
| Assignee | A. Wilcox (awilfox) |
| Reported | 2019-02-27 13:26:03 -0600 |
| Modified | 2019-02-27 13:26:03 -0600 |
| Status | CONFIRMED |
| Version | 1.0-BETA2 |...| | |
| --- | --- |
| Bugzilla ID | 86 |
| Reporter | Michael Siegel |
| Assignee | A. Wilcox (awilfox) |
| Reported | 2019-02-27 13:26:03 -0600 |
| Modified | 2019-02-27 13:26:03 -0600 |
| Status | CONFIRMED |
| Version | 1.0-BETA2 |
| Hardware | All / All |
| Importance | --- / minor |
## Description
Section "The shell environment"[1] currently starts like this:
The shell environment, also called a terminal or console, is an interface
where you type commands in to a command processor (the shell), and view the
results of the command on your screen.
I'd suggest to change that a bit, to something like this:
The shell environment, also referred to as the terminal, the console or the
command line, provides a text-based interface where you type commands into a
command interpreter (the shell) and view the results of their execution on
the screen.
[1] https://help.adelielinux.org/html/admin/introduction.html#idm703613607780961.0-BETA3https://git.adelielinux.org/adelie/docs/-/issues/85GRUB installation wiki page: Add warning about changed drive labels after reboot2021-05-12T03:52:54ZEmilyGRUB installation wiki page: Add warning about changed drive labels after reboot| | |
| --- | --- |
| Bugzilla ID | 85 |
| Reporter | Michael Siegel |
| Assignee | A. Wilcox (awilfox) |
| Reported | 2019-01-13 10:00:03 -0600 |
| Modified | 2019-01-13 10:00:03 -0600 |
| Status | CONFIRMED |
| Version | 1.0-BETA2 |...| | |
| --- | --- |
| Bugzilla ID | 85 |
| Reporter | Michael Siegel |
| Assignee | A. Wilcox (awilfox) |
| Reported | 2019-01-13 10:00:03 -0600 |
| Modified | 2019-01-13 10:00:03 -0600 |
| Status | CONFIRMED |
| Version | 1.0-BETA2 |
| Hardware | Adélie Linux / All |
| Importance | --- / minor |
## Description
When you're installing Adélie manually from the live system on a USB key, the USB key will be seen as /dev/sda by the system, while your first internal hard drive will be seen as /dev/sdb (it may also be /dev/hda vs. /dev/hdb or /dev/vda vs. /dev/vdb, depending on the hardware).
This will create a problem later, if you run
# grub-install --boot-directory=/boot /dev/$disk
with the value of $disk derived from what the currently running live system sees it as (sdb) because once the USB key is removed, the system will see the internal drive as sda.
Now, if the grub.cfg created during installation contains root=/dev/sdb<partition number>, this will cause a kernel panic because the root fs cannot be found. You'll have to change it back to /dev/sda<partition number> to work properly.1.0-BETA3https://git.adelielinux.org/adelie/docs/-/issues/2Installation Handbook: Chapter 1: Maybe don't use `/dev/sdX` as target device...2020-05-11T13:31:54ZMichael SiegelInstallation Handbook: Chapter 1: Maybe don't use `/dev/sdX` as target device name parameter for `dd` command.I've just realized that, in the instructions on how to create a bootable installation medium on Linux or BSD, I used `/dev/sdX` as the parameter for the target device. However, `sd[[:alpha:]]` seems to be a Linux thing. On BSD, device na...I've just realized that, in the instructions on how to create a bootable installation medium on Linux or BSD, I used `/dev/sdX` as the parameter for the target device. However, `sd[[:alpha:]]` seems to be a Linux thing. On BSD, device names may look quite different. The [chapter on creating installation media](https://www.openbsd.org/faq/faq4.html#MkInsMedia) in the OpenBSD FAQ says a few things about that.