s243a wrote: 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.
the idea is fantastic!
but, after a lot of weeks reading that message, I don't see the real progress especially compared with the first Wary 64 bit from BK ((very) good working (really), size was a dream, 64 bit = probably more heavy than 32 bit, and supplied with a complete package of usual great applications! so I am actually searching for the event. devx for it). it is in my opinion the optimal stage to be better
in matter of minimal philosophy: the cli or no bone or one bone version has to become a bit smaller as Wary to succeed as new minimal leader of Puppy minimalistic in the extended Puppy family (as it is not (yet) a real Puppy, exactly as the first Wary 64 is not some real Puppy but simply a Quirky Wary...)
But ...
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 interfer with the system (statup 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
... I don't know what a
Devaun is! perhaps it would of course explain my bad comprehension...
According the " subject" of the thread I suppose it is simply a wrong spell?
Ok.
As s243a is knowing this different stuff:
- SliTaz
I miss a bit a main clear design for a minimalistic project (BK did abandon some kind of absolute minimalistic: no cli, no no-bone, no one-bone, always about complete distributions, -excepted in one older Quirky beeing a bit more that a one-bone-).
SliTaz did have an answer to that design problem: the splitted initrd working like the Russian dolls:
- just starting (through grub) and working (the CL interpreter)
- working in CLI with all old (SliTaz specific) absolute minimal tools like clex, nano, retawq (is compilable for AMD64 and works as well or bad as for i386), rhapsody irc, and the 4 major SliTaz specific tools, especially TazPkg to handle with all extensions, also in CLI mode (you can add other text mode browser, email and messaging client, samba, cups and gutenprint, sound, as well as a x-window client, today xorg. But also you can also begin to install tools to begin to develop (in Puppy would a minimal devx have the same function).
- starting in xwindow with adequate tools but no real applications for some work excepted system work
- usual set of applications with the beautiful Slitaz panel on TazWeb (build on webkit first version; this is the reason why SliTaz did continue to stay on webkit first version, espec. concerning Midori, Midori is only a little package as added to webkit first version, but would be a big package more, if it would be actualized up to date)
I miss such a clear design of stages / domains of development in tiny puduan or analog projects...
next point, is important, alexej (the actuel contributor of SliTaz making a lot of development) did immediately explain in the wiki in detail (step by step) his methods to allow other really to stick to the exact methods of development from scratch. I did observe that a lot of willing-supplementary-developer did be defeating and explain it in the Puppy forum without to see real improvement of that situation and it can be the reason why the Puppy attractivity seems to be decreasing: nobody needs a Linux where you can about only do what it was yet possible in Puppy 1.0, a small set without differentiate all purpose extensions confronting you to main unsatisfied dependency problems if you use the depositories of some Ubuntu, Debian or Devuan because of a cribble design of the minimal core set compared to those of Ubuntu, Debian or Devuan...