this post was submitted on 13 Oct 2023
690 points (92.8% liked)

Memes

45753 readers
2418 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 

Meme transcription: Anakin & Padme

[Panel 1] Anakin tries selects “Update and shut down” from the Windows start menu.

[Panel 2] Padme, labeled as “Windows”, cheerily says: ”You mean ‘Update and restart’, right?”

[Panel 3] Anakin takes an annoyed look.

[Panel 4] Padme, still cheery, says “I’ll just ‘Update and Restart’.”

you are viewing a single comment's thread
view the rest of the comments
[–] Qvest 31 points 1 year ago (2 children)

One thing I give Linux credit for is how it handles updates. Like, yeah, Linux doesn't force updates, that we all know, but I like how at least in the GNOME desktop, there is no "Update and action" button, there is only the shutdown and restart buttons, where if I am to press either, the system will ask me if I want to install updates or not with a nice box to tick the option. Nowhere near as cluttered as it is in the picture.

[–] [email protected] 19 points 1 year ago (2 children)

On most distros you don't need to restart to update. Mint will just put an icon on the taskbar when updates are ready, and you can even tell it to just do it in the background. No restarts or shutdown warnings.

[–] [email protected] 7 points 1 year ago (2 children)

Don't kernel updates need a restart?

[–] [email protected] 14 points 1 year ago

Yeah but no work has to be done during the restart, it's just booting into the new kernel.

[–] [email protected] 4 points 1 year ago

Usually yes, but you'll never be forced or even nagged to restart. You could keep your computer going for months on the same kernel until you decide that it's time to reboot, at which point your computer will boot with the new kernel.

[–] Qvest 3 points 1 year ago (2 children)

Yeah. GNOME does this probably because it's safer and ensures that the packages are downloaded in full before applying updates in an environment that is less likely for something to go wrong (Although I particularly don't know how true this is)

[–] erev 6 points 1 year ago

I'm guessing it's moreso that Gnome likes to make changes that can break things like extensions, and they probably don't hot swap shell components. The biggest reason you need to restart after Linux updates is that certain things are only loaded during the boot process (i.e. the kernel, initramfs, some boot or filesystem options) and can't easily be reloaded while the system is running. But you update something like dnsmasq, you probably just need to restart the service. At worst you need to reload the systemd daemon for config changes to take. And if you're just updating binaries, unless it's something like PAM that can also be not fun to restart and is constantly running, you probably don't need to do very much.

[–] [email protected] 4 points 1 year ago

Firefox will occasionally act up if it's updated in the background while it's running. It detects this pretty quickly though and prompts you tobrestart thr browser when you open a new tab. That's just about the only app I've had issues with though.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (5 children)

I’ve been looking at mint but I’ve been using windows all my life. I’m worried about the steep learning curve and terminal “language”

Would a noob like me survive on linux for gaming?

[–] [email protected] 4 points 1 year ago

These days the learning curve for Linux isn't all that steep; I've tricked people into thinking my Linux Mint machine was running "Windows 9." What you should expect are culture shocks. We're going to call things different names, some things are done differently. Where Windows has "shortcuts" Linux has "Links" (to files) and "Launchers" (to run programs). Same functionality, two concepts instead of one. We actually use our app store, but since everything in there is free we don't call it a "store," we call it a "package manager."

As for the 'terminal "language",' let's demystify this a bit. Yes, the Command Line Interface does consist of a more or less complete programming language with loops and conditionals and such, but all that isn't really necessary to use it as a basic user interface. It's actually pretty simple.

You type the name of a program, hit enter, and it runs that program.

Like if I want to open VLC from the terminal, I can just type vlc and hit enter.

There are some nuances to it but that's generally it.

For example, let's say I want to listen to the very hottest new track by my favorite band in VLC, and for some reason I want to use the terminal instead of clicking the mouse a bunch of times. I can type vlc /Music/don't_you_want_me_baby.mp3 into the terminal and VLC will open and immediately begin playing that track. But what if just one run of the song isn't enough? What if I want to hear the groundbreaking sound of The Human League over and over? I can add --repeat to the command as an option, and it will repeat the track endlessly. Options will either be one dash and one letter, or two dashes and a word. -R is the same as --repeat in this case. If you want to know what the options are for a given program, you can type [program name] --help. I used vlc --help to find out about the --repeat option.

