qdesjardin: (Default)
This is the "Dairy" scheme - primarily aimed for roguelike players, but also for everyday command use, as well as programming. With other colour schemes, there were one or more tidbits that I didn't like, that made it unfeasible to use in the long run:
  • ugly/indistinguishable colour combinations
  • too monochromatic
  • dark blue is difficult to read, and blue is hard to distinguish from cyan
  • cooler hues that wouldn't play well under redlight
  • base16 colours that made it guesswork to figure out if a colour was meant to be "bold/highlighted" text
  • coloured text which grew tiresome after a while
After years of intense tweaking, I came up with something definitive, in the sense you won't be fiddling around for a long while. All colours are original, and do NOT obey modern trends. The colour scheme (hex) is as follows, and can be applied to terminals, or anything which uses 16 colours:

 darklight
black#070605#865870
red#9a0b20#ee3a43
green#19b25a#a9ecad
yellow#a35834#f5db7b
blue#003d79#009ada
magenta#b269ff#f4b8f4
cyan#007485#7be3f6
white#f0cbbe#ffffff

Below are examples - "Dairy" on left, default Windows/xterm scheme on right.



qdesjardin: (Default)
This morning, as I was tinkering with my Arch system, I thought of installing LibreSSL, which is said to be a more secure code-base. So I installed it from the AUR (Arch User Repository), ignoring the fact it said "EXPRIMENTAL ONLY" [sic] in the description.

It broke the majority of my system. So much depends upon OpenSSL, including sudo, and pacman (Arch's package manager). As a result, you can't just re-install OpenSSL back because pacman is going to complain about its broken dependencies.

What can you do?

One method is using the ArchISO. Boot from there, and mount your disk's Arch partition(s) onto /mnt. Then, you can use pacman with the "--sysroot /mnt" parameter (originally I used pacstrap, which worked, but someone on Reddit suggests this method is better as it doesn't risk overwriting all the base files):
  • pacman --sysroot /mnt openssl
Once you have OpenSSL back, do a double-check. Here, I chrooted into the disk's Arch, and did a basic pacman -Syu, along with reinstalling OpenSSL-1.0 (it threw some file dependency errors on the first reinstall, then went smooth after trying it again).

And voila, Arch Linux is back to normal! Of course, you can follow the above procedures if you need to fix something else (i.e. you did an oopsie in sudo, removing pacman of all things! whilst in a drunken LSD-induced fit).