They don’t require an account (username/password) for you to use. You pay them for an account number and use Mullvad VPN by inputting it.
They were about to be raided but they managed to get out of that with their lawyers.
It’s also very easy to use on Linux because there’s a GUI, which is great. CLI seems overkill for an app that needs to be turned on and off (i.e. NordVPNJ my old VPN).
I honestly think CLI control is essential in any app. Because this is the most rudimentary and accessible way for other apps and scripts to interact with the apps features and control over the system.
My daily driver right now is an old Lenovo Ideapad (50-70 I think) with EndeavourOS, I have a few other assorted Thinkpads and Ideapads running mainly EOS or Arch, and home servers running Arch. I use Arch btw.
The “backup” laptops are flexible though, I distro-hop on them fairly often. Older Lenovos are usually great for Linux compatibility.
You don’t have to use an LTS version if you don’t want to stick to it… Also Fedora is on a yearly upgrade cycle too, just so you know, it’s not a rolling distro. You can actually upgrade sooner on Ubuntu because it’s on a 6-month upgrade cycle.
Fedora is on a six monthly cycle just like non-LTS Ubuntu; neither distro is on a yearly release cycle. The previous release is just supported for an extra six months, for one year of support per release for Fedora.
Fedora itself isn’t rolling but the kernel and mesa packages do roll between releases, and it is more bleeding edge than Ubuntu generally.
Alternatively, you can use you phone to USB-tether? Or if you’re on NixOS or Guix, where binaries stop working, you can build a custom ISO image with the necessarily tools already available.
Two more things that came to mind. If you want to use another desktop environment than gnome (default), you should be aware of spins: fedoraproject.org/spins/
Spins work against the same repositories, they just come with other sets of packages preinstalled.
Also, you said you’re using amd gpu. Fedora has the drivers for that out of the box. But due to fedora’s strict FOSS policy, some hardware acceleration features are stripped out of the amd driver. I mentioned you can get the unstripped drivers from rpmfusion. That is detailed here: rpmfusion.org/Howto/Multimedia
Those packages work together with the drivers from the official repos. They can get out of sync. That never happened to me, yet. But if an update mentions some conflict with mesa-*, just don’t do that update until that conflict disappears. If you ever run into the issue you can also undo the last update with the dnf history commands.
When I had no (useful) Internet where I was living a few years ago I would save a list of packages to download from Synaptic to a drive and then when I was somewhere I could I would download them, then when I got home I could plug in the drive and update/install them.
Are you leaving behind the dotfiles because you don’t want to bring over any of your old configuration?
For whatever it’s worth, you can remove Snap support from your Ubuntu system. If you want more current software, AppImage and Flatpaks are good for that.
Removing snap is somewhat unwise. Ignoring it is the safe way to go. Ubuntu might ship a system component you’re not aware of via snap. If you kill snap support you may end up with a broken system. To avoid headaches, simply ignore snap.
Zorin, Mint and Pop all are Ubuntu based distros that replace snaps with flatpak by default. I don’t know what would make any of those any more difficult than straight up Ubuntu. I’d even argue that most mainstream distros aren’t any harder to use than one another. Most of the differences between traditional distributions are behind the scenes: package manager, init system, default applications/configurations…
Even Arch, which has a reputation of being “hard”, isn’t particularly hard to use. It’s the lack of an installer that makes people freak out. The rest is just Linux. Once you plop in a GUI for package management and a proper desktop environment, from an end user perspective, nothing of it is inherently harder.
Solving problems is what becomes more difficult. There’s rarely issues with the happy path. The further away you move from mainline, the more components are different, the fewer of the solutions on askubuntu.com work by simply copy-pasting them. A novice user has no idea what the solutions do and why they don’t work. Instead they have to keep trying other copy-pasta hoping some would work. At best taking longer to solve it, and at worst some copy-pasta breaking something on their system.
Copy pasting random stuff from askubuntu is how you break your install in the first place. Novices don’t “have” to do that, they get told to do it by randoms on askubuntu that should not do that. Understanding an issue is key to fixing it, regardless of the problem’s nature.
I’ve yet to hit anything that worked on Ubuntu that didn’t on Mint. Hell, I find half of what I need on Arch Wiki even when not using Arch.
While you’re right, this expectation is unrealistic. Not only is it unrealistic for novice hobbyists, it’s unrealistic for people who use Linux to do other things, not for the sake of using Linux or learning its innards. For example my family members who use it for work an leisure. They couldn’t and won’t be bothered with learning how hibernation on Linux works. They want hibernate to work. The have me to make it work for them but folks who don’t will go to askubuntu.com, grab a well upvoted answer and copy-paste it straight into a terminal.
That’s what I mostly do now. But it requires some extra work, as some apps are not available in Ubuntu DEB repository. Also, I don’t like the approach that Canonical takes, pushing snaps so much
Well, my original plan was to copy configuration over after I install apos that are not available as flatpaks. Looks like I can copy configuration for those too, just to another location
Yeah, that should work. ldd “$(command -v “$cmd”)” will list the dynamic dependencies for $cmd, so you can find those (probably) in /lib and /usr/lib; I’m not familiar enough with the dynamic library loading process to give you the specifics. I would put the binaries in /usr/local/bin and the libraries in /usr/local/lib; but you could also modify path variables to point to the usb drive. Ideally you could find statically linked versions somewhere, so you don’t have to mess with the libraries.
Alternatively, most package managers have commands to download packages; then you can copy the package cache over to the new machine and install them that way. If the commands are common enough, you could download one of the bigger install media and add its package repo to your machine. These of course are distribution specific processes.
Finally, you could get a cheap USB ethernet adapter and connect to the internet that way. On newegg most of these products will have at least one review saying whether they work on linux.
I’ve never had this as an issue with KDE. Do you have the command for prime render offloading on the Steam launch options? I usually launch my games through Lutris and it handles that pretty well.
Lol I’m going through the same thing, I’m choosing the distro that helps my needs, but I’m not sure how to use the vst bridge and wine for my audio plug ins.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.