That's mostly how you're going to use the terminal at first, by typing the name of the program you want to run, and maybe some options or arguments (--repeat is an option, the name of the file is an argument).

You can, of course, open up the file explorer to your Music folder and double click the file you want to hear, or launch VLC from the app menu and drag and drop the file, or click Open and deal with the dialog, the GUI exists for a reason. Where you're probably going to encounter the terminal early on in your Linux journey is when you're having some problems, and you ask for help on a forum or Lemmy community or something. The experienced Linux users who offer to help will ask you to run a terminal command and copy-paste its output. Because it's fast and easy for you to copy-paste the command I want you to run, and the text it spits out as output. Compared to "Right click on the task bar and click Properties, then go to Devices and click Driver Manager..."

As for whether a noob like you will survive on Linux for gaming: At this point it still depends on your taste in games, because especially competitive multiplayer shooters often exclude Linux on purpose because "something something anticheat." I play a lot of indie and small studio games, single player or cooperative multiplayer, stuff like Stardew Valley, Factorio, Subnautica, Unrailed. These work great, and to get up and running I have to do less on Linux than on Windows.

My recommendation: Download VirtualBox, download Linux Mint Cinnamon Edition, and run Linux in a virtual machine. Give it a try. You might like it.

[–] hinterlufer 4 points 1 year ago

Mint with Cinnamon is very Windows like from the UI. You probably won't need to touch the terminal for running steam games - there's a GUI for pretty much anything a normal user would need.

[–] [email protected] 2 points 1 year ago (1 children)

The learning curve is not as bad as it used to be. Almost everything can be done through the GUI, many tutorials exist, and steam will run almost any game without tinkering with it. ProtonDB is your friend.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Tell me about it… As a stem deck user, I’d fuck proton If could

[–] [email protected] 1 points 1 year ago

There will be things to learn and unlearn, but modern Linux distros are fairly smooth sailing for basic tasks if your hardware supports Linux well. Laptop support is a little more spotty, where there may be issues with suspend, or the Wi-Fi needing 3rd party drivers, but desktops will probably work without much fuss (and there are plenty of laptops with no issues).

Gaming has been made much easier thanks to wine and proton, particularly valve’s contributions. For steam games, many of them will just work out of the box or after ticking a checkbox. ProtonDB is invaluable for quickly seeing how well a game will run on Linux.

But as you’ll see as you read some of the reports on ProtonDB, there will likely be a more troubleshooting than you’re used to on windows. As long as you know how to Google the name of your distro + the problem you’re seeing, you’ll usually find a solution.

You don’t need to be a terminal master to use Linux nowadays. But most things are easier to explain with terminal commands than with step by step gui instructions, so many guides online will have you use the terminal to some degree.

Honestly, the best advice I can give is just try it. If you have a spare drive (internal or usb), just go ahead and install Linux to it. If you want to be extra sure you won’t do anything to your existing windows install, remove the windows drive first (or disable it in bios). Then play around with things and see how it feels.

[–] [email protected] 1 points 1 year ago (1 children)

Yes. Most things can be done without the terminal, and when it's required, 99% of the time you'll easily find a guide with instructions you can just copy/paste.

I wouldn't recommend it for my 78 year old mother who needs me to add her email account to her tablet, but anyone remotely computer-savvy can handle the transition.

The Linux community is generally very helpful and welcoming. If ever you can't figure something out, someone somewhere will probably be willing to help.

[–] ShadowCatEXE 1 points 1 year ago

Just be careful when copy/pasting commands. Especially when updating/removing packages.

I’ve shot myself in the foot a number of times where I’ve nuked my desktop environment from existence because deleting a package also deleted the entire environment. Definitely on me though, I didn’t read properly. So just keep an eye on what you’re doing, read what it’s updating and removing and the majority of the time you’ll be fine.