Recent comments on posts in the blog:

RSS Atom
comment 1

I too got a WLE1216V5 for 5ghz, but went with an AR5BXB112 for 2.4ghz (for the more open ath9k driver). I differ on antenna arrangement as I put 2.4ghz to middle and 5ghz on the two new antennas for balance(I doubt it matters in use). I don’t think I’ll upgrade it with AX or BE, as the PCIe link would limit bandwidth even if some of the other advancements would be nice to have. I also put a mSATA ssd in slot three and consider the unit maxed out now.

Comment by NOSNHOP —
consider contributing to IkiWiki?
Very interesting, thanks. This is an approach I had not yet considered. I likewise get a low level of spam on my IkiWiki site; too low for me to have done much about improving the tools to handle it. But the tools could be a lot better. If you do look at this any further, just to say that IkiWiki would be open to improvements at its layer.
Comment by Jon —
LVM encryption in Ubunto 24 version
I tried these method but not able recover from intrimfs terminal after implementing LVM encryption during installing then i decided to make a boot key to recover from boot with out asking any encrytion key
Comment by Danish —
Works in a worktree as well.

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.

Comment by alecthegeek —
Doesn't seem to work with nginx, had to use the webroot option, but maybe it's me...

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:

Comment by Anonymous —
Thank you so much for your detailed instructions
I am so excited that I now have a "Safe" way to run Windows for devices that do not support Linux. I walked away from all MS products in favor of Linux over a decade ago. I love that VM gives you full control over what resources Windows can see. I can download under linux and drag and drop onto the Windows VM and Windows will never have access to the internet. Thank you for your very detailed instructions. This has opened up many devices for me that are not supported under Linux.
Comment by Daniel - N2FY —
debian wiki suggestion

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?

Comment by peter —
unattended-upgrades?

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.

Comment by Marius Gedminas —
Get "partition table exists" and other warning when trying to create mdadm

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.

Comment by James —