corepup

A home for all kinds of Puppy related projects
Message
Author
wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#761 Post by wanderer »

hi nosystemdthanks and rockedge

why don't you guys just open whatever threads or links you need

and just post a reference to the work on this thread

that way people reading this thread can follow what is going on
but other people don't have to feel there is a need
to wade through this whole thread

I try to tell people to go to the end of the thread
but its human nature to try to read the whole thing

I am following what you are doing with awe
I can also just follow the links

thanks for all your work

wanderer
Last edited by wanderer on Wed 01 Aug 2018, 13:48, edited 1 time in total.

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#762 Post by wanderer »

hi nosystemdthanks

I intend to keep up with the various new versions of tinycore
going to tc 9 next
however I will also keep playing with tc 6.4.1
because it works well on older hardware

the specifics of turning tinycore into corepup
are not important

this thread is just about merging
the tinycore and puppy concepts
(and whatever else anyone can think of)
into an improved system

feel free to use your system
to build whatever version of tc you want

in the end it will all become one thing

thanks again

wanderer

User avatar
nosystemdthanks
Posts: 703
Joined: Thu 03 May 2018, 16:13
Contact:

#763 Post by nosystemdthanks »

wanderer wrote: I intend to keep up with the various new versions of tinycore
going to tc 9 next
its a goal of mcorepup to run parallel to corepup where possible and reasonable.

i figured the idea of starting with 6.x was for older hardware. it was a good starting place, and so far mcorepup works pretty well if you set 6.x or 9.x in calls to addpackages.

its also good to know that corepup is moving to tc 9 and running a little more parallel to tc. i understand that for you, moving to tc 9 doesnt mean entirely closing the door on 6.x.
this thread is just about merging
the tinycore and puppy concepts
(and whatever else anyone can think of)
into an improved system
understood, thanks.
[color=green]The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives.[/color]

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#764 Post by wanderer »

hi nosystemdthanks and rockedge

could you please post a short overview of mcorepup on this thread
you guys are moving so fast its hard to keep up

thanks

wanderer

User avatar
nosystemdthanks
Posts: 703
Joined: Thu 03 May 2018, 16:13
Contact:

#765 Post by nosystemdthanks »

i will ask rockedge to guide on what i leave out, or if he prefers, fill it in using his words.

mcorepup is a script to create corepup automatically.

it presently consists of two branches: mcorepup and mxencore. it is written in a language designed for beginners and non-coders, which compiles to python. it makes a lot of calls to bash code too, which arent reasonable or practical to avoid.

mcorepup is the basic / introductory system that has profiles to allow for different people to make different contributions. that wont scale to 1000 contributors, but thats not how it was designed anyway. at that scale, there would be more than one branch. woof doesnt have that many maintainers either.

mxencore is the personal side branch to incorporate more of fig os and xenial pup into the same system that mcorepup is designed around.

both mcorepup and mxencore (which is based on mcorepup 0.5) are capable of producing tcz packages in a way that is fairly convenient and can be as simple as you want it to be. there are some extra tcz-related features in both versions, that can be used optionally.

mxencore incorporates and manages additional files from xenial pup. this is a work in progress, and will actually slow down mcorepup progress a little in the short run-- but ultimately it will probably be merged with mcorepup to help achieve one of corepups main goals-- to mix tc with puppy linux.

the tcz packages mxencore creates can be used directly in corepup or mcorepup.

more to the point, the code from mxencore that creates packages from xenial can be used in mcorepup. its just a bit early to complicate mcorepup with all that, so mxencore is a branch where that can be worked on without making mcorepup too complex.

fig os and mcorepup and mxencore are all part of the distro-libre project, an effort to make distros in general more amenable to user control and automated (rather than manual) remastering and distro building.
[color=green]The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives.[/color]

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#766 Post by rockedge »

nosystemdthanks

that is an excellent explanation of the entire project....well done!

