RE: pet-be gone and ldconfig -background info FYI when you compile a program, and use new2dir to remove the bloat, the script uses installwatch, sed, grep etc... to copy files to the appropriate directories main, DEV, DOC and NLS one of the strings the script looks for is "config" (assuming that the developer would setup the package before distribuition and it would not be neeeded) Also when a pet is created in this way, you should get a package_name.files that lists all of the files. These files could be used in Pet-be-gone. We could even keep them in a small repository to save space.

This brings up another point. It would be nice if .pet posts also had the CFLAGs, CXXFLAGs, LDFLAGs and ./configure settings used (where applicable) and package database entry... otherwise I will probably end up recompiling it. I will probably do the same thing if the packages aren't split into DEV, DOC and NLS as well. This is mainly a quality control issue and a quick pet for testing is still fine for submission, but if you spend hours tweaking the perfect combo of FLAGs and hand editing the makefiles or something please let me know. I just don't want to end up having a devx docx or nls sfs that is missing stuff, packages that are missing dependency lists or bloated/broken packages Publishing the flags and setting will allow others to reproduce the package if a new version comes out and you are busy. I will try to address most of these with Pcompile as it progresses, but if all of this sounds like a foreign language to you, don't be afraid to post a pet, suggestions or feedback._________________Check out my github repositories. I may eventually get around to updating my blogspot.

That could be a good job for you
If you started with French, maybe others could follow your lead after and use your examples.
ttuuxxx

O common, not again. How much longer can Puppy be blind to the real world? Please have a look at how the bigger Linux distros are handling localization. There have been truly heroic Puppy-translators, like MU, esmourguit, magerlab, hacao and many others, but just how long can a human being continue that kind of endless work?
What's needed, yes I said it before, is a standardized, unified, teamwork-enabling localization system.

To return to Technosaurus's topic, I was very pleased to see this as the first point on his wishlist:

Quote:

On the fly sfs mounting: Choicepup style or symlink style

Yes, dynamic sfs mounting, a dream come true. I do not understand what the "symlink style" means, but if it works as well as choicepup, I'm a happy end-user

I support Choicepup's point of using a small core with additional sfs of the users choice.

Modular is very good and long overdue.

Loop or union is of no matter to me but whatever works for new users...at least, just look at this for a very interesting and may I add a cool way to build a small fast and full featured fork/distro..Eric_________________Be not afraid to grow slowly, only be afraid of standing still.
Chinese Proverb

to add, like jrb has done with his naming of the "ch" in front of his sfs files...

If sfs packages are built with a corresponding version number to a main core version number the package manager will be able to tell what package goes to the proper version of the modular core by default from any repo.

If it's not already built I would think there are enough coders that can make it a reality and work for us dumb guys...just a thought...Eric_________________Be not afraid to grow slowly, only be afraid of standing still.
Chinese Proverb

and LDFLAGS
-Wl,-O1,-relax,--gc-sections,--sort-common,--no-keep-memory,--as-needed,-s
(--as-needed doesn't always work but it can significantly improve startup times)_________________Check out my github repositories. I may eventually get around to updating my blogspot.

As long as we are rewriting init...
zdrv.sfs as standard (does anyone know why Barry didn't use it?)
additionally load sfs files from same dir as the pupXXX
browser.sfs if found
pluspack.sfs if found
userdefined.sfs if found
also eliminate the crazy amount of time it takes to "search for puppy files"- only look in the the the dir specified in menu.lst entry by phome= which can be set automatically when you make your save file

add something like this to the save file script

Code:

sed -i 's/\n#phome/ phome=$HOMEDIR /' /mnt/home/boot/grub/menu.lst

such that if grub was like this

<puppy's menu.lst entry here>
#phome

it would then look like this after setting up a save file

<puppy's menu.lst entry here> phome=sdaX/mypuppyhome

just thinking out loud right now - wondering what else seems to take the most time during boot ... building the kernel module maps? copying to ram?_________________Check out my github repositories. I may eventually get around to updating my blogspot.

I can find my way around fine and do basic stuff, but can you maybe post an example of what this modified grub file would look like?

I'd love to reduce the amount of time puppy takes trying to find it's self on this old computer.

Thanks,
Sonsum.

*EDIT: Oh, and I tested the abiword-2.7.9-i486.pet package on the base 4.3 install. It installed lightning fast (almost too fast?) but abiword still works. Oddly, the about abiword section now doesn't list a version number.

Is there a PET-Be-Gone for 4.3 yet? Cause I think you may need to uninstall the original Abiword first...

It is more likely that I got carried away with cutting abiword down to try and fit it on the forum - you shouldn't need to uninstall the original (2.7 has its own directories and the /usr/bin/abiword will overwrite the old one)

I have been playing with using xz compression in petget - had to recompile a later version of tar (bonus - it's smaller too). I am going to upload a tarball of the files I changed so someone can do an idiot check on me. This includes the scripts that make and convert pets - the new format will be .pxt

xz should reduce some bandwidth and server space requirements and allow for quicker downloads - install speed is basically unchanged

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum