There is a lot of confusion and wrong information in the internet about the Unified Extensible Firmware Interface (UEFI) and how to set it up correctly – especially under GNU/Linux. What makes things worse and also confused me a lot is that all vendors tend to implement this “standard” differently. So although UEFI is defined as a new industry standard replacing the BIOS, it can hardly be called “standard” at this time. Yet another problem of understanding UEFI is, that people seem to mix up words that have a special meaning.
My old notebook still uses the old BIOS-MBR setup, not capable of any UEFI fancy-ness. But it is dying, so I recently bought a new one. It is an “HP EliteBook 840 G1”. I used that opportunity to familiarize myself with UEFI and GNU/Linux.
This article explains two things (only taking GPT setups into account):
How is UEFI implemented in practice and set up with GNU/Linux?
I finally got myself a Raspberry Pi and it obviously needs a case. (By the way, it runs the ARM version of Arch Linux, naturally.) Of course I wanted to build one myself, rather than buying one of those boring cases that almost cost more than the device itself. I already had a vague idea about the concept but nothing solid yet. The concept had to be simple (but solid), because besides a Dremel and an electric drill I only had standard tools at hand. (You do not even need a Dremel if you have a small saw instead.)
This was an old project of mine. A few years ago I had a huge load of data comming in (~4 TiB) and the amount of storage I needed suddenly more than dubbled. Until then I was using two 1.5 TB HDDs which I mirrored by hand using rsync, because I’m paranoid of loosing data. It was annoying to always copy all data to each disk to have redundancy – and certainly not a smart solution. Now that data wouldn’t fit onto the two disks anyway, so it was time to think of a new solution. I had enough of wasting my time with copying files from one hard drive to another.