Based on tests on my machine (2013 MacBook Pro, 2.6 GHz i7, 16 GB RAM) generated by https://github.com/pragdave/map_performance
Elixir v1.0.4
| #!/usr/bin/env bash | |
| # You can call this script like this: | |
| # $ ./volumeControl.sh up | |
| # $ ./volumeControl.sh down | |
| # $ ./volumeControl.sh mute | |
| # Script modified from these wonderful people: | |
| # https://github.com/dastorm/volume-notification-dunst/blob/master/volume.sh | |
| # https://gist.github.com/sebastiencs/5d7227f388d93374cebdf72e783fbd6a |
| #!/usr/bin/bash | |
| #source: https://gist.github.com/Blaradox/030f06d165a82583ae817ee954438f2e | |
| id=5555 | |
| function get_brightness { | |
| xbacklight -get | cut -d '.' -f 1 | |
| } |
Based on tests on my machine (2013 MacBook Pro, 2.6 GHz i7, 16 GB RAM) generated by https://github.com/pragdave/map_performance
Elixir v1.0.4
| #!/bin/bash | |
| #Beta 4 to Final Public Release (Must be run in Recovery Mode) | |
| csrutil disable | |
| #Beta 1-3 | |
| sudo nvram boot-args="rootless=0";sudo reboot |
| #!/bin/bash | |
| sudo apt-get update | |
| sudo apt-get -y install linux-image-extra-$(uname -r) | |
| sudo sh -c "wget -qO- https://get.docker.io/gpg | apt-key add -" | |
| sudo sh -c "echo deb http://get.docker.io/ubuntu docker main\ > /etc/apt/sources.list.d/docker.list" | |
| sudo apt-get update | |
| sudo apt-get -y install lxc-docker |
| package main | |
| import ( | |
| "fmt" | |
| "math/big" | |
| "runtime" | |
| ) | |
| func main() { | |
| runtime.GOMAXPROCS(runtime.NumCPU()) |
| ------------------------------------ | |
| .git/config | |
| ------------------------------------ | |
| [diff] | |
| tool = ksdiff | |
| [difftool "ksdiff"] | |
| cmd = ksdiff \"$LOCAL\" \"$REMOTE\" | |
| ------------------------------------ |
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
To audit memory or to debug with external tools it can be useful to get a dump of the running memory of an app.
To do so on a device you'll need a Jailbreak, SSH access, and gdb. See this or this.
If instead you're up to a simulated app, things are easier: apps running in the simulator are actually just native processes on your Mac OS X.
So, how to get a core dump of a Mac OS X process? Sadly gdb can't do so. Mac OS X Internals comes to the rescue with this article.