Firmware available here for both devices.
BCM Board ID | 96345 |
---|
Firmware available here for both devices.
BCM Board ID | 96345 |
---|
This is a cheat sheet for how to perform various actions to ZSH, which can be tricky to find on the web as the syntax is not intuitive and it is generally not very well-documented.
Description | Syntax |
---|---|
Get the length of a string | ${#VARNAME} |
Get a single character | ${VARNAME[index]} |
/* Allow members in 'wheel' to use machinectl without password authentication | |
* | |
* Thanks to the followings: | |
* - https://unix.stackexchange.com/a/595725 | |
* - https://wiki.archlinux.org/index.php/Polkit#For_specific_actions | |
*/ | |
polkit.addRule(function(action, subject) { | |
if ( | |
( |
/** | |
* MIT No Attribution | |
* | |
* Copyright 2020-2024 Anna Zhukova | |
* | |
* Permission is hereby granted, free of charge, to any person obtaining a copy of this | |
* software and associated documentation files (the "Software"), to deal in the Software | |
* without restriction, including without limitation the rights to use, copy, modify, | |
* merge, publish, distribute, sublicense, and/or sell copies of the Software, and to | |
* permit persons to whom the Software is furnished to do so. |
#!/usr/bin/perl | |
use strict; | |
sub deswappify { | |
my $pid = shift; | |
my $fh = undef; | |
my $start_addr, $end_addr; | |
if(open F, "/proc/$pid/smaps") { |
The purpose of this gist is to set up a virtual machine in such a way that the on-disk image in the host machine automatically grows and shrinks as needed by the guest machine. This utilizes the (still undocumented) "--discard" and "--nonrotational" parameters in "VBoxManage storageattach" which make the attached image appear as an SSD to the guest. Guest OS will then issue TRIM commands to the virtual controller where such an image is attached. VirtualBox is then able to capture the commands and punch holes in the attached VDIs.
Although there is some initial setup needed, I think the time saved with babysitting the VDIs is worth it. Usually you would need to zero out the free space with zerofree or sdelete and then run "VBoxManage --compact" on your images. With this setup you can allocate a large dynamic VDI (1TB or so) and it will keep itself at minimum size for easy syncing, backup, etc. You can also set it up in a template machine if you use one for clones etc.
Either copy the aliases from the .gitconfig
or run the commands in add-pr-alias.sh
Easily checkout local copies of pull requests from remotes:
git pr 4
- creates local branch pr/4
from the github upstream
(if it exists) or origin
remote and checks it outgit pr 4 someremote
- creates local branch pr/4
from someremote
remote and checks it out