Prefer using Wayland over Xorg. Xorg’s design predates modern security practices and is considered insecure by many. For example, Xorg applications may record keystrokes while inactive.
If you must run Xorg, it is recommended to avoid running it as root. Within Wayland, the Xwayland compatibility layer will automatically use rootless Xorg.
I don’t use awesomewm anymore, but used to. I am wondering if maybe it wouldn’t make sense to have a tiling wm community instead for content reasons. Could split out an awesomewm one later when there’s more lemmy users?
Just an idea. (also, I wouldn’t mind the space to talk about i3)
To be honest I’ve argued the exact same in many parts where people have suggested having individual communities which would split larger ones. Lounge hangers suggesting one per game. Or anime fans wanting one per anime.
So I kinda agree. Except this one time! 😜
Cos I like Awesome and wanted a chance to promote it to people.
Cos I’m full of optimism that Lemmy will explode in success such that we’ll need an individual AwesomeWM community pretty soon.
So I’m maybe a tiny bit hypocritical. But I prefer the term “hopeful”.
If you have any ideas, wanna help out, have any questions about Awesome, whatever! Reply or gimme a shout!
I am using Borg for years. So far, the tool has not let me down. I store the backups on external hard drives that are only used for backups. In addition, I save really important data at rsync.net and at Hetzer in a storage box. Which is not a problem because Borg automatically encrypts locally and for decryption in my case you need a password and a key file.
Generally speaking, you should always test whether you can restore data from a backup. No matter which tool you use. Only then you have a real backup. And an up-to-date backup should always additionally be stored off-site (cloud, at a friend’s or relative’s house, etc.). Because if the house burns down, the external hard drive with the backups next to the computer is not much use.
By the way, I would advise against using just rsync because, as the name suggests, rsync only synchronizes, so you don’t have multiple versions of a file. Which can be useful if you only notice later that a file has become defective at some point.
More/better atomic distros, like Silverblue, Kinoite, VanillaOS, etc. Silverblue is already excellent, easy to use and extremely solid, but there are still some odd rough edges that I think would make it less appealing to new users. When we can offer newbies a personally unbreakable Linux system that does basically everything they want and more, then I think it'll be easy to recommend. At this point it's hard to imagine going back to a traditionally updated distro.
The next steps for PipeWire, which has improved and streamlined audio (and sometimes video) handling and production immensely. I can imagine a future where we can easily send, audio, video, midi, and all kinds of other data streams between arbitrary programs on Linux, easily routing things with GUI frontends, having connections establish automatically, etc. I don't know how much this stuff is in the works, but I think PipeWire has a ton of potential left to be explored.
I’m a happy user of Fedora workstation. What makes Silverblue better? I’ve never tried it. I’ve done lots of changes but my system has been rock solid since Fedora 36.
I was on Fedora workstation before switching to Silverblue and they're both quite solid, to be fair. The big feature that differentiates Silverblue is immutability--you can't easily make changes to the base system.
Now, to some people I think that's going to sound awful, but it has its pros and cons. The biggest benefit being that your base system is solid (and not just solid as in unlikely to break, but literally unchanging over time). Updating your system is effectively replacing it with a different system entirely (delta compressed, so it's not too inefficient, if I understand correctly), and you can rollback/revert/swap between systems on the fly, in the unlikely event that an update makes something worse, though I haven't needed to. You can even rebase your Silverblue (Gnome) system into a Kinoite (KDE Plasma) system, pin both "commits" and swap between them. I haven't tried that though, since I'm pretty happy with the Gnome workflow. Long story short, immutable distros like Silverblue are basically as solid as solid can be.
There are two drawbacks that I can think of, and then a couple of minor nitpicks. The biggest being that you need to restart your system after making changes or installing packages. You don't need to restart between each package install or anything, but any system-level changes that you make won't take effect until you restart. The second drawback is that layering packages is not always ideal and working inside docker/podman containers (often via toolbx/distrobox) is the best way to do some tasks. For example, if you're a programmer and need to install a lot of dependencies to build some program, I find it's best to create a "pet container" to work in. That doesn't both me much though, in fact I kind of like that workflow.
So basically, it's probably not for everyone, especially people who really love to tinker and customizes everything. But if you want a basically unbreakable Linux machine, it's worth looking into.
Thanks much for the detailed reply. It’s obviously not for me since I do a lot of tinkering and I’m used to the traditional system. But it definitely should be suitable for some scenarios. Scools and kiosks come to mind.
The base os is immutable, but you can still change configuration files, compile and install local software (but not in the immutable directories), install desktop environment extensions, add custom repositories, etc. You can also layer packages, but most graphical software is best installed as flatpaks (but not mandatory). So it depends on what tinkering means for you. If it means messing around with binaries in the default locations, like /usr/bin, then it’s not for you, but for many other things there is a way, it’s just a matter of getting used to the separation between the immutable base layer and the things that you build around and on top of it.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.