Lup Yuen Lee 李立源 @lupyuen@qoto.org

@lupyuen
Ok, that is cool. Thanks for explaining it to me. Does it still run in a similar frequency range to wifi, ie 2.4-5.6ghz? I'm just thinking about if using it could also reduce interference with wifi devices...

@lupyuen
It does, thanks... and the benefit of using it over the more established wifi protocol/ networks is...?

@lupyuen
I still don't quite get what #LoRaWAN is. It sort of sounds like a wifi based LAN over a larger distance, that doesn't take as much power, but I have a feeling I'm probably way off.

@lupyuen @mzan You can still use a syslog daemon a daemontools or anything else beside journalctl on the same host or use a daemon other host via rsyslog. Systemd doesn't forbid to use other tools if you prefer in some specific cases. But it also allow a lot of things that couldn't be easily made with former system management, including user side daemon management, memorize the state (enable/disable) of a deamon, independently of the current usage (start/stop). There is an homogeneous syntax for services now, and lot of possible, prebuild dependencies/limits/notification parameters : man systemd.service
On ArchLinux, it take 24.3MB installed, that is a bit too big, for some architectures.

@lupyuen Swapfiles are always going to be less likely to work than swap partitions because there's so much more code involved due to the filesystem being in between the vm subsystem and the storage device.

Personally, I run my systems with no swap at all. But almost every computer I own has the maximum amount of ram possible installed.

@rgegriff @lupyuen
my first Mastodon post 🙂 ...

Systemd can introduce problems, because it tries to integrate a lot of different services that were distinct and customizable in the past. I think to logginng for example: with Systemd you have integrated logging. But if you have a very big server, generating a lot of logs, it is difficult to customize the Systemd default logging system, while before Systemd you had a lot of different options from which choose.

Before Systemd, the service specification was less elegant, but Linux administrators were in full control, because they can swap parts. With Systemd they had to accept the choices of Systemd, and in some usage scenario, when they need to swap parts, it is not configurable/customizable enough.

It is a complete change of philosophy for Unx, because in Unix usually you assume to being in control of the details of the system, when you need this.

@lupyuen I only learned of the existence of Apache Arrow yesterday, but might it have a role to play here?