Just be aware that some solutions like gocryptfs are provided on a user-space filesystem (Fuse). This has a very low performance and most importantly if you require inotify on the decrypted data for some application then it won’t be available. In short inotify is what allows apps to watch a filesystem for changes and act accordingly in real time.
If the risk of physical data theft is high, your data is at risk. If the risk of physical access to you machine is rather low, encryption might actually increases the risk of losing your data simply by the chance of losing the means to access your data (forgotten passphrase, lost hardware key…).
I essentially did the same. Used GNOME for almost 10 years, then got my first try of KDE last year and don’t plan on going back either. GNOME has some really good points, I wouldn’t have used it so long if it didn’t, but I can actually use an honest to goodness theme on my desktop and customize without having extensions break on every update. Also, the UI in GTK is just too big and chunky for me, it’s like every window is designed for tablets or something. I don’t need a title bar that’s practically an entire inch tall. If you like GNOME, awesome, I will likely never say GNOME is bad, but I’m a KDE guy now.
EDIT: apparently I need to specify that the “entire inch tall” comment is exaggeration, because internet. My point being that GNOME’s UI is too big for my tastes.
Yeeees, GTK looks awesome but I just cant see how apps like Plasma systemsessings, qBittorrent etc using Qt could work like that.
Gimp 3 alpha is pretty crazy, as GTK2 was very nice and usable, but already with GTK3 everything got huge, so now the buttons dont fit as well anymore.
Also I have to say GNOME would have some big issues for me.
I dont want a top panel on a laptop, as it makes me look down more
docks are weird as they waste screen space. Why not use a normal panel, everything there, at the bottom or side?
not seeing all my open apps is weird, also not being able to open or close from the panel is weird
I and I guess 99% of Desktop users dont need virtual Desktops. As they dont change the panel and more, I dont even use Workspaces on Plasma
thus, normal window decorations are necessary
hitboxes need to be in the upper corner and not some padded thing in the center. Every decoration failing this (looking at you Firefox & Thunderbird) just sucks
UIs need to be compact when needed. Not everyone is a child and settings are not that simple.
Gnome has some nice apps like Loupe that are actually more secure. And it probably is way more stable. But KDE apps are so great, at least for usability! Could not live without Dolphin for example
Gimp 3 alpha is pretty crazy, as GTK2 was very nice and usable, but already with GTK3 everything got huge, so now the buttons dont fit as well anymore.
not seeing all my open apps is weird, also not being able to open or close from the panel is weird
The extensions that enable this are so simple too. Its a real shame its not built into the settings out of the box, even if they want that to be the default. I wish they made extensions more discoverable too, since you kinda need to know they exist in order to go get them, and easier discoverability would help people solve tbose problems faster.
UIs need to be compact when needed. Not everyone is a child and settings are not that simple.
I really wish these things were built in settings. Thunderbird Supernova’s setting for this is a fantastic example of how much of a difference it makes. Yeah, it’s a bit spacious by default. But once you drop the spacing to medium or small based on your needs and dpi, it feels great. Opinionated design done well makes for great consistency and feel, but it also needs to have some room for adjustments without needing to install stuff.
Agree, if they had the flatpak extensionmanager installed by default that would be cool. But dash to panel is still much worse, way less tray icons fit there, the app menu may be inconsistent.
Also I have to say that the complete lack of .desktop entry modification makes distinguishing flatpaks from native apps, or creating entries with slightly changed parameters, appending arguments like “force X11” etc. very hard.
Nautilus may be solid but it lacks so many features and I still dont know how to deal with it. If you know how to add a real “delete” entry that would be great.
I also think the traditional decorations extension is gone? But I dont know.
Didnt know you could change the UI density, thats cool.
Gnome is great because of the large UI size. Like my 14" notebook has a roughly 2800x1600 screen resolution and it’s still pretty usable without any UI scaling. If the bars are an inch tall, you’re either using a huge TV or a screen from the garbage dump. Gnome really needs a modern system.
Puppy Linux: It’s a solid live boot environment but it’s not really ideal in comparison to the major distros on a permanent install.
Alpine Linux: Since it uses musl instead of glibc, you’re likely to run into problems
Linux from scratch: Going through LFS is a great way to get a solid understanding of Linux, but unless you want to spend more time maintaining your system than using it, it’s going to be a frustrating experience.
Try one of the distros others have suggested.
Edit: I checked the specs on that hardware and yeah that’s going to struggle. Maybe Alpine would be ok. It’s fairly easy to spin up and might be fun to play with on that hardware. You’ll probably want a fairly large swap if you’re planning on using a desktop environment.
In my experience, if you need to do Linux kind of things on a Windows computer, it’s far less glitchy, buggy and laden with weird caveats and edge cases than the alternatives (like Cygwin and Git Bash).
To be fair, I’ve never used it. But I’ve been the guy people come to when shit doesn’t work. Switching from Cygwin or Git Bash to WSL frequently fixes issues.
Okay, folks. NixOS needs your help. No bull. I’m talking documenters, designers, coders, package maintainers. Why? Because the NixOS community has a lot on it’s plate right now.
Like I can understand why flakes haven’t become standardised, why it’s still marked as unstable, even though it’s pretty much feature complete, and that’s because nix is a complex environment builder and the current contributes are taxed to the max.
But what is nix?
Nix’s job is to create reproducible environments where you can put any library, any service, any application. It does this through compile time flags and modifying ELF headers to isolate applications on a system to their own, exclusive UNIX path. These are linked together as clojures, or a dependency graphs, that can share libraries, applications and services intetchangably with each othet, or use another version or patched version without causing any dependency conflicts.
You can fire up pretty much whatever you want and it will be reproducible elsewhere. It’s like if you took a package manager, build environments, as well as VMs and micro services and make them kiss.
You can spin up a nix environment on any supported system and expect it to run 1:1. This however breeds complexity and there’s a lack of NixOS contributors.
If only you spin up a nix environment on a VM or use it to replace your current build systems (because nix can use several build systems in one single environment), and then contribute back with some changes to nixpkgs, then you are helping to bring about the most powerful deployment tool since kubernetes.
No joke. Check out how you can contribute, because at the end of the day learning nix is gaining a new superpower.
There is also AppImage Launcher which works nicely for me. It automatically integrates AppImages into the DE (e.g. search and start menu) and a few other nice things.
I’m new to NixOS. Do I have to do anything extra to update NixOS? Or do I just update my flake and run nixos-rebuild switch --flake like I normally do to update packages?
If using flakes you could just for instance add another input. You can also set the input URLs to specific states of the nixpkgs repository by eg referencing specific commits. Then, you should be able to just, e.g., pick Firefox from unstable, another package from the current stable channel, and maybe a broken package from a pull request fixing said package.
If you are not using flakes you can also add system wide channels. IIRC you can then import these channels into your configuration.nix and select packages from the corresponding channels. But here the channels/inputs are not part of configuration itself in contrast to when using flakes.
When not using flakes, nixos-rebuild switch --upgrade is equivalent to apt update; apt upgrade. The equivalent to dist-upgrade is nix-channel add $NEW-CHANNEL-URL nixos and then performing a regular update.
I’m a bit confused about what you actually want? Do you just want to update your packages, but stay on the same NixOS version? Just continue like before. Do you want to stay on your current version, but use some packages from the next version? That should also be possible if you somehow include that channel in your configuration.nix (though I don’t know how this would work in practice).
Personally, I just run with unstable though, then the releases aren’t that important.
I think unstable and the fixed versions use the same Firefox package, so you wouldn’t gain anything. The difference is rather in libraries that get used and how the distribution does things. For example, the changes listed in nixos.org/manual/nixos/stable/release-notes#sec-r… just appeared mostly one by one for me; one day, I wanted to update my system and got the error that the fonts option got renamed, so I had to change my configuration.
The fonts.fonts and fonts.enableDefaultFonts options have been renamed to fonts.packages and fonts.enableDefaultPackages respectively.
While when using a fixed point release, these changes won’t happen. Only when you switch releases. That’s what “unstable” refers to.
You need to update your inputs so that you’re using the 23.11 branch of nixpkgs instead of the old one. In my experience, a couple of things will break, but there’s usually warnings about it.
If you are using flakes you should check your flakes’ inputs (probably the one called nixpkgs) and then change the URL to match the channel for 23.11. Finally, you should of course rebuild your system.
Wayland is just a protocol. The WMs, compositors and applications need to implement the features the X server used to provide.
Those that don’t will become useless when X is gone.
Right so I guess I should have over specified that I hope ALL the other bits that actually make it function the same will also catch up and for example something as basic as forwarding GUI programs will simply work without jumping through a bunch of tedious flaming hoops with pitfalls on either side. It doesn’t really matter to me that Wayland has decided it’s somebody else problem.
For many uses, Wayland has feature parity now or is even the superior option. That is how it can be the default on so many systems ( including RHEL9 as per the article ).
Compositors that do not provide the features that uses want will fail to compete ( what you mean by become useless I assume ).
That said, different users will want different things and, unlike X, Wayland allows competing compositors to address different communities. Some compositors will lack features some users want while offering features that other users need. A composite targeting embedded use cases may not need multi-monitor or fractional scaling features for example. A security focussed option may think that global hot-keys and external lock-screens are anti-features. I think the Wayland world could be quite interesting.
Other than the way you installed the packages there’s nothing intrinsically arch on that wiki. I recommend you read the page and see if it helps before assuming it doesn’t because you’re using a different distro, arch wiki is great even if you don’t use arch.
Ah, sorry, your reply was 8 min after I sent the link which seemed awfully short to test the different approaches listed there, I assumed you hadn’t read it and just discarded for being a different distro. Sorry I couldn’t be more helpful.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.