If you want to connect to a server's IPMI over the network, you normally need to authenticate as some IPMIuser. When you set that IPMI user up, you'll give it one of threeor four privilege levels; ADMINISTRATOR, OPERATOR, USER, or what Ibelieve is rarely used, CALLBACK. For years, when I tried to setup IPMIs for things like reading sensors over the network, remotepower cycling, or Serial over LAN console access , I'd make a specialIPMI user

Today on lobste.rs I saw a story about another 'shame people whodon't have IPv6' website .People have made these sites before and they will make them againand as people in the comments note, it will have next to no effect.One of the reasons for that is a variant on how IPv6 has oftenhad low user benefits .

As a practical matter, almost all servers that people want to begenerally accessible need to be accessible via IPv4, because thereare still a

My major use of Git is to keep copies of the public repositoriesof various projects from various people. Every so often, one of thepeople involved gets sufficiently irritated with the life of beingan open source maintainer and takes their project's repository private ( or their currentGit 'forge' host does it for other reasons ). When this happens,on my next 'git pull', Git skids to a halt with:

; git pullUsername for 'https://gitlab.com':

This

One of the things that make browsers interesting programs, in onesense, is that they generally have a lot of options, which leadsto a lot of potential different behavior, which creates plenty ofplaces for bugs to hide out. One of my favorite ones in Firefox isa long-standing user interface bug in Firefox's general UI for addonupdates, one that's hard for ordinary people to come across becauseit requires a series of unusual settings and circumstances.

If you have automatic updates for your addons

There is a person running a Python program on one of our servers, which is something thatpeople do regularly. As far as I can tell, this person's Pythonprogram is using some Python framework that supports on the flyreloading (often called hot-reloading) of changed Python code forat least some of the loaded code, and perhaps much or all of it.Naturally, in order to see if you need to hot-reload any code, youneed to check whether a bunch of files have

Due to the pre-beta Ubuntu 24.04 issue I found with grub updateson systems with software RAID root filesystems and BIOS MBR booting , for a while Ithought we'd need something that rewrote a debconf key tochange it from naming the software RAID of the root filesystem tonaming the devices it was on. So I spent a bit of time working outhow best to do that, which I'm going to write down for any futureuse.

At one level this question seems silly

Recently I ran across (and eventually reported) an issue onpre-beta Ubuntu 24.04 where a grub package update would fail forsystems with software RAID root disks and BIOS MBR booting . The specificerror was that grub-install could not install the new version ofGRUB's boot-time code on '/dev/md0', the (nominal) device of theroot filesystem, reporting an error to the effect of:

grub-install: warning: File system `ext2

Bash has aninteresting and broadly useful feature called ' programmable completion '(this has sort of come up before ).Programmable completion makes it possible for Bash to auto-completethings like command line options for the current program for you.Unfortunately one flaw in Bash's programmable completion is that itdoesn't understand enough Bash command line syntax and so can get inyour way.

Suppose, not hypothetically, that you are typing the following onthe Bash command line on a Debian-based Linux system, with

Often, programs have build time configuration settings for featuresthey include, paths they use, and so on. Some of the time, peoplesuggest that the way to handle these is not through systems like'configure' scripts (whether produced by Autoconf or some other means)but instead by having people edit their settings into things suchas your Makefiles or header files ('source code' in a broad sense).As someone who has spent a bunch of time and effort building otherpeople's software over the