Looking forward tomorrow 3 days hackfest organized by @tbernard
The main topic is GNOME mobile, but I expect there will be lots of collateral topics such as camera, hardware enablement, adaptive apps, UX, platform APIs, interoperability, and coordination.
Well so far playing around with #VoidLinux on an old laptop I've #SwayWM up and running along with all my other stuff. I've built #Spotify from source without issue and just setup printing / scanning . Using #Runit for services is a doddle too no cumbersome #Systemd . Could :void: be about to replace #ArchLinux on my daily ?
I think I need more time just to make sure that it's really for me but the results so far are in favour of Void.
Hack of the day: keep the Emacs server running in the active login session
Prereqs for this hack being useful to you: (1) you use GNU Emacs; (2) you keep a single Emacs running in your session and use emacsclient to open files for editing in it; (3) you have Linux computers that use systemd on which you keep mul
I have always used systemd processes inside /etc/systemd/system/. But what are /lib/systemd/system/ processes for and should I still have processes under /etc/systemd/system/ for the same things? It seems if I remove mastodon-web etc. under /etc/systemd/system/ everything goes awry. Yes, daemon-reload has been run and processes are in place. Can someone explain this bit to me? #MastoAdmin#SysAdmin#Linux
HOSIANNA! Ich habe #systemd besiegt 💪 Nachdem systemd ja frechweg das (dokumentierte) Flag "keyscript" in /etc/crypttab ignoriert, musste eine eigene Lösung her. Die Idee "ein systemd-Service, der das Schlüsselmaterial bereitstellt", war an sich richtig - das Skript zur richtigen Zeit ausführen zu lassen hingegen extremst tricky, es gibt nämlich kein Target das unmittelbar vor dem verschlüsselten Mounten liegt.
Dafür weiß ich jetzt, was Generators sind und woher die services für crypttab kommen
Have you ever noticed that there are certain directories everyone has? ~/Documents, ~/Downloads, ~/Desktop, and so forth? Some of them you don't need, some of them you might wish were named differently, but any time you rename or delete them, the originals reappear?
You see, these directories follow a standard so that all programs know where they are—with the right tools under your belt, you can customize them.
I mean, there's obviously things about Plan9 that you really like that differentiate it from everything else, so yes, I totally read your toot at face value.
Of course, that's coming from someone who's quite used to making impassioned proclamations and then walking them back (xref. anything I've ever said about #systemd -- not that I love it or anything, but I've had a wee bit of time to simmer down. XD )
If you're a user of WireGuard, Ansible, and systemd-networkd, you may be interested to know that I've just published version 2.0.0 of my 'ansible-systemd-network' roles collection. The addition in this version is a role to manage WireGuard tunnels 🙂
@twoolie@Natanox How about staying with the defaults and not fucking around?
Shit like this like the "Church of [#SystemD haters" aka. #Devuan] is why #Linux didn't already overtook the #Desktop and dominated it more than it does the #Server market.
People just want to shit work, and who besides a handful of people doesn't want to have the sane defaults?
But yeah, I guess this is why I'll stick with maintainable #LTS distros and would rather pay #RedHat cuz for the $$$$$ they cost they do sth.
I’d like to configure networking declarative (i.e. by writing to files, or at least by being able to run idempotent commands, meaning they shouldn’t fail or break anything when being run multiple times), and if possible without having to install additional software. Oh, and also, I’d like to rename my network interfaces based on their MAC address.
I’m a reasonably experienced admin, but new-ish to Fedora. Happy for any pointers & best practices. Thanks!
Okay. I have disabled NetworkManager, enabled #systemd-networkd instead (thanks for the idea @littlefox, seems to work!), written a .network file with IP configuration (which gets applied correctly) and a .link file to rename the device (which doesn’t).
Running SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/eno1 tells me that it sees my renaming rule, udevadm trigger -s net -v tells me that it triggers for eno1 – but no renaming happens. What am I missing?
Reading this Essay today makes me want a couple more featues in #illumos SMF. MacOSX is really a different beast of an OS with interesting capabilities all blocked because it is proprietary. #freebsd might had some looks into OSX too?
That's basically the idea, yes. If you've heard of #fbterm or the old #kmscon that used to be part of #systemd (but was quietly removed from it several years ago, with far less fanfare than when it was originally added) it's the same sort of idea, but structured significantly differently to and more flexibly than those two.