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.

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.

It kinda is though. Iirc it received an interrupt it shouldn’t have received and doesn’t know how to resolve. It is not supposed to ignore it, but then the only other option is crashing at this point. Basically it continues in a dazed and confused state.

Of course the message could be clearer, but at least it also makes the message easily searchable.

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

Up to 355687428096000? That’s impressive!

That’s actually cool. I have to remember it next time I have to deal with html mail.

Now do html mail!

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.

None of the tools are really made for the most trivial use cases though. Although it doesn’t take much effort to set everything up in a simple project I would probably also skip most of it. But this discussion about tiny one off projects is kinda pointless as you don’t have many of the problems to solve anyway.

I implemented a reddit frontend (kiosk mode) a while back using only vanilla JS for fun, because a previous implementation by someone else broke. There was not really a point though as it wasn’t even simpler than using the proper tools. It was just for the hell of it, but nowhere close to a “real” project.

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.

And the simple answer is no. You can remove a layer here and there, but this is what the modern dev environment looks like.

I mean sure you can implement all that yourself and carry all the extra cognitive load, but it is not productive to even skip babel or so. There is no point, but the challenge.

Of course it is a bit more complicated to pick the right tools and you don’t have to use everything, but that’s a whole different discussion.

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.