renzev

Lmao these losers are paying for brave search results? Just go to search.brave.com its free hahahaha

/j

I wish women were real

Glad I could help 🫡

There is a thread on dvach that's been going since june 2020: https://2ch.hk/wp/res/71875.html

Considering the overlap between homelessness and untreated mental disorders, sadly both of your descriptions are likely to fit the potential attic-dweller.

Yes, but the "shall be used for Good, not Evil" part is part of the json license, not the PHP extension? https://json.org/license

OK but how can json have a license? I understand a particular json parser having a license, but how can a specification, which contains no code, even be considered "software"?

The complaints about yaml's quirks (no evaluating to false, implicit strings, weird number formats, etc.) are valid in theory but I've never encountered them causing any real-life issues.

If GRUB is too confusing, just uninstall it? You said you have a UEFI system, you don't need a bootloader. You can just put the vmlinuz and initramfs onto the ESP and boot into it directly. You can use efibootmgr to create the boot entry, something like this:

efibootmgr \
	--create \
	--disk /dev/sda \
	--part 1 \
	--index 0 \
	--label "Void linux" \
	--loader /vmlinuz-6.6.52_1 \
	--unicode " \
		root=PARTLABEL=VOID_ROOT \
		rw \
		initrd=\\initramfs-6.6.52_1.img \
		loglevel=4 \
		net.ifnames=0 \
		biosdevname=0 \
		nowatchdog \
		iomem=relaxed \
		"

• --disk /dev/sda: What disk is the esp on?
• --part 1 What partition number (counting from 1) is the esp on?
• --index 0 At what index in the boot menu should the boot entry appear?
• --loader Path to the vmlinuz file. These are normally in /boot, you have to move it to the esp yourself
• root=PARTLABEL=VOID_ROOT this is the linux root partiion. I'm using PARTLABEL to identify mine, but you can use pretty much anything that /etc/fstab supports
• initrd=\\initramfs-6.6.52_1.img Again, you have to move the initramfs file from /boot into the esp. For some reason this uses backslashes, not forward slashes as path separator (double backslashes in this case are to prevent the shell from interpreting it as an escape sequence)
• The rest of the arguments are just misc kernel parameters that I use

Just search for EFISTUB for more info.

It's not their official policy, but my personal philosophy with alpine goes like this:

1. If it doesn't work with musl/busybox, find an alternative that does
2. If I can't find an alternative, then I patch it myself
3. If I don't have the time/skill to patch it myself, then I throw it into a container that has glibc/gnu coreutils

This take is honestly bewildering to me. What do you mean "for no reason"? You learn it to write quickly and legibly. What other option is there? Writing in block letters like a kindergartener?? inb4 "bUt eVeRyThInG iS dIgItAl nOw". I'm a programmer, about as digital as you can get, and even I whip out the pen and paper for mindmapping and notetaking.