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

Two new hobbies to keep me in the reality^tm.

So this is it. The enshittification has reached slowlorris levels.

No mention of KDevelop? ;__;

I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I’m been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)

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.

I intended this an sarcastic example; I think it’s worse than putting the main outside of the branch because of the extra indent-level. It does have an upside that the main() doesn’t exist if you try import this as an module.

Btw, ld.so is a symlink to ld-linux-x86-64.so.2 at least on my system. It is an statically linked executable. The ld.so is, in simpler words, an interpreter for the ELF format and you can run it:

ld.so --help

Entry point address: 0x1d780

Which seems to be contained in the only executable section segment of ld.so

LOAD 0x0000000000001000 0x0000000000001000 0x0000000000001000
     0x0000000000028bb5 0x0000000000028bb5  R E    0x1000

Edit: My understanding of this quite shallow; the above is a segment that in this case contains the entirety of the .text section.

I would put my code in a def main(), so that the local names don’t escape into the module scope:

if __name__ == '__main__':
    def main():
        print('/s')
    main()

(I didn’t see this one yet here.)

Holy hell, thats rough. :D

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

I’ll just comment about one thing that keeps popping up in the discussions: grid-level storage. There is no such thing yet really that would last a full day cycle, and the 100MW or so units we are building are mostly for frequency stabilization and for buying enough time to turn on a base-load plant when the renewables drop out. I’m not arguing against storage - it is absolutely needed.

The problem is the scale, which people don’t seem to get. Largest amount of energy we can currently repeatedly store and release is with pumped hydro, and the locations where this is possible are few and far between. Once the batteries reach this level-of-capacity, then we have a possibility to use them as grid-level storage that lasts a few days instead of hours.

My favorite so far:

$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list

Thread 1 "gdb" received signal SIGABRT, Aborted.

I once wrote bind_front() and move_only_function likes in C++17. This nearly drove me mad because you cannot refer to a overload set by a name.

On the otherhand, I can now decipher the template error mess that the (g++) C++ compiler spews out.

what the actual fuck. 🤮

$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list

Thread 1 "gdb" received signal SIGABRT, Aborted.

Yeah, try debug that.

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)

1. Every 2 weeks minimum pacman -Syu
2. Every 3 months merge/update configs in /etc.

I 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.