I have previously posted a similar topic on how to set the default dimension for Alacritty at launch. However, recently, Alacritty switched to TOML for its configuration. Here is the setting needs to be added to ~/.config/alacritty/alacritty.toml: [window.dimensions] columns = 133 lines = 40 Reference: https://blog.khmersite.net/p/set-alacritty-default-dimensions/

This evening while I was running the system update on one of the guest VMs running on my XCP-ng host, I accidentally rebooted the XCP-ng host. Why? Accident! The guest VM is very important, it’s running Xen Orchestra for this XCP-ng server. Semi-fortunately, I remember I had a snapshot for this VM. The challenge for me was, how could I restore the VM using that previous snapshot without Xen Orchestra....

Happy New Year 2024! This is going to be a very short post on how to use ‘df’ command to display the disk space usage in megabytes. To display the output in MB (megabytes), we can use the -m flag with the df command as the following: ❯ df -m Filesystem 1M-blocks Used Available Use% Mounted on devtmpfs 4 0 4 0% /dev tmpfs 852 0 852 0% /dev/shm tmpfs 341 6 336 2% /run /dev/mapper/almalinux-root 7578 2068 5511 28% / /dev/vda2 1014 280 735 28% /boot /dev/vda1 599 8 592 2% /boot/efi tmpfs 171 0 171 0% /run/user/1000 It’s simple, isn’t it?...

FreeBSD 14.0-RELEASE just got relesed at the end of last month, and I wanted to upgrade my NAS server running FreeBSD 13.x-RELEASE to 14.0. Using the installation instruction from [1], I was able to upgrade smoothly without any issues. Here are the steps: # freebsd-update fetch # freebsd-update install # freebsd-update upgrade -r 14.0-RELEASE # freebsd-update install Reboot: # reboot After rebooting, freebsd-update(8)[2] needs to be run again to install the new userland components:...

So I have an EC2 instance running RHEL 8.9 which was recently upgraded from RHEL 7.9. Now, I want to upgrade it all the way to RHEL 9. Here is the worklog which recording the steps I performed to achieve that goal. Step 0, perform a snapshot of the root volume of the instance, or create an AMI from it. In my case, this is just a test instance, so I skip taking the snapshot....