As others have mentionned downloading the .deb and running it will also work, but I feel nobody gave your a tldr of why you may want to follow those instructions instead, so here it is:
Those instructions configure your package manager (apt) with a new repository for this application.
The upside to that is that anytime you will look for updates, this app will also get updated.
It’s a bit more work up front, but it can pay off when you have dozens of app updating as part of normal system operations.
Imagine a world where windows updates would also update all your software, that’s what this is.
Also, no, this is not an ideal way to do this. Ideally every package you want is in your distro’s repos so you’d just need to do “apt install [package]”.
The reason this one isn’t is because mullvad wants to make sure you use their tested, secure, and updated version and they don’t want to maintain that for every distro. So they have you configure your package manager to use their repos.
This is relatively uncommon to come across in Debian. You’ll normally only find it in security applications or very niche ones. The Debian repos aren’t the most comprehensive but they’ll contain the vast majority of common softwares.
No, hibernation saves state to disk, and turns the computer off, drawing no power. Deep sleep is what was for me just sleep until recently: it uses power to keep data in ram, so it’s faster to wake up than hibernation. The amount of power used is really small, so unless you don’t use your lap top for a couple of days, it won’t deplete the battery. New hardware has this new “S2 Idle” state, that is basically an “On” state minus the screen and it’s OS’s job to try to use as little power as possible usually by telling each and every device to chill as much as possible (this is my understanding, but don’t quote me on this). On Windows, with the first party device drivers, this sorta works OK + OS drops to deep sleep or hibernation depending on battery or something.
I was trying to do that but I’m unsure what to edit to do that, since most tutorials are using either a Debian based or Arch distro.
I was using a similar guide, and it also talked about the locale.gen, but that file was never to be found, I just searched a bit more into that and this popped up. So it seems Fedora handles things differently, but now I’m unsure what commands to execute since I’m not sure the ones in that thread are also valid for me.
Yeah, it really isn’t for everyone. The advantagees it provides is mostly for developers and companies. If you’re a company, managing a NixOS fork is useful, so all users of the system are on the same page always.
Otherwise the package manager itself can be used on its own. It’s neat being able to use packages from basically any distro without even needing to use a VM.
Nix is daunting indeed, but cool for those who want such tooling
This is a lot to take in; it’s basically an overview of all the interesting features of Nix. When starting out, you don’t need this kind of in-depth knowledge. I personally gathered most of what was covered here in over 6-12months of using it and I did just fine.
It might still not be for you but don’t take this as the reference point.
“You’ÏÏ never yay again.”
Sorry that all I can do is let the air out a bit op. Hopefully someone will swoop in to teach us both something before too long.
I was using a similar guide, and it also talked about the locale.gen, but that file was never to be found, I just searched a bit more into that and this popped up. So it seems Fedora handles things differently, but now I’m unsure what commands to execute since I’m not sure the ones in that thread are also valid for me.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.