Puppy Linux Discussion Forum

nothing should be changed in woof-ce i was just giving my opinion (a joke) on the busybox symlinks woof-ce should build the initial iso initrd only busybox ash and then the next step is to get woof-ce to build the initial basic -x main.sfs file iso both isos can be placed in the community puppy ...

the problem here

is not building an initrd
that has busybox in it (all busybox symlinks should be in /bin)

the problem is getting woof-ce to do this

remember this is a subproject of woof-ce
and has to remain compatible with woof-ce development

william

hi taersh the community puppy system will be primarily targeted at users hoping to introduce them to building puppies and teach them enough to possibly even become developers that is why the system is designed to be so simple it is all based upon a simple iso build script and templates all a non ...

hi s243a when last i manually broke apart puppy and the init file if the initrd could not find the main.sfs file it would drop to the busy box ash shell in the initrd for trouble shooting that is what we need to start with the bare minimum then other things will be added as sfs files one can do this ...

thank you very much s243a for all your work in my opinion the first iso should only include the 1. bootloader - syslinux 2. kernel 3. initrd - busybox only 4. and a main.sfs module with what the initrd copies over all it needs to do is boot to a busybox ash shell do you know how to build this in ...

just a few things to remind myself all modules should be sfs files that way the iso build script and module maker script only need to deal with one type of file every module should have a unique number (as well as the name) like m12345-wifi that way the build script doesnt have to worry about ...

hi all again i envision the community puppy project which will be a subproject of woof-ce to consist of 1. a community puppy module repository 2. a script to build modules - sfs files 3. a build script to assemble isos from the modules in the repository 4. templates (text files) that tell the build ...

hi s243a and 666phib thank you very much for all your help my goal with this part of the community puppy project is not to build a complete puppy system just the most minimal base almost everyone that is interested in fossapup64 will use the full version even people that want a cut down puppy will ...

hi s243a thanks for your help and compassion my problems are that 1. i dont understand woof-ce well enough to know how it builds its iso 2. i dont know the minimal packages in distro specs that are needed for a base both of these things would be known by a woof-ce guru but im not a woof-ce guru so i ...

hi taersh

bit off more than i want to chew

keep up the good work
looking forward to your initrd

fossapup64 is very modular already
so no real change in the community puppy

your initrd should solve the multiple sfs issue

william

hi all first let me apologize for wasting everyone's time with my incessant and annoying posts but its all coming back to me as i play with woof-ce and puppy internals again for some strange reason i keep forgetting what i have learned again and again i love puppy the finished product polished by ...

hi taersh

great

i will follow along
and test when i see how you guys are using it

william

hi taersh i am now trying to get woof-ce to build the 2 base isos for the minimal modular system this will be a long process since i have to figure out what woof-ce requires for it to make a bootable system how do you test your initrd do you simply replace the initrd in an iso of fosspup64 william

thanks

i see there are already scripts to do the conversion

now back to trying to figure out the 2 templates

william

it would be nice to have a script that made pets into sfs files
so they can be used as modules
but that can come later

william

you can add more to the initrd to have a more complete set of shells and support stuff but you dont really need to you can add more shells and support stuff by adding sfs files likewise with the basic x sfs but this means you are only working on 2 small parts of woof-ce much simpler to work with ...

hi everyone i suddenly realized what should have been obvious to me from the first there is no need to have more than 2 base templates for distro specs 1. the initrd iso 2. the base x iso everything else can be added as sfs files made from pets which would be the natural way to add things anyway im ...

i agree wiak what i am doing is strictly for my own amusement and so is done at my own pace as for the community puppy well thats for the community i have been around long enough not to expect others to do my work probably i should have not posted this idea on the community puppy thread but i do ...

hi bigpup you have bought up the key issue what do you need for each build the only way i can think is for a guru to make various templates of distrospecs for each build right now i am only interested in the 2 primary builds 1. initrd only 2. x jwm xterm so i am playing with distrospecs to make ...

hi wiak

not set in stone

you choose the template you want
or make your own

just allows people (like me)
who dont know what components are required
to see a list of what is needed for each build

william

hi wiak i agree only the minimal base puppy stuff should go into iso 1 - initrd only iso 2 - x jwm xterm you can add what you want later i envision 2 base distro specs templates that will allow the building of iso 1 and 2 and further distro specs templates that will allow you to put more stuff in in ...

thank you 666phib and everyone i will try your suggestions as i said i want this project to be just an extension of woof-ce 1. to make things more accessible to non woof-ce folks (so they can build a puppy from woof-ce quickly and easily) 2. as well as making system that can be built up from a ...

hi wiak the unionfs is inherently weak and limited i dont really intend to use it as the main mount system long term but since woof-ce is built that way i will start with it yet another way to link things is to have one image with multiple application folders inside you only need one loop device to ...

so now i have to relearn woof-ce
so i can modify the files that specify what is added to the build

william

when i work things out i will have the gurus push these new functions into the woof-ce master so anyone can build a minimal modular distro from woof-ce you will also be able to use a local repository so you don't have to use woof-ce or git to build a puppy this will just be an additional function ...

hi bigpup

yes i want to start from the bare minimum

i actually will break it down further
separating out the window manager and xterm

if i have any issues with unionfs

i will just use symlinks which have little overhead and no limits

william

hi 666philb and everyone i would like to try to make a more minimal modular form of fossapup64 from woof-ce that is get woof-ce to build just 1. an iso with only the initrd and an empty main.sfs file 2. an iso with iso 1 + a main sfs file that only contains basic x jwm and an xterm so that one can ...

hi peebee

thanks very much for your reply
and the info

and for upupbb32

william

hi peebee

i would like to use your upupbb32
as the base for the community puppy
since it is flawless

is the woof-ce stuff still available for the older builds
since i use one of the older builds

william

hi s243a and dimkr and everyone so after some thought here is a proposal from a non guru 1 script to run a woof-ce build to the end including just the pets that are needed for a shell (pets a b c) another script to squash pets into sfs files to be loaded when desired either by unionfs or symlinks ...