I've used Byron Rakitzis's Unix reimplementation of Tom Duff's rc Plan 9 shell for a long time (for a varietyof reasons ). One of the ways that rc is differentfrom standard Unix shells is that it has an unusual and surprisinglyconvenient additional feature in how it handles searching your $PATH .

In most Unix shells, if you type ' fred/barney ' as a command nameto execute, it's immediately interpreted as a relative path. Forexample, if you do:

Suppose, not entirely hypothetically ,that you have a Fedora laptop and you want it to use minimal bandwidthfor things that you don't specifically do. Unfortunately there areonly a few things that I know of to do, and I'm not sure they'recomprehensive. Most of my information comes from this old r/Fedorapost .

First, turn off dnf-makecache . DNF's cacheupdates can apparently download significant amounts of data if youlet them. Second, set your connection as metered

When I think about new metrics sources for our Prometheus setup,often one of the things on my mind is the potential for a metricsexplosion ifI add metrics data that might have high cardinality. Now, sometimeshigh cardinality data is very worth it and sometimes data that might be high cardinality won't actuallybe , so this doesn't necessarily stop me.But in all of this, I haven't really developed an intuition forwhat is a lot of metrics (or time series) and what isn

TLS Certificate Transparency is a system where browser vendors require TLS Certificate Authoritiesto publish information about all of their TLS certificates incryptographically validated logs, which are generally run by thirdparties. Or you can read the Wikipedia article , whichdescribes it somewhat differently. A crucial ingredient in certificatetransparency are CT logs, which need to keep operating properly forthis whole thing to work.

Well, except that sometimes things go wrong in CT log operation ; for instance,there's been at least one CT log that became corrupt

A while back I wrote an entry about how TLS increasingly existsin three different worlds ; the world of publicHTTPS ( web TLS ), the world of non-web public TLS as used byprotocols like IMAP, and the world of internal TLS . That entrymostly took the perspective of operating services, but there'sanother perspective where there is web TLS and private TLS .This is the perspective of TLS certificate issuance and TLS CertificateAuthorities.

This web TLS world of TLS certificate issuance is now mostlyautomated,

At work, we reinstall our servers to "upgrade" OS versions , rather than try to upgrade them inplace, so our OS installs all have a finite lifetime. Sometimesthis is a pretty long lifetime (we still have CentOS 7 machinesrunning and will probably run them until close to when CentOS 7goes out of support), but more often this is around four yearssince we mostly use Ubuntu LTS .However, this is not what I do on my own machines, as I mentionedrecently in my entry

Apache Nutch is, to quote its web page, "a well matured, productionready Web crawler". More specifically, it's a web crawler engine,which people can take and use to create web crawlers themselves.However, it has a little issue, which I put in a tweet :

If you write a web crawler engine, you should make it very hardfor people to not fill in all of the information for a properuser-agent string (such as a URL explaining the crawling).

Almost a year ago, I had problems with Firefox's WebRender on myLinux machine , including both bad jankand bad performance under some circumstances .Back then I turned it off with the gfx.webrender.force-disabledsetting in about:config and forgot about the whole thing. RecentlyI updated my build of Firefox Nightly to the current one and allof a sudden my problems came back. The reason for this isstraightforward; as time marches on, Mozilla invariably forcespeople into the future, whether or

One of the things I've come to believe about labels on Prometheusmetrics is that all metrics for a particular host should have alabel for its hostname. I tend to call this label "host" ( eg ) in my entries, but when we set up our setup I actually called it" cshost ", with a prefix, to guard against the possibility thatsome metrics source would have its own "host" label.

The purpose of this label is to have something that can be used tostraightforwardly group