Bashed Up Bits

Lingo: Destructive Buy-in Definition : Enough buy-in from employees and/or management to approve an idea or project, but not enough buy-in to execute it successfully. Origin: Corporate lore from a now-defunct biotech firm in MA, USA. First seen in an early Scott Adams interview in the form "destructive agreement".

What to do if you need to install or build a package on Linux and it wants a missing file/library/etc... Have you ever tried to install package or some vendor software, only to find that the install fails due to a missing library? Here is a collection of methods for finding the package that contains the missing file. Red Hat Enterprise Linux/CentOS Using yum yum whatprovides /full/path/to/missing/filename Note: In all of these processes, fill in the actual filename and path for which you are looking. Using rpmfind site Browse to http://rpm.pbone.net/index.php3/stat/2/simple/2 Enter filename or /full/path/to/missing/filename in the search box (start with just the filename) Check boxes of rpm-based distributions in which you want to search Click search Debian/Ubuntu apt-file sudo aptitude install apt-file sudo apt-file update apt-file search filename or apt-file search /full/path/to/missing/filename Using Debian's website Browse to http://www.debia

echo -e "3,4,5,5\n4,5,6,8" | sed "s/$/\n-/" | sed -e "s/,/\n/g" | sed -e "s/^/|/" | awk 'BEGIN { print "{|class=\"wikitable sortable\" style=\"vertical-align:top; background:lightblue;\"\n!key value!!col 1!!col 2!!col 3\n|-" } { print } END { print "|}" } '

Instructions for connecting external IP devices to the second NIC on a Debian/Ubuntu box using Local-link Address networking (169.254.0.0/16) e.g. connecting a Axis 206M camera. Install on the Debian/Ubuntu PC: dhcp3-server avahi-autoipd To configure dhcpd, add the following lines to /etc/dhcp3/dhcpd.conf: subnet 169.254.0.0 netmask 255.255.0.0 { range 169.254.8.2 169.254.8.20; } Add a route to 255.255.255.255 to the second NIC in order to send UDP broadcast traffic to it. This is accomplished by the last two lines below in /etc/network/interfaces: % cat /etc/network/interfaces auto lo eth0 eth1 iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 iface eth0 inet dhcp iface eth1 inet dhcp post-up route add -net 255.255.255.255 netmask 255.255.255.255 metric 99 dev eth1 post-down route del -net 255.255.255.255 netmask 255.255.255.255 metric 99 dev eth1

A quick note... If you are getting the following error on Mac OS X 10.6 with XCode 3.2.1, while compiling ffmpeg with software scaling (libswscale): 32-bit absolute addressing is not supported for x86-64 then you need to pass --arch=x86_64 to "configure" Cheers, -Adam

Idea:Relatively Reliable Ram Disk Server (specs updated 2012-Q2) Two commodity servers Parts (for each) MB with 8 or 16 DIMM slots Two 10G ethernet cards for storage SATA RAID Four smallish enterprise drives: Two drives in a mirrored pair for OS Two drives for backing store 32GB DIMMs of ECC Registered RAM Parts for file server node Bonded pair of 1G or 10G cards Building Make a large RAM disk on each (leave 2GB for OS) On one machine: Share the RAM disk with the other machine via one crossover network (one of the 10G cards on each machine) via iSCSI Share pair of backing drives via iSCSI On other machine (file server) Using md, on each, mirror the iSCSI RAM disk to the local RAM disk. Make a filesystem on mirrored RAM disk Share RAM filesystem via NFS and SAMBA. Combine iSCSI drives and local drives into RAID 0+1 backing store.  Make journaled filesytem on backing store disk. Mount backing store Put each server on a sizable independent UPS wit