This is the exact build environment for Lucid Puppy 5.2.5. It builds the lupu-525.iso and the devx_lupu_525.sfs. The build takes about 10 minutes.

Errata: 2byte figured out that it may only work correctly in Lucid 5.2 or 5.2.5. It seems to correct the problem to delete /packages-lupu/firstrun/pinstall.sh.

The only thing to download is EZ-Woof-525.tgz, which is about 431MB. There is nothing else to download and no packages to build--that has already been done. I have found that EZ-Woof is great for experimentation--I just built Lucid 5.2.5 with alsa 1.0.24.

Quick Start: 1) Download EZ-Woof-525.tgz to a disk with at least 2GBs free space, and then 2) open a terminal in that disk and run ‘tar -xvf EZ-Woof-525.tgz’. Don’t try to unpack it with Xarchive--it never finishes. 3) Open the folder and run woof_gui Choose the Kernel tab and use ‘linux_kernel-2.6.33.2-tickless_smp_patched-L3‘. Then choose the Build tab and you are on your way. It wouldn’t hurt to read the rest of this though.

Explanation. The reason for EZ-Woof is that Lucid Puppy 5.2 and 5.2.5 made use of many packages that were not a part of Ubuntu Lucid Lynx 10.04. The easiest way to deal with those packages was to undeb or unpet them, and then move them directly into /packages-lupu, replacing the folder that was there. For instance, to update pmusic, I would download the latest pmusic pet, change the extension to tgz, unpack it, and then move the folder into /packages-lupu, deleting or renaming the pmusic folder that was already there, and changing the folder name to simply pmusic (rather than pmusic-1.1.6, etc.). You can do this also, of course. Be warned that some packages such as ffmpeg, could get pretty hairy.

The other main thing you must know is that the “recipe” for the distro is in the file DISTRO_PKGS_SPECS-ubuntu-lucid. A package name with a yes will be included in the build. As it is delivered that file will build Lucid 5.2.5. To eliminate a package from the build, you would just change the yes to no. If you wanted to make an addition, you would have to first put the folder into /packages-lupu and then create an entry in DISTRO_PKGS_SPECS-ubuntu-lucid for it. Before you get fancy you might just build the default to see how everything works.

While building, I would do several things manually. When the build process stopped to ask me if I wanted to include the i810, I would do these things.

1. copy PKGS_MANAGEMENT, Packages-puppy-lucid-official, and DISTRO_PET_REPOS, from current Lucid /root/.packages to /sandbox3/rootfs-complete/root/.packages. (The reason is to set up the PPM to the pet-packages-lucid repo.)

2. check /sandbox3/rootfs-complete/usr/share/backgrounds and copy into that folder whatever backgrounds you want--check also that default.jpg has content. (The reason is that Woof automatically culls some backgrounds plus if the background you want is in a different folder there would be a problem with an empty default.jpg.)

3. (tweak) copy .gtkrc-2.0 from current /root to /sandbox3/rootfs-complete/root/ (This would over ride your choice of gtk theme but do some things for fonts--maybe.)

One forum member has voluntarily taken a GIANT step forward. And, it looks like he could use a little of our help.

He has built, compiled, tested, and has now moved beyond the concept phase into the "practical use" phase. His implementation is very note-worthy as it is aimed at the very PCs that PUPPY (Not WARY or QUIRKY) is published to be used on. And, it appears his implementation is, in fact, a PUPPY 5.25. but, it addresses ALL RAM size PCs.

If anyone has a moment, please take a look at thiis and provide him with any feedback. Everything he is doing is same for what is done for the things we did for PUPPY 5.25, except, he is providing one-significant and useful advancement that we should take note of.

Anything we do in review or help is the very same thing(s) we are going to be doing, with the very next PUPPY, here.

His efforts are here!
Hope this helps._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Frankly it did not.
Larrys new code above might make others efforts more viable.
Great potential. Many thanks Larry..

