Loading...

Tag trends are in beta. Feedback? Thoughts? Email me at [email protected]

We got hit by an alarmingly well-prepared phish spammer

Thoughts on having SSH allow password authentication from the Internet

The history and use of /etc/glob in early Unixes

There are different sorts of WireGuard setups with different difficulties

I think Go union type proposals should start with their objectives

A gotcha with importing ZFS pools and NFS exports on Linux

Good union types in Go would probably need types without a zero value

Some things that make languages easy (or not) to embed in Unix shell scripts (2022)

When power cycling your (x86) server isn't enough to recover it

The long (after)life of some of our old fileserver hardware

Maybe we should explicitly schedule rebooting our fleet every so often

Buffered IO in Unix before V7 introduced stdio

We have an unusual concern when we use Let's Encrypt

Union types ('enum types') would be complicated in Go

Python type hints may not be not for me in practice

Losing NFS locks and the SunOS SIGLOST signal

The missing text focused programming environment

Python type hints are probably "worth it" for me

I feel that NAT is inevitable even with IPv6

IPv6 networks do apparently get probed

The history of Unix's ioctl and signal about window sizes

Potential pragmatic handling of partial matches for HTTP conditional GET

The question of whether to still allow HTTP/1.0 requests or block them

Go's new small language features from 1.22 and 1.23 are nice

Traditionally, init on Unix was not a service manager as such

Daemonization in Unix programs is probably about restarting programs

I wish (Linux) WireGuard had a simple way to restrict peer public IPs

Go and my realization about what I'll call the 'Promises' pattern

In practice, abstractions hide their underlying details

Operating system threads are always going to be (more) expensive

More →