rwv's Blog

Linux Server Initialization Checklist

Tue, 18 Mar 2025 10:07:03 +0800

APT Configuration

Change sources to HTTPS, upgrade the system, and install commonly used tools:

sed -i 's/http:/https:/g' /etc/apt/sources.list
apt update && apt upgrade -y
apt install -y curl wget git screen htop zsh sudo rsync nano nload

Configure SSH

Set up SSH key-based login:

mkdir -p ~/.ssh
nano ~/.ssh/authorized_keys

Disable password login and enforce SSH key authentication:

sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config
systemctl restart sshd

Install oh-my-zsh

sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
nano ~/.zshrc
source ~/.zshrc

Install Docker

curl -fsSL https://get.docker.com | sh

Configure Automatic Updates

apt-get install -y unattended-upgrades apt-listchanges
dpkg-reconfigure unattended-upgrades

Enable ZRAM

apt install -y zram-tools
echo -e "ALGO=zstd\nPERCENT=60" | tee -a /etc/default/zramswap
service zramswap reload

Enable BBR Network Optimization

# Check if BBR is enabled
sysctl net.ipv4.tcp_congestion_control

echo "net.core.default_qdisc=fq" >> /etc/sysctl.conf
echo "net.ipv4.tcp_congestion_control=bbr" >> /etc/sysctl.conf
sysctl -p

Configure Time Synchronization (Chrony)

apt install -y chrony
nano /etc/chrony/sources.d/corps.sources

# Add the following time servers:
pool time.apple.com iburst
pool time.google.com iburst
pool time.cloudflare.com iburst nts

chronyc reload sources

Configure DNS Service (systemd-resolved)

apt install -y systemd-resolved
systemctl enable --now systemd-resolved
nano /etc/systemd/resolved.conf

# TODO: Use sed to configure Cloudflare DNS and fallback DNS
DNS=1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
FallbackDNS=8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google 9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
DNSOverTLS=yes
MulticastDNS=no
LLMNR=no

systemctl restart systemd-resolved

After completing these steps, the server is ready for use.

Add Giscus Multilingual Support in Hugo PaperMod

Wed, 22 Jan 2025 13:18:04 +0800

Giscus actually supports multiple languages, as you can see in giscus/giscus/locales. However, it doesn’t automatically detect the language, so manual configuration is needed. Hugo PaperMod doesn’t have a simple way to set different comment components for different languages, so we need to configure it manually.

Configure Giscus

First, create a comment component at giscus.app, which looks like this:

<script
  src="https://giscus.app/client.js"
  data-repo="[ENTER REPO HERE]"
  data-repo-id="[ENTER REPO ID HERE]"
  data-category="[ENTER CATEGORY NAME HERE]"
  data-category-id="[ENTER CATEGORY ID HERE]"
  data-mapping="pathname"
  data-strict="0"
  data-reactions-enabled="1"
  data-emit-metadata="0"
  data-input-position="bottom"
  data-theme="preferred_color_scheme"
  data-lang="en"
  crossorigin="anonymous"
  async
>script>

Notice the data-lang attribute - this is what we use to set the language.

Configure Hugo PaperMod Template HTML

First, set PaperMod’s comments to true so that the comment component will be displayed in every article.

PaperMod Documentation - Comments

params:
  comments: true

Then create layouts/partials/comments.html with the following content:

