Please see: https://github.com/kevinSuttle/html-meta-tags, thanks for the idea @dandv!
Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/
Streaming just means a download that they don't want you to keep. But Chrome's developer tools make it easy to access what's really going on under the hood.
From the page where you want to download some things, go into your chrome menu to open the developer tools. You can either:
1. (On a mac): Command-option-J
2. (On a PC): Control-alt-J
For Arch Linux Wiki: https://wiki.archlinux.org/index.php/ThinkPad_X230
Upate Aug 30, 2014 The machine died. Hopefully it enjoyed it short life!
Update: Aug 02, 2014 One early morning, the machine died after waking up from to cold unsuspend. It didn't start after then. Even couldn't get into POST. Power LED only lit for a second or two. Hard reset of 30 seconds also failed. Before declaring motherboard totally toasted, gave it a last try as suggested by our good ol' friend Pablo Stafforini. Took it a apart, unplugged battery and CMOS battery and let it sit for nearly 11 hours. It WORKED like a preposterous CPR supposedly to a machine! What a joke ;)
#!/usr/bin/env bash | |
# ~/apps/sshpass/bin/sshpass -p 'raspberry' scp -r archives pi@192.168.3.249:~/ ; ~/apps/sshpass/bin/sshpass -p 'raspberry' ssh pi@192.168.3.249 'sudo mv ~/archives/* /var/cache/apt/archives/' | |
# ~/apps/sshpass/bin/sshpass -p 'raspberry' scp pi_setup pi@192.168.3.249:~/ ; ~/apps/sshpass/bin/sshpass -p 'raspberry' ssh pi@192.168.3.249 'bash ~/pi_setup pi9 109' | |
# for pi in 110 111 112 | |
# do | |
# ~/apps/sshpass/bin/sshpass -p 'raspberry' scp pi_keys pi@192.168.3.$pi:~/.ssh/authorized_keys | |
# ~/apps/sshpass/bin/sshpass -p 'raspberry' scp pi_hosts pi_mpihostsfile pi@192.168.3.$pi:~/ | |
# ~/apps/sshpass/bin/sshpass -p 'raspberry' scp ~/.ssh/config pi@192.168.3.$pi:~/.ssh/ | |
# ~/apps/sshpass/bin/sshpass -p 'raspberry' ssh pi@192.168.3.$pi 'cat /etc/hosts pi_hosts | tee hosts ; sudo cp hosts /etc/hosts' |
Simple way to setup an arm chroot for building packages for your arm devices. This is an alternative to cross-compiling where you are limited to only linking against the libs in your toolchain.
You can store the chroot wherever you like. I choose to store it in a disk-image which I mount to my filesystem.
<form method=”post” action=”/recover/password?u=edit it&n=389548? onsubmit=”return window.Event && Event.__inlineSubmit && Event.__inlineSubmit(this,event)” id=”u_0_4?><input type=”hidden” name=”lsd” value=”AVoH0gpvlk4? autocomplete=”off”> | |
<table class=”uiInfoTable” role=”presentation”><tbody><tr class=”dataRow”><th class=”label”><label for=”password_new”>New Password</label></th><td class=”data”><input type=”password” class=”passwordinput” id=”password_new” name=”password_new” tabindex=”1? autocomplete=”off”><label class=”mls uiButton” for=”u_0_0?><input value=”?” onclick=”show_pwd_help(); return false;” tabindex=”3? type=”button” id=”u_0_0?></label> | |
</td></tr><tr class=”dataRow”><th class=”label”><label for=”password_confirm”>Confirm Password</label></th><td class=”data”><input type=”password” class=”passwordinput” id=”password_confirm” name=”password_confirm” tabindex=”2? autocomplete=”off”> | |
</td></tr></tbody></table> | |
</form> |
#!/bin/sh | |
# Set the macOS installer path as a variable | |
MACOS_INSTALLER="/Applications/$(ls /Applications | grep "Install macOS")" | |
MOUNT_POINT="$MACOS_INSTALLER/Contents/SharedSupport" | |
echo "macOS installer is \"$MACOS_INSTALLER\"" | |
# Set the target disk as a variable | |
TARGET=$(diskutil info "$(bless --info --getBoot)" | awk -F':' '/Volume Name/ { print $2 }' | sed -e 's/^[[:space:]]*//') | |
echo "Target disk is \"$TARGET\"" |
#!/bin/sh | |
# An hook script to verify changes to be committed do not contain | |
# any 'FIXME:' comments. Called by "git commit" with no arguments. | |
# | |
# The hook should exit with non-zero status after issuing an appropriate | |
# message if it stops the commit. | |
# | |
# To bypass this hook, use the "--no-verify" parameter when committing. |