Snowpuppy is an excellent Puppy version and again is vastly better than my two days remaster. Simply because of efforts to improve and get working the components. I used it for about a week and also chatted with pemasu on IRC. A good guy. The new experimental Ice version is certainly worth providing feedback as suggested. Pemasu is to be congratulated

Puppy thrives on experimentation, feedback and new ideas.
No matter how crude or faulty our feedback, we can all test

Just remember what something like EZ-Woof-525 gives you.
An operating system. For you. Customised to your needs and specs..
Such fun. _________________Puppy WIKI

I love Snowpup and use it 24/7 but sadly the new Ice are based on teh latest kernel and that one seems to be more demanding on the hardware.

CPU works more and the overall temperature seems to rise. But I know too little. I do support Pemasu's efforts though. Snowpup to me was a new era for my gears.

Back on topic. So had I had a normal brain and not this confused one then I would be able to make a puppy too Reading post one I realize it is still too difficult to me to keep all that in my head. But a good step forward indeed.

All such should be welcomed with open arms and big smile._________________I use Google Search on Puppy Forum
not an ideal solution though

Larrys new code above might make others efforts more viable.
Great potential. Many thanks Larry..

Lobster, This is all Barry's Woof--just a subset of it, tailored to build an exact or variant copy of Lucid 5.2.5. The packages are already downloaded and built exactly as in Lucid 5.2.5, so all a person has to do to build Lucid 5.2.5 is start Woof, choose the kernel, and Build.

It seems useful for experimenting with different kernels too, because all one needs to do there is to put the new kernel.pet into packages-pets and then it will show up and be used when choosing the kernel.

Thanks Playdayz. Downloading now. And thank you of sharing the info, how you recommend to tweak with woof. About the same prochedures as I have done. Not much to add. I have made my own tweaking script, so that the script do those changes from appropriate folders.
I execute the script after there has been gui to select the wallpaper etc...

I will test this with linux_kernel-2.6.38.2-lupe15.pet. It looks most promising so far.

Thank you Playdayz of ALL your work. Your guidance and templates and all woof info with your ubuntu base has made my Snow Puppy possible. Also it is the base for Ice Puppy also. Maybe this EZ prebuild woof platform will be the base for new kernel also.

There is a folder named zzLupu_Utilities. it contains many of the customizations for Lucid Puppy. If you are using EZ-Woof to possibly make a derivative for public use, you probably should look through that folder and make sure you know what it in there. If you are getting wonky results and do not know why, you might also look in zzLupu_Utilities for the reason--for instance, a file of yours may be getting overwritten by something in there.

I've been trying for a couple of days to remaster a working system with an additional menu category with entries.

No matter how I try I cannot get it to work as a live cd with my choices.

There seems to be some sort of problem,so I gave up for now.

I then tried downloading bones and woof but ended up with corrupted files after a marathon session i gave up.

I've since come across this excellent system and so far I've yet to achieve what I want, even though I modify the packages etc.

As suggested I started at basic and achieved a standard default iso which I burned to CD which worked perfect..

I then tried again adding my package after decompressing the pet. I altered the specs as explained.
I made other changes, in particular I wanted the default to be jwm. But no matter what I do I end up with a default iso again and openbox as wm.

Now, the odd thing is when I reach i810 as you suggest I look into the sandbox files and my stuff is there. I made changes to the windowmanager file to jwm etc but still I end up with a default iso with no changes or additions.

Am I missing something quite simple here ?_________________Rob
-
The moment after you press "Post" is the moment you actually see the typso

I then tried again adding my package after decompressing the pet. I altered the specs as explained.
I made other changes, in particular I wanted the default to be jwm. But no matter what I do I end up with a default iso again and openbox as wm.

Hey tasmod, EZ-Woof is basically for making something either identical or very close to Lucid 5.2.5. It sounds like you are probably successfully adding your programs.

Ah, go into the DISTRO_PKGS_SPECS-ubuntu-lucid and put a no in front of openbox and fbpanel. I bet that might do it.

