Base URL:
http://169.254.169.254/latest/
- meta-data/
ami-idinstance-id
| # on the linux host | |
| sudo docker run -it --rm -p 445:445 -v "$PWD":/shared dperson/samba -s "temp-share;/shared;yes;no;yes;all;all;all" -p | |
| # in windows | |
| net use D: \\<yourip>\temp-share | |
| # in case windows is yappin about guest security | |
| Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" -Name "AllowInsecureGuestAuth" -Value 1 |
| # put this into /etc/vimrc (bottom, top sometimes does not work) | |
| inoremap jk <Esc> |
Base URL:
http://169.254.169.254/latest/
ami-idinstance-idIf you need to manually control (silence) the fans of a HPE Proliant Gen8/9 servers with iLO 4 follow these steps:
sudo modprobe -r hpilo.sh ./CP027911.scexe --unpack=ilo_250
cd ilo_250Latest ams do not work as expected with old Gen8 (iLO 4) servers.
Install the one from focal and install outdated dependencies:
curl https://downloads.linux.hpe.com/SDR/hpePublicKey2048_key1.pub | gpg --dearmor -o /etc/apt/trusted.gpg.d/hpe-key.gpg
echo "deb https://downloads.linux.hpe.com/SDR/repo/mcp focal/current non-free" > /etc/apt/sources.list.d/hpe-mcp.list
wget http://security.ubuntu.com/ubuntu/pool/main/j/json-c/libjson-c4_0.13.1+dfsg-7_amd64.deb| # Work in progress for finding the ultimate keyboard repeat rate for extrem speed. | |
| xset r rate 150 20 |
Install kdenlive, movit and rtaudio:
s pacman -S kdenlive movit rtaudioManually compile mlt shared libs (this should now detect and link against movit and rtaudio):
yay -S mlt-gitInstall starship, kitty and nerd font
yay -S starship kitty ttf-firacode-nerdSet starship as default shell
echo 'eval "$(starship init bash)"' >> ~/.bashrcGenerate a certificate signing request (this generates the privkey.pem and includes the public key in the csr):
openssl req -new -nodes > req.csrThen convert the public key to a public certificate and sign it with its own private key.
openssl x509 -req -in req.csr -signkey privkey.pem -out cert.pemIf you want to use multiple aws accounts over one sso login, the local setup looks like this:
Configure sso sessions using the --profile flag to generate a profile associated with the session:
aws configure sso --profile MyProfile-ProdCreate a session and give it a locally unique name (e.g. 'prod').