{{ $giscusLang := "en" }} {{ if eq site.Language.Lang "zh" }} {{ $giscusLang =
"zh-CN" }} {{ else if eq site.Language.Lang "zh-tw" }} {{ $giscusLang = "zh-TW"
}} {{ else if eq site.Language.Lang "zh-hk" }} {{ $giscusLang = "zh-HK" }} {{
else if eq site.Language.Lang "ar" }} {{ $giscusLang = "ar" }} {{ else if eq
site.Language.Lang "be" }} {{ $giscusLang = "be" }} {{ else if eq
site.Language.Lang "bg" }} {{ $giscusLang = "bg" }} {{ else if eq
site.Language.Lang "ca" }} {{ $giscusLang = "ca" }} {{ else if eq
site.Language.Lang "cs" }} {{ $giscusLang = "cs" }} {{ else if eq
site.Language.Lang "da" }} {{ $giscusLang = "da" }} {{ else if eq
site.Language.Lang "de" }} {{ $giscusLang = "de" }} {{ else if eq
site.Language.Lang "el" }} {{ $giscusLang = "gr" }} {{ else if eq
site.Language.Lang "eo" }} {{ $giscusLang = "eo" }} {{ else if eq
site.Language.Lang "es" }} {{ $giscusLang = "es" }} {{ else if eq
site.Language.Lang "eu" }} {{ $giscusLang = "eu" }} {{ else if eq
site.Language.Lang "fa" }} {{ $giscusLang = "fa" }} {{ else if eq
site.Language.Lang "fr" }} {{ $giscusLang = "fr" }} {{ else if eq
site.Language.Lang "he" }} {{ $giscusLang = "he" }} {{ else if eq
site.Language.Lang "hu" }} {{ $giscusLang = "hu" }} {{ else if eq
site.Language.Lang "id" }} {{ $giscusLang = "id" }} {{ else if eq
site.Language.Lang "it" }} {{ $giscusLang = "it" }} {{ else if eq
site.Language.Lang "ja" }} {{ $giscusLang = "ja" }} {{ else if eq
site.Language.Lang "km" }} {{ $giscusLang = "kh" }} {{ else if eq
site.Language.Lang "ko" }} {{ $giscusLang = "ko" }} {{ else if eq
site.Language.Lang "nl" }} {{ $giscusLang = "nl" }} {{ else if eq
site.Language.Lang "pl" }} {{ $giscusLang = "pl" }} {{ else if eq
site.Language.Lang "pt" }} {{ $giscusLang = "pt" }} {{ else if eq
site.Language.Lang "ro" }} {{ $giscusLang = "ro" }} {{ else if eq
site.Language.Lang "ru" }} {{ $giscusLang = "ru" }} {{ else if eq
site.Language.Lang "th" }} {{ $giscusLang = "th" }} {{ else if eq
site.Language.Lang "tr" }} {{ $giscusLang = "tr" }} {{ else if eq
site.Language.Lang "uk" }} {{ $giscusLang = "uk" }} {{ else if eq
site.Language.Lang "uz" }} {{ $giscusLang = "uz" }} {{ else if eq
site.Language.Lang "vi" }} {{ $giscusLang = "vi" }} {{ end }}

<script
  src="https://giscus.app/client.js"
  data-repo="[ENTER REPO HERE]"
  data-repo-id="[ENTER REPO ID HERE]"
  data-category="[ENTER CATEGORY NAME HERE]"
  data-category-id="[ENTER CATEGORY ID HERE]"
  data-mapping="pathname"
  data-strict="0"
  data-reactions-enabled="1"
  data-emit-metadata="0"
  data-input-position="bottom"
  data-theme="preferred_color_scheme"
  data-lang="{{ $giscusLang }}"
  crossorigin="anonymous"
  async
>script>

This way, the comment component will be displayed in every article and will automatically set its language based on the article’s language.

Note: Prettier will automatically format the code, which is why it might look a bit messy.

References

Migrating Blog System from Hexo to Hugo

Wed, 22 Jan 2025 09:22:52 +0800

After four years, I’m ready to start blogging again. However, I felt the need to tinker with the system as Hexo wasn’t quite meeting my needs, so I decided to migrate to Hugo. Another important reason was that yilia hasn’t been updated for a very long time and doesn’t even support dark mode.

Migration Motivation

Here are the main advantages of migrating from Hexo to Hugo, along with avoiding some existing technical debt (such as messy git logs and lack of open source):

Faster Build Speed: Hugo is written in Go, making it faster than Node.js-based solutions
Simpler Deployment: Single binary file, no complex dependency management needed
Powerful Content Management: Page Bundles feature makes article and resource management clearer
Active Community: Rich ecosystem of themes and plugins
Internationalization Support: Hugo’s built-in multilingual support makes internationalization easy
Better Theme Options: The PaperMod theme suits my aesthetic better than yilia and supports dark mode

Migration Steps

Creating a Hugo Site

# Install Hugo (macOS)
brew install hugo

# Create site
hugo new site my-blog
cd my-blog

# Install PaperMod theme
git init
git submodule add https://github.com/adityatelange/hugo-PaperMod themes/PaperMod

Modify the basic configuration file hugo.toml

baseURL = "https://blog.rwv.dev/"
title = "My Blog"
theme = "PaperMod"
languageCode = "en"

You can reference my configuration here: config/_default

Content Migration

Converting article formats:

Move articles from source/_posts to content/posts
Convert front matter format:

