View command.md

This command will find all the files of the given extensions in the current directory recursively, print the output to console and also write it to list_of_hidden_files file in the current directory:

find . -regextype posix-extended -regex ".*\.(EXTENSIONS)" | tee list_of_hidden_files 

where EXTENSION can be any regex expression:

For example to look for .docx, doc, and odt just replace extensions for:

View gist:e636e8cc095651580a1230673ede603e
### Keybase proof
I hereby claim:
* I am chibby0ne on github.
* I am chibby0ne (https://keybase.io/chibby0ne) on keybase.
* I have a public key whose fingerprint is EA67 1980 505E B9D6 7D8E 5399 9292 84BA BCCF F39D
To claim this, I am signing this object:
View dep.md

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

View dep.md

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

View instructions.md

If you run

dep init

On a project for vendoring its dependencies, the versions choosen by dep for some of the dependencies might not be all that recent or if they are they might not be the versions that you want.

How do you manually change the versions then?

View gist:be7d4512f60f8bb42a8f00fa3e650b22
To make minicom use the entire terminal window, after sessions has started check that the terminal emulation is set to ANSI.
For this you need to press:
Ctrl-A Z for help
In the menu that appears select Terminal settings by pressing 't' key.
Then in that menu press 'a' To switch Terminal Emulation. By default minicom uses VT102 which only uses a small portion of the screen.
View gist:0a7d459a437dfe09b6f32f6a729fda51

To verify a shasum or any other integrity hash, from a website that hosts a file with its shasum, you would normally take the following approach:

  1. Download the file and its SHASUMS file and place both of these files in the same directory
  2. run sha256sum -c SHASUMS

If the file integrity is intact then it would output:

filename: OK

But what if you only have the file and the shasum and no file? Case in point: Downloading boost libraries from official website

View RaspberryPi 3 Retropie OS Wifi using DHCP with DNS and Gateway in different devices
The main three things are these:
1. Inside /etc/network/interfaces:
The wifi interface should be set as dhcp as have the usual settings for using wpa_conf
2. Inside /etc/dhcpcd.conf:
Disable ipv6
Add the the gateway (router) as static routers=...
3. Create a file /etc/sysctl.d/40-ipv6.conf, where you disable ipv6 for all AND for each interface
(more info about ipv6 disabling in https://wiki.archlinux.org/index.php/IPv6#Disable_IPv6)
View gist:ad576b3a360b7b898acb69246b8fc053
There are 3 ways of disabling power save on the Raspberry Pi 3 depending on how you wifi is configured:
1. Configured using NetworkManager
Follow this gist: https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55
2. Configured using Command Line editing `/etc/network/interface`
The accepted known method is to add the following line *AFTER* the setting up of the interface
View listdirs.sh
#!/bin/bash
find -maxdepth 1 -type d -print | grep -v \\.