Maybe you want to migrate a PostgreSQL database to a newer version without starting PostgreSQL server.
Maybe you installed OpenSSH but don’t want sshd to run yet, because you haven’t hardened the configs.
Maybe you installed Nginx as a part of a migration from Apache httpd, but httpd is already running.
In addition, Arch hardly configures your system in a custom way, too. When you install a package, most of the time, it responds with “here are the files from the developer that you asked for.”
If you don’t like this philosophy, then your feelings are perfectly valid, and this is a textbook example of why different distributions exist 👍
This is one of the reasons why I am very unsure about the whole archinstall thing. On the one hand, it lowers the barrier of entry for less techy people, which is always good. On the other hand, it allows for installing the OS without ever having to use the archwiki, which leads to people making a blog post like this that could be solved by looking for “bluetooth” in the archwiki and following the instructions. To somebody not familiar with the OS, this makes it seem like arch is much more complicated than it actually is. “To run arch, you have to hope that there is a blog post or youtube video for simple things like bluetooth!”
No, you simply go here: wiki.archlinux.org(Also very useful resource if you are on any other distro btw)
What on Earth for. I don’t think I’ve used it more than a couple of times over the last 5 years, and that was for arcane stuff like enabling rc.local (which is something every user should probably not know about…)
Plex, CUPS (printing services), Minecraft servers, VPN, file sharing, DHCP/DNS/Wifi, bluetooth are some examples of basic level things systemd can help regular users manage.
Add screensavers or take X11 out of my cold, dead hands. I don’t use a CRT but still like screensaver since it prevents me from having to wait 5 years for my screen to turn on.
Wayland breaks global hotkeys: I present to you: Hyprland (where you can get global hotkeys). Now, it is normally not allowed by design, as a security measure
Not disagreeing at all, but I’d like to add some information here to support your correction
There’s a GlobalShortcuts portal ( flatpak.github.io/xdg-desktop-portal/docs/#gdbus-… ), and this is implemented for hyprland in xdg-desktop-portal-hyprland ( github.com/hyprwm/…/hyprland.portal#L3 )
So, technically, there is nothing in the wayland collection of protocols that supports global keyboard shortcuts, but (along with lots of other supporting functionality), this is addressed via the collection of portal APIs
Any desktop can provide an implementation of the GlobalShortcuts portal, and any app can adopt it as required (although if it’s implemented within popular toolkits/frameworks, then app developers won’t have to even think about it)
I’m pretty familiar with Linux server management, but haven’t ran Linux on the desktop in a very long time (I still remember the days of XFree86, which was the predecessor to X.org). If I install a mainstream desktop distro today (Ubuntu, Mint, whatever is popular now), does it come with X11 or Wayland out-of-the-box?
Depends on which DE in which version it is using, but anything with recent Gnome (Fedora, Ubuntu) will. Not sure if KDE distros generally default to it, and for more niche DEs the answer is probably “no”, unless it was explicitly made for Wayland.
Yeah, people are trying to make Wayland work so hard… Thanks to the open source community behind it but let’s be honest: Wayland is badly designed and coded.
After 10 years I can still not share my screen easily, always need to switch to X11.
Wayland are for little hobbyist kids who want to have fun with Linux, not people who need to do actual stuff.
If Wayland was doing half of the work it should be doing then we would adopt it. But it’s just bad software and brining all of Linux down with it.
Wayland is not poorly designed or coded, screensharing works perfectly as long as the apps properly support wayland.
That’s not a problem with waylands design or code, that’s a problem with apps design or code, the thing you may want to take issue with is the notion that we could change things like this while still being poorly supported generally.
What I do is use Claws Mail with POP3, it has an option that allows a message to only be deleted from the server after a configurable period of time. So if you set it for 10 days for example the message will exist both locally on your PC and on the server for 10 days, after which it will only exist on the PC.
It works pretty well in general. The only account giving me some trouble is Yahoo, which I suspect has some quirks, which occasionally cause the messages to be downloaded again and duplicated. Thankfully it’s easily fixed because Claws also has a feature to delete duplicates.
This approach is different from IMAP, which would maintain a local offline cache of the live inbox, but you wouldn’t be able to only keep local messages — any change in one side would be reflected in both.
However, Claws allows you to do both. You can have both a POP3 and an IMAP account connected to the same live box use the POP3 for offline archival, and the IMAP for when you want to put something back on the server, or if you need to look at other folders on the server besides inbox (POP3 cab only see the inbox, not trash, sent etc.)
Normally I only do folders locally on the PC, on the mailbox connected with POP3, so none of the organization is reflected on the live mailbox, which is inbox only. Every once in a while I connect via IMAP to recover emails from the sent folder, which I’ve sent with webmail or from mobile (using IMAP on mobile too).
If this doesn’t fit your workflow turn there are lots of IMAP syncing tools like you’ve noticed. IMAPsync is pretty good.
The last step for my workflow would be to self host an IMAP server that will index the POP3 mailbox, and expose it read-only (without SMTP) through a webmail app, for archival and search only. I may have to look at Piler. The quirk here is that the Claws mailbox format is slightly different from IMAP, it’s very similar to mbox but not identical, will have to see if any IMAP server will accept it.
Thunderbird is no go unfortunately, its main box format is to keep all messages on one big file instead of individual files, which complicates things a lot.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.