# Hexo format
---
title: Example Post
date: 2024-01-22 14:30:00
tags:
  - hugo
  - blog
---

# Hugo format
---
title: Example Post
date: 2024-01-22T14:30:00+08:00
tags:
  - hugo
  - blog
aliases:
  - /2024/01/22/example-post/
---

The original URL path in Hexo was permalink: :year/:month/:day/:title/. In Hugo, we need to set aliases to prevent old links from breaking.

Configuring Comments System

I also replaced the original Disqus commenting system with giscus. Here’s the specific configuration:

# config/_default/params.yml
comments: true


<script
  src="https://giscus.app/client.js"
  data-repo="your-github-username/your-repo-name"
  data-repo-id="xxxx"
  data-category="Announcements"
  data-category-id="xxxx"
  data-mapping="pathname"
  data-strict="0"
  data-reactions-enabled="1"
  data-emit-metadata="0"
  data-input-position="bottom"
  data-theme="preferred_color_scheme"
  data-lang="en"
  crossorigin="anonymous"
  async
>script>

Configuring GitHub Actions

I’m using GitHub Actions to automatically deploy the blog to both Cloudflare Pages and GitHub Pages for better disaster recovery (although such scenarios are unlikely). In the future, I might deploy to more platforms, possibly even IPFS, though I’m skeptical about IPFS’s stability.

You can find the specific code in .github/workflows/ci.yml

Why not use Cloudflare Pages’ own build system? Because Cloudflare Pages has concurrent build limitations, and their Hugo version is too old to compile successfully. GitHub Actions’ build system is more reliable.

Open Source

Taking advantage of this migration, I’ve made the blog open source. The project is available at rwv/blog, and you can find the ‘Edit’ button at the top of each article to go directly to the source code. Here’s the specific configuration:

editPost:
  URL: "https://github.com/rwv/blog/blob/main/content"
  appendFilePath: true # to append file path to Edit link

Code: config/_default/params.yml#L21-L23

Conclusion

Hugo provides a more efficient blogging experience. While migration requires some effort, in the long run, it will enable me to write more blog posts. So the migration was worth it.

Mounting Network UNC Paths to Drive Letters in Windows CMD

Fri, 26 Apr 2019 13:40:17 +0800

There are two methods to mount a network UNC (Universal Naming Convention) path to a local drive letter in Windows Command Prompt. While pushd is commonly used, it has a significant limitation that may affect certain scenarios.

Common Method: Using `pushd`

set unc_path=\\Host\a\b\c
pushd %unc_path%
:: Your commands here
popd

When using pushd, Windows automatically mounts \\Host\a to the first available drive letter (for example, Y:), then changes the working directory to Y:\b\c. However, this approach has a critical limitation: if the user has permissions for \\Host\a\b\c but lacks access to \\Host\a, all commands in this directory will fail with an Access is denied error.

Alternative Method: Using `net use`

set unc_path=\\Host\a\b\c

:: Mount the UNC path to an available drive letter
net use * %unc_path%

:: Extract the assigned drive letter
for /f "tokens=2,3" %%i in ('net use') do if '%%j=='%unc_path% set drive_letter=%%i

:: Change to the mounted drive
%drive_letter%

:: Your commands here

:: Clean up: unmount the drive
net use %drive_letter% /delete /y

This alternative approach first assigns an available drive letter to the path using net use, then retrieves the assigned drive letter. The key advantage over pushd is that net use mounts the specific subdirectory rather than the root directory, thereby avoiding the permission issues mentioned above.

Note: When executing these commands directly in the command prompt (rather than in a batch file), replace %%i and %%j with %i and %j respectively.

Create a ZeroTier Moon Node with Docker in Two Commands

Sun, 13 May 2018 19:46:00 +0800

While creating a ZeroTier moon node isn’t overly complex, it does involve several steps. To simplify this process, I’ve created a Docker image that lets you set up a moon node with just two commands.

Basic Setup

First, create the ZeroTier moon node:

docker run --name zerotier-moon -d -p 9993:9993 -p 9993:9993/udp seedgou/zerotier-moon -4 1.2.3.4

(Replace 1.2.3.4 with your moon node’s public IP address)

Then, retrieve your moon ID:

docker logs zerotier-moon

Note: Each new container generates a new moon ID. To preserve your moon ID after container restarts, use docker start zerotier-moon instead of creating a new container. For persistent moon ID storage across new container creations, see the Mounting Configuration Directory section below.

