initial working commits for deb-build infrastructure

Changes:
- Drop woof-distro and replace with my own.
- Drop merge2out and change with setup.sh
- deb-build and build-iso
- initrd changes: 
--- always assume aufs except when told otherwise
--- always use devtmpfs
--- copy DISTRO_SPECS to pup_new
- rootfs changes: pinstall.sh, rc.sysinit - always use devtmpfs

On Mon, 16 Jun 2014 13:55:30 -0700
Mick Amadio <notifications@github.com> wrote:

> 
> Just one point on this. I'm using Barry's old udev-167. Do I need to
> upgrade? I certainly can use slackware's (182 IIRC). It did seem to work
> fine in slacko64. This will have implications for 666philb too as I'm
> pretty sure he has 167 too.
> 
> 

No implication for older udev. Fatdog64 600 (up to 631) series also used udev 167, and have been using devtmpfs for years (actually from 600 alpha).

Earlier udev has the ability to make device nodes, it simply overwrite the nodes that devtmpfs has created.

Newer udev (from 176 onwards) doesn't make device nodes anymore, and require devtmpfs.
Here: http://git.kernel.org/cgit/linux/hotplug/udev.git/tree/NEWS?id=HEAD
So debian joked that perhaps they should: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=105;att=0;bug=722580

cheers!