swuniq
sysbox
Our great sponsors
swuniq | sysbox | |
---|---|---|
1 | 9 | |
5 | 206 | |
- | - | |
0.0 | 4.8 | |
about 2 years ago | 8 months ago | |
C | Go | |
MIT License | 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.
swuniq
-
Ask HN: Tools you have made for yourself?
https://github.com/mterron/swuniq
Like uniq but works on unsorted input to be used as a pipe filter with constant memory usage.
Feels like this should exist before I made it but all the options that I could find had unbounded memory requirements. I use it in long running pipelines all the time.
sysbox
-
OpenBSD cron(8) now supports random ranges with steps
Yes, I first learned this and the name "splay" from CFengine, back in the day.
I put together a small busybox-like collection of sysadmin tools, and one of the subcommands is "splay" to sleep for a random amount of time. It's one of those things that is useful surprisingly often, even outside cron.
-
The Rust Implementation of GNU Coreutils Is Becoming Remarkably Robust
I remember in 1999 there was a project to reimplement a bunch of these tools in perl:
I even contributed a little, back then. I guess writing basic versions of "ls", for example, is trivial. But there's a lot of work getting all the tools done, with all the flags implemented and behaving as expected.
I guess there are tools like busybox, toybox, and similar, which also implement a lot of "stuff" to varying degrees of completion. From my side the biggest takeaway from those projects is the sheer convenience of deploying a single binary and installing symlinks to change functionality.
I replicated something similar with my sysbox project, collecting tools together in one golang binary with various subcommands:
I use at least one of those tools on a daily basis, though I suspect they're not so universally useful.
-
Operating Systems
If you've got perl installed you'll might have a "GET" binary present, mine is /usr/bin/GET, which comes with the WWW-module.
Although this is written in portable perl, rather than being compiled, so the static vs. dynamic choice doesn't really mean much it is a simple alternative.
Otherwise I built a simple busybox-inspired collection of tools, written in golang, which includes a simple HTTP client too:
Those are just a couple of examples, I'm certain there are multiple other choices out there. But I guess curl is ubiquitous enough that most people just use it directly, and add it when missing!
- sysbox: sysadmin/scripting utilities, distributed as a single binary
- Show HN: A collection of sysadmin utilities, in a single binary
-
M4 – the one true templating language
That's pretty cool.
I wrote something similar in my static collection of sysadmin tools - https://github.com/skx/sysbox - In my simple pre-processor I only allow two special things:
#include "file/goes/here"
-
Ask HN: Tools you have made for yourself?
I bundled together a small collection of sysadmin/scripting-tools here:
Those are probably amongst the things that I use most often which are non-standard.
-
Sd: My Script Directory
I used to have very full ~/bin, and ~/$(hostname), directories. In the end I pared them back and started bundling things together in one binary.
The end result is very similar to this approach, I run "sysbox blah", or "sysbox help", and use integrated subcommands.
Very helpful and makes deployment easy by having only a single binary:
Not bash/shell, but similar and useful idea to experiment with.
-
New Cli Tool (Golang) for custom commands (input during the execution) and with REPL
I support that in my sysbox utility-box, via the subcommands processor, and it is very helpful.