well, not quite. couldn't figure out how to get the code to work. figured out a couple of ways to edit the initrd directly (by extracting it twice, which seemed a bit odd, and through woofy), and it wasn't that hard to get to etc/distrospecs, but i was unclear about what to overwrite with what. there seemed to be a mix of precise571 and 572 references and i didn't want to risk breaking up some sort of internal look up or referral string, so i basically chickened out of messing with it. so it's still in function an upgrade of precise rather than a distinct entity. for the smaller of the two isos, i think woofy allowed some sort of suffix before the final ".sfs," but i doubt this will affect much.mavrothal wrote:Is a bit ( ) more complicated but basically, yes.Puppus Dogfellow wrote: i could use some clarification. you mean i open those two files (say, with geany) and find the "precise-5.7.2."es there and change the names to something like p573 (or anything other than "precise-5.7.2") and no one will have any problems? also, if someone's already installed 572, they'll also have no worries as the installation will just let it be?
DISTRO_FILE_PREFIX is the variable that determines the savefile (and some other things).
If you change DISTRO_PUPPYSFS and DISTRO_ZDRVSFS you have to change your SFSs accordingly.
A final important variable is the DISTRO_IDSTRING that must be added at the end of the puppy sfs and the vmlinuz so init can find them.
'echo -n "$DISTRO_IDSTRING" >> puppy.sfs' will do that (path, name and string must be adjusted for actual).
Make sure you type ">>" and not ">"
The DISTRO_SPECS file should be identical in initrd.gz and the main sfs. So make one as you like and copy it over to the other.Puppus Dogfellow wrote:
thanks. next version uploaded will have that addressed.
***
update of possible interest: new palemoon browser by OscarTalks available in repo.