unix-and-linux-sysadmin-notes
daemon
| unix-and-linux-sysadmin-notes | daemon | |
|---|---|---|
| 5 | 2 | |
| 459 | 18 | |
| 11.1% | - | |
| 7.5 | 6.6 | |
| 5 months ago | about 2 years ago | |
| Shell | C | |
| - | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unix-and-linux-sysadmin-notes
daemon
-
Funtoo Linux is shutting down
While it sounds great that it's finally getting some much-needed love, I'm not sure I'm a huge fan of "we need to have everything systemd has". It's good to be opinionated and come up with solutions of your own. Systems work fine without systemd's entire featureset, and it's not openrc's job to be compatible.
Out of those you listed, I only think readiness notifications are necessary for the existing OpenRC featureset to work more reliably. I'd rather enshrine a different method of doing user services (for example[1]) instead of having openrc require elogind to take over user session tracking, and I'm not a huge fan of socket activation bloating up the amount of running processes the longer the machine runs, outside of the user's control.
[1]: https://github.com/raforg/daemon/
-
Systemd: The Good Parts
> You mean Slackware users on some random forum.
Believe it or not, that's actually the official slackware forum. And whatever solution those guys come up with, it will likely become the official solution.
> Besides, the solution they came up with uses XDG autostart which has nothing to do with systemd.
The slackware solution involves a project that nobody has heard of before, just so it can imitate the "user-level service" feature provided by systemd: https://github.com/raforg/daemon
> Not to mention that it's not even doing the exact same thing as the Gentoo solution and running two more commands in addition to pipewire.
The slackware solution requires starting those 3 processes (pipewire, pipewire-media-session, pipewire-pulse) separately from 3 different .desktop files, likely because the daemon tool above can't properly reap the pipewire-pulse process (not sure whose fault is this though).
On the other hand, the gentoo solution can start all 3 processes with just 1 .desktop files, because `pkill` takes care of it. Simple and effective.
I think the key difference, in this case, is that the slackware guys are trying their best to imitate a systemd feature, while the gentoo guys seem to focus more on finding the best way to allow users to enjoy pipewire.
What are some alternatives?
ipset-country - Block countries using iptables + ipset + ipdeny.com
openssh-portable - Portable OpenSSH
ansible-mfsbsd-install-via-linux-lite - MfsBSD. Installing and booting MfsBSD from running Linux, via grub.
rapiddisk - An Advanced Linux RAM Drive and Caching kernel modules. Dynamically allocate RAM as block devices. Use them as stand alone drives or even map them as caching nodes to slower local disk drives. Access those volumes locally or export them across an NVMe Target network. Manage it all from a web API.
LinuxMirrors - GNU/Linux 更换系统软件源脚本及 Docker 安装与换源脚本
stress-ng - This is the stress-ng upstream project git repository. stress-ng will stress test a computer system in various selectable ways. It was designed to exercise various physical subsystems of a computer as well as the various operating system kernel interfaces.