<Add>Yes. I tested and it worked for me--booted right up in jwm. That's the Woof way--change the DISTRO_PKGS_SPECS-ubuntu-lucid and then rebuild, and rebuild, and rebuild As I recall there is some problem that I never bothered with that makes a conflict booting jwm first with openbox on the system--it is more than changing /etc/windowmanager..

So all you people who change first thing to jwm can make yourself a Lucid 5.2.5 that only has jwm!!! The reason for Openbox is that gnome-mplayer just did not work well with jwm, but that is all fixed now, basically thanks to ttuuxxx's gnome-mplayer 1.0.2 build.

That is one thing I like about EZ-Woof. I was able to test that in about 7 minutes And if I screw up the EZ-Woof I am using I can just unpack it again and be back to a pristine Lucid 5.2.5.

Plus, anyone could make an EZ-Woof for any Woof-based iso, Spup or Snow Pup (I think he uses Woof). Anyway, that would be a way to get more people experimenting on a release in development.

No changes other than to change openbox and fbpanel to `no` in PKG specs.

Run build and when gui options window appears for theme and background I set my straightforward choices. light-blue background, polished blue theme.

At this point alongside the gui in the terminal window, error messages came up for gtkobject errors at each selection. (sorry, unable to copy them)

I continued and when build was finished I added 'build' iso to grub menu and rebooted using the 'build' iso.

Sadly, no joy.

Still a standard build with no changes made. Still openbox. When I checked etc there was openbox.windowmanager entry. Background was leaves, theme was same with no change.

Where on earth am I going wrong. I know I'm a bit slow on the uptake at the moment but this should be 'simples' for me.

Making any changes in the build files at the 'i810' point just doesn't seem to be reflected in the final build either._________________Rob
-
The moment after you press "Post" is the moment you actually see the typso

Tasmod. Woof building follows its straightforward logic, you can be sure of it. Something does not go according to that logic now.

Unbuilding is anyway easy. Delete everything from the sandbox folder. Everything. Remove from packages-lupu fbpanel and openbox folders. Then they are not included.
If you still get them in the new iso, then you surely are using wrong iso or files from another build.

Still a standard build with no changes made. Still openbox. When I checked etc there was openbox.windowmanager entry. Background was leaves, theme was same with no change.

Where on earth am I going wrong. I know I'm a bit slow on the uptake at the moment but this should be 'simples' for me.

Making any changes in the build files at the 'i810' point just doesn't seem to be reflected in the final build either.

You might not have gotten the proper DISTRO_PKGS_SPECS-ubuntu-lucid

Code:

no|fbpanel||exe,dev>null,doc,nls
no|openbox||exe,dev>null,doc,nls

Is it possible you have a lupusave file on that disk that the new build is picking up? Or have you copied a previous lupu-525.sfs to the hard disk to make for faster booting. You might go to the Specifications tab in Woof and change the number and/or the prefix--remember to Save.

I think pemasu might not understand that you are using EZ-Woof. It shouldn't be necessary to delete anything. The no in the DISTRO_PKGS_SPECS-ubuntu-lucid will do it. But he is being extrememly safe

I made a test last night with the no to openbox and fbpanel--it booted fine to jwm, but when I went to Shutdown there was a problem--nothing happened. CTRL-Alt-Backspace fixed that.

At the i810 you make changes to the /rootfs-complete filesystem.

It really sounds like some other lupu-525.sfs or a lupusave is getting in the way.

No doubt this is is something simple that we are overlooking. When the process ends, the new files are in the /Build folder in /sandbox3 and the lupu-525.iso is in /sandbox3.

Playdayz. I understood it right. It was just an ultimate solution to not have some packages included. When you dont have them, you cant include them. If the booting puppy still have them, then......
I thought about your possible reasons also, but I was a bit vague in my post.
Not using the right specs or the booting process picks the previous same named sfs is both possible.

I have used and build one 525 build already, everything went as it should.
Because it is so easy to unpack the ez woof again, the removing of the created packages from the build is really one way to not include them.
./3builddistro script complains about those missing packages but wont affect to the outcome.

And thank you of bringing this ready made woof platform for everyone to test it, use it, play with it and at last, create something new that didnt exist before.......

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