Add new post. Multiple other uncommited changes.
This commit is contained in:
1 parent
aa7043fd1c
commit
3c2d8da31d
7 files changed
+56
-20
No files matched your search
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: "Bash has a builtin network client"
|
||||
author: "James Pace"
|
||||
date: "2024/01/12"
|
||||
---
|
||||
|
||||
I've been playing with using Rust on microcontrollers that have
|
||||
ethernet support with the microcontroller using UDP to communicate
|
||||
with the rest of the world.
|
||||
|
||||
When testing the code I wrote on the microcontroller, I searched for how to send
|
||||
udp packets from the command line (expecting to find the right incantation for
|
||||
netcat, which I've used in the past but don't remember the options for.)
|
||||
What I actually found was more interesting.
|
||||
|
||||
Apparently, bash has builtin "pseudo devices" that allow you to read and write
|
||||
from a TCP or UDP port like you were reading or writing from a file.
|
||||
For example, to send the string "hello" to my microcontroller at 192.168.1.109 on
|
||||
port 1337, I used the command
|
||||
```bash
|
||||
echo "hello" > /dev/udp/192.168.1.109/1337
|
||||
```
|
||||
|
||||
Bash supports the same thing for TCP connections as well using similar syntax.
|
||||
|
||||
That is a lot easier to remember than netcat, and I'll definitely use
|
||||
it again.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Quick Review of Just"
|
||||
title: "Just: A quick review"
|
||||
author: "James Pace"
|
||||
date: "2024/01/10"
|
||||
---
|
||||
@@ -24,6 +24,7 @@ test:
|
||||
the command `just test` will call `cargo test --features log` in the current terminal window.
|
||||
|
||||
Compared to `make`, `just`:
|
||||
|
||||
1. Eliminates the need for manual .PHONY target creation, saving you time and reducing
|
||||
clutter in Justfiles compared to Makefiles.
|
||||
2. Can be called below the directory the `Justfile` is in and still find the `Justfile`
|
||||
|
||||
@@ -0,0 +1,19 @@
|
||||
---
|
||||
title: "Summary of Free Self Hosted Git Options"
|
||||
author: "James Pace"
|
||||
date: "2024/01/12"
|
||||
draft: true
|
||||
---
|
||||
|
||||
<!--
|
||||
Why:
|
||||
1. All sorts of programming tools support git and using git for versioning.
|
||||
2. Expecially with gitops being a real thing.
|
||||
3. But we want to maintain control and be able to still operate completely offline.
|
||||
|
||||
Options:
|
||||
1. Gitea
|
||||
2. gitlab
|
||||
3. onedev
|
||||
4. gerrit
|
||||
-->
|
||||
Reference in new issue
Block a user