Stuart Longland (VK4MSL)

192 Followers
576 Following
25 Posts

Back-up account for @stuartl in case my server goes down. If I follow you here, I will probably follow you on my home server as well.

Posts made here expire after 2 months.

Things nobody said in the 1980s...

Helicopter parent? Tiger mom?

#Cats #Kitten #Caturday

🇦🇺AUSTRALIA Weekly COVID Update: 10 April 2026

🔹SA: ⬇️(-29.8%)
🔹QLD: ⬇️(-20.8%) 64 in hospital
🔹NSW: ⬇️ (-7.7%)

🔹WA: No data last week; comparison not available. Avg 13/day in hospital

🔸TAS: Next update: 17 Apr
🔸VIC: Next update: 17 Apr

🔹Aged Care: The Australian government ended weekly COVID reporting

Worked out a handy way to deploy software to a PocketBeagle SBC today.

The USB port enumerates a CDC-ACM serial interface (console) and a CDC-Ethernet port, however by default, there's no route to the Internet. To connect it to the Internet, you must set your machine up as a router, and make it use your host as a default route.

Alternatively, you direct things to use a HTTP proxy. Like this:

https://proxypy.readthedocs.io/en/latest/

```
log.info("Sending deployment script")
os.system(
"scp deploy.sh [email protected]:/tmp"
)

# Send the deployment script over via SSH
with proxy.Proxy(port=0) as p:
log.info("Running deployment script")
os.system(
"ssh -R 8080:localhost:%d [email protected] bash -ex /tmp/deploy.sh" % p.flags.port
)
```

In the top of `deploy.sh`:

```
# Never sure whether things use upper or lower case here
export HTTP_PROXY="http://localhost:8080/"
export http_proxy="http://localhost:8080/"
export HTTPS_PROXY="http://localhost:8080/"
export https_proxy="http://localhost:8080/"
```

(Some applications use upper case, others use lower case.)

Now `apt-get`, `git` and friends, can pull files over HTTP/HTTPS via your proxy.

The same technique would work with the Raspberry Pi Zero family.

#Python #Proxy #BeagleBoard #RaspberryPi

Proxy.Py 2.4.11.dev3+gfec682b documentation

New comic: Name that Bellicose Babbler

#war #language #cartoon #uspol #quotes

And no, I don't know what a "mimsmatch" is either…

Still going… seeing a lot of messages like this:

```
ref mismatch on [35132342272 8192] extent item 1, found 0
data extent[35132342272, 8192] bytenr mimsmatch, extent item bytenr 35132342272 file item bytenr 0
data extent[35132342272, 8192] referencer count mismatch (root 256 owner 227508 offset 149012480) wanted 1 have 0
backpointer mismatch on [35132342272 8192]
owner ref check failed [35132342272 8192]
repair deleting extent record: key [35132342272,168,8192]
Repaired extent references for 35132342272
ref mismatch on [35132350464 8192] extent item 1, found 0
data extent[35132350464, 8192] bytenr mimsmatch, extent item bytenr 35132350464 file item bytenr 0
data extent[35132350464, 8192] referencer count mismatch (root 256 owner 227508 offset 149020672) wanted 1 have 0
backpointer mismatch on [35132350464 8192]
owner ref check failed [35132350464 8192]
repair deleting extent record: key [35132350464,168,8192]
Repaired extent references for 35132350464
```

Whatever `btrfs` did, it did a proper job of it.

10 hours later and `btrfsck --repair` still grinding away. Yes I took a snapshot of the disk before making changes.

Straße von Hormus
Strait of Hormuz

#Iran #Trump #NATO #cartoon #karikatur