-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New branches 'legacy' and 'rationalise' #789
Comments
I have removed some (not referenced above are I left |
gyro posted 2 patches in the forum
Regarding kernel-kit, I have to offer this as a slightly improved version Check it out and provide your impressions about it. initrd_progs: how exactly it should be merged? There are replacement for commands and bb-create-symlinks I'll copy rootfs-skeleton to my system to make sure everything is ok, i'll also start building a pup to make sure I don't break anything. |
|
@01micko, I actually have 5 in the pipeline.
|
Indeed that is the one @gyrog 😄
With some fairly trivial changes to @wdlkmpx has already began adding commits, most notably restoring 'init' and 'rc.sysinit' to the original place and deleting the old I look forward to your contributions and if anything is unclear, while I am a bit busy, I'll be as attentive as practical. Cheers! |
I think the static binaries (initrd_progs) must be in a repo. All of them in a tar.xz archive in this format: initrd_progs-binaries-$date.tar.xz I want initrd_progs to be used as a standalone app as well as part of a greater scheme (3builddistro). Perhaps a new switch: -prebuilt (build.sh will and download use already compiled binaries) and 3builddistro can call initrd_progs/build.sh this way (or another):
|
The init script needs a refactor to allow proper translations. The current implementation runs a modified init to do so.. crazy. Network Wizard has the right approach, it sources the the main english *.po file (actually a script with variables only, each variable contains a message), then it sources other files according to your locale. The same logic is applied in my modified MSCW.. that's the way to go. This is something that needs to be discussed with many people, specially translators. And those translations can go directly in the initrd-tree.. the initrd_progs repo can be used to advance this.. |
The init script could do with more than just a refactor to facilitate translations. It could use a major rewrite to simplify it, as well. |
gyro I think you should open a thread about the init rewrite and the work should be done in initrd_progs... when initrd_progs lands on woof-CE some directories will be deleted and in fact that would mean a new version of woof I strongly recommend you to "build" a initrd.gz file with a tahrpup or slacko, use it to test, and inspect the new apps and possibilities. Just run ./build.sh (will download about 150-200MB of stuff) and hit enter at any prompt (2), and then a initrd.gz file is ready. I'm also simplifying build.sh while adding some new functionality to make it completely independent ( puppylinux-woof-CE/initrd_progs@a627c92 ), so if you have any issues, just let me know, and do add your changes as soon as you see it's working, if something is broken i'll perhaps notice it and i'll notify you. |
@wdlkmpx, |
The whole "woof-arch" should disappear or at least most if it. I can add a "pkg" to initrd_progs to compile and archive all the support/boot apps and that can be downloaded afterwards. The commit history will grow by 15mb for no apparent reason and, i would suggest to restart in a few months but before that put the repo including commit history in a tar.xz archive ready to download for everyone to see what happened before and look for the legacy branch, though nothing of value would be lost, except perhaps Arch compat, but again and i can make it come back, but it has gone the wrong way.. I wonder what .bac files need translation into a more reasonable language, i don't understand baCon though, looks primitive like a Windows shell script |
BaCon is structured Basic. It's fairly easy to grasp. It converts the code into C then compiles it, but the C sources produced are rather cryptic. Probably just as easy to go back to shell. Another thing to consider is updating encryption to support dm-crypt instead of the old DES and XOR, then we can update losetup >= util-linux-2.22 instead of sticking with the ancient version which dropped support -
https://www.kernel.org/pub/linux/utils/util-linux/v2.22/v2.22-ReleaseNotes |
Yeah that should be a priority. I'm already using util-linux 2.27, the losetup in the new initrd is from util-linux 2.28... looking at the config file of the kernel i'm using, i see this: CONFIG_DM_CRYPT=m The agent said that this was implemented in fatdog long ago, so anybody using fatdog paste code here to look at it As usual, the Arch wiki also provides lots of info to read https://wiki.archlinux.org/index.php/Dm-crypt I'll look into this |
After commit puppylinux-woof-CE/initrd_progs@f3f2944 initrd_progs is ready to be merged so I can actually face a problem that I will solve. I will create a pull request |
I opened a thread at the forum: http://murga-linux.com/puppy/viewtopic.php?p=907290#907290 meanwhile micko... i was not able to get the armv6l cross compiler to work. Perhaps it works in your slacko64, type |
busybox built, exited on disktype. |
Well, slacko packages are taking forever to download. If there are 10 mirrors, on each download choose a random mirror (between 1 and 10).. Obviously this is just me doing and thinking about everything, and it will continue that way until i shut up... so I wonder where a lengthy discussion about all of this can happen.. |
I think that by now it's safe to wipe compatibility with Red Hat or RPM based distros such as Mageia and Scientific Linux and just remove any RPM traces from the build scripts... petget should keep supporting that format, some very basic binaries should work on any distro.. It would also be a good idea to create a newer LFS Puppy, like the old one, for those who want to port Puppy by compiling themselves, but this task is huge. I know this is something already done, perhaps by fatdog? (never used it). If there is code, something already usable, we should just use it and try to improve it................ |
2createpackages can get very heavy when processing packages with lots of files, reminds me of the new2dir script, the same logic and heavy processing. It tries to strip binaries.. and that happens again in 3builddistro-Z Half the code in 3builddistro is commented out... should be deleted. I see repetitive code in all the build scripts, this can be simplified by sourcing a script with functions.. |
I think we should start with mass-scale code deletion, before we do any refactoring. Something in the spirit of |
Yes of course, time to delete |
I created pull requests for Scientific/RHEL and Arch. Low-hanging fruit. |
So it's being deleted. Apparrently debian squeeze was the last release before multi-arch took over, so it has be deleted anyway in order to fix 2createpackages 3builddistro-Z
Bear in mind that @mrfricks is trying to push a reasonably stable xenial pup. I would leave testing alone, let him get that out the door then go for it. |
@peabee, Thanks for the iso, downloading now, I'll give it a go. |
What copies rc.sysinit and rc.update to the save-layer? |
Ok, so I'm running slacko64-6.9.5 built from slackware64-14.2 packages and it's all running pretty smooth. loaded libreoffice and @peabee 's latest chromium64 sfs's and no dramas there, even after rebooting a couple of times. I'll upload this for broader testing.
The very latest (but I have a couple of patches to upload later today - slacko specific) Probably take a few hours to upload on my brilliant connection.. might even use my phone so it's faster. |
Bugger.. nearly as slow on my phone - 4G 😕 |
@gyrog I see that bug too. Also functions4puppy4 is copied and rc.country |
I don't see where it happens. in rootfs-skeleton i see greps in sfs_load (to be deleted) and a few other scripts.. but is that enough? Probably something outside woofce or maybe an aufs bug? Does this also happen in tahrpup gyro? |
In the rationalise branch sfs_load does not even grep rc.sysinit.
actually nothing touches rc.sysinit, pmodemdiag greps a temp
rc_sysinit. There is no evidence..
|
anyway, slacko64-6.9.5 alpha is released .. http://www.murga-linux.com/puppy/viewtopic.php?p=920437#920437 |
The rc.* copyup "bug" is part of first boot in LxPupSc-16.08.992, I'll try tahrpup 6.0.5. |
looks like they get copied up in rc.update... if they were never copied in the first place then that code wouldn't be needed. |
Or maybe not but the fact that that code is in rc.update shows that it is intentional. |
In tahrpup 6.0.5, rc.update only copies rc.sysinit if it thinks it's a version update, and then it also copies lots of other stuff including rc.services. |
I just did a pristine boot of my latest slacko and there is a huge clue as to why these files are copied up at initial boot in /tmp/bootsysinit.log
So I guess it is the SSS or whatever it is that translates files. |
So.. when quicksetup is run then SET_LOCALE="yes" .. therefore Ok, we have the cause but the solution may not be so easy. |
But locating the cause is a good start. |
All DISTRO_IDSTRING processing in Woof-CE rationalise can be removed. |
I just created a ydrv conatining the flag file in /etc/ that stops quicksetup from running, then did a first boot of LxPupSc-16.08.992, I didn't get any quicksetup screen, and I didn't even close the welcome screen, simply looked in /initrd/pup_rw/etc/rc.d and the 5 squatters were there. |
The "bug" occurs somewhere in rc.sysint, they're not there at the beginning, but they're there at the end. The bootsysinit.log also contains messages abot translating these files just after eth0 network message. |
Xenialpup-7.0.4 has the "bug" - DISTROSPECS doesn't say which version of woof-ce it's built with..... |
It looks like 'fixscripts' is being run. The question is by what and why? |
Many scripts need to be audited, some pivotal scripts should be in
rootfs-skeleton, i see why development stopped at some, it's probably
a matter of geological eras..
I see James C reported an important bug, he has many partitions and a
distro installed in each one of them. So it's probably a good idea to
create many partitions in a usb with different filesystems to see the
performance..
|
If you're talking about the "jumbled" drive icons, then robin2 has it right, they're not jumbled, the partition names are just sorted alpabetically. A local comparision function might be required. |
Re eCryptfs for save layer encryption: |
So... plan B? crypsetup?
|
There is no plan B. |
so it seems a "rebase" to fix something caused a little trouble. i'll add a script to download and setup a local woofce git repo in a few seconds. i'll just edit the one i have which i've used it for all the repos i contributed to before. i think the petbuilds should be in the main repo.. or at least a "special" petbuilds.. the reason is that i want to add some "standard" builds... busybox, util-linux, coreutils, wget etc.. to be compiled one by one. this will bring consistency and would help older woofce distros.. the templates should follow the same logic regarding what apps are chosen/discarded. |
@@this is a script to download and setup a woofce local repo ready to be properly synchronized with the remote repos (github) when a user enters commands, it only does the basic stuff... |
For more information, I will refer readers to this blog post.
I have created 2 new branches
legacy
andrationalisation
.Important
As @mrfricks and myself are in development please keep changes to testing as bugfix only or minor updates unless there is a pressing need for change. After release of xenialpup and slacko-63x (bugfix) it is intended that
rationalise
branch will be merged withtesting
and deleted. Hopefully this will only be a matter of weeks. Of course all xenialpup changes before and at release should land intesting
so that we can merge that withmaster
.'legacy'
legacy
branch is purely in place to preserve old code. Read the README before making changes to that branch - changes are discouraged.'rationalise'
rationalise
branch is for sweeping new changes including but not limited to:fdrv
is dealt with. See fdrv appears in DISTRO_SPECS but is not loaded #785kernel-kit
and rationalisation of codeNotes
I expect that @zigbert will keep updating his progs in
testing
. Therefore, before anyone makes a commit or PR torationalise
be sure that you have merged the changes intesting
. This will make for minimal conflicts whenrationalise
is merged back into testing.Of course any minor bugfixes and enhancements should land in
testing
first. So if you have a change to make, carefully consider if it is major or minor before committing.As usual, have fun!![:octocat: :octocat:](https://github.githubassets.com/images/icons/emoji/octocat.png)
The text was updated successfully, but these errors were encountered: