Patrik Bachan diggit

2020-06-19 update:

I just published a blog post with a few other options and info on decluttering Google's search results page.

Disabling "People also search for" box in Google search results

😡😡😡

Collection of CAN bus packages and tools

This document assumes the use of Linux as the chosen development platform. Items in bold are highly recommended.

It is recommended to use SocketCAN when working with CAN bus on Linux. It is supported by the Linux kernel mainline and follows the Linux interface model, allowing you to use other network tools such as Wireshark. This also allows the creation of virtual CAN interfaces where no physical hardware is required to simulate or replay CAN messages.

SocketCAN Linux kernel support - Linux >= 2.6

This page is no longer maintained, go to https://help.vivaldi.com/article/html5-proprietary-media-on-linux/ for help

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

	[Trigger]
	Operation = Upgrade
	Type = Package
	Target = linux

	[Action]
	Description = Restore Linux kernel modules
	When = PostTransaction
	Depends = coreutils
	Depends = rsync

	server {
	listen 80;
	server_name localhost; # Change this with your domain name

	root /var/www/grav; # The place were you have setup your Grav install;
	index index.php;

	error_page 500 502 503 504 /50x.html;
	location = /50x.html {
	root html;

	#!/bin/sh
	# Mount an NFS share on Android

	# Requirements:
	# - Busybox
	# - A kernel supporting nfs (either built-in or as a module)

	# On my Nexus 7 2012 I use the following kernel:
	# http://forum.xda-developers.com/showthread.php?t=2107224
	# Remember: if you have problems of system space, simply delete some of the default stuff.

	# Select the i2c bus
	i2c dev <bus>
	i2c dev 0

	# Probe the device
	i2c probe <chip>
	i2c probe 0x60

	# Read from the device
	i2c read <chip> <chip address> <length> <memory address>

	'Twas the night before Christmas, when all through the racks
	Not a server was alerting, not even Compaqs.
	The backups were written to tapes with care
	In hopes that later the data would be there.

	The machines were nestled all snug in their sleds
	Whilst visions of vengeance danced in their heads;
	And oncall in his three-wolf and I in my rack.
	Had just settled down for some syn and some ack.

	motivation
	* test xmpp bot behavior with different servers, measure throughput and reliability.
	* figure out numbers for prosody, nothing seems to be published at the time of writing
	* the goal was _not_ to push the servers to their limits, so the test environment was not highly optimized.

	test setup
	* macbook pro hosting ubuntu raring on vmware fusion.
	* communication flow: xmpp client (osx) > xmpp server (ubuntu) > xmpp bot (osx).
	* client opens 20 connections to server and pumps 150 iq stanzas (similar disco#items) to bot. this is being repeated 40x.
	* servers: