#prefix for distro files... exs: woof_600.sfs, woof_save.2fs
When the distro is built, this file ends up at /etc/DISTRO_SPECS.
If built with a 'zdrv' file, it is named 'woof_zdrv_600.sfs', or whatever the variables specify.
I have modified all the scripts accordingly.
One advantage of this system is that if you wanted to create a derivative of Woof, say 'Bark', change these:
All files will be prefixed with "bark", for example 'bark_save.2fs', so they can't get mixed up with any other derivative.
All messages in dialog boxes and elsewhere will display this as the distro name. For example, the main Help page will have "Welcome to Bark Linux".
Comments:Posted on 13 Nov 2008, 15:29 by Lobster
Good news about Woof, in particular a possible Python based language 'PupPy'
I recently created a simple puplet based on 4.1.1
Linux Tmxxine Dark Force
It includes the full Python and Idle Editor
During the construction I had to manually put LIT
(a program that runs on Startup) in the Startup directory (created as a temp directory)
Should the contents of the Startup Directory be automatically added to any remastering?
Posted on 13 Nov 2008, 17:13 by Leon
8 characters in filenames
From my experience with one of the earlier releases of Grafpup a system file with more then 8 characters in filename could cause problems when using grub4dos frugal install in DOS/FreeDOS/Windows environment. Author of Grafpup then changed the name of the file to 8 characters in name.
I suggest to keep 8 characters naming conventions as used in Puppy.
Posted on 14 Nov 2008, 7:07 by BarryK
yes, I was wondering if I really needed to stick to that format.
I suppose also:
Posted on 14 Nov 2008, 7:13 by BarryK
Or, for consistency:
woofrxxx.sfs #"r" is for "root filesystem", (or "v" for version)
Posted on 15 Nov 2008, 5:26 by Leon
Yes, that seems to be better.
The Sort order is interesting too.
woofrxxx.sfs #"r" is for "root filesystem"
woofvxxx.sfs #"v" for "version"