Basil Crow

Minimalist

[Basil Crow @bcrow]

@AnthropicAI I’m having a billing issue, and the support bot isn’t working, nor have I received any response in 5 days since the issue was escalated. Please connect me with a human who can resolve my billing issue.

[Basil Crow @bcrow]

@Romanos911 https://t.co/jAuUG4746B

[Basil Crow @bcrow]

That feeling when Claude Code, upon reviewing Codex CLI’s recent work, says: “The refactor velocity here is unusual” 🤣

[Basil Crow @bcrow]

@Nil053 Codex implementing and Opus reviewing.

[Basil Crow @bcrow]

@Nil053 Same. I’ve switched to Codex as my primary coding model.

[Basil Crow @bcrow]

Linux coredumps bury the arguments and environment variables on the initial process stack. My ptools project walks the auxiliary vector from AT_RANDOM to recover every argument and environment variable intact.​​​​​​​​​​​​​​​​ https://t.co/1oGTnsSHc2

[Basil Crow @bcrow]

Ever tried to figure out why a Linux process is hung? You probably cobbled together output from GDB, lsof, and /proc, each with its own interface, its own flags, and its own quirks. And if all you have is a core dump? Good luck.

Solaris solved this decades ago with its "ptools": pstack, pfiles, ptree, and others. They have one consistent interface for inspecting live processes and core dumps alike. It's one of those things that, once you've used it, is hard to live without.

So I've been building ptools for Linux: a collection of Linux process inspection utilities modeled after the Solaris originals. Written in Rust, available on https://t.co/ZaLkaQrWdo, fully open source (Apache 2.0), and ready to meet your production debugging needs today:

- pstack: Thread stack traces for live processes and core dumps, with optional DWARF source locations
- pfiles: Every open file descriptor with paths, offsets, socket details, and flags
- ptree: Process trees for the whole system or a single process
- penv: The *current* environment of a running process, not just a snapshot from startup. No other Linux CLI tool does this.
- pargs, pauxv, pcred, psig, plgrp, plimit, prun, pstop, ptime, pwait, and more

Postmortem debugging support is a first-class feature. Most tools work seamlessly with Ubuntu/Debian Apport .crash files or systemd-coredump core dumps on RHEL/Fedora/SUSE, making postmortem debugging feel as natural as inspecting a live process. We've even upstreamed changes to Ubuntu Apport to enable postmortem analysis of open file descriptors.

ptools will be shipping in Fedora 44 next month. But why wait?

https://t.co/RkaBWMICiE

[Basil Crow @bcrow]

@MyFonts Thank you! I have successfully purchased it and now have the complete font family. This ticket can be closed.

[Basil Crow @bcrow]

@MyFonts On https://t.co/XREkAurbT5 I see

Trump Mediaeval LT Pro Roman
Trump Mediaeval LT Pro Italic

but I do not see

Trump Mediaeval LT Pro Bold

or

Trump Mediaeval LT Pro Bold Italic

[Basil Crow @bcrow]

@MyFonts @MyFonts How is this going?

[Basil Crow @bcrow]

ptools v0.2.5 is out! 🚀

https://t.co/XytzOHPdqN

New: Major pfiles upgrades for socket/file introspection (TCP state, peer process info, IPv6, and more), plus new psig for process signal actions, and updated manual pages.

ptools is a collection of Linux utilities written in Rust for inspecting process state, inspired by the original Solaris/illumos tools.

[Grok @grok]

@AshuSinghIN Jenkins, as more teams migrate to GitHub Actions for its seamless integration and scalability. It's not vanishing overnight, but its dominance is fading@AshuSinghIN Jenkins, as more teams migrate to GitHub Actions for its seamless integration and scalability. It's not vanishing overnight, but its dominance is fading.

[Basil Crow @bcrow]

The bold and italic styles are available in the Pro Cyrillic release, but not the Pro release. However, the Pro Cyrillic release doesn’t contain Roman or Italic styles. All the glyphs are available in one release or another, but the problem is the release structure itself is illogical: no single release contains the entire Latin alphabet in all weights. This is illogical. Please escalate this to someone in Linotype who has visibility into the releases.

[Basil Crow @bcrow]

@MyFonts This is a Linotype font, so your company is the designer.

[Basil Crow @bcrow]

The Python 3 documentation for priority queues has a fun Theory section: https://t.co/3JMXRlu7yM

Turns out it was written about 25 years ago by François Pinard https://t.co/sjxObOkXAP

Don’t miss the fun anecdote about tape sorting in the 1960s https://t.co/bFud2lh2Rz

[Basil Crow @bcrow]

@Nil053 Congrats!

[Basil Crow @bcrow]

“the indignities of trying to monetize open source infrastructure on a VC timeline”

[DHH @dhh]

Anthropic buying Bun is a beautiful act of corporate patronage. There's no compelling technical or strategic argument, but I fully support saving a great runtime from the indignities of trying to monetize open source infrastructure on a VC timeline ��� https://t.co/c6OCzGnuSl

[Basil Crow @bcrow]

@Nil053 Don’t impress your interviewer with memorized problems – memorize concepts that impress your interviewer.

[Basil Crow @bcrow]

Sun Microsystems might be dead, but I still treasure its leadership principles.

[Basil Crow @bcrow]

Don’t allow your sparkling prose – heaven forbid – to be mistaken for AI slop! Follow Robert Bringhurst’s advice about dashes:

“The em dash is the nineteenth-century stand­ard, still pre­scribed by many edit­or­ial style books, but the em dash is too long for use with the best text faces. Like the over­sized space between sen­tences, it belongs to the pad­ded and cor­seted aes­thetic of Vic­torian typography. Use spaced en dashes – rather than em dashes or hyphens – to set off phrases.”