A Puppy built with woof-Next and is created by s243a.

Thread: http://murga-linux.com/puppy/viewtopic.php?t=116418
Thread: http://murga-linux.com/puppy/viewtopic.php?p=1029434#1029434
thread: http://murga-linux.com/puppy/viewtopic.php?t=116046


At this point this is a very experimental release. It is built using woof-next.

Package managers

There are two package managers:
1. Sc0ttman's - Pkg - CLI package manager
2. mistifires - Puppy Package Manager (modified) v3.0

Has..JRB's portable browser installer

If you want a newer browser than is available via the package manager then you can use JRB's portable browser installer (available in the menu). It asks you which partition you want to install it on but I modified it so that you can install anywhere (see rufwoof's security concerns). 

Networking

Originally, I only had fresbee installed and I decided to also install network_wizard, which seems to also install simple networking wizard. Frisbee is sufficient and I recommend using it. The menu is a bit cluttered with some other networking options. These are here because I wanted to experiment with some CLI networking tools. Just hide the ones from the menu that you don't want to use. 

A minimal Philosophy?

The reason that I wanted to experiment with some CLI networking tools is that I'm interested in minimal systems. The current iso isn't that minimal 213mb but I think it's probably about 100mb smaller then the typical puppy equivalents (ie.g. dpup stretch or puduan ascii. This is probably mostly due to not including a browser. There are lots of stuff that I could remove but I both wanted a system that works well, and didn't give me any error reports due to missing files.

Some of said errors (I would get if I stripped out some non-essential packages) would be due to puppy doing things at start-up that aren't strictly essential. Others might be due to unnecessary library dependencies that are compiled into the library. In the first case we can rectify the error by modifying the puppy startup script and in the latter case we need to use different binaries for some libs (e.g. recompile). In the latter case I might rectify these errors by re replacing a lib with the tinycore version.

Why the name tiny_devaun?

The name tiny_devaun is for two reasons. The first is that it is somewhat minimal and I eventually plan to make it more minimal by pushing more things to optional sfs files. The second is that both libc6 and busybox is from tinycore. I also included some other random tinycore stuff just to see what it is but anything that I thought would interfere with the system (startup stuff and user related stuff) is not included.

The tinycore components are from the tinycore9 iso which uses a newer version of libc6 that both devaun ascii and debian stretch. I will think about how I might implement more tinycore components