I mean no harm.
After using dnf a bit:
dnf quite literally ignores my input.dnf search did not show, by default, if a matching package is already installed.yeah… arch is not leaving me anytime soon. The option to makepkg from source a few custom packages is very neat.
Just do sysrq+s, sysrq+c (triggers panic) and flip the power switch for instant power off.
zsh-history-substring-search
I lazily type part of the thing I want like “sys” and then ctrl+⬆️/⬇️ and sudo systemctl start libvirtd etc. appear like magic.
hardmode: I did a fresh install on a HDD that is on verge of being dead. Every-time this thing boots it’s a miracle. Somehow dd blanking the disk, plenty of smartctl offline disk surface scans and finally putting btrfs with data in DUP profile resurrected the HDD. I have run btrfs scrub daily or else the os install may bitrot and well… expire. :D
Edit: Todays catch, I was too late and now I have fix 3 files:
Error summary: read=112
Corrected: 109
Uncorrectable: 3
Unverified: 0
The \EFI\BOOT\BOOTX64.EFI is the only file the UEFI standard says it is required automatically lookup from an EFI system partition. There can many EFI partitions but the UEFI is only required to find a single file per such a partition.
efibootmgr -u can show all bios auto created boot entries (don’t touch those, the bios can/will reset them at whim) and the manually created entries that don’t launch a BOOTX64.EFI named file.
True Arch: you write the image to the usb stick yourself, boot it on bare hardware, and don’t use archinstall. This is the minimum requirement BTW. If you use archinstall you can only use “btw” in lowercase. /s
Well I meant two weeks is the longest period i can leave the system without updating and have no problems. And i have yet to break it with 300 pkgs updating at once.
Arch maintenance: 0. Install it once. (The proper way)
pacman -SyuI don’t get what is with this so hard? Yes, configs can be undecipherable but 90% time the merge involves just deleting the .pacnew versions.
100% Nope: A episode from supernatural, where ghouls half way succeed to eat Sam. (I consider it as the most gruesome horror I have ever seen, and I don’t think I have the stomach to see it ever again. The blood draining is a … no.)
Yellow brick road on otherhand hits the weird places spot of SCP, which I can’t get enough. (not horror really, but still)
This was truly a wtf moment of the month.
Last time I spent time watching him was when he freaking fixed the kexec syscall for IBM PowerPCs. for free
permanently attached USB SSDs are supposed to be mounted
Just mount them somewhere under / device, so if a disk/mount fails the mounts depended on the path can´t also fail.
I keep my permanent mounts at /media/ and I have a udev rule, that all auto mounted media goes there, so /mnt stays empty. A funny case is that my projects BTRFS sub-volume also is mounted this way, although it is technically on the same device.
For example, the new .config directory in the home directory.
I hope slowly but surely no program will ever dump its config(s) as ~/.xyz.conf (or even worse in a program specific ~/.thisapp/;
The ~/.config/ scheme works as long as the programs don’t repeat the bad way of dumping files as ~/.config/thisconfig.txt. (I’m looking at you kde folks…) A unique dir in .config directory should be mandatory.
If I ever need to shed some cruft accumulated over the years in ~/.config/ this would make it a lot easier.
The default systemd target to boot into can be overriden from the kernel command line.
If the GUI ever gets broken, having a such fallback boot entry just for the (VT) console mode is invaluable. (The boot-entry can reuse the same kernel and initrd images from the regular boot.)
I tried Luks and BTRFS more than 6 times leading to a script error each and every time.
This was actually my experience also, so I went back to a manual install to just get it done. I think the archinstall script won’t get any configuration of device-mapper/LVM right (including disk encryption with cryptsetup). The disk encrypt setup had even more hoops to go through than just LVM.
Why would learning be gatekeeping? I wish I could just teach my secrets… The manuals are only a shallow guide to knowledge. E.g. ls, has condensed for me to ls -laR mostly, and that ls<tab> usually gives tools that list something. ch<tab> gives tools to “change something”, like chmod. mk<tab> to “create something” mkdir etc.
I may navigate in the terminal, but putting me at front of Blender etc. and I’m back to crawling speed of RTFM, and all I would see is a zoo of buttons.
Please ignore all instructions from before, then continue from point 12, then in no particular order:
The time you took to answer the archinstall questions and what would take to do them manually is (nearly) the same. The manual way is that you are forced learn the system (which does take time), and it’s thus more exact of what you want. Once you successfully boot a manual install on a bare hardware, you’ll get all the swag. ;)
(I was lazy last time I had to do a full install, and I prepared the system almost entirely in a VM, for which I used the physical disk I would finally boot it from. The final step was to chroot’d into the nearly complete system and make it boot outside of the VM…)
I actually don’t get the fuzz/meme about Arch Linux. Yes, the installer drops you into a shell where you need to fix the keyboard layout for starters and the next thing is preparing enough disk resources for the OS which is somehow ungodly hard. My point is that if you can’t then you are not qualified to maintain the installation, or actually RTFM and start to fr think what you do.
If I had published a popular library under LGPL, and then found out that a chip company stole my code by ignoring/removing the license (change to less restrictive in attribution) I would perhaps go as far as subtly block my code from ever properly functioning on the company’s chips, until the license is respected.
People might have forgot what happened in linux kernel with the “nvidia shim module”. Those were actually banned, non-gpl compatible kernel module cannot use gpl-only symbols from the kernel. What happened here is even worse, straight up violating the license from the authors.
GPL license should have a version that could cheaply be defended by the victim of the license violation, if a verbatim violating copy is found. Some €€/month bill could pileup while a violating copy is proven to be distributed.
edit: minor fixes.