Advanced Usage

ZeroTier Management

docker exec zerotier-moon /zerotier-cli

Mounting Configuration Directory

docker run --name zerotier-moon -d -p 9993:9993 -p 9993:9993/udp -v ~/somewhere:/var/lib/zerotier-one seedgou/zerotier-moon -4 1.2.3.4

This command mounts a local directory (~/somewhere) to the container’s /var/lib/zerotier-one directory, enabling configuration persistence. Without this mount, each new container will generate a fresh moon ID.

IPv6 Support

docker run --name zerotier-moon -d -p 9993:9993 -p 9993:9993/udp seedgou/zerotier-moon -4 1.2.3.4 -6 2001:abcd:abcd::1

Replace both 1.2.3.4 and 2001:abcd:abcd::1 with your moon node’s IPv4 and IPv6 addresses respectively. In IPv6-only environments, you can omit the -4 option.

Custom Port

docker run --name zerotier-moon -d -p 9994:9993 -p 9994:9993/udp seedgou/zerotier-moon -4 1.2.3.4 -p 9994

Replace 9994 with your desired port number.

Source Code

https://github.com/rwv/docker-zerotier-moon

Fixing Time Synchronization Issues Between Hackintosh and Windows

Sun, 04 Mar 2018 22:51:52 +0800

By default, macOS and Windows handle the system BIOS clock differently. macOS interprets the BIOS clock as UTC (Coordinated Universal Time), while Windows reads it as local time. For example, if the BIOS clock shows 00:00, Windows will display it as 00:00 local time. However, macOS will interpret this as 00:00 UTC and adjust it to show 08:00 for users in GMT+8 time zones (like Beijing time). This difference in interpretation causes the time to appear inconsistent between the two operating systems.

Solutions

Method 1: Using Registry Editor

Open Registry Editor by pressing Win + R and typing Regedit
Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Create a new DWORD (32-bit) Value named RealTimeIsUniversal
Set its value to 1

Method 2: Using Command Prompt

Run the following command in an Administrator Command Prompt:

Reg add HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation /v RealTimeIsUniversal /t REG_DWORD /d 1

This change will make Windows treat the BIOS clock as UTC time, matching macOS’s behavior.

Reference

MAC 系统同 WIN10 时间不一致的问题-远景论坛-微软极客社区

Solution for autojump_chpwd:4: nice(5) failed: operation not permitted Error in WSL

Thu, 01 Feb 2018 01:26:41 +0800

When using autojump in Windows Subsystem for Linux (WSL), you might see this error message:

autojump_chpwd:4: nice(5) failed: operation not permitted

While this error doesn’t affect autojump’s functionality, it can be annoying to see this message every time you use the command.

Solution

Add this line to your ~/.zshrc:

unsetopt BG_NICE

Example Configuration

Here’s a complete example of a .zshrc file configured for WSL with autojump. You can find this configuration on GitHub Gist.

# If you come from bash you might have to change your $PATH.
# export PATH=$HOME/bin:/usr/local/bin:$PATH

# To Fix the autojump_chpwd:4: nice(5) failed: operation not permitted error.
unsetopt BG_NICE

# Path to your oh-my-zsh installation.
  export ZSH=$HOME/.oh-my-zsh

# Set name of the theme to load. Optionally, if you set this to "random"
# it'll load a random theme each time that oh-my-zsh is loaded.
# See https://github.com/robbyrussell/oh-my-zsh/wiki/Themes
ZSH_THEME="ys"

# Set list of themes to load
# Setting this variable when ZSH_THEME=random
# cause zsh load theme from this variable instead of
# looking in ~/.oh-my-zsh/themes/
# An empty array have no effect
# ZSH_THEME_RANDOM_CANDIDATES=( "robbyrussell" "agnoster" )

# Uncomment the following line to use case-sensitive completion.
# CASE_SENSITIVE="true"

# Uncomment the following line to use hyphen-insensitive completion. Case
# sensitive completion must be off. _ and - will be interchangeable.
# HYPHEN_INSENSITIVE="true"

# Uncomment the following line to disable bi-weekly auto-update checks.
# DISABLE_AUTO_UPDATE="true"

# Uncomment the following line to change how often to auto-update (in days).
# export UPDATE_ZSH_DAYS=13

# Uncomment the following line to disable colors in ls.
# DISABLE_LS_COLORS="true"

