scyto

Enable Dual Stack (IPv4 and IPv6) OpenFabric Routing

this gist is part of this series

This assumes you are running Proxmox 8.2 and that the line source /etc/network/interfaces.d/* is at the end of the interfaces file (this is automatically added to both new and upgraded installations of Proxmox 8.2).

This changes the previous file design thanks to @NRGNet for the suggestions to move thunderbolt settings to a file in /etc/network/interfaces.d it makes the system much more reliable in general, more maintainable esp for folks using IPv4 on the private cluster network (i still recommend the use of the IPv6 FC00 network you will see in these docs)

This will result in an IPv4 and IPv6 routable mesh network that can survive any one node failure or any one cable failure. Alls the steps in this section must be performed on each node

mutin-sa

Google Public NTP [AS15169]:

time.google.com

time1.google.com

time2.google.com

time3.google.com

dentechy

How to automatically start ssh server on boot on Windows Subsystem for Linux

Microsoft partnered with Canonical to create Bash on Ubuntu on Windows, running through a technology called the Windows Subsystem for Linux. Below are instructions on how to set up the ssh server to run automatically at boot.

1. Edit the /etc/ssh/sshd_config file by running the command sudo vi /etc/ssh/sshd_config and do the following
   1. Change Port to 2222 (or any other port above 1000)
   2. Change PasswordAuthentication to yes. This can be changed back to no if ssh keys are setup.
2. Restart the ssh server:
   • sudo service ssh --full-restart
3. With this setup, the ssh server must be turned on every time you run Bash on Ubuntu on Windows, as by default it is off. Use this command to turn it on:

Te-k

000stthk.exe|Toshiba Hotkey Configuration|NONE
007ssinstall.exe|007 Spy Software|NONE
00thotkey.exe|Toshiba Keyboard Helper|NONE
123downloadsuk[1].exe|123Mania Hijacker|NONE
12popup.exe|12Ghosts Popup-Killer|NONE
153.exe|??? Dialer.W32.153 ???|MALICIOUS_SOFTWARE
180sainstalleradperform.exe|180Solutions Zango|NONE
180sainstallernusac.exe|180SearchAssistant|NONE
1xconfig.exe|SCM MicroSystems Helper|NONE
2portalmon.exe|2wSysTray|NONE

mitchellkrogza

#!/bin/bash

# Bash Script by https://gist.github.com/mitchellkrogza
# ************************************************************
# This script clears the log file and database of Fail2Ban
# This resets Fail2Ban to a completely clean state
# Useful to use after you have finished testing all your jails 
# and completed your initial setup of Fail2Ban and are now
# putting the server into LIVE mode
# ************************************************************

fljot

<!-- put this to IDEA keymaps config folder. For v13 it is <userdir>\.IntelliJIdea13\config\keymaps\ -->
<?xml version="1.0" encoding="UTF-8"?>
<keymap version="1" name="Mac OS X 10.5+ Windows Ctrl" parent="Mac OS X 10.5+">
  <action id="$Copy">
    <keyboard-shortcut first-keystroke="meta C" />
    <keyboard-shortcut first-keystroke="meta INSERT" />
    <keyboard-shortcut first-keystroke="control C" />
    <keyboard-shortcut first-keystroke="control INSERT" />
  </action>
  <action id="$Cut">

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

andsens

#!/bin/sh
## backup each mysql db into a different file, rather than one big file
## as with --all-databases. This will make restores easier.
## To backup a single database simply add the db name as a parameter (or multiple dbs)
 
## Putting the script in /var/backups/mysql seems sensible... on a debian machine that is
## Create the user and directories
# mkdir -p /var/backups/mysql/databases
# useradd --home-dir /var/backups/mysql --gid backup --no-create-home mysql-backup
## Remember to make the script executable, and unreadable by others