LUKS2 encrypted BTRFS system partition with Limine/Snapper integration and hybernate to swapfile
| Windows Registry Editor Version 5.00 | |
| [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\BraveSoftware] | |
| [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\BraveSoftware\Brave] | |
| "BraveAIChatEnabled"=dword:00000000 | |
| "BraveRewardsDisabled"=dword:00000001 | |
| "BraveVPNDisabled"=dword:00000001 | |
| "BraveWalletDisabled"=dword:00000001 |
To start, read the official release notes.
If your system is "vanilla Debian plus maybe a handful of 3rd-party repos", then this guide for a simple upgrade to Debian 13 "trixie" from Debian 12 "bookworm" can be helpful. 3rd-party repos are handled with a find command.
If you are on a fork of Debian such as RasPI OS, use their instructions, not this gist.
Note upgrade is only supported from Debian 12 to Debian 13. If you are on Debian 11, upgrade to Debian 12 first. Then once on Debian 12, you can upgrade to Debian 13.
The maintained version now lives at Enable & Using vGPU Passthrough, part of scyto/homelab-docs.
Questions or troubleshooting? Continue the conversation here — a Q&A discussion where replies thread properly, answers can be marked, and everything is searchable. The 188 comments below stay exactly where they are as an archive.
The maintained version now lives at ProxMox Cluster - Soup-to-Nutz, part of scyto/homelab-docs.
Questions or troubleshooting? Continue the conversation here — a Q&A discussion where replies thread properly, answers can be marked, and everything is searchable. The 51 comments below stay exactly where they are as an archive.
| # This file contains pin mappings and other defaults for the Weefun/Weedo | |
| # Tina2s based on the GD32F103. It won't work with the ATMega-bsed | |
| # Tina/Tina wifi/monoprice cadet. | |
| # The biggest issue with this printer is that the USB-serial CH340G's DTR pin | |
| # is tied to reset with a 1k resistor - not a capacitor circuit like most. | |
| # restart_method of 'tina2s' was added to make sure DTR is held high during | |
| # normal operation | |
| # Pins were found in https://github.com/weedo3d/TINA2Sfirmware and confirmed |
| #!/usr/bin/env bash | |
| ##################################################################### | |
| # REFERENCES | |
| # - https://cloud.google.com/compute/docs/oslogin/manage-oslogin-in-an-org | |
| # - https://cloud.google.com/compute/docs/instances/managing-instance-access#configure_users | |
| # - https://cloud.google.com/iam/docs/configuring-resource-based-access | |
| # - https://cloud.google.com/iap/docs/using-tcp-forwarding#grant-permission | |
| # - https://cloud.google.com/iap/docs/audit-log-howto | |
| # - https://cloud.google.com/compute/docs/oslogin/view-audit-logs#view-logs |
- Make an install directory somewhere convenient and switch to it
mkdir -p ~/.local/share/authy
cd ~/.local/share/authy
- Fetch the current Authy snap
- Figure out how to set up 1 global hotkey in your chosen desktop environment,
- Assign to it some simple dummy target ommand. Which you know always works. And is easily verified
That will ensure you can check and test that a specific hotkey assignment is actually definately working independantly of the specific desired action. This is important because the desktop environment can also occupy pre-configured 'system keys' and if they are already being mapped to something other default system wide actions then (likely) will silently be ignored.
So being independant here from the subsequent specific desired target actions in some special app or whatever. Which themselves definately might have other own different issues or not behave correctly. And especially when being invoked from the compositor via this method (rather than a logged in user terminal etc.)