Tuesday, September 11, 2012

Arch Linux VM Fun

Messed around with another VM this morning. Awaiting my new 11 inch MacBook Air, I keep watching my tracking number with anticipation! I have an old serviceable machine at home that has been upgraded motherboard and all over the years, but it's nearing end of life. It's currently running Windows 7 and has 8 GB Ram. Nothing fancy, but it works.

The VM I was working with early this morning was ArchLinux, I haven't used it before but got caught in some permissions matrix that I will have to sort out later. I spent enough time on it that I will have to move on. Old me would have gutted it out and stayed up all day, but I'm learning better habits. I'll try and make a post another day and fix the Arch Linux upgrade path. No promises, though. Pictures from the nightmare below, and some links. I should note this is all with pacman package manager, and its permissions and desires.

Summary of what I tried:
= Updating pacman "pacman -S pacman"
= Updating the entire core "pacman -Syu" and clearing the cache "pacman -Sc"
= Trying a forced update with no confirmations: "pacman -Syuf --noconfirm" (probably a bad idea!)
= Adding SigLevel = Optional TrustAll to the /etc/pacman.conf
= Above all this, doing a "pacman-key --init" to update the pgp keys
= Trying to force the update further with "pacman -S filesystem --force"

Links:
Pacman "error: failed to commit transaction (conflicting files)" (Page 1) / Pacman & Package Upgrade Issues / Arch Linux Forums

[SOLVED] "signature from is unknown trust."






During all of this, took mental breaks and cleaned around the house, and played with HTML/CSS.

No comments: