egrep -c '(vmx|svm)' /proc/cpuinfo</code></pre> A result of 1</code> or more means the CPU supports virtualization extensions. A result of 0</code> means it does not, though double-check the BIOS and see if the extensions are available and just need to be enabled. Install packages:sudo apt install qemu-system-x86 libvirt-clients libvirt-daemon libvirt-daemon-system virtinst virt-manager bridge-utils</code></pre> Add my user to the kvm</code>, libvirt</code>, and libvirt-qemu</code> groups: sudo adduser $USER kvm sudo adduser $USER libvirt sudo adduser $USER libvirt-qemu</code></pre> Log out and back in. Directories</h2> Default directory to hold VM images is /var/lib/libvirt/images</code>. The large amounts of space that these VM images occupy might pose an issue if /var</code> is mounted separately, or its included with the root</code> directory on a relatively small partition (i.e. separate root</code> and home</code> partitions). If this is the case, consider storing VMs on the partition with the greatest amount of free storage and symlink to that location. My installation of LMDE</a> has a large, separate partition for my home</code>, so I create a vm</code> directory there to store the VM images: mkdir -p ~/vm/images</code></pre> Delete the existing (empty) images</code> directory and create a symlink to the new location in vm</code>: sudo rmdir /var/lib/libvirt/images sudo ln -s ~/vm/images /var/lib/libvirt/images</code></pre> I also create an iso</code> directory to store Linux install images: mkdir ~/vm/iso</code></pre>Permissions</h2> libvirt.conf</h3> mkdir ~/.config/libvirt cp /etc/libvirt/libvirt.conf ~/.config/libvirt/</code></pre> Open the file for editing and uncomment: uri_default = "qemu:///system"</code></pre>qemu.conf</h3> For storage file permissions, modify /etc/libvirt/qemu.conf</code> by setting user</code> to my username (example: foo</code>) and group</code> to libvirt-qeumu</code>: user = "foo" group = "libvirt-qemu"</code></pre>Services</h2> Start the libvirt</code> service: sudo systemctl start libvirtd systemctl status libvirtd</code></pre>Create VM</h2> Create a VM using virt-manager</code>. Click the +</code> icon to add a new VM, and work through the series of dialog boxes to configure. During the creation of a VM, the network selection option defaults to Virtual network 'default': NAT</code>. If the default</code> network is not active, virt-manager</code> will prompt to start it. Or start manually with: virsh net-start default</code></pre> Each VM (in default</code> network) will be a member of 192.168.122.0/24</code>, with an IP address in the range of 192.168.122.2</code> to 192.168.122.254</code>, and are accessible via SSH from the host. Resize VM guest window</h2> In the virt-manager console window, navigate to Edit->Preferences->Console</code> and set: Graphical console scaling</code> to Always</code> Resize guest with window</code> to On</code></li> </ul> </li> </ul> Install a spice agent inside a VM (example: for Debian and Debian-based VMs): sudo apt install spice-vdagent</code></pre> Reboot the VM. In the VM guest window, navigate to View->Scale display</code> and check Always</code> and Auto resize VM with window</code>. Now click-and-drag the window edge to resize display, or use xrandr</code> to set display size. Video acceleration</h2> Using VirtIO its possible to create a virtual 3D accelerated GPU and pass through the hardware capabilities of the VM host’s graphics card. With the VM shutdown, open the VM hardware details window. Click on Video Virtio</code> and set Model: Virtio</code>, check the box for 3D acceleration</code>, and Apply</code> the modifications. Click on Display Spice</code>, set Type: Spice Server</code> and Listen type: None</code>, check the box for OpenGL</code>, and Apply</code> the modifications. Virsh and virt-clone</h2> Some useful commands: Start network: virsh net-start <network_name></code></li> List networks: virsh net-list</code></li> List of VMs: virsh list --all</code></li> Start, reboot, and shutdown VM: virsh start <VM></code>, virsh reboot <VM></code>, and virsh shutdown <VM></code></li> Show IP addresses: virsh net-dhcp-leases <network_name></code></li> Clone VM and create storage image: virt-clone -o <VM> -n <new_VM> -f /var/lib/libvirt/images/<new_VM>.qcow2</code></li> </ul> Resources</h2> Arch Linux Wiki: libvirt</a></li> Running VMs with VirtIO 3D Acceleration</a></li> </ul> You can like, share, or comment on this post on the Fediverse</a> 💬

