![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Ah, gotcha! Thank you for the explanation.
Ah, gotcha! Thank you for the explanation.
Aren’t all commercial plane turbine engines high bypass turbofans? (excluding turboprop)
Serious question, because I assumed that’s how they all worked, but this sounds like it is special or in spite of and it got me wondering.
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.
I think mixing horizontal and vertical is impractical, because it will mess up the whole layout once you resize a single window, but on one axis the concept is actually sound. There exists PaperWM for gnome 3 which is basically just this.
Isn’t it also super common in Mexican cuisine?
I love cumin and it is probably in my top 5 of most used spices in the kitchen. You would hate me!
Ben Duerr is one of my favorite metal vocalists! I didn’t know the song, but of course I had to check it out and I don’t regret it.
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.
Unfortunately it has a habit of jumping around due to its asynchronous weird fuzzy search. So when typing fast you sometimes randomly launch the wrong action. It is especially inconsistent, because files are also indexed and by default it also includes web searches so the behavior is always changing.
I believe this got introduced with Windows 10 and feels just bad. Unless you are typing slowly and actually scan the results the search is doing a bad job as an application launcher like it was with Windows 7 for example.
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
I almost forgot it existed. It was a slight improvement, but with a whole bunch of new problems (most notable race conditions which were never fixed) and it was made obsolete by systemd.
It was a good evolutionary step only used by Ubuntu iirc. It was better at that time than the previous init system, but not more than that and it never found wide adaption.
I used Linux (and some Unix) before systemd was a thing and init scripts are jank. So much boilerplate and that was before things like proper isolation existed and other more modern features.
I don’t understand why anyone would want that back.
A replacement of systemd with something else would be fine, but please no more init scripts and pointless run levels.
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.
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.