I am still pushing forward exploring, breaking and fixing....... I do read all messages and documentation.

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#767 Post by wanderer »

hi nosystemdthanks and rockedge

yes thanks for the great overview
it is much appreciated

if you can please post at least updates/notes/links to this thread
so that people (me) reading this thread can follow what is going on

thanks again for all your work and creativity
it definitely is the future of this project

wanderer

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#768 Post by wanderer »

hi nosystemdthanks

my corepup is made up of 4 basic parts

the menu syslinux.cfg and isolinux.cfg
the core.gz with a mod in tc-config
the corepup.tcz with corepup-jwm and the logo and
the corepup-mods directory with everything else

the menu system does not need to be static
because other people use different systems like grub etc

the core.gz does not need to be modified
because the change to tc-config is not used
it was just a demonstration of adding boot codes

so a simple way to make my corepup and your script compatible
is to move the info on the menu and tc-config to the mods directory
and you are then left with the
corepup.tcz and the corepup-mods directory
which can added as components by your script

this is what i will do for tc 9 and above

i will probably build my versions as well
and post them on the smokey01 site
but they will not affect you builds

once again thanks for all your work and genius
i look forward to following the plot

wanderer

User avatar
nosystemdthanks
Posts: 703
Joined: Thu 03 May 2018, 16:13
Contact:

#769 Post by nosystemdthanks »

the stage where you try to merge two entire distros together is the most tedious part: http://murga-linux.com/puppy/viewtopic. ... 94#1001394

and especially when the two distros use different means of organisation.

refracta (devuan based) and puppy tahr are actually really easy to mix together. xenial and tc are equally possible to mix, though more tedious-- there are simply more differences to resolve, which is less fun.

any time its way too tedious and boring, its time to make a little tool for it. even if its a sucky tool that does a very good job and is unmaintainable and pointless to distribute.

for example, i spent more than 45 minutes going through 5000 lines of stuff. then i spent 10 more minutes making a tool with fig (slightly more, not a lot more than a nice bash one-liner, processing arrays and reversing strings more cleanly than rev does.)

10 minutes of custom code saved hours, then i started spending 30 more minutes-- instead i finally spent 10 more minutes adding half a feature to the existing tool i made, total of 20 minutes of fiddling with code saved 2 or 3 hours of drudgery.

but if you dont make the right decisions, you take longer to do boring stuff. thats why this part is not very much fun. its sort of worth it, it gets better as you do it, but only after you do it.
[color=green]The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives.[/color]

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#770 Post by wanderer »

hi nosystemdthanks

i certainly appreciate all your doing

by making your scripts
you not only allow tasks to be automated
(which may be the only thing
that allows some very tedious tasks
to be done at all)
but they allow others less knowledgeable
to use tools that you invented

like it said i will continue to follow the plot

thanks again

wanderer

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#771 Post by wanderer »

hi all

I am following the work
nosystemdthanks and rockedge
are doing on their threads

I advise anyone interested in corepup to do the same
as I feel they are doing the real work
of merging puppy and tinycore

I will continue to play with my manual system
and will post on this thread
just to update what I am doing

once again
thanks nosystemdthanks and rockedge
for all your work

wanderer

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#772 Post by wanderer »

hi all

just an update and review

i continue to play with both
nosystemdthanks mcorepup build system
and my own manual build system

there are 4 basic components of corepup

the boot loader
the kernal
the core.gz
a selection of tcz

the additions i add are
a corepuptcz
and the corepup-mods directory

the boot loader and kernel can be left untouched
since they are the preference of the user

core.gz can be modified over time
perhaps by incorporating functions
from puppy's init file into corepup's tc-config file
but that is for the future

that leaves adding custom tcz

nosystemthanks mcorepup build system
can make tcz automatically

so that is the way to go generally

of course one will always want to occasionally
build and tweak things manually
for some unique tcz
like the primary corepup.tcz
and whatever you want to add to the corepup-mods directory