NetBSD 11.0 Installation with Disk Encryption

Thu, 06 Aug 2026 00:00:00 +0000

The first time I installed NetBSD</a> I used sysinst(8)</a>, a menu-based program launched at boot that runs in the console. It has a clear and concise layout and I was quickly up-and-running on my new BSD</a> system.

For my next install I wanted to include disk encryption to protect personal data in case the device is lost or stolen. Its not really enough to simply encrypt home directories. Passphrases and sensitive data can linger and be extracted from locations such as system logs and swap memory. There is a trade-off to be made between how much to encrypt, the convenience of operating the system, and the ability for the system to boot.

Start Here</a>

Acquire an installation image</a></li>
Prepare the USB installation medium</a></li> </ul> </li>
Configure the Live Environment</a>

Connect to the internet</a></li>
Remote login to the installer</a></li> </ul> </li>
Prepare the DISK</a>

Identify disks and partitions</a></li>
Define DISK variable</a></li>
Wipe DISK</a></li>
Partition DISK</a></li>
Define wedge variables</a></li>
Format and mount the ESP wedge</a></li>
Add EFI boot entries to ESP</a></li>
Format and mount the root wedge</a></li> </ul> </li>
Disk Encryption</a>

Create encrypted device</a></li>
Create disklabels</a></li>
Verify encrypted device</a></li>
Format and mount disklabels</a></li> </ul> </li>
Installation</a></li>
Configure the System</a>

Chroot</a></li>
Directories</a></li>
Devices</a></li>
Root password</a></li>
Superuser</a></li>
Fstab</a></li>
Startup</a></li>
Keyboard</a></li>
Timezone</a></li>
Network interface</a></li>
Terminals</a></li> </ul> </li>
Finish Up</a></li>
Resources</a></li> </ul>

