I mean no harm.
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
Nah, I’m not that paranoid and I need the mic for calls.
This might just push my fear of targeted ads enough to give in to my idea of a nearly soundproof box for my phone when I’m not using it. :(
They got credited for scientific research: link
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.
MSRs have negative temperature reactivity coefficient and outlet temps around 700C at atm pressure. PWR is at measly 300C and 150 Bar.
If all control is lost, the salt expands as it heats up pushing the expanded volume out from the reactor core. The fission stops once the fuel is leaves the core region where the moderator is. Reverse is also true: you pull heat off from the loop, so the fuel-salt becomes denser, increasing reactivity. MSRs can naturally “follow” the load, if done right.
Too much water. And it’s all either fresh, slush or solid.
Because of the lack of salt, we have salmiakki. /s
Sugar is half bad, half good: the glucose part causes no harm and whole body can use it. The fructose part on otherhand is bad and has to/can only be processed by the liver first.
Yeah, it feels like I blinked and it’s now October already…
(2024 was and still is a heck of an year for me. I have almost climbed out of the ditch on this year. Yay!)
You don’t know untill you try. For me, maybe consuming 400 existential dread doses a day doesn’t register.
(/s maybe, this is a tongue in cheek post… )
The point when the AI hallucinations become useful is the point where I raise my eye brows. This not one of those.
I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…
I have begun to see that YT is being hostile to adblocker users - and this worries me. I assume YT is already probing the clients to see which are circumveting the ads.
I had an (let’s say unconventional) idea at one point: an add-on which only purpose is to show the YT ads in the background which uBO blocked. All of the blocked ads would be played (eventually) - except that the user can just ignore this happening in background and wouldn’t be actually seeing the ads. I.e. the browser would just move playing the ads into a background container not visible to the user.
Jokes on merge… when a rebase editing goes wrong after +15 commits and six hours, and git hits you with a leadpipe: “do it. Do it again, or reassemble your branch from the reflog.” I.e. you commited a change very early, went over bunch of commits resolving/fixing/improving them and at middle way forget if you should commit --amend or rebase --continue to move forward. Choose wrong, and two large change-sets get irreversilbly squashed together (that absolutely shouldn’t), with no way to undo. Cheers. 👍
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.)
The short version:
This means that you reset your password with a 32-character long generated password, which is saved in your vault, PlayStation saves a 30-long password and then you use the 32-long password to log in, which fails because it isn’t the same.
That password prompt should be scorched to earth.
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.
So this is it. The enshittification has reached slowlorris levels.