Dao's BLOG

firewall-cmd --zone=public --add-interface=<internet interface> --permanent
firewall-cmd --zone=internal --add-interface=<intranet interface as gateway> --permanent
firewall-cmd --set-default-zone=public --permanent
firewall-cmd --reload
firewall-cmd --get-default-zone
firewall-cmd --new-policy internal-public --permanent
firewall-cmd --reload
firewall-cmd --policy internal-public --add-ingress-zone=internal --permanent
firewall-cmd --policy internal-public --add-egress-zone=public --permanent
firewall-cmd --policy internal-public --set-target=ACCEPT --permanent
firewall-cmd --reload
firewall-cmd --info-policy internal-public

First, use

rpm -q gpg-pubkey –qf ‘%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n’

to identify keys from obsolete repositories, then use

rpm -e gpg-pubkey-xxxxxxxx-yyyyyyyy

to remove the keys that were imported from the SHA1 era.

Then have the offending packages removed by

rpm -q –nosignature –querybynumber xxxx

where you can get the xxxx from the stderr messages from

rpm -qa >/dev/null

It was found that systemd-logind malfunctioned,

By restarting it —

systemctl restart systemd-logind

The problem is resolved.

Recently I noticed a tcsh behavior change.

CentOS7, Rocky 8, Ubuntu 20.04, Fedora 41, and Linux Mint if you have a string variable in tcsh,

like

set a=”mystring”

and attempt to get its path when treating is as a filename:

set b=”$a:h”

it will return $a itself.

To be noted that the expect behavior when a=”mypath/mystring”,

set b=”$a:h”

get string $b as mypath

However, in Rocky9, $b will be “” empty string when $a does not contain any slash.

This behavior caused some of our tcsh scripts to malfunction.

The reason is still under investigating.

It happened to me that when I attempt to install Chinese/Japan/Korean input method to my windows 11 box, it fails on installing the “Basic Typing” after attempted to download for about 30 seconds with error

“Sorry, we’re having trouble installing this feature. You can try again later. Error code 0x0”.

And all other components like Handwriting, Text-to-speech, Speech recognition also fail. And the installed Asian keyboard does not work showing the feature is not ready.

I tried the tricks in this: [https://answers.microsoft.com/en-us/windows/forum/all/windows-11-unable-to-download-language-packs/b78b04da-2c75-45d8-a828-f553441b220f] but none of them works.

The workaround I found is to download

26100.1.240331-1435.ge_release_amd64fre_CLIENT_LOF_PACKAGES_OEM.iso

from https://files.rg-adguard.net/file/025cfc5d-f5fa-7d00-246e-76c04a40e210

and extract the corresponding language pack .cab files like

Microsoft-Windows-Client-Language-Pack_x64_zh-cn.cab

Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

Microsoft-Windows-LanguageFeatures-Handwriting-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

Microsoft-Windows-LanguageFeatures-Speech-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

Microsoft-Windows-LanguageFeatures-TextToSpeech-zh-cn-Package~31bf3856ad364e35~amd64~~.cab

and install them one by one in PowerShell with Admin privilege like:

Add-WindowsPackage -Online -PackagePath “.\Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~.cab”

After all of these, the “Basic typing” is still not available but the input method works.

Sometimes when you attempt to restart docker.service, it fails on cannot restart docker0 network interface.

In this case, you can simple do

ifdown docker0

Then you can start docker.service again.

If only to replace a system drive, doing a dd of old drive to new drive will work.

However, in most of cases the driving force of replacing drives is that the drive size is not big enough to host increasing size of system files.

In this case, only doing dd will screw you up in the same partition sizes.

There is a workaround, that you can do dd of the boot sector as well as the first partition, then use gparted to expand the first partition to the desired size. Then create a second partition, using dd to sync the second, then expand it to desired size, then the third, until it is done.

In this process, the new partitions of the second and beyond will carry a different UUID, which will prevent you from booting into the new drive properly.

You can either boot into a live CD/USB drive to change the UUIDs to the same with your old drive, or edit the /etc/fstab and /boot/grub2/grub.cfg to replace the corresonding UUID of each mount.

This method is tested working.

If you are using tcsh shell, and your login script has screen output like an echo line, scp will be interrupted.

To prevent this, knowing that for an interactive ssh session, it will open a tty, but embedded session like scp will not generate a tty.

Thus this can be distinguished by checking if the variable $SSH_TTY is defined. For example, you can put this in your ~/.cshrc

if ($?SSH_TTY) then
(do your login environment settings here)
else
set sh = /bin/bash
set cmdline = “tr '\0\n' '\n\1' </proc/$$/cmdline“
if ($#cmdline > 2) then
exec $sh -c ‘exec “$0” -c “$(printf %s “$1” | tr “\1” “\n”)”‘ $sh $cmdline[3]:q
endif
endif

This, will launch a log in script free session for embedded sessions like scp.