Same. I forgot all about it before this post.

It was almost 20 years ago when I built a cluster using around 40 desktop computers for purely academic purposes in our lab. Since then I never heard of it again even though I was working with HPC for a few years.

Not the person above, but if it is an issue you ever run into you are doing it “wrong”. Not really, but let me explain.

Having it on a separate partition has a few advantages like different mount flags (e.g. noexec), easier backup management (especially snapshots) and some other benefits like using your home for a new installation (like OP wants to) or it prevents some critical failures in case you accidentally fill it up (e.g. partial writes or services cannot start).

I often cannot decide on specific mount sizes either, because requirements may change depending on what you do. Hence I would just stick with some reasonable defaults for the installation and use some form of volume manager instead. If you want to use ext4, xfs etc I would recommend using LVM as it gives you a lot of freedom (resizing of volumes, snapshots and adding additional drives, mixed RAID modes etc) or there are btrfs, zfs or bcachefs to name the most common file systems which implement their own idea of storage pools and volumes.

Never should you need to resize a partition, there are more modern approaches. Create a single partition (+ a small EFI partition somewhere) and never bother with partitions ever again. The (performance) overhead is negligible and it gives so many additional benefits I didn’t even mention. Your complaint is a solved problem.

Würde Autofahrer definitiv ganz oben sehen. Rücksichtslos sind alle, aber dort ist es am schlimmsten.

Klar fahren die Roller und Fahrräder an Orten wo die es nicht dürfen, aber selten rege ich mich deswegen auf.

Ich rege mich aber drüber auf, wenn ich am Zebrastreifen vom Auto fast umgefahren werde, wenn das Auto viel zu schnell durch die 30er fährt und mich fast dabei mitnimmt. Dann der Lärm, der Gestank und vor allem das Gehupe was teilweise an Körperverletzung grenzt.

According to a ProtonDB user the specific crashes I am referring to have been finally fixed with 545.29.02. So two weeks ago for a 5 years old card. Good job Nvidia!

I would have loved having that earlier, because I threw mine out after all the frustration with Nvidia and I still doubt that it is fully working now.

Don’t get me wrong it’s great for others stuck with Nvidia hardware though. I would never ever recommend buying any Nvidia hardware for Linux though. The experience is miserable compared to AMD.

Try playing games like Cyberpunk. I dare you :)

You are lucky if you can play without a crash for even one minute with that card. I am not exaggerating. Something is seriously messed up with the 20XX series.

Also Wayland is still a mess for Nvidia cards overall which is becoming more and more important.

You could try disabling VRR in your display settings. I believe it is set to auto by default if supported, but it does not work properly for some monitors causing flickering.

Same. A 7800 XT is on its way as we speak replacing my 2080 Super. I am just sick of Nvidia even though performance wise it wouldn’t be necessary.

I am aware, but check the referenced issues. Support has been merged like a year ago and at least gnome on Wayland should work out of the box. It’s incomplete, but it should be working

Also barrier is considered abandoned at this point the previous maintainers forked it which actually is leap input.

Check the input leap project. While I haven’t tested it myself, Wayland support got added like a year ago. You still needed to rebuild some packages, but reading the issue tracker now it seems to have gone a long way.

Unfortunately it is still not considered production ready. At this point I assume they will have it implemented and ready way before synergy though.

Sounds like you don’t clean your package cache. You can enable the paccache.timer to handle it for you on a weekly basis.

https://wiki.archlinux.org/title/pacman#Cleaning_the_package_cache

There was or is a bug with WebKit when using Nvidia. If that’s the case remove the Nvidia driver and use nouveau instead. After logging in you can reinstall the Nvidia driver again.

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2498

You are actually correct. I just checked the manifest of RHEL and it provides vim-minimal and not vi like I assumed.

I noticed that it behaves a bit different than the version available on AIX for example which for sure uses real vi, but I never gave it a second thought. Interesting.

No. If you have vim installed that’s true on many (some?) systems. As I said some distros have vi available, but not vim which is the annoying part.

There is not really anything to learn. It is just lacking some useful features and shortcuts which make it slower to use. It’s still much better than nothing.

Usually my biggest issue is that I am so used to write vim over vi. At least for small edits.

I am surprised that vi is often available, but not vim. It’s really annoying on many RHEL based distros, because I am so used to typing vim. Otherwise there is just git I deem essential.

Personally I didn’t like Deepin and I didn’t really use it for long so I can’t say much about it. Anyway, it is part of the the extra repositories of Arch, so you can expect a current and maintained version.

It should be the same for other Arch based distros. Just stay clear of Manjaro. It should not be used by anyone.

Yea, no. It doesn’t work with ssh agent and it cannot read includes and other configuration options. I believe it also tries to install some components remotely which is bad enough, but causes additional issues in environments with proxies or without internet access at all. Iirc also plugins must be installed remotely to work.

In a normal professional context it just does not work and it is a hassle to deal with. It might work in a home lab, but nowhere beyond that.

In general it is safe to install as many DEs as you want. There is some overlap between (user) configuration files though which might be annoying.

It should be fine to experiment, but you might need to restore some settings afterwards. For daily use I would just stick to one DE. Personally I don’t think there is really a reason to use multiple DEs as a single user. It would throw me off and mess with my workflow.

Also keep in mind that many DE also provide a set of default tools which add clutter. So you probably want to keep it low for this reason alone.

Ausgewogene Makros ist Unsinn. Proteine und Fette braucht der Körper, Kohlenhydrate nicht wirklich (doch, aber die kann der Körper selbst aus Fett produzieren). Eine gesunde Ernährung kann einfach die Nudeln, Reis und Kartoffeln mit Brokkoli, Blumenkohl, Erbsen etc ersetzen, sogar in größeren Mengen. Plötzlich hast du genug Kalorien gespart, dass du noch eine Tüte Gummibärchen naschen könntest oder eben nicht, wenn du abnehmen willst.

In den Kohlenhydraten stecken die Kalorien, auf die anderen beiden Makros kann man halt nicht verzichten. Daher ist Low carb vermutlich die einzige brauchbare Diät neben einfach weniger essen. Von beiden gibt es diverse Varianten, aber alles außerhalb davon ist eigentlich immer Unsinn oder sogar gefährlich.

I would put shell scripting basics higher up on the list as part of the introduction to cli, because that’s one of the major benefits over using a gui.

Otherwise it looks really good, maybe sprinkle some vi(m) in there, because it is the defacto default editor outside of Ubuntu and few others.

Also maybe focus more on iptools2 over the legacy commands like ifconfig, netstat etc as they are not available everywhere anymore (use ip or ss instead). It is still very useful to know both though.

Finally you should pay close attention to anti patterns like “sudo su”, “ps aux | grep …”, “cat … | grep …” etc and make sure to teach proper usage of the tools. I have seen it way too often done wrong in beginner guides.