The solution to this is to start your own instance and federate the other instances that you want to make sure you can always reach. This is a solved problem, really.

Those people aren’t great at thinking things through. They’re “idea people”.

No it shouldn’t.

Well considering I’ve been using it for 25 years and it literally has had its own Wikipedia page since basically Wikipedia existed… no. It’s not a buzzword. It’s just a term used to describe an idea.

Why? This sounds like FUD.

Yes. Containers are awesome in that they let you use an application inside a sandbox, but beyond that you can deploy it anywhere.

If you’re in the sysadmin world you should not only embrace Docker but I’d recommend learning k8s, too, if you still enjoy those things.

Which is funny because I’m the other way around. I’ll try doing something with the CLI but if it’s like a calculation or something and I can’t figure it out with awk, etc, I’ll defer to a spreadsheet.

It would effect any UEFI based system regardless of OS from one of the affected manufacturers (which is basically all of them).

Correct.

Just sit them down with it. Kids can figure new technology out.

For anyone doing this, set up your spending and budget alerts and actions. It’s possible to accidentally fuck something up and end up with an aws bill that’ll suck, but this will give you some measure of protection from that in case you accidentally misconfigure something.

Note: Create your partitions from your empty space. You may need to resize your existing partition to do this. But don’t practice on your main drive.

This is a simple job, in that the steps are few, but it’s something that causes catastrophic data loss if you get it wrong.

I’d recommend buying a cheap second drive, doesn’t have to be big or even good. Partition it, mount it, make sure you can make the partitions automatically mount, teach yourself to copy data around, umount it and remount, make sure you got it right.

Just… these are all very simple things. I wouldn’t hesitate to repartition my own drives. But if you fuck it up you fuck it up good. Make sure you know the operations you’re taking first. Measure twice, cut once, all that jazz.

Boot from a live distro so you can modify your boot disk. Use the disk utility to create partitions. Copy the data to the relevant partitions ensuring to maintain file ownership and permissions. Modify /etc/fstab to mount the partitions at the designated locations in the filesystem.

I don’t bother putting anything but /home on its own dedicated partition, but if you ask 10 people this question you’ll get 12 opinions, so just do what feels right.

Actually just saw btop mentioned on Lemmy the other day lol

htop and/or btop are more modern user friendly alternatives to the classic top

You might check out xfce. It’s gtk like Gnome but the development team doesn’t have their heads up their asses; pretty much every aspect of xfce can be customized. It should be a simple install from your package manager, whatever distribution you’re using. The downside of this, however, is it might take extensive tweaking to get it to look how you want as it’s a pretty bare bones UI by default. Personally I like it, but ymmv.

That’s the beautiful thing about the Linux world. If you don’t like some aspect there’s virtually always an alternative.

You’ll thank yourself for it later. Things like this take a little longer up front but putting them off has a way of making you have to work around it again and again until, when you get around to correcting it, it takes far more time to undo the workarounds than it would’ve taken to correct it the first time.

I don’t think you understand what root is. By definition it has those permissions because it’s root.

If a different user doesn’t exist then you obviously can’t run the command as that different user. The only solution here is to create a new user account.

Also your image is improperly configured which is something you should fix first.

Because I also want to poop.