rapiddisk
daemon
Our great sponsors
| rapiddisk | daemon | |
|---|---|---|
| 4 | 1 | |
| 281 | 12 | |
| - | - | |
| 4.2 | 6.6 | |
| 11 days ago | 8 months ago | |
| C | C | |
| GNU General Public License v3.0 only | 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.
rapiddisk
-
How do I load RapidDisk --
I found that an alternative on Linux is RapidDisk. I installed it with no issues. However, I have to open terminal and enter a couple of commands manually to re-load the RAM drive as cache after boot, specifically:
-
PrimoCache equivalent for Linux (Ubuntu)?
Rapiddisk https://github.com/pkoutoupis/rapiddisk
- Using PrimoCache + 40GB RAM has reduced my SSD wear by 40% with mad max plotter
-
Plotting destination file system
As for ramdisk cache, what I was looking into is Primo Ramdisk which was mentioned a LOT around here, especially with high density plotting. Unfortunately that is only for Windows, but I found something similar for Linux: https://github.com/pkoutoupis/rapiddisk/ At this point I havent tried it, maybe indeed kernel module compiling will be enough, maybe not.
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?
chia-plotter
e1000e-dkms-debian - Intel e1000e ethernet adapter driver (DKMS version) for Debian
AnLinux-App - AnLinux allow you to run Linux on Android without root access.
DTLS-Examples - Examples for DTLS via SCTP and UDP using OpenSSL
wg-install - Wireguard auto-installer for Ubuntu, Debian, CentOS and Fedora
gentoo - [MIRROR] Official Gentoo ebuild repository
chiapos - Chia Proof of Space library
arcan - Arcan - [Display Server, Multimedia Framework, Game Engine] -> "Desktop Engine"
oksh - Portable OpenBSD ksh, based on the Public Domain Korn Shell (pdksh).
rpm-ostree - ⚛📦 Hybrid image/package system with atomic upgrades and package layering [Moved to: https://github.com/coreos/rpm-ostree]
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.