for me
building other components into corepup
like
linked directories in the corepup-mods directory
the save directory image
dcore sce
and using multiple concurrent components
etc
are also a focus

anyway

have a nice life

see you soon

wanderer

User avatar
nosystemdthanks
Posts: 703
Joined: Thu 03 May 2018, 16:13
Contact:

#773 Post by nosystemdthanks »

it should be mentioned that (although ive tried to make it as easy as possible) all the build thing does to make tcz is create folders with mkdir -p and run squashfs tools to create the tcz.

so other people could make easy tcz tools too.

but i like the way the build does it.
[color=green]The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives.[/color]

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#774 Post by wanderer »

hi all

just an update to say hello

I continue to play with corepup

I move slowly because of my limited abilities
and demands in my life I must attend to

however as I have posted before
the basic system is completed
so from now on it is just further development

there are an infinite number of modifications/improvements
that can be done but I won't list them now
since I have reviewed most of them before
and I have to get back to my real job

I hope this is of interest/amusement to others
but its my hobby so that's enough for me

the latest tinycore is tc 9
and that is what I am working on now

I will post the iso to the smokey01 site when I am done

see you soon

wanderer

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#775 Post by rockedge »

thanks for the update wanderer

I will experiment with OS when you have the iso ready

User avatar
nosystemdthanks
Posts: 703
Joined: Thu 03 May 2018, 16:13
Contact:

#776 Post by nosystemdthanks »

been waiting for an update from you guys.

i will abandon tc6 for mcorepup and other related work-- tc9 from now on.

if someone has a serious interest in running mcorepup or other things like it, switching back to tc6 shouldnt be too difficult. but from now on, its tc9 by default.
[color=green]The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives.[/color]

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#777 Post by rockedge »

Hello nosystemdthanks!
I am still experimenting with version tc6 but have some difficulty in getting it to run consistently with the same set up every time and have not gotten PHP to run with the Apache server....yet.

I have been compiling real time kernels to use in Tahr, Xenial and Bionic for the musicians and audio people....maybe they run in Slacko ..don't know for sure yet. So I have been booting mcorepup and using the script on occassion to build newer versions after learning new things by this compiling of real time or low latency kernels and then stuffing them into Puppy Linux built using woof-CE or just manually swapped in an existing Puppy variation.

looking forward to continuing my quest to run a LAMP and zoneminder in an mcorepup....a real candidate for tiny OS capable of running zoneminder...and very little else.

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#778 Post by wanderer »

hi all

with a special hi and thanks to nosystemdthanks and rockedge

just a post to annoy everyone
and report that i continue to play with corepup
pretty much concentrating on tc 9

i have had a huge amount of real work to do lately
so i have been a little out of the loop
i will do things as i get the time

just as an advertisement
i want to remind everyone
that this system has a lot of advantages
and could be useful to the puppy community
so i encourage everyone to give it a try

anyway i will post again soon
unless mr murga gets tired of putting up with me

wanderer

User avatar
nosystemdthanks
Posts: 703
Joined: Thu 03 May 2018, 16:13
Contact:

#779 Post by nosystemdthanks »

given your reputation and past threads of this nature i doubt youll ever have problems with mr murga. if you do, however unlikely, theres a second forum waiting for you.

not much is being done with mcorepup right now, but other things are being worked on. mcorepup will probably be tc9-based from now on. i think the most recent version of it was (0.6)

http://smokey01.com/nosystemdthanks feel free to adapt that readme file to your needs.
[color=green]The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives.[/color]

wanderer
Posts: 1098
Joined: Sat 20 Oct 2007, 23:17

#780 Post by wanderer »

hi all

just a post to annoy everyone

and remind them to look into this minimal modular structure idea

if they are building or modifying something

you might even play with corepup


I continue to work on corepup as I get the time

and have learned a lot and had a lot of fun


see you soon

regards

wanderer

Post Reply