Fryboyter

Changing the label should also work during operation.

For example, it should be sufficient to run sudo btrfs filesystem label / newlabel to change the label of the root partition (/) to newlabel.

If I'm not mistaken (can't test it right now), you have to specify the mountpoint when the partition is mounted. And in unmounted state the device (e.g. /dev/sda).

The problem of systemd is that it hasn’t been just a replacement of init as they initially claimed

Apart from the PID 1 part of systemd, almost all tools are optional.

Although I have a positive opinion about the systemd project, I used netctl instead of systemd-networkd for a long time without any problems. And even today I don't use systemd-resolved because I use a combination of unbound and Pi-Hole in my private LAN. And so on.

So you can't say that the systemd project has replaced various solutions in such a way that you don't have a choice anymore.

Is the current SystemD rant derived from years ago (while they’ve improved a lot)?

In my experience, the same arguments against systemd (not systemD) are still used. No matter how often they have been disproved or whether the problem has been fixed in the meantime. With many users I am sure that it is only about making the project systemd bad.

Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?

I would prefer it if there were no rants at all. No matter what the topic. Because that doesn't help in any way. It would make more sense to invest the energy in the projects in question or in alternative projects to improve them.

I would recommend always testing shell scripts with https://github.com/koalaman/shellcheck. Often there is room for improvement that you don't think of yourself.

You guessed wrong. I speak here from experience that I have made with third parties but also myself.

In the two decades I've been using Linux myself, I've broken quite a few Linux installations because I played around with something in the terminal emulator that I had no or too little knowledge of.

If I now imagine that these but also other advanced settings would be possible in the Mandriva control center or in the control center of Plasma with a few clicks, I would have destroyed my installations much more often. From therefore I remain with my opinion. Some settings should not be made easily accessible in pre-installed standard tools. Especially since beginners often do not know how to undo these changes if there are problems. I also think that the developers of e.g. the System Settings of Plasma have already thought about why one only has the configuration options that the tool offers. And also a warning that is displayed when you start the advanced mode, for example, will not be useful. Nowadays, this will be often ignored.

And as already written, it is not so easy for some tools to offer a graphical interface at all. For example because they have a lot of parameters. Usually a GUI becomes so confusing in these cases that it is still easier to use them in the terminal emulator.

FreshRSS is explicitly mentioned on https://github.com/martinrotter/rssguard. I therefore assume that there should be no problems.

If such settings are easy to change via a graphical interface, I see the danger that users with insufficient knowledge will tinker with them, which may lead to problems.

In addition, there are often so many setting options that it is not possible to manage them with a graphical user interface, or at least not in a reasonable way.

Maybe Borg is a possibility. However, I have not yet backed up an entire system with it, but only certain files.

• The file permissions have always been correct when restoring files in my case.
• Which compression (LZ4, zlib, LZMA or zstd) and which compression level is used can be specified when creating a backup.
• Backups can be mounted via FUSE, so that you can restore individual files with an file manager or a terminal emulator, for example.

With the command hdparm -I /dev/sdX you can check if ATA Secure Erase is supported by the respective hard disk. If the output shows among others things supported: enhanced erase this is the case. Instead of sdX you must of course specify the respective hard disk.

Edit: You should run this command anyway to make sure that the hard disk in question is not frozen (https://archive.kernel.org/oldwiki/ata.wiki.kernel.org/index.php/ATA_Secure_Erase.html#Step_1a_-_Ensure_the_drive_is_not_frozen:).

The post is dated June 26, 2020, so I wonder if this is even up to date?

This has nothing to do with RSS Guard. The link does not work in general. Https://lemmy.ml/feeds/u/dessalines.xml?sort=New, for example, does work. There seems to be something wrong with lemmy.ml. The administrators have to take care of that.

In my experience, there are no problems with either VirtualBox or VMware when it comes to Arch. Personally, I mainly use VirtualBox.