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

Thank you Karl for patch.

I sat down to think about it for a while (I haven't axed the rest of the static dev code yet...), and then I remember why I wanted devtmpfs in the first place - it's because going forward, newer udev will need devtmpfs. Devtmpfs has been around since 2.6.32 or so, that was two years ago, so I think there is really no reason not to go with it. The only exception is when you want to output messages to kernel *before* devtmpfs gets mounted, but that's rare...

So I guess, for woof-next at least, unless someone can give me a reason why I should not drop static dev dir, I'll always assume that devtmpfs is the way forward. (Even in static dev dir, the way to do it is have a tmpfs mounted to /dev and then use busybox mdev or technosaurus's code to populate it --- so in the end it works like devtmpfs anyway). 

cheers!

On Sun, 15 Jun 2014 16:10:58 -0700
KarlGodt <notifications@github.com> wrote:

> > @@ -196,7 +196,8 @@ KERNELVER="`uname -r`"
> >  PUPDESKFLG=1 #130515 this may be changed to 0 by 3builddistro.
> >  
> >  ##130612 detect CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y...
> > -DEVTMPFSFLG=0 #130618 set it from 3builddistro.
> > +DEVTMPFSFLG=1 #130618 set it from 3builddistro.
> 
> ```sh
> grep -q 'devtmpfs' /proc/filesystems && FLAG=1 || FLAG=
> ```
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/puppylinux-woof-CE/woof-CE/pull/472/files#r13788962


-- 
James B <jamesbond3142@gmail.com>