Thanks for the tip.

This also works in a checkout worktree.

I have an obscure usecase:

If you need to clone a repo and you can't control the checkout branch (because you are using another tool that assumes the default branch), you can still control which branch will be checked out on clone.

certbot certificates

Found the following certs: Certificate Name: www..org . Domains: mail..org www..org xmpp..org

certbot delete www..org

usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

certbot delete --cert-name www..org

Are you sure you want to delete the above certificate(s)? (Y)es/(N)o: y Deleted all files relating to certificate www..org

certbot certonly -d www..org -d mail..org --duplicate

Saving debug log to /var/log/letsencrypt/letsencrypt.log Error while running nginx -c /etc/nginx/nginx.conf -t.

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/www..org/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:

this is a little over my head, so trying to learn a bit, I searched the Wiki.

It needs some help, nothing about this issue is mentioned. https://wiki.debian.org/NetworkConfiguration#Using_systemd-resolved_for_DNS_resolution

can you add something to help others?

Do you use special filename prefixes to ensure that this script is the last daily cron script to run? Because I'm not sure I'd trust cron to resume running the rest of the scripts automatically after the reboot.

I tend to enable automatic reboots in unattended-upgrades at a fixed hour when I know no cron scripts are supposed to be running (Unattended-Upgrade::Automatic-Reboot "true"; Unattended-Upgrade::Automatic-Reboot-Time "04:30"; in /etc/apt/apt.conf.d/50unattended-upgrades-local). So far it has worked out well.

I've followed the instructions, but when it comes to the "mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/sdh1" command, I get:

mdadm: partition table exists on /dev/sdh1

mdadm: partition table exists on /dev/sdh1 but will be lost or meaningless after creating array

mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90

Continue creating array?

...I answer no at that point, but what should I do?

My OS is AlmaLinux, but I would think the instructions would apply. It uses an LVM partition system, but other instructions I've found that include LVM have the same steps.

Thanks for any help.

@Some Guy: there exist backends to make directly-network-attached scanners available to the sane ecosystem. Look for "sane-escl" (part of core Sane project, airprint/airscan protocol) and/or "sane-airscan " (3rd party open source, airprint/airscan + Microsoft WSD "WEB Service for devices" ).

Debian Wiki goes into more detail: SaneOverNetwork > escl protocol

Sorry to interupt but what's about nftables?

I have not yet switched to nftables, though it's on my list. In other words, I don't know yet.

So is this done in the bare repo or where?

Yes, in the bare repo.