podman pod create \
--name YOUR_POD_NAME \
-p 8080:8080
# podman Cheat Sheet | |
**create a pod** | |
``` | |
podman pod create --name=my-pod | |
``` | |
**create a container in a pod** |
# Delete System User on Ubuntu | |
**kill active sessions** | |
``` | |
sudo loginctl disable-linger [USER] | |
sudo loginctl terminate-user [USER] | |
``` | |
**delete user and remove home directory** |
After creating a machine and BEFORE starting the machine with the ISO, make the following changes:
cd "C:\Program Files\Oracle\VirtualBox\"
.\VBoxManage modifyvm "macOS Monterey" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
.\VBoxManage setextradata "macOS Monterey" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1"
.\VBoxManage setextradata "macOS Monterey" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
.\VBoxManage setextradata "macOS Monterey" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278895"
.\VBoxManage setextradata "macOS Monterey" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
.\VBoxManage setextradata "macOS Monterey" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
pv FILE.tar.gz | tar -xz
Hey student,
Big O notation is a complex concept to grasp, but ironically, the point of it is actually to try simplify the description of your code! The way I like to think about Big O notation is to think about the number of lines of code that have to be executed with extremely large inputs and to visualize what this actually looks like. This is probably better explained with some examples (look along with this image: https://apelbaum.files.wordpress.com/2011/10/yaacovapelbaumbigoplot_thumb.jpg):
def get_value(elements, index):
return elements[index]
This is O(1) (gray line) because no matter how big the elements
array is and no matter what the index
value is (assuming it's valid), the time to execute the code will always be the same.