Since I could not find a quickstart to run opengrep with the full set of rules from their fork I thought I'd document what I found out. Setup Download the opengrep binary from github and make it executable with chmod +x . Clone the rules repo: git clone git@github.com:opengrep/opengrep-rules.git and clean it up to make it usable to opengrep: cd opengrep-rules rm -rf ".git",".github",".pre-commit-config.yaml", "elixir", "apex" find . -type f -not -iname "*.yaml" -delete rm -rf .github rm -rf .pre-commit-config.yaml Ensure opengrep can load the rules with: opengrep_manylinux_x86 validate . The same can be done for custom rules maintained in a separate repository. AFAIU Multiple repositories can be specified by repeating -f option as needed, see below. We are now ready to scan a repo, from the repo root directory run: opengrep_manylinux_x86 scan \ -f <path_to>/opengrep-rules \ --error \ --exclude-rule=VAL some ti...
The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive. Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive from the same removable disk.
Preparation of updates for Peugeot cars is supported on OSX, but will fail consistently because OSX adds metadata folders and files to the update sub-folders causing a checksum failure on the car. The following commands, ran after a new version of the software or maps has been downloaded and before plugging the stick in the car reliably solved the issue for me: sudo mdutil -X /Volumes/NEW sudo mdutil -i off /Volumes/NEW cd /Volumes/NEW sudo rm -rf System\ Volume\ Information sudo find . -name "._*" -delete sudo rm -rf .fseventsd sudo rm -rf .Spotlight-V100 sudo find . -name ".DS_Store" -delete BTW, the Peugeot update app is still an Intel app which means it will stop working soon .