mcorepup ; a script to create corepup

[nosystemdthanks]

mcorepup 0.4

creates corepup-7.iso

first version of mcorepup with a tcz builder

[nosystemdthanks]

mcorepup 0.5

creates corepup-7.iso

allows sending a parameter to functions through the profile...

1. normal profiles work exactly the same as before, you dont have to learn the "new way" unless you want to use it

2. except "addchanges" is now "profiles" sorry

3. now you can optionally add a parameter to your profile like this:

mcorepup-0.3

that will tell mcorepup 0.5 to create tcz packages for the following versions:

mcorepup03.tcz
mcorepup04.tcz
mcorepup05.tcz

each of these packages is about 10k, so if you want to create packages for all versions of mcorepup, just add this profile:

mcorepup-0.1

if you just want the latest:

mcorepup-0.5

[rockedge]

I found out when I use only addchanges = "rockedge" and none of the others in 04 the ISO is 83 megs....I can by using wanderer's reduce the iso down to 10 megs and anywhere in between.

I am going to try out 05.....with the "profiles" changes

[nosystemdthanks]

profiles doesnt work any differently than before, the function that accesses it is still called changeforwhom (which works the same as before) and there is now a second function (optional) called changeforoption.

changeforoption works the same way, except that if you want to write a more complex function (if you dont, just use the older changeforwhom function) then changeforoption lets you use a profile called rockedge-etcpath-sdd4 and then instead of just checking for the profile, it can check for rockedge-etcpath and gets the sdd4 part as a parameter.

which means you could say, tell it to look for rc.local in far more locations than there are profiles for.

but yes,

"wanderer" profile is corepup-6, which i still havent tried. mcorepup 0.1 makes corepup-6 for sure.

"wanderer wanderer-minimal" is 7,

"wanderer wanderer-minimal wanderer-core" is 8.



so "wanderer wanderer-minimal rockedge" would be "corepup-7 plus rockedge changes"

this worked the same way in mcorepup 0.4 and 0.3

[rockedge]

I have tried 01 - 04 and trying out 05 now.
built all the variations with success and getting to know the in's and out's

all of them work some have quirks but that's okay as it is all part of getting to know how to really use the scripts.

thanks for the clarification...mostly for those who would like to try out the scripts.

I am going to see if i can get my additions to work. Also I have begun to set up a corepup-7 for ZoneMinder....I have the Apache 2.4 web server running and configuration of PHP is moving along. then comes the mysql database server.

[nosystemdthanks]

all of them work some have quirks but that's okay as it is all part of getting to know how to really use the scripts.

thanks for the clarification...mostly for those who would like to try out the scripts.

absolutely. by the way, never feel shy about sending me a pm with a quirk youve found. that goes for other people who are trying to get it working.

youre obviously free to post stuff about that here, too-- the only difference is that when its here, i might try to clarify more for other people whats going on. in pm, i dont have to worry about people thinking its more complicated than it is.

i will never promise to fix or change whatever people want-- i have already designed it around the idea of making it as easy as possible for people to take it in different / "better" directions.

that said, im very interested in knowing what challenges come up for users. thats useful when i look for improvements to make.

one guy said python was complaining about the first line not being valid code, and after that i moved up the note about how it was a python-based language, "youll need fig 2.9 or 4 to use this."

that note had made its way farther down, and i thought it was a very good time to put it closer to the top again.

for every 15th report or so i will tell you that youre just wrong, to keep things fun and interesting. but your feedback is extremely valuable, and the thank you is sincere.

im particularly glad that you seem to be having fun. when im not swearing at it, i have a lot of fun doing this stuff. despite experience with bash, javascript, python obviously, and 25 years of coding in basic-- i swear a lot less when i code in fig. thats why its designed that way. im very happy with it.

im also aware thats theres a lot of shell code in mkfigos and mcorepup. thats because its more to the point, but i lean on fig when it saves me a lot of trouble. i would have never written mkfigos or mcorepup in any other language--

i dont have the patience for that, and 10 years into learning bash, i dont have the level of skill for it either! https://ptpb.pw/UFuV

[nosystemdthanks]

mcorepup 0.6 is based on tc9 and has the 4.14.10 kernel. it modifies coreplus 9, downloads 9.x packages, it includes some of wanderers modifications and (i boot with icewm desktop) it boots into the gui with the corepup background.

so far, wanderer has made no public modifications to corepup based on tc9, so this does not include his custom core.gz but it does include corepup.tcz

this is basically the tc-9 version of corepup-6.iso, minus the custom core.gz.

it should be easy (via profiles) to produce similar corepup-7 and corepup-8 files.

this is based on mcorepup 0.5 with slight changes made. it is a proof of concept, maybe rockedge will run it out of curiosity, and post a screen cap with the term running "uname -a" so wanderer can go "oh".

but basically it looks like corepup-6, its just based on tc9 (newer everything) instead.

[rockedge]

Corepup-7 built using the mcorepup06.fig script.