# Uncomment the following line to disable auto-setting terminal title.
# DISABLE_AUTO_TITLE="true"

# Uncomment the following line to enable command auto-correction.
# ENABLE_CORRECTION="true"

# Uncomment the following line to display red dots whilst waiting for completion.
# COMPLETION_WAITING_DOTS="true"

# Uncomment the following line if you want to disable marking untracked files
# under VCS as dirty. This makes repository status check for large repositories
# much, much faster.
# DISABLE_UNTRACKED_FILES_DIRTY="true"

# Uncomment the following line if you want to change the command execution time
# stamp shown in the history command output.
# The optional three formats: "mm/dd/yyyy"|"dd.mm.yyyy"|"yyyy-mm-dd"
# HIST_STAMPS="mm/dd/yyyy"

# Would you like to use another custom folder than $ZSH/custom?
# ZSH_CUSTOM=/path/to/new-custom-folder

# Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*)
# Custom plugins may be added to ~/.oh-my-zsh/custom/plugins/
# Example format: plugins=(rails git textmate ruby lighthouse)
# Add wisely, as too many plugins slow down shell startup.
plugins=(
  git
  autojump
)

source $ZSH/oh-my-zsh.sh

# User configuration

# export MANPATH="/usr/local/man:$MANPATH"

# You may need to manually set your language environment
# export LANG=en_US.UTF-8

# Preferred editor for local and remote sessions
# if [[ -n $SSH_CONNECTION ]]; then
#   export EDITOR='vim'
# else
#   export EDITOR='mvim'
# fi

# Compilation flags
# export ARCHFLAGS="-arch x86_64"

# ssh
# export SSH_KEY_PATH="~/.ssh/rsa_id"

# Set personal aliases, overriding those provided by oh-my-zsh libs,
# plugins, and themes. Aliases can be placed here, though oh-my-zsh
# users are encouraged to define aliases within the ZSH_CUSTOM folder.
# For a full list of active aliases, run `alias`.
#
# Example aliases
# alias zshconfig="mate ~/.zshrc"
# alias ohmyzsh="mate ~/.oh-my-zsh"

Reference

GitHub Issue #474: autojump_chpwd:4: nice(5) failed: operation not permitted

Opening UTF-8 CSV Files with Microsoft Excel on macOS

Fri, 26 Jan 2018 01:25:40 +0800

Microsoft Excel on macOS doesn’t provide a direct way to set character encoding when opening files. This makes it challenging to properly open UTF-8 encoded CSV files. However, there’s a workaround using Excel’s Get External Data feature that allows you to successfully open UTF-8 CSV files.

Steps

Create a new blank Excel workbook
Navigate to the Data tab and select Get External Data > Import Text File...

Locate and select your CSV file. In the import wizard, choose Unicode (UTF-8) as the file origin, then click Next.

In the next screen, select your desired delimiter options, then click Finish.

That’s it! Your UTF-8 CSV file should now be properly imported with all characters displaying correctly.

rwv's Blog

Linux Server Initialization Checklist

APT Configuration

Configure SSH

Install oh-my-zsh

Install Docker

Configure Automatic Updates

Enable ZRAM

Enable BBR Network Optimization

Configure Time Synchronization (Chrony)

Configure DNS Service (systemd-resolved)

Add Giscus Multilingual Support in Hugo PaperMod

Configure Giscus

Configure Hugo PaperMod Template HTML

References

Migrating Blog System from Hexo to Hugo

Migration Motivation

Migration Steps

Creating a Hugo Site

Content Migration

Configuring Comments System

Configuring GitHub Actions

Open Source

Conclusion

Mounting Network UNC Paths to Drive Letters in Windows CMD

Common Method: Using pushd

Alternative Method: Using net use

Create a ZeroTier Moon Node with Docker in Two Commands

Basic Setup

Advanced Usage

ZeroTier Management

Mounting Configuration Directory

IPv6 Support

Custom Port

Source Code

Fixing Time Synchronization Issues Between Hackintosh and Windows

Solutions

Method 1: Using Registry Editor

Method 2: Using Command Prompt

Reference

Solution for autojump_chpwd:4: nice(5) failed: operation not permitted Error in WSL

Solution

Example Configuration

Reference

Opening UTF-8 CSV Files with Microsoft Excel on macOS

Steps

Common Method: Using `pushd`

Alternative Method: Using `net use`