One-liner to find the Linux systemd "predictable name" of a hardware network device like the embedded ethernet card on a desktop motherboard.
udevadm test-builtin net_id /sys/class/net/eth0 | grep '^ID_NET_NAME_'
Answer by "GnP" in this post.
One-liner to find the Linux systemd "predictable name" of a hardware network device like the embedded ethernet card on a desktop motherboard.
udevadm test-builtin net_id /sys/class/net/eth0 | grep '^ID_NET_NAME_'
Answer by "GnP" in this post.
The assumption here is that you're now starting with a Ubuntu 22.04 LTS Server or newer, rather than Desktop, base (Ubuntu Desktop deploys NetworkManager rather than systemd-networkd by default). This box has an AMD Ryzen CPU.
The goal is networking configured for static addressing using systemd-networkd and netplan. Note that punctuation (including hypens, '-') and indentation are significant when working with netplan YAML files.
There are a lot good arguments against using netplan. I have tried NetworkManager (packages named "network-manager", but the service is "NetworkManager.service" -- go figure) on Ubuntu Server, and was
The built-in DHCP server (based on dnsmasq) included with KVM (libvirtd) has limited configuration options compared to other DHCP servers like the one published by ISC, but it can be set up to specify a search domain for clients.
Edit the network configuration using virsh. The examples below assume configuration will be of a network named "default" (by default this is the first network set up by libvirtd).
$ virsh net-edit default
Sometimes you just have to make sure that anything going to an old site winds up on a designated page over at the new.
RewriteEngine On
RewriteRule /.* https://new.example.com/newhome [R=301,L]
The foward slash dot star is what makes this redirect matching rule the most greedy of all. The "R=301" flag forces an external redirect (to another host) and tells the browser it is permanent. The "L" flag marks this as the end of the rewriting process.
Model used: Dell Inspiron 3181 (11" screen)
This can be done any time, but it's probably a best practice to create a backup on initial install and update occasionally afterwards.
This procedure uses utiltiies in the acl package, which should be installed by default.
To backup:
$ cd /
$ sudo getfacl -R . >/tmp/root-perms.txt
Debian or Kali Linux installed to as KVM (libvirtd) guests do not automatically have qemu-guest-agent or spice-vdagent installed. This will prevent seamless movement of the mouse cursor between the guest and host desktop in Virtual Machine Manager (requiring the use of a Ctrl-Alt to release the cursor from the guest window).
To cure this, install both qemu-guest-agent and spice-vdagent on each guest and reboot (the guests).
$ sudo apt install qemu-guest-agent
$ sudo apt install spice-vdagent
Notes on setting up Sublime Text.
$ wget -qO - https://download.sublimetext.com/sublimehq-pub.gpg | sudo apt-key add -
$ sudo apt-get install apt-transport-https
$ echo "deb https://download.sublimetext.com/ apt/stable/" | sudo tee /etc/apt/sources.list.d/sublime-text.list
$ apt update
Most of the guests I use for testing are desktop machines created using the graphical virt-manager tool. These have a single partition virtio disk that's formatted ext4 when Linux, without LVM. This is the procedure I follow to grow the disk when more space is needed:
$ sudo qemu-img resize myguest.qcow2 +20G