EndeavourOS Raspberry Pi .img

ARM Installation
21

At that time I had been doing ARM development for a little over 3 years. At that time, we were using Plasma/Calamares to configure the image.

Then these developments occured.

  1. Calamares had to be compiled specifically for aarch64 devices. At this point, Calamares would no longer compile for aarch64. Never figured out why as it was above my pay grade
  2. At this point there was myself and @sradjoker doing the ARM development. For personal reasons, sradjoker had to take a sabbatical from ARM development.
  3. I started doing ARM development in the late 2019 or early 2020 time frame. I had plenty of free time on my hands due to mandates, etc. I was glad to have something to get my mind off the circumstances. Then after that was over, I had less time for development.

These combined factors made a complete do over for how I approached ARM development. I needed to get back to KISS and make things more efficient time wise.
This was going to take a lot of time, so I suspended development until I decided if this could be done, and then get it done.

Creating an image with a complete Plasma Desktop Environment solely for the purpose of running Calamares was extremely inefficient. It looked nice, but inefficient. Considering the only thing we were using Calamares for was the entry of personal information. Such as
Name, username, hostname passwords, time zone. Then if the user chose a different DE than Plasma, Plasma had to be completely removed and the desired DE installed.

So I came up with the procedures currently being used. Creating images is now more efficient and stable. Personal data entry is done in a simple TTY console window. No theming, etc.
Personal data is entered via Dialog Windows. I decided I could fit this into my current schedule so EnOS ARM arose from the ashes like the Phoenix. It has worked well for some time now.

Pudge

7 Likes
22

This change was mildly annoying as Arch Linux Arm don’t currently release any Pi-5-specific root filesystem tarballs.

1 Like
23

How come it uses the GUID Partion Table?

24

Why not?

25

I don’t know. I’m just wondering.

26

Summary:
A GUID Partition Table (GPT) is a modern standard for partitioning hard drives that allows for larger disk sizes and more partitions than the older Master Boot Record (MBR) system. It uses unique identifiers for each partition, making it more efficient and reliable for managing disk space.

Pudge

27

Yeah but that’s Microsoft. I’m only using 256GB drives. Trying to get out of the habit of storing things on my drives for many reasons.

28

GPT has greater redundancy of the partition table, employing a backup copy, and CRC32 checksums to validate table integrity.

2 Likes