(Abandoned) New Init Scripts + SFS-Load Script for Woof-CE?

[taersh]

Hi.

I made some additions to the init script plus the sfs_load script 3.0.
It's the init scripts from BionicPup32 (UPupBB 19.03), BionicPup64 8.0 and FossaPup64 9.5 (Bionic64).

These scripts are ready to use bdrv, cdrv, gdrv, mdrv, ndrv and vdrv extra sfs.

Perhaps there is possibility to add these extended versions to Woof-CE for next Puppies to be built?

All scripts are inside the archive attached.

[peebee]

Hi @taersh

You need to join GitHub Woof-CE and raise a Pull Request.......

[greengeek]

I would be keen to try a new init script in Tahr32. (It's a fantastic puppy but on some of my hardware it wont boot from usb reliably due to inability to find main puppy sfs)

Would these scripts be suitable for Tahr32?

[taersh]

Sorry, but no.

Beyond Tahr Puppy the init script has changed a lot.

[bigpup]

Have you submitted these changes to Woof-CE?

If you really want this to get into Puppy, the code is there in Woof-CE.
https://github.com/puppylinux-woof-CE/woof-CE
Make a pull request to submit to Woof CE.

You have to make a sign in account to be able to post at Github.
But it is no different than what you do to be able to post to this forum.

Any changes like these need to be discussed at Woof-CE.
The people there are really going to understand the inner workings of Puppy.

Be prepared to discuss what you offer.

There is also this:
woof-CE patch generator!
http://www.murga-linux.com/puppy/viewtopic.php?t=98740

[taersh]

No, I haven't submitted any of this to Woof-CE.
Just don't want to register to github.

[Clarity]

Might be the best approach for this community of users, should you have something associated with the boot process of value for all. Git will benefit you, as well, in understanding.

@BigPUP is trying to help you see.

[bigpup]

No, I haven't submitted any of this to Woof-CE.
Just don't want to register to github.

Why?
What do you think is going to happen by registering at Github??

It is best if you register using the same name as the one you use in this forum.
People at Woof-CE will recognize you!

They always need helpful submissions to Woof-CE.

[taersh]

Why?
What do you think is going to happen by registering at Github??

I don't know if there's anything happen.

When I joined the murga forum in September 2011, I returned to the internet after a long time of absence. I don't like the internet at all, though like the Puppy forum/forums very much. For some years of activity, the Puppy forums was the only activity for me one being online.

In the beginning of the 2000's I had my own web-site trying to do something around my music with it. But it was too much work, too much money and too much disappointment. So, in 2011, when I returned to the web I swore to myself not again getting that much attached to the web.

For some years now this worked very well. But meanwhile I'm registered to YouTube, Soundcloud, Ebay, Puppy forum. Plus Email and Weebly. I didn't even found the time to update/finish my Weebly page for around 2 year now.

So, I'm really not sure if I would need another registration. Need to think about it...

[taersh]

Damn!

I feared exactly this: after registering to GitHub I tried to make a pull request. But this site is that much complicated, I failed in complete!

I think I'm going to remove my GitHub account again. This s...s.

Edit:

I don't understand the complete structure of that site. I don't know what a branch is rather than how to compare branches and/or what to compare. At the moment to me it seems I have to go visit a university to get that damn site working for my needs/wants.

I gave up, it's much too complicated. Even the documentation sites aren't really helpful to understand what's going on. It's filled up with words I don't understand, I never heard and technical descriptions etc.pp. All I want to do is to upload my files and to tell the Woof-CE guys what these files are meant for and to ask, if them are interested to apply those changes to the init script and to the sfs_load script.

It's much more easier to develop that all on my machine and publishing it on the forum for those users who may be interested in.

Either that site is crap or I'm just too old and stupid to understand it

My place is on the forum, not at GitHub.

[wiak]

Damn!

I feared exactly this: after registering to GitHub I tried to make a pull request. But this site is that much complicated, I failed in complete!
...

My place is on the forum, not at GitHub.

My feeling of using git is that it provides amazing revision control, but... it is very non-intuitive (complex) to master and unless you use it very regularly you have to relearn what you know all over again. I suspect it is really very simple to master and that I may simply not have concentrated or praciticed with it for long enough. I know it enough to use it to keep track of my simple development activities, but if anything goes wrong with a push or pull then I'm in trouble, and though I have read over and over again how to merge branches or fix things that won't merge, I haven't really much a clue in practice about either, except that 'things' have to match appropriately at both ends. Pity, really, because I realise git... does all I would need, and I keep meaning to spend more time mastering its finer points, because I really see how useful it is for my overall needs and grand plans, but alas there are too many things in my todo lists and too little time in the day.

[rerwin]

taersh,

I had the same feeling of being overwhelmed by GitHub, so wrote a tool, pgitprep, to manage updates to the woofCE repo. I posted it in the old forum but plan to add it to the new forum soon.

The package as at:
http://oldforum.puppylinux.com/puppy/vi ... ed#1012495

Please consider trying it before killing your account. Although there is no detailed tutorial, it may be somewhat intuitive. Just ask me any questions necessary to keep you going with it. It does everything on your PC except create the pull request, which you create online.

Richard

[taersh]

@rerwin

Thanks.

I will give it a try.

[taersh]

@rerwin

Ok, I have setup everything with success.

The GUI of pgitprep is now at maintain branches. I don't know what to do right now.

Am I going to replace the init script plus the sfs_load script inside my local Woof-CE branch/directory (or whatever it's called)?

What's my next step to do?

Thanks in advance.

[taersh]

Hi.

After doing a manual comparison between the init script of Woof-CE and the init script of FossaPup64 I found differences.
So, the init script of Woof-CE has already changed. Then it wouldn't make any sense to submit my modified init script to Woof-CE, unless I would apply the changes to the new init script of Woof-CE.

That's disappointing. Hurdles after hurdles and one is even more time consuming then the other.

[rerwin]

After doing a manual comparison between the init script of Woof-CE and the init script of FossaPup64 I found differences.
So, the init script of Woof-CE has already changed. Then it wouldn't make any sense to submit my modified init script to Woof-CE, unless I would apply the changes to the new init script of Woof-CE.

That's disappointing. Hurdles after hurdles and one is even more time consuming then the other.

Thanks for trying the tool. It is better to find out up-front that there is a newer version than to regress things or be rejected later in the process.

I infer that you have created a "branch" different from "testing", or you would not have gotten this far.

Now you know to merge your changes into the latest version. You can either edit the (newest) copy already in puppylinux-woof-CE.d or modify a copy of your version to add the differences in the new version (or vice versa) and then "import" (in pgitprep) your merged version into the branch.

[taersh]

No, it was the testing branch.

At least it's named on top of the GUI of pgitprep.

Which one is the one to fork?
Master?

[taersh]

I had forked the master branch on github, removed my local branch and started from the beginning.
Though, the new locally created branch is again the testing branch.
Do I need to remove my forked testing branch on github?
If so, how?

Edit:

I downloaded the master branch .zip and extracted it into a new local directory. No success at all.
The GUI in the end still shows testing being the branch.

This is a waste of time!

[taersh]

Ok.

After clicking Ok on maintain branch, I choose to select another branch and entered master.
Now the GUI shows master as the active branch. Somehow the content of directory 0initrd looks different.
However: the init script is still different compared to the one of FossaPup.

So, I stuck here, as I don't have time to apply my changes to this new Woof-CE init script.
I'm working on a new Puppy. First time ever I build it with XFCE Desktop.

[rerwin]

The way I do it, I create the local repo with pgitprep. It downloads the testing branch to puppylinux-woof-CE.d, wherever you tell it to put that directory. That branch cannot be modified. You also connect the local repo to your github account. Those are done by the first two radio buttons in the main window.

Skip the "Synchronize" button because 'testing' is already sync'ed.

Create a branch for your new scripts. That will be the "container" for your changes.

Then you can go to "maintain code", to make your changes, verify them with a slick two-pane difference display (by kdiff3 if you installed it), stage and commit them, then "push" the commit to your github repo.

[taersh]

Ok thanks.

I wasn't aware that I can skip syncronize of testing.
Just clicked Ok all the time.

How do I skip this?
When do I skip this?
After what action do I need to skip this?
Do I need to click Cancel somewhere?
When?

There is no Skip buttons to click. There's only Ok and Cancel buttons (plus Yes and No) on all the GUI's that pops up.
Cancel to me means don't continue anyway.

Please give a bit more clear information on how to use this.
Then I will give it another go, when I found time to apply the changes to the new init script.
Of course, I will build a new local repo first.

Create a branch for your new scripts. That will be the "container" for your changes.

What does it mean?

I don't enter master and using a different name?

[rerwin]

By "skip", I mean that you do not need to synchronize the testing branch if you have just downloaded it by using the first button in the main window. I synchronize 'testing' whenever I start a new set of updates, to be sure I have the latest versions of files before modifying.

The buttons to control the tool are only:
'OK' to effect the selected button's action
'Done*' to exit the window

I see that the window for adding or changing a branch name has the 'Cancel' button, which I infer from your question is confusing. I will change that button to "Done - No change', to be clear. Note that the 'X' button in the upper right corner of a window always aborts the tool immediately.

In the 'Maintain code' window there are 3 'Modify' buttons but nothing about getting to the 'init' file. For that special case, select any 'Modify ...' button (& OK), then select 'Edit...' or 'Import...' (& OK), then double-click on '..' twice to go up two levels, then double-click directory initrd-progs/, then 0initrd/ to get to where 'init' resides.

If you haven't done so already, please use the "Help" buttons, on the windows that have them, to see what to expect with the tool. If you find anything confusing or not explained, please tell me, because I want the help text to be useful to newcomers.

[m1k3]

I wish we could have used Fossil SCM. It’s so much more intuitive to me.

[taersh]

@rerwin

Hi.

I think the problem is with the buttons of the GUI that's automatically translated to DE.
They always say "In Ordnung" und "Abbrechen" which I translate to "Ok" and "Cancel"

I still don't know/understand what to enter into the entry field for a branch

I never get to the part where are 3 Modify buttons.

May I ask you to go through all the steps necessary and doing a screenshot of each step?
Explaining what you did on each step?
Then put the screenshots and explanations together and attaching it to a post?

Thanks in advance...

[rerwin]

I think the problem is with the buttons of the GUI that's automatically translated to DE.
They always say "In Ordnung" und "Abbrechen" which I translate to "Ok" and "Cancel"

I still don't know/understand what to enter into the entry field for a branch

The automatic translation of OK and Cancel makes sense since there is probably no translation of the rest of pgitprep. Now I understand your confusion about what "Cancel" means. It means you are finished using the window, instead of activating the selected option.

The branch cannot be 'testing' or 'master'. Create a name that reflects what you will be updating. It identifies the set of changes/additions you make on top of the testing branch. Consider that to be the top-level group for your changes. Later, you will sub-group them into one or more "commits". You can add further updates to the branch and commit them later.

You can organize branches and commits however it makes sense to you. For example, I recently grouped my networking updates into a branch named 'network_connect_20200820', containing changes to SNS, frisbee, pgprs and the connectwizard components. I submitted separate commits for each of those, not necessarily at the same point in time.

As you commit files, they disappear from view but are not forgotten. When you "push" the branch, the queued commit(s) get copied to your github fork repo.

For your case, the changes implement an expansion of the number of dedicated "drv" file system layers. So, your branch could be "add_lettered_drvs". Everything could go into a single commit, since the changes all relate to the same feature.

May I ask you to go through all the steps necessary and doing a screenshot of each step?
Explaining what you did on each step?
Then put the screenshots and explanations together and attaching it to a post?

That is asking for a lot of work on my part. I prefer to improve the help information to give you what you need in order to understand how to use the tool.

I see in the "help" for the main window that it gives the overview but does not summarize the typical operation steps. I will work on that, for starters, and post the results here.

[rerwin]

Here are the help segments that I have. They differ slightly from what you see in the pgitprep version you are using.

Let's edit those or add some new ones.

=== Main window help:

The GIT Preparation Utility allows users to maintain code updates locally and then transmit them to a GitHub account for pull requests. Users can maintain code separately from the woodCE GIT repository and then import the new or modified files to the local woofCE repo. Or the user can edit files directly in the local repo. Then the updates can be verified, committed and then uploaded to the corresponding GitHub user repository.

This utility utilizes the kdiff3, meld or xfdiff graphical differencing tool and the git gui repository browser, which supports staging and committing of changed, added or deleted files.

Before using this utlity, create your "forked" GitHub woofCE repository.

To operate this tool, use the radio buttons to (1) build a local copy of your github fork of woofCE seeded with the testing branch, (2) connect it to that fork, (3) create a branch to contain your updates, then (4) make your code changes for that branch.


=== build help:

To build a local woofCE repository, you must have created your fork of the woofCE github project, https://github.com/puppylinux-woof-CE/woof-CE.

First, designate or create a development directory to contain the repository subdirectory. Your directory could be one already used for development. If it contains a repo, you will be asked whether to replace it.

The repo will then be built from the github repo, as directory 'puppylinux-woof-CE.d', and will populate it with the content of the 'testing' branch -- wait for it to complete (SUCCESS!).


=== Connect help:

"Connecting" associates your local repository with your fork of the woofCE project.

You will need your github user ID and password in order to connect your new local repository to your github fork.


=== Synchronize help:

As the "testing" branch is maintained on GitHub, the local repo testing branch, as well as that in your corresponding fork on GitHub, will fall behind the GitHub testing branch. Synchronizing downloads the GitHub "testing" branch into the local repo and then uploads it to your GitHub fork. Your local updates are preserved, until you delete a branch (usually because they are now in "testing").


=== Maintain branches help:

Branches are used to collect and manage related updates in a bundle that is submitted online for integration by a "pull request". A branch must be specified (but not "testing" or "master") in order to make any updates and commit them for integration. Deleting a branch will remove all of its updates from the local repo and restore the "testing" branch versions, but will not affect the GitHub copy of the branch.


=== Maintain code help:

To maintain code in the local repository, choose one of the Modify buttons. You can edit text files directly, import files or entire directories or delete files. Navigate the file trees in file/directory selection windows. (Double-click ".." to move up one level.)

To import files or subdirectories:
1. Select repo (sub)directory to receive the imported files.
2. Select (sub)directory containing the file(s) to be imported.
3. Select a file within that directory and click "OK".
Or click "Done..." to return to the previous window(s).

[taersh]

Thanks.

I will try to include the new Help texts into the pgitprep and give it a go then.

[taersh]

Damn!

There's another problem. The sfs_load script has changed also.
It's changed from 3.0 to 3.1w. The changes are somehow hard for me to follow.
Since I'm not the developer of sfs_load I can't guarantee to successfully apply my mods to the new sfs_load.
It was easy for me to do in 3.0 after I applied the first mod of having the mdrv ability in 2.3.7 and tested with success.
For 3.1w I would need to start from scratch!
Further more I would need to make durable tests while using the mods in 3.1w.
The 3.0 version I'm using now for a long time in my own build of Bionic64.
I fear some more changes may take place during these testing period of the modified 3.1w.

So, what to do?
Is shinobar a member of the new forum?
If so, would he be willing to introduce the --no-copy option to the latest sfs_load?
Or even better to apply also the bdrv, cdrv, gdrv, mdrv, ndrv and vdrv ability to sfs_load 3.1w?

I'm clueless...

[taersh]

Ok!

I'm done. I deleted my github account.
I will work on and use my modifications for my personal needs in the future only.
They will be added also to the Puppies I'm creating/publishing only.

The time needed for such I can afford. Anything else is too much time consuming for me,
as my main purpose is doing music. Never mind.

Thanks for the support.

Edit:

As I wrote earlier: my place is on the forum, not at github.

[rerwin]

There is a tool that facilitates merging two versions of a file. It is kdiff3, which takes a common base (fossapup) and merges the changes from two updated files.

I am willing to do that for you, give them to you for testing and then send the merged versions to github.

I can also send you the command to use for a kdiff3 merge of your changes, so you can see how neat kdiff3 is.

Richard