Start Here</h2>
Throughout this HOWTO, if you see square brackets []</code> in code blocks, that means the word of code (square brackets included) should be replaced with something else. This is detailed in the instructions before or after the code block.
NetBSD will be installed as the sole operating system on a single disk using a four-partition layout:
Partition ESP</code> is the EFI system partition.</li> Partition root</code> hosts a minimal root filesystem that boots to an encryption passphrase prompt, which upon entry unlocks…</li> … the encrypted device on partition syscgd</code> containing the contents of var</code>, usr</code>, and home</code>.</li>
Partition swap</code> is swap memory auto-encrypted at boot using a random key.</li> </ul> A few assumptions:Target device is amd64</code> architecture using UEFI to boot.</li> Secure boot is disabled on target device.</li> Network access during install uses a wired interface.</li> </ul> Sysinst does not provide the option for encrypting the system in this manner, so early in the install process I switch to the console and proceed to manually install NetBSD. Acquire an installation image</h3> The latest official installation images (as of August 2026) are available here: Images and torrents</a> Download the NetBSD-11.0-amd64-install.img.gz</code> image and the SHA512</code> file for verification: wget https://cdn.netbsd.org/pub/NetBSD/images/11.0/NetBSD-11.0-amd64-install.img.gz wget https://cdn.netbsd.org/pub/NetBSD/images/11.0/SHA512</code></pre> Verify the image using sha512sum</code>: sha512sum -c --ignore-missing SHA512 </code></pre> Decompress the image: gunzip NetBSD-11.0-amd64-install.img.gz</code></pre>Prepare the USB installation medium</h3> Write the installer to an unmounted USB storage device running the dd(1)</a> command as root</code>. WARNING Be very careful to note the proper device (which can be identified with lsblk</code>). All contents on the device will be lost! Example: On a Linux system, if a USB stick appears as sdx1</code>, then write the installer to sdx</code> (omit partition number): dd bs=4M conv=fsync oflag=direct status=progress if=NetBSD-11.0-amd64-install.img of=/dev/sdx</code></pre>Configure the Live Environment</h2> Boot the target device from the NetBSD installation medium. Select Option 1</code> (default) to Install NetBSD</code>. After the installer has successfully booted into the NetBSD kernel, a prompt appears to select which language will be used for installation messages, followed by a prompt to select a different keyboard type if desired or leave unchanged. Next up the menu-based sysinst program is launched: NetBSD-11.0 Install System >a: Install NetBSD to hard disk b: Upgrade NetBSD on a hard disk c: Re-install sets or install additional sets d: Reboot the computer e: Utility menu f: Config menu x: Exit Install System</code></pre>Connect to the internet</h3> At the Install System</code> main menu, select >e: Utility menu</code> then >c: Configure network</code>. Available interfaces</code> lists the network interfaces detected by the NetBSD installer. Example: With my target device Available interfaces</code> lists two: wm0</code> (wired) and iwn0</code> (wireless). I choose to configure the wired ethernet interface: Network media (empty to autoconfigure) [autoselect]: <enter> Perform autoconfiguration? >a: Yes Your host name: foobox Your DNS domain: home.arpa The following are the values you entered. [...] Are they OK? >a: Yes</code></pre>Remote login to the installer</h3> Make this manual installation process easier (i.e. cut-n-paste commands) by remotely logging into the installer via ssh</code> from another computer. Open a shell by selecting >a: Run /bin/sh</code> from the Utilities</code> menu. Set a password for root</code>: passwd</code></pre> Open the sshd_config</code> file for editing using the vi</code> editor: vi /etc/ssh/sshd_config</code></pre> Set permission to allow root</code> to login: PermitRootLogin yes</code></pre> Save changes and exit. Start the sshd</code> daemon: /etc/rc.d/sshd onestart</code></pre> Retrieve the IP address for the active interface configured earlier (example: wm0</code>): ifconfig wm0</code></pre> Switch to the other computer and ssh</code> into the target device: ssh root@[ip_address]</code></pre> …where [ip_address]</code> is the target device’s address obtained with the ifconfig</code> command above. Prepare the DISK</h2> NOTE For the purposes of this HOWTO, the example target device has a single NVMe disk with an existing install of Linux</a> that will be erased and replaced by NetBSD. Device IDs and storage sizes will vary between devices. Identify disks and partitions</h3> Discover what disk devices and partitions have been recognized by the kernel: # sysctl hw.disknames hw.disknames = ld0 dk0 dk1 dk2 dk3 sd0 dk4 dk5</code></pre> NVMe devices show up as ld</code> and hard disks are identified by wd</code>. USB devices usually show up as sd</code>. The dk</code> devices are partitions (know as wedges in NetBSD parlance) on the storage devices, and this early after boot are usually displayed in order, that is: dk0</code> through dk3</code> are wedges on the NVMe target device ld0</code>, and dk4</code> and dk5</code> on the USB installer sd0</code>. Verify by asking for a list of wedges on sd0</code>: # dkctl sd0 listwedges /dev/rsd0: 2 wedges: dk4: EFI system, 262144 blocks at 2048, type: msdos dk5: 30c4cc4e-5369-449c-8994-a4b1ea665b4b, 4853760 blocks at 264192, type: ffs</code></pre> Verify which device the installer booted from: # dmesg | fgrep "root on" [ 4.158650] root on dk5</code></pre>Define DISK variable</h3> The NVMe storage device detected above as ld0</code> is where NetBSD will be installed. Adjust accordingly for your own storage device: DISK="ld0"</code></pre>Wipe DISK</h3> Wipe existing file systems and partition table on DISK: gpt destroy $DISK && gpt show $DISK</code></pre>Partition DISK</h3> NOTE I typically set the swap partition size equal to the amount of physical RAM to a maximum 8g</code>. Create a GPT partition table on DISK with the following layout: Number</th> Size</th> Type</th> Use as</th></tr></thead> 1</td> 550m</td> efi</td> ESP partition</td></tr> 2</td> 6g</td> ffs</td> Root partition</td></tr> 3</td> 8g</td> swap</td> Encrypted swap partition</td></tr> 4</td> ->END</td> cgd</td> Encrypted system partition</td></tr> </tbody></table> Create a new GPT partition table: gpt create -f $DISK</code></pre> Create the wedges: gpt add -l "ESP" -t efi -s 550m $DISK gpt add -l "root" -t ffs -s 6g $DISK gpt add -l "swap" -t swap -s 8g $DISK gpt add -l "syscgd" -t cgd $DISK gpt show $DISK</code></pre>Define wedge variables</h3> List wedges: # dkctl $DISK listwedges /dev/rld0: 4 wedges: dk2: ESP, 524288 blocks at 34, type: msdos dk3: root, 16777216 blocks at 524322, type: ffs dk4: swap, 33554432 blocks at 17301538, type: swap dk5: syscgd, 1902669165 blocks at 50855970, type: cgd</code></pre> NOTE Your dk[number]</code> numbering may differ from above. Adjust accordingly: Define variables: DK_ESP="dk2" DK_ROOT="dk3"</code></pre>Format and mount the ESP wedge</h3> newfs_msdos /dev/r${DK_ESP} && mount /dev/${DK_ESP} /mnt</code></pre>Add EFI boot entries to ESP</h3> mkdir -p /mnt/EFI/boot && cp -v /usr/mdec/*.efi /mnt/EFI/boot</code></pre> Unmount wedge: umount /mnt</code></pre>Format and mount the root wedge</h3> Format and mount the root wedge with the FFSv2</code> file system with support for extended attributes and access control lists: newfs -O 2ea /dev/r${DK_ROOT} && mount /dev/${DK_ROOT} /targetroot</code></pre>Disk Encryption</h2> NetBSD uses the cryptographic device driver</a> (CGD) to create and manage encrypted devices. Create encrypted device</h3> Using cgdconfig</code>, a parameters file is generated that stores the encryption type, key length, and a random password salt for the new encrypted device. There are a few different encryption ciphers supported</a>. I choose aes-xts</code> with a 512-bit key: mkdir -p /targetroot/etc/cgd && chmod 700 /targetroot/etc/cgd cgdconfig -g -V disklabel -o /targetroot/etc/cgd/syscgd aes-xts 512</code></pre> NOTE NAME=syscgd</code> is the label for the CGD wedge created earlier. Create the encrypted device and assign it a passphrase. This passphrase will be used to open the CGD device at boot: cgdconfig -V re-enter cgd0 NAME=syscgd /targetroot/etc/cgd/syscgd</code></pre>Create disklabels</h3> NOTE Disklabels c</code> and d</code> have special meaning in NetBSD</a> and should not be used. Within the encrypted device, three disklabels are created: Disklabel</th> Mountpoint</th> Size</th></tr></thead> cgd0a</td> /var</td> 8G</td></tr> cgd0b</td> /usr</td> 48G</td></tr> cgd0e</td> /home</td> ->END</td></tr> </tbody></table> Create the labels using disklabel</code> in interactive mode: # disklabel -Ii cgd0 Enter '?' for help ...</code></pre> Create cgd0a</code>: partition>a Filesystem type [4.2BSD]: <enter> Start offset ('x' to start after partition 'x') [0c, 0s, 0M]: <enter> Partition size ('$' for all remaining) [947594c, 1940672512s, 947594M]: 8G a: ...</code></pre> Create cgd0b</code>: partition>b Filesystem type [unused]: 4.2BSD Start offset ('x' to start after partition 'x') [0c, 0s, 0M]: a Partition size ('$' for all remaining) [0c, 0s, 0M]: 48G b: ...</code></pre> Create cgd0e</code>: partition>e Filesystem type [unused]: 4.2BSD Start offset ('x' to start after partition 'x') [0c, 0s, 0M]: b Partition size ('$' for all remaining) [0c, 0s, 0M]: $ e: ...</code></pre> Write the label and quit: partition>W Label disk [n]?y Label written partition>Q</code></pre>Verify encrypted device</h3> Set configuration in target device: echo 'cgd0 NAME=syscgd /etc/cgd/syscgd' > /targetroot/etc/cgd/cgd.conf</code></pre> Close the CGD device: cgdconfig -u cgd0</code></pre> Unlock the CGD device again with the passphrase set earlier: cgdconfig cgd0 NAME=syscgd /targetroot/etc/cgd/syscgd</code></pre> The cgd0</code> drive should now be open and the disklabel visible: disklabel cgd0</code></pre>Format and mount disklabels</h3> Format: newfs -O 2ea cgd0a newfs -O 2ea cgd0b newfs -O 2ea cgd0e</code></pre> Mount: mkdir /targetroot/var /targetroot/usr /targetroot/home mount /dev/cgd0a /targetroot/var mount /dev/cgd0b /targetroot/usr mount /dev/cgd0e /targetroot/home</code></pre>Installation</h2> The new system is composed of sets (collections of packages) installed to the target device. These sets are located in /amd64/binary/sets</code>. Move into that directory: cd /amd64/binary/sets && ls</code></pre> NOTE Adding flag p</code> to the tar</code> command is important. It ensures that all files preserve their owners</code> and mode</code>. At a minimum, you must select a kernel and the base</code> and etc</code> sets. Below are the sets I choose to install for a desktop setup: # for set in base comp etc games gpufw kern-GENERIC man misc modules rescue tests text xbase xcomp xetc xfont xserver; do > tar -xvzpf $set.tar.xz -C /targetroot > done</code></pre>Configure the System</h2> Chroot into the freshly installed NetBSD and configure the new OS. Chroot</h3> chroot /targetroot</code></pre>Directories</h3> Create the kern</code> and proc</code> directories: mkdir kern proc</code></pre>Devices</h3> cd dev sh MAKEDEV all</code></pre> On a previous install, after rebooting the boot process halted with the error message: /etc/defaults/rc.conf: cannot create /dev/null: read-only file system /etc/rc: cannot create /dev/null: read-only file system</code></pre> MAKEDEV</code> had created null</code> but it was incorrectly configured: # ls -l /dev/null -rw-r--r-- 1 root wheel 0 Aug 6 14:10 /dev/null</code></pre> To avoid this error, remove the existing null</code>: rm /dev/null</code></pre> Re-create null</code> with mknod</code>: # mknod -m 0666 -u root -g wheel /dev/null c 2 2 && ls -l /dev/null crw-rw-rw- 1 root wheel 2, 2 Aug 6 14:12 /dev/null</code></pre>Root password</h3> passwd</code></pre>Superuser</h3> Create a user account assigned to the wheel</code> and operator</code> groups: useradd -G [groups] -m [username]</code></pre> Example: Create an account for user foo</code> and assign a password: useradd -G wheel,operator -m foo passwd foo userinfo foo</code></pre>Fstab</h3> # cat > /etc/fstab << EOF NAME=root / ffs rw,log,noatime 1 1 NAME=swap none swap sw,dp 0 0 tmpfs /tmp tmpfs rw,-m1777,-sram%25 kernfs /kern kernfs rw ptyfs /dev/pts ptyfs rw procfs /proc procfs rw tmpfs /var/shm tmpfs rw,-m1777,-sram%25 /dev/cgd0a /var ffs rw,log,noatime 1 2 /dev/cgd0b /usr ffs rw,log,noatime 1 2 /dev/cgd0e /home ffs rw,log,noatime 1 2 EOF</code></pre>Startup</h3> Open rc.conf</code> for editing: vi /etc/rc.conf</code></pre> NOTE In this HOWTO, my hostname was earlier set to foobox.home.arpa</code> during network setup, and my wired interface is wm0</code>. Adjust accordingly: # If this is not set to YES, the system will drop into single-user mode. # rc_configured=YES # Add local overrides below. # # Wait for CGD to be unlocked before mounting. critical_filesystems_local="OPTIONAL:/var OPTIONAL:/usr" dhcpcd=YES dhcpcd_flags="-qM wm0" hostname=foobox.home.arpa sshd=YES ntpd=YES ntpdate=YES wscons=YES cgd=YES</code></pre> Save changes and exit. NOTE Any Error: /dev/ttyp0: No such file or directory</code> messages can be safely ignored. Keyboard</h3> A full list of keyboard mappings and variants can be found in wskbd(4)</a>. Set encoding [type_of_keyboard]</code> in wscons.conf</code>. Open file for editing: vi /etc/wscons.conf</code></pre> Example: I use the non-default colemak</code> keymap: encoding us.colemak</code></pre> Save changes and exit. Timezone</h3> Create a symlink to the appropriate timezone for your localtime</code>: ln -sf /usr/share/zoneinfo/[region/<city_or_sub-region] /etc/localtime</code></pre> Example: Set localtime</code> to Canada/Eastern</code>: ln -sf /usr/share/zoneinfo/Canada/Eastern /etc/localtime && date</code></pre>Network interface</h3> ifconfig.if(5)</a> contains the configuration details for each network interface. Example: Create an interface file for the wm0</code> interface that is assigned an IP address via DHCP: # cat > /etc/ifconfig.wm0 << EOF up media autoselect EOF</code></pre>Terminals</h3> Set the status of terminals ttyE1-ttyE3</code> in ttys</code> from off</code> to on</code>. Open file for editing: vi /etc/ttys</code></pre> This is how it should look: # name getty type status comments # console "/usr/libexec/getty Pc" wsvt25 off secure constty "/usr/libexec/getty Pc" wsvt25 on secure ttyE0 "/usr/libexec/getty Pc" wsvt25 off secure ttyE1 "/usr/libexec/getty Pc" wsvt25 on secure ttyE2 "/usr/libexec/getty Pc" wsvt25 on secure ttyE3 "/usr/libexec/getty Pc" wsvt25 on secure</code></pre> Save changes and exit. Finish Up</h2> Exit chroot: exit cd /</code></pre> Unmount: umount /targetroot/home umount /targetroot/usr umount /targetroot/var umount /targetroot</code></pre> Close encrypted device: cgdconfig -u cgd0</code></pre> Reboot system: shutdown -r now</code></pre> NOTE When prompted for the passphrase to unlock the encrypted device, keymap is us qwerty</code> regardless of keymap that might have been set in wscons.conf</code>. User is prompted for the passphrase to unlock the encrypted syscgd</code> device. Upon success, boot resumes: NetBSD/amd64 (foobox.home.arpa) (constty) login: root Password:</code></pre> Welcome to NetBSD! To shutdown/poweroff the system: shutdown -p now</code></pre>Resources</h2> This HOWTO posted by vsis</a> was crucial in getting my own system configured with encryption: NetBSD - UEFI installation with Full Disk Encryption</a></li> Alternative approach for disk encryption using a ramdisk on BIOS boot systems: NetBSD Full-Disk Encryption with CGD (BIOS/GPT)</a></li> NetBSD INSTALL: Installation procedure for NetBSD/amd64</a></li> NetBSD Wiki: Installing NetBSD on a x86 system with UEFI</a></li> NetBSD Guide: Chapter 14. The cryptographic device driver (CGD)</a></li> Suggested tools for inspecting disks: Disk management from Installation ISO</a></li> Skipping sysinst install for a more “hands-on” approach: Manual NetBSD install on GPT/UEFI</a></li> Swap encryption is now automatic using the vm.swap_encrypt=1</code> sysctl(8)</a> variable: Announcing NetBSD 10.0</a></li> </ul> You can like, share, or comment on this post on the Fediverse</a> 💬

Create Public and Private Keys</h2>

Disable Password Logins</h2>

Create an Alias</h2>

Keychain</h2>

Create SSH keys</h2>
Create an SSH public/private key pair to facilitate passwordless logins to remote servers and (optional) configure remote access to the localhost. Read More</a></p>

Permissions</h2>

Resources</h2>

Arch Linux Wiki: libvirt</a></li>
Running VMs with VirtIO 3D Acceleration</a></li> </ul>
You can like, share, or comment on this post on the Fediverse</a> 💬 </p>

Disk Encryption</h2>
NetBSD uses the cryptographic device driver</a> (CGD) to create and manage encrypted devices.</p>

Configure the System</h2>
Chroot into the freshly installed NetBSD and configure the new OS.</p>

Daniel Wayne Armstrong

Configure SSH for Passwordless Logins to FreeBSD Servers

Start Here</h2>

FreeBSD: After the First Boot

Install FreeBSD (Short and Sweet Version)

Virtualization in Debian Using KVM + QEMU + Libvirt

NetBSD 11.0 Installation with Disk Encryption

Daniel Wayne Armstrong

Configure SSH for Passwordless Logins to FreeBSD Servers

Start Here</h2>

On BOTH the CLIENT and the SERVER</h3> Create the .ssh</code> directory and authorized_keys</code> file in $HOME</code>:</p>

Create Public and Private Keys</h2>

On the CLIENT</h3> Create the SSH public/private key pair (example: ed25519</code>) protected with a passphrase:</p>

Share Public Key</h2>

On the CLIENT</h3> Upload the public key to the SERVER and append to the authorized_keys</code> file:</p>

Disable Password Logins</h2>

Create an Alias</h2>

Keychain</h2>

FreeBSD: After the First Boot

Package management</h2> Package management is one area where the differences between the Linux philosophy and the BSD philosophy about how to build a system becomes apparent.</p>

Alias for root mail</h2> Rather than login to root to collect system mail, I forward the root user’s mail to my non-root user’s inbox.</p> Open the aliases</code> file for editing:</p>

Message of the day</h2> To slim down the “message of the day” (motd(5)</code>) output after logging into the system, displaying only the Last login</code> and FreeBSD version info:</p>

Clear system console at logout</h2> For the fish</code> shell I modify config.fish</code>:</p>

Install FreeBSD (Short and Sweet Version)

Installation</h2> Boot target device from the install media. In the FreeBSD Boot Menu</strong> press <Enter></code> to launch the installer.</p> </p>

Virtualization in Debian Using KVM + QEMU + Libvirt

Permissions</h2>

qemu.conf</h3> For storage file permissions, modify /etc/libvirt/qemu.conf</code> by setting user</code> to my username (example: foo</code>) and group</code> to libvirt-qeumu</code>:</p>

Resources</h2> Arch Linux Wiki: libvirt</a></li> Running VMs with VirtIO 3D Acceleration</a></li> </ul> You can like, share, or comment on this post on the Fediverse</a> 💬 </p>

NetBSD 11.0 Installation with Disk Encryption

Disk Encryption</h2> NetBSD uses the cryptographic device driver</a> (CGD) to create and manage encrypted devices.</p>

Configure the System</h2> Chroot into the freshly installed NetBSD and configure the new OS.</p>

Resources</h2>

Arch Linux Wiki: libvirt</a></li>
Running VMs with VirtIO 3D Acceleration</a></li> </ul>
You can like, share, or comment on this post on the Fediverse</a> 💬 </p>

Disk Encryption</h2>
NetBSD uses the cryptographic device driver</a> (CGD) to create and manage encrypted devices.</p>

Configure the System</h2>
Chroot into the freshly installed NetBSD and configure the new OS.</p>