mbw

Ich benutze seit Jahren borgbackup, nachdem ich zuerst mit rsync und dann rsnapshot angefangen hatte. Automatisches Backup erfolgt denke ich entweder über udev-Regeln (Backup beim Anschließen), oder in regelmäßigen Intervallen (benutze ich nicht) wie z.B. hier beschrieben.

Borg hat im Gegensatz zu rsync rsnapshot den Vorteil, dass auf der Sub-File-Ebene dedupliziert wird, d.h. nur weil eine Datei sich an einer Stelle geändert hat, wird der Rest der Datei nicht nocheinmal kopiert. Das einzige was ich zusätzlich empfehlen würde, wäre von vornherein mit compression --zstd,9 oder so zu arbeiten.

I used tmsu (“tag my shit up”) for a while, but it required too much discipline and then I dropped it.

In addition, tools like fzf for fuzzy file-search (comes with shell integration to e.g. replace the default history search in bash) and ripgrep-all made this kind of organization unnecessary for me. It now suffices to have a vague idea where a thing is located and I can do a brute-force search in a few seconds.

The next-level filesystem argument is brought forward every few months, but I’m not buying it.

and then suddenly there’s the perfect use case

Yeah but like WHAT?

Just so that you have an additional data point, here’s how I do it.

I run a backup first, using borg-backup. I used rsync in the past, then rsnapshot and now borg since it allows for compressed incremental backups, diffing on the “chunk” level, meaning I won’t backup the entirety of a modified file again and safe a lot of space.

I used yay before, but like you I didn’t want to go into it blindly and do some modicum of sanity-checking the PKGBUILD for changes beforehand. Since it wasn’t obvious on what would be the best way of using yay for doing this, I asked around on the ArchLinux Forum, and ultimately decided to try one of the simpler tools suggested in the Arch Wiki, aurutils.

After setting it up (the author helped me migrate), I now use it as follows:

• aur repo --upgrades: Searches for new versions of aur packages and displays them
• aur sync --upgrades --no-build: Performs a git-pull under ~/.cache/aurutils/sync and opens vifm so that I can look at a diff of the PKGBUILD and all the other changes in the affected directory.
• aur sync --upgrades --no-view: Builds the package. It is now available as part of the custom (local) repository used only for aur packages, but hasn’t been upgraded yet. That is, a package.tar.gz or whatever has been created and put into ~/.cache/aurutils/sync/, where the PKGBUILD resides as well
• sudo pacman -Syu: Upgrades all packages from all repositories, including the ones from the custom repository

I won’t argue pro or against one aur helper or the other, but I feel like I have a little more insight about what happens under the hood since I made the switch. That being said, in the very beginning, I managed aur packages manually. This works also, but at some point became too tedious for my taste. I am happy with the semi-automatic approach I am using now.

Ich schnappe immer wieder mal was auf von https://news.ycombinator.com/ oder https://lobste.rs. Eine weitere interessante Quelle von kleinen, unbekannten Blogs könnte https://blogs.hn sein, insb. mit Shuffle.

Ich hab mir über die Jahre eine kleine Auswahl angesammelt mit meinem RSS-Reader. Über die Jahre sammelt sich da echt was an und man kann die Feeds auch durchsuchen, falls man sich nur noch dunkel an einen Titel erinnert den man vor Jahren gelesen hat z.B.

Um noch einen konkreten Blog hierzulassen: https://brr.fyi/ ist von einem Mitarbeiter von McMurdo Station, Antarktis. Ist ausnahmsweise mal nicht technischer Natur sondern hat auch etwas Slice of Life - Charakter.

It might be a dud, but at least you’ll know :) In any case, I would consider checking https://forums.debian.net/ as well, in your case. Thinkpad + Debian sounds like a common combination, so the search function there might show some results.

I don’t know if this will be terribly useful for helping with your problem. I had this problem very seldomly and I believe it was related to some X.org problem which was fixed after an update, but it could of course be something entirely different for you.

As a very first step, I would maybe look if there is anything suspicious going on in the output of sudo journalctl -S . Possible invocations are sudo journalctl -S 2023-08-14, or -S today or -S yesterday, or just sudo journalctl but then there may be a lot of output.

Oorrr, your distro doesn’t use systemd and this command doesn’t work (in which case you could try dmesg or looking under var/log manually, probably one of the most recently modified logfiles in there.

Depending on your distro there may be of course dedicated forums where the problem may already be known. The usual advice about updating packages etc. I will assume you have already followed^^

Ebenso, wenngleich ich natürlich ein leicht schlechtes Gewissen habe, dem Aufruf nicht nachzukommen sondern nur zu konsumieren :/

I think you generally can’t know if someone shared their code with the intention that others may use it, but it’s a reasonable assumption.

I find this unnecessarily derisive. There are good reasons for a UI or README not being user-friendly, the top-most one being (imo) that it is really, really hard to get right, takes a lot of time and doesn’t primarily solve the problem the project was started for.