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.

Hu, that was weird. Kinda cool animation though. Maybe it’s a new channel to binge. Thanks!

The problem is always having the bad option being enabled by default. Not even the ads are the biggest problem. I didn’t even mention their current ads in the terminal. The problem is the same Microsoft is having now, that your keyboard input gets sent to an untrustworthy third party.

Your comment got cut off. If you wanted to dispute the paid paid claim. It is about Ubuntu Pro, that’s literally all what the basic tier is. We recently even had the case where a patch with a highish CVE rating was only available to subscribers of the service. We also verified that the same patch was already available on Debian. Even without my anecdote it should be obvious why it is bad.

Emphasis on it was. It started to go downhill with Amazon integration and now we have paid security updates. They are holding back developed and available security packages for their OS!

There is no way to still recommend Ubuntu. No need to even talk about the other questionable decisions like snap.

It is a race between mayo and mustard. Having to pick one I’d prefer mustard.

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!

sudo is not simply a tool to give admin privileges, but a tool to manage elevated permissions or run commands in a different users context.

These things become a lot more relevant once you use the tools professionally. In a well configured system you are only allowed to run the things you are explicitly allowed.

To be completely honest sudo is basically pointless in a single user context. There is almost no reason to even have it installed. It makes dealing with different environments easier though.

Anyway as I said it does not matter in many cases if you are the systems administrator. On the other hand there is also no benefit in getting used to bad practices in case you have to unlearn them later.

One more thing: what you suggest with chroot is one of the very reasons why you should not do that. You might have handed over the keys to break out of chroot. It is a well known vector which boils down to never run anything as root in a chroot environment.

sudoedit opens the editor as your user and just writes the file as root. For a single user who is also admin on the system this does not matter in many cases.

In a multi user context you can easily escape your editor and run a shell which allows a non admin user to escalate their privileges. So from a security implementation standpoint this must exist and it does for this reason.

Of course this also prevents some mistakes from happening and a bad plugin cannot destroy your whole system easily and so on. It boils down to good practice.

Arch Linux and Cinnamon.

I like it simple without being too opinionated like some other DEs. I am eagerly awaiting Wayland support though

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.

Yea, kinda. It forces it hard though.

There is no obvious way to skip the MS account. You can select that it is a managed device and create a local user that way, but afaik that’s the last option left and obviously it is there for a very different intention.

I am sure that if MS could remove it completely they would.

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.

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