I’m using a Dell Inspiron 2in1 and from the linux side everything runs great. In the three years I have this laptop I tried multiple distros and all worked fine. Besides that the biggest problem was to find a program to make handwritten notes. I really recommend Rnote as it has matured very well over this year and is the only option if you need an infinite canvas to draw on.
I can’t recommend you the hardware tho as it is really aweful. The trackpad gets stuck sometimes and does not come back up with the keyboard showing the same symptoms now, the aluminum chassis gets greasy really fast and the hinges aren’t the best either. Also you must use the cheapest version of all Dell pens because the screen is only compatible with that one pen.
Respectfully, I love how powerful KDE is but my god they can’t make things visually consistent to save their lives!
From inconsistent icons, to different KDE apps using wildly different design languages, to padding being inconsistent all throughout the DE and their apps, to fonts and their sizes kinda being all over the place
But at least a custom theme is trivial to install and solves most of it
Good looking out. I installed this and verified it’s working, but does this automatically start at start up? I can’t seem to get systemctl enable to work on it.
appimaged should create the everything itself in order for auto start to work after launching it once via ~/Applications/appimaged-*.AppImage
e.g. systemctl --user status appimaged.service says that the service is enabled for me.
(Maybe you were missing the –user flag?)
I would follow the installation instructions and if that does not work, the uninstall instructions in reverse to create the service yourself (probably with systemctl --user enable --now appimaged.service)
I just want kde on Wayland not to have blury font with fractional scaling. It’s just unusable. Once that’s fixed, I’m all set to use it as my daily driver.
Just your regular 27" 4k monitor. If I set it to 200%, everything is fine, but things are huge. I have to have it on 175%, and that makes the font very blurry. Also, any window decorations that are not default plasma get blurry, too. I’ve already posted about it in the kde instance and zamunda (a KDE dev) said it was fixed in plasma 6. So, I guess I’ll just wait it out.
Can’t watch the video rn so going to be THAT person who asks a question that may be answered in the video…
I have a remote server running PopOS! I use with the gnome DE, I use xrdp to connect to it, have done some hinting in past about ways to use Wayland instead but had no luck. Does this slow decom mean development for Wayland over rdp may be coming soon?
Linux only package manager that works across distros. It supports sandboxing via bubblewrap, but be cautious because by default most programs in Flathub are not as sandboxed as they should. You can host your own repository but it is heavily centralized towards Flathub, controlled by Red Hat, IBM.
Flatpak uses OSTree to distribute and deploy data. The repositories it uses are OSTree repositories and can be manipulated with the ostree utility. Installed runtimes and applications are OSTree checkouts.
AppImage
You’re basically packaging your program and every single dependency up to the C library. Linux only.
An AppImage is basically a self-mounting disk image that contains an application and everything the application needs to run on the target systems
Canonical’s take at flatpaks. They are quite similar, but snaps use AppArmor instead of bubblewrap and the server is proprietary, so an inferior option and should be avoided. The only “advantage” is that it’s used by default in Ubuntu.
Nix/Guix
multi distro package manager with reproducible builds support, more akin to a traditional package manager (eg apt)
Snappy and Flatpak talk about how they make library versions work better together and blabla and how they solve a lot of issues but that’s just a praetext, the real elephant in the room is that they are a big wink to proprietary software, they were designed for that, they just can’t say it so they focus on other things in their PR statements.
How Nix and Guix work is that they are traditional “package managers” as such the user or the distributor must have access to the source code to compile it into a package, the interesting difference is that it is capable of keeping library versions apart and will automatically share libraries if they are exactly the same. But packaging still occurs downstream, not upstream.
Snappy and Flatpak allow packaging to occur completely upstream at the developers side, which means they no longer have to cough up source code to whomever who will package. Which leads to an inferior solution to the user with far higher memory and storage consumption.
this one is something in between Nix and traditional package managers. It’s main advantage is that it works in other UNIX-like OSs, like FreeBSD, NetBSD, IllumOS as well as in Linux. The only not Linux specific option in this list (other than docker, which is not a package manager but a container)
Docker
I wouldn’t recommend this one, since it requires packaging a whole OS that creates a lot of overhead. And it can be tricky to use with GUI programs.
Overall, I think that Nix/Guix present the most advantages, with Pkgsrc being a less known close second and Flatpak being in the third position due to it’s relative popularity and overall advantages over snaps and docker. Docker might be decent option if it’s a program designed for servers, tho.
I’d also recommend that you add your program to the AUR, because even if it only works on Arch and Arch based distros, it’s incredibly easy to do and maintain as long as the building of your program doesn’t change drastically between versions.
I believe Pkgsrc compiles the program at install, so it’s native. But it’s been a long time since I used it, you might need to look into it.
And you’ll have a hard time finding a “native” package format, because distros have different libraries versions: arch libraries will be much more updated than Debian’s, so things might break trying to execute programs depending on those libraries. That’s why Flatpak, AppImages, Nix, etc bring their own libraries, because if they don’t, things will break.
They are native in the sense that they are Linux executables, but it’s true that they bring their own dependencies, but as I said, that’s necessary for cross distro support.
Nix allows you to download a binary of a proprietary package because every input is hashed. You may need to patch it to work with the correct paths, but these tools already exist.
If I would not get so many old computing devices that fulfill my needs (I don’t game on PC/Linux) I guess I’d buy one of those. I live in Switzerland and having a german company for support would be superior to me. And I heard that build quality should be great 😇 😂I guess I’d really like to have one, but as I said, for my needs, my macbookpro5,3 running arch does the job.
This is honestly why anyone and everyone should invest in at least a small UPS that can keep your PC powered for at least five minutes so in this kind of scenario you can cancel the update, shut down safely, and resume when the power is back.
Btrfs snapshots + Timeshift that is configured to run pre-update is great for this, though I cannot remember if Fedora’s layout is compatible with Timeshift’s expected configuration.
OP, If you really want to go 100% with this, something like NixOS (which is definitely an extreme investment) or an Atomic distro like Fedora Silverblue works very well for this.
As you mentioned, with Fedora the best alternatives are immutable spins. Updating means downloading a new base image, applying overlays and additional installations to it and on the next reboot you start from that image. You can configure it to keep as many previous versions as you need and boot into those directly on startup. Since you never change your current image once it’s built, you can’t break a known good system. You can only ever break your next version and in that case, just boot the previous.
I’ve created an Ansible playbook that configures a vanilla Kinoite the way I want it. No need to back up the system if I can recreate it with less than a megabyte of text files. Secrets are in my password vault, personal files are in my personal cloud and get synced to and from the laptop continuously. I would never go back to backing up system files as opposed to recreating it with a playbook. That seems so wasteful in hindsight.
the init is just a binary, the others systemd features are different programs from different binary, and you are not forced to use them, you can use only the init and don’t use the others, it’s not gonna affect security, systemd init is the most tested one
and you can’t, a lot of technology that make NixOS and others immutable distros works exists only because of systemd
and if others init system worked as well, the entire of the linux community would not have changed voluntarily nor indenpendently to it
What do you think of some day seeing a fork of nixOS that uses other init systems and works well? Or is it just me that likes this idea?
doubt, is too much work just to make a systemd alternative, without the reliability and support that systemd have, but i think it could be a fun hack
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.