| from zipfile import ZipFile | |
| import csv | |
| import os | |
| def find_file(): | |
| for file in os.listdir("./"): | |
| if file.endswith(".zip"): | |
| return file |
Scan for access points (run multiple times for more complete scan):
# connmanctl scan wifi
Scan completed for wifi
I hereby claim:
To claim this, I am signing this object:
| From: https://www.jeffgeerling.com/blogs/jeff-geerling/controlling-pwr-act-leds-raspberry-pi | |
| March 15, 2015 | |
| All Raspberry Pi models have a few built-in LEDs; the earlier models had PWR, ACT, and networking status LEDs all lined up on the board itself; for the B+ and model 2 B, the networking LEDs moved onto the network jack itself, leaving just two LEDs; PWR (a red LED) and ACT (a green LED). | |
| Normally, whenever the Pi is powered on—except if the power supply dips below something like 4.5VDC—the red PWR LED remains lit no matter what. If you wanted to 'disable' the LED, you'd have to put a piece of tape or something else over the LED, or get out a soldering iron and modify the hardware a bit. | |
| Raspberry Pi model 2 B, B+ and A+ | |
| Luckily, with the Pi 2 model B, B+, A+, and Zero, you can control the LEDs in software, in a few different ways. The simplest way to change the way these LEDs work is to modify the trigger for each LED by setting it in /sys/class/leds/led[LED_ID]/trigger, where you replace [LED_ID] wi |
| From: https://blog.lobraun.de/2015/06/06/mount-sd-cards-within-virtualbox-on-mac-os-x/ | |
| Mount SD Cards within VirtualBox on Mac OS X | |
| Sometimes you need to mount your SD cards inside a VirtualBox machine to work with the files on the card. Working with the Raspberry Pi SD card on Mac OS X is an example for this. | |
| My Raspberry Pi runs on Linux with some version of the EXT file system. While there is some support for this on Mac OS X, the available solutions have a lot of limitations, especially when it comes to write support on EXT file systems. As I do not have an USB keyboard, I sometimes need to mount the filesystem on another system to fix a startup problem when some of my experiments go wrong. | |
| VirtualBox in theory allows for passing the internal card reader of the MacBooks to the virtual machine. Unfortunately, this does not work for me (and it seems for many other people). |
| from https://ncona.com/2011/07/how-to-delete-a-commit-in-git-local-and-remote/ | |
| It has happened to me more than once that I make a commit without verifying the changes I am committing. Time after that I review the commit and I notice that there is something in the commit that doesn’t belong there. | |
| In those times what I want to do is make a patch with the changes of the commit, delete the commit, apply the patch and then redo the commit only with the changes I intended. In this post I will only explain how to delete a commit in your local repository and in a remote repository in case you have already pushed the commit. | |
| Delete a local commit | |
| Anthony Dentinger showed me in the comments that you can delete a local commit by doing: | |
| git reset –hard HEAD~ |
| 1. Copy system upgrade file to main directory of Kindle. | |
| 2. Disconnect Kindle from computer. | |
| 3. Go to the main menu, settings, device options, update your kindle. | |
| 4. After the update/restart plug the kindle back into the computer | |
| 5. Copy Screensaver and Python update files into the mrpackages folder and eject kindle | |
| (Files can be found here: https://www.mobileread.com/forums/showthread.php?t=225030) | |
| 6. enter `;log mrpi` into the search box. | |
| OR | |
| 6. install the packages via KUAL if that is working. |
| ### 1. Clone your fork: | |
| git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git | |
| ### 2. Add remote from original repository in your forked repository: | |
| cd into/cloned/fork-repo | |
| git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git | |
| git fetch upstream |
source: https://savedlog.com/uncategorized/letsencrypt-ssl-certificate-namecheap-hosting/
The “Positive SSL” certificate I bought along with my domain is invalid with any of my subdomains and cannot be used with wildcards. One annoying thing is that namecheap doesn’t offer auto installation of free let’s encrypt certificates, even though, they are saying “Namecheap is dedicated to data security and privacy for all internet users. We believe the movement to encrypt nearly all web traffic is a positive direction. As more sites embrace HTTPS and use of security products, providers of free SSL are beginning to come online.”
Let me show you what it needs to be done in order to “encrypt nearly all web traffic”.
First, not required but it’s helpful to enable ssh access, it is not enabled by default on the base hosting plans, just go an start a live chat and request ssh access.