MacOSX: telling tmux where libevent is
Friday, 8th August, 2014
tmux depends on libevent but after installing libevent, tmux still won’t configure:
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... etc/install-sh -c -d
...
checking for pkg-config... no
checking for LIBEVENT... no
checking for library containing event_init... no
configure: error: "libevent not found"
$
You have to tell it where lib event is installed. I did a vanilla configure && make && sudo make install and it seems to have ended up in /usr/local/, so:
$ DIR="/usr/local/"
$ ./configure CFLAGS="-I$DIR/include" LDFLAGS="-L$DIR/lib"
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... etc/install-sh -c -d
...
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
$
Done.
Thanks to stackexchange.
Get rid of gpointing-device-settings / gsynaptics and use xinput
Monday, 21st October, 2013
All the info is on this thread:
gpointing-device-settings is a braindead gui from Gnome. Worst of all, it doesn’t remember your settings, so every time you boot up, you have to fiddle about with the gui again.
The post linked to shows how to use xinput to get/set configurations for peripherals, and how to wrap xinput commands in scripts.
DragonFly BSD: copying the image onto a USB stick under MacOS X
Friday, 6th May, 2011
On Unix-like systems low-level byte-to-byte copying is done with dd:
dd if=[input file] of=[output location]
n.b.: of is a location, not a filename, so you can’t use the file path to your USB stick, as in:
dd if=dfly-i386-gui-2.10.1_REL.img of=/Volumes/MyUSBStick
The path to the device location is required, as in:
dd if=dfly-i386-gui-2.10.1_REL.img of=/dev/disk1
On MacOSX, how to find out the dev name of your USB port is described in this Ubuntu help page. The following will list the currently mounted devices, with their dev names:
$ diskutil list
This will unmount the device, ready for dd:
$ diskutil unmountDisk /dev/[name]
And this will do the deed:
$ dd if=/path/to/input/image of=/dev/[name] bs=2048
Finally, this will make your device safe for removal.
$ diskutil eject /dev/