- seamless container logs (journalctl), no weird separate logger
- service start/stop/enable-at-boot no weird separate command
- integration with system/user slices, triggers, cronjobs (timers), exposing containers as first class commands overall!
Basically it's worth seeing container services work with non-container services.
If you don't like systemd, or have no stake in it, sure, have fun without it, but it's definitely added value when you're running services, and want to start containerizing some of them without abandoning all the good tools you are using in favour of docker logs docker run etc.
Podman has good systemd integration, in the form of quadlets.
It lets you define a systemd job with some custom syntax and run it as a systemd service, and even stretches to allow some form of kubernetes YAML to be run as local (single node, rootless) containers!
It's a protocol/tool for async file transfer, built for disconnected/intermittent connectivity amongst known parties (trusted friends as p2p), allowing even for sneakernet-based file transfer.
It's started as a modern take on usenet, but it boggles my mind how cool it is:
Want to send a TV Series to your friend? send it via nncp, and it will make it through either via line-based file transfer (when connection allows, pull or push, cronjob, etc), or even via sneakernet if there is "someone going that way".
Comms priority system lets you hi-prio message-checking via expensive network link vs bulk file transfer using trunk lines later.
It even can be configured to run arbitrary commands on message receive, to allow indexing/processing of files (like a ZFS-receive hook, mail/matrix ingestion...)
Anyone have a good introduction to Bluetooth ~4.0 + reasonable documentation ?
I've always loved bluetooth, the concept of P2P file exchange got me through high school[1] to think about all the levels of tech involved in making your music shared with someone else's phone, but very let down by the documentation and implementation aspect.
As a curious hacker who would like to decentralize his life, I've always wanted to start programming stuff over Bluetooth for any task (remove dependency on internet for purely-local services). But when I tried actually doing so, I was met with an incredibly complex ecosystem I couldn't find RFCs for (or Russian equivalent), with only Bluez as partial reference [2].
I got the impression that if you're not some deep pocketed company or are doing something with phones (preferably with IoT as key buzzword), you're not welcome to the Bluetooth(®) club.
[1] My first bluetooth headset, a Jabra BT620s, bought for 30€ online, is still functional (if a little beaten) after 14 years, delivering about 6 hours of music streaming before recharge. I had to use earbuds recently for a project, and got myself really crossed with the wires thing. How pampered I have been !
[2] At the time I was interested in using BTLE with a linux laptop that clearly supported it, and a flagship Nexus 5. I gave up when I realised at the time, Bluez had only command line tools to access the Low Energy stuff, and some guy had to reverse-engineer the binaries to access some level of API. I really hope this changed/changes.
- seamless container logs (journalctl), no weird separate logger
- service start/stop/enable-at-boot no weird separate command
- integration with system/user slices, triggers, cronjobs (timers), exposing containers as first class commands overall!
Basically it's worth seeing container services work with non-container services.
If you don't like systemd, or have no stake in it, sure, have fun without it, but it's definitely added value when you're running services, and want to start containerizing some of them without abandoning all the good tools you are using in favour of docker logs docker run etc.