this thread is largely related to corepup, and if it has to be merged there i figure wanderer will be fine with that; ive read through about half of the corepup thread and one thing i can tell you-- wanderer and i have a lot in common.
wanderer wrote: its not really needed
or actually desirable
if i start making isos
people will just wait for the next iso
and will never learn the system
the present version of corepup is based on coreplus 6.4.1:
http://tinycorelinux.net/6.x/x86/archive/6.4.1/
it produces this iso, which ive got running in ram (details available) on the monitor next to this one: http://smokey01.com/wanderer/corepup-6.iso
i can tell you the difference between these two isos, because i have a tool called distdiff:
these files in corepup and their hashsums:
< 36172640730af955bd17410afeb6ccc9 /boot/core.gz
< 123a3254252f6f0e1885a5e992d76763 /cde/onboot.lst
< dd006344d3489ff17cb3ec21910afb85 /boot/isolinux/isolinux.cfg
< a63ef89b84dafa513041ab049a776527 /boot/isolinux/isolinux.bin
change hashsums to:
> b962559370267eec2ac9242f46b35440 /boot/core.gz
> 484abcd0d80515fab732756d89a34985 /cde/onboot.lst
> a78fff2a84e9edba70b6c2516bf5b254 /boot/isolinux/isolinux.cfg
> dc2e8ebda9cdd24c4f2d4336646348ef /boot/isolinux/isolinux.bin
and apart from those changes, these files are added to create the presently available version of corepup:
leafpad is added: (excellent choice)
> 5072ab3ebb80015d261af6393bdcd3c2 /cde/optional/leafpad.tcz
> 806e226d95b342341b7ba7aab1c224f7 /cde/optional/leafpad.tcz.md5.txt
> 1a63067c0686b724b0f476da72436cc3 /cde/optional/leafpad.tcz.dep
gtk1 is added: (very cool)
> 8a85227d0434a14c8d211596bf8bac8e /cde/optional/gtk1.tcz.md5.txt
> 68a85ad4fb84027de749d9e8c7d74574 /cde/optional/gtk1.tcz.dep
> 3e40448a1acadbfd6a4792297ddd50ab /cde/optional/gtk1.tcz
glib1 is added:
> ce5ef5a42a222464b6d4ef1649d45cd8 /cde/optional/glib1.tcz
> 500692842724022d846c32408303eb72 /cde/optional/glib1.tcz.md5.txt
emelfm is added:
> 0e3da35f474d8ac9c23baa73e50ae93f /cde/optional/emelfm.tcz
> b097947487b4e77b604b6927eb193cca /cde/optional/emelfm.tcz.dep
> 095795fa5c6f371dd41007de573e2085 /cde/optional/emelfm.tcz.md5.txt
dillo is added:
> 56c46e01c6b6be56881e4a1b437d413f /cde/optional/dillo.tcz
> d94e570bab119deeb512299ab257c0a2 /cde/optional/dillo.tcz.md5.txt
> 6a31b66e0a749242f7c05631c2cd7e6c /cde/optional/dillo.tcz.dep
and this file called corepup.tcz is added:
> 25f0d8bdb27224abe72c9df6b783fc90 /cde/optional/corepup.tcz
just as most of the differences in two debian-based livecds would be in the squashfs (which distdiff mounts and compares) most of the differences in corepup are in these archives.
while it may appear that i am looking to duplicate corepup (why?) i am actually trying to create a corepup-making machine.
i am aware that wanderer is likely to continue using isomaster and doing this "by hand," some of that "by hand" stuff is only going to apply to coreplus 6.4.1; im not sure how much of it is documented, or how easy it will be to move to later versions of coreplus (such as 9.)
if it turns out that the only important part of this is actually corepup.tcz and core.gz, thats great! that means this gets a lot easier.
my approach will be largely the same then, only it will be easier to work on. at the moment, i am working under the assumption that there is actually more to this than corepup.tcz and core.gz.
the other thread has 40 pages, and i am already adding to those. i hope this thread will make the other thread easier to manage; i believe it is its own topic, even if it is related.
http://murga-linux.com/puppy/viewtopic. ... 523#995523
wanderer wrote: that is the beauty of this system
and why I posted the official tinycore isos
just download one of the official isos
and add apps (or other stuff) to the iso
by downloading or making a tcz
the only 2 other files that I change
are syslinux.cfg in the boot directory
and tc-config in the core.gz image
syslinux.cfg sets up the boot loader to load to the corepup version
and tc-config sets up the services
like init in puppy
I leave the rest alone to keep things simple
and maintain compatibility with tinycore
this approach of wanderers, of work on something and occasionally explain it, is something i like. thats the concept of this thread too. let me know if you have questions-- bonus points if the first reply is thoughtful (wanderers thread is very open to comments, this one might as well try to be similar in what it accepts.)
however, i am not wanderer. he has the patience of 10 saints, while i am probably working on too many things right now to care if this thread goes well or not. but that would certainly be nice.
i have also talked about "restructuring puppy" and at present, im waiting for more details on that from or dancytron. presently, im not sure if i understood him in the first place, but i thought i did.