sudo snap remove --purge firefox
sudo snap remove --purge snap-store
sudo snap remove --purge snapd-desktop-integration
sudo snap remove --purge gtk-common-themes
sudo snap remove --purge gnome-3-38-2004
sudo snap remove --purge core20
sudo snap remove --purge bare
sudo snap remove --purge snapd
# Step 1 -> get wgcf (cli for Cloudflare WARP) | |
https://github.com/ViRb3/wgcf/releases | |
# Step 2 -> create account -> wgcf-account.toml | |
wgcf register | |
# Step 3 -> generate WireGuard profile -> wgcf-profile.conf | |
wgcf generate | |
# Step 4 -> extract values from wgcf-profile.conf |
""" | |
Test cloudflare WARP endpoints | |
Select all the best WARP endpoints | |
Thanks to https://gitlab.com/Misaka-blog/warp-script#warp-endpoint-ip-优选脚本 | |
""" | |
import asyncio | |
import csv | |
import ipaddress | |
import logging |
# To prevent repository packages from triggering the installation of Snap, | |
# this file forbids snapd from being installed by APT. | |
# For more information: https://linuxmint-user-guide.readthedocs.io/en/latest/snap.html | |
Package: snapd | |
Pin: release a=* | |
Pin-Priority: -10 |
# MSI laptop random screen brightness bug | |
# https://askubuntu.com/questions/777754/brightness-randomly-up-and-down-on-msi-laptop/808785#808785 | |
Section "InputClass" | |
Identifier "Spooky Ghosts" | |
MatchProduct "Video Bus" | |
Option "Ignore" "on" | |
EndSection |
This is a brief guide on how to configure an SSH reverse tunnel that automatically establishes on boot and will continuously attempt to re-connect when it fails.
It is very useful if you are deploying a device somewhere without a public IP, e.g. behind a NAT, and need to be able to SSH into it from the wider internet.
Let's refer to the NAT'ed device as the client. This guide assumes that the client is able to create outgoing SSH connections to at least destination port 443.
You will need root access to a server with a static IP on the internet which runs an openssh server.
On my-server.example.com
add the following to /etc/ssh/sshd_config
, changing tunnel-user
to whichever username you want to use (this will be a new user, not an exising user) and changing the PermitOpen
line:
There is good news for you. I made a new repository with a single Dockerfile to build every combinations of versions of Ubuntu LTS and gcc you like
Find out more on https://github.com/alexandreelise/install-gcc
server: | |
module-config: "subnetcache validator iterator" | |
chroot: "/usr/local/etc/unbound" | |
directory: "/usr/local/etc/unbound" | |
username: "unbound" | |
port: 5353 | |
do-ip4: yes | |
do-ip6: no | |
do-udp: yes | |
do-tcp: yes |
You can use ssacli
(smart storage administrator command line interface) tool to manage any of supported HP Smart Array Controllers in your Proxmox host without need to reboot your server to access Smart Storage Administrator in BIOS. That means no host downtime when managing your storage.
CLI is not as convenient as GUI interface provided by BIOS or desktop utilities, but still allows you to fully manage your controller, physical disks and logical drives on the fly with no Proxmox host downtime.
ssacli
replaces older hpssacli
, but shares the same syntax and adds support for newer servers and controllers.
Before starting, make sure you have a backup, and make sure to have a linux live boot ready to rescue your system. It's easy to mess this up!
- Use gdisk to convert the partition table to GPT.
gdisk /dev/sda
- Create the "BIOS boot" partition that GRUB needs.
n
to create a new partition. Needs to be about 1MB. You can probably squeeze this in from sectors 34-2047. UseL
orl
to look up the code for "BIOS boot" (ef02). - Write the new partition table.
w
- Reload the partition table.
>
partprobe /dev/sda