franzflasch

Disabling GNOME Tracker and Other Info

GNOME's tracker is a CPU and privacy hog. There's a pretty good case as to why it's neither useful nor necessary here: http://lduros.net/posts/tracker-sucks-thanks-tracker/

After discovering it chowing 2 cores, I decided to go about disabling it.

Directories

Don't use VPN services.

No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.

Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.

A Russian translation of this article can be found here, contributed by Timur Demin.
A Turkish translation can be found here, contributed by agyild.
There's also this article about VPN services, which is honestly better written (and has more cat pictures!) than my article.

Original link: http://www.concentric.net/~Ttwang/tech/inthash.htm
Taken from: http://web.archive.org/web/20071223173210/http://www.concentric.net/~Ttwang/tech/inthash.htm
Reformatted using pandoc

Integer Hash Function

Thomas Wang, Jan 1997

last update Mar 2007

	yum -y install texlive texlive-latex texlive-xetex
	yum -y install texlive-collection-latex
	yum -y install texlive-collection-latexrecommended
	yum -y install texlive-xetex-def
	yum -y install texlive-collection-xetex
	Only if needed:
	yum -y install texlive-collection-latexextra

	#!/bin/sh

	##
	## Usage: ./ovpn-writer.sh SERVER CA_CERT CLIENT_CERT CLIENT_KEY SHARED_SECRET > client.ovpn
	##

	server=${1?"The server address is required"}
	cacert=${2?"The path to the ca certificate file is required"}
	client_cert=${3?"The path to the client certificate file is required"}
	client_key=${4?"The path to the client private key file is required"}

	#! /bin/bash
	set -e
	trap 'previous_command=$this_command; this_command=$BASH_COMMAND' DEBUG
	trap 'echo FAILED COMMAND: $previous_command' EXIT

	#-------------------------------------------------------------------------------------------
	# This script will download packages for, configure, build and install a GCC cross-compiler.
	# Customize the variables (INSTALL_PATH, TARGET, etc.) to your liking before running.
	# If you get an error and need to resume the script from some point in the middle,
	# just delete/comment the preceding lines before running it again.

	% Take 100Hz signal, amplitude modulate it with 2.5KHz, then run it through FFT
	clear ; close all; clc

	freq1 = 100;
	period1 = 1 / freq1;
	w1 = 2 * pi * freq1;
	num_tsteps = 1000;
	num_periods = 2;
	tstep = num_periods * period1 / num_tsteps;
	t = 0:tstep:(num_periods * period1);

	Byobu Commands
	==============

	byobu Screen manager


	Level 0 Commands (Quick Start)
	------------------------------

	<F2> Create a new window

	/* --- Usage --- */
	g++ server.c -o server
	g++ client.c -o client
	./server
	./client 127.0.0.1

	/* --- server.c --- */
	#include <sys/socket.h>
	#include <netinet/in.h>
	#include <arpa/inet.h>

	/*
	http://stackoverflow.com/questions/1371460/state-machines-tutorials/1371654#1371654

	State machines are very simple in C if you use function pointers.

	Basically you need 2 arrays - one for state function pointers and one for state
	transition rules. Every state function returns the code, you lookup state
	transition table by state and return code to find the next state and then
	just execute it.
	*/