Multiple SFS support in initrd
Hi @Mavrothal
Just for the sake of understanding and consistent with this discussion, if you have a 64bit PC and a blank CD/DVD, pull LH64 Mariner and boot it pfix=ram
It wont take you longer than 2 minutes to see the operational aspect of his simple SFS processing at boot time. Copy2RAM is an unnecessary convenience. But, you'll see why.
Here to help
Just for the sake of understanding and consistent with this discussion, if you have a 64bit PC and a blank CD/DVD, pull LH64 Mariner and boot it pfix=ram
It wont take you longer than 2 minutes to see the operational aspect of his simple SFS processing at boot time. Copy2RAM is an unnecessary convenience. But, you'll see why.
Here to help
Hi mavrothal.
Thanks, this is helpful a lot.
Any hints on this differences?
ZDRV:
ADRV:
RSH
Thanks, this is helpful a lot.
Any hints on this differences?
ZDRV:
Code: Select all
ZLAYER=':/pup_z=ro'
Code: Select all
ALAYER='/pup_a=ro:'
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]
Hi
hehe.. I just built a POC Slacko, updated 3.8.2 kernel (supporting HFS, btrfs and f2fs) with an A drive only.. works beautifully. I may even upload it, but i want to figure out f2fs.
I also hacked 3builddistro to support the a drive concept, it does nothing more than produce a sane DISTRO_SPECS. An iso with A drive needs to be made manually afterwards. Patch later.
Thanks mavrothal
hehe.. I just built a POC Slacko, updated 3.8.2 kernel (supporting HFS, btrfs and f2fs) with an A drive only.. works beautifully. I may even upload it, but i want to figure out f2fs.
I also hacked 3builddistro to support the a drive concept, it does nothing more than produce a sane DISTRO_SPECS. An iso with A drive needs to be made manually afterwards. Patch later.
Thanks mavrothal
Puppy Linux Blog - contact me for access
zlayer is the last one, alayer a middle one.R-S-H wrote:Hi mavrothal.
Thanks, this is helpful a lot.
Any hints on this differences?
ZDRV:ADRV:Code: Select all
ZLAYER=':/pup_z=ro'
RSHCode: Select all
ALAYER='/pup_a=ro:'
Do the replacement in
Code: Select all
mount -t aufs -o udba=reval,diropq=w,dirs=${UMNTRW}${UMNTRO0}${ALAYER}${YLAYER}${UMNTRO1}${ZLAYER}${UMNTRO} unionfs /pup_new
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
That's a good start but spitting at build time is even better01micko wrote:I also hacked 3builddistro to support the a drive concept, it does nothing more than produce a sane DISTRO_SPECS. An iso with A drive needs to be made manually afterwards.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
For sure.. or even renaming a custom sfs to the adrive, more flexible, less prone to error. (Maybe more chance of acceptance upstream ). Baby steps.mavrothal wrote:That's a good start but spitting at build time is even better01micko wrote:I also hacked 3builddistro to support the a drive concept, it does nothing more than produce a sane DISTRO_SPECS. An iso with A drive needs to be made manually afterwards.
Puppy Linux Blog - contact me for access
I'll be rebooting my machine again in a few days to add some drives... I'll do a few startup schemes and get you some hard results. From memory... yes I have seen memory usage, but memory isn't always the most accurate thing. Give me some time and I'll get you the info.mavrothal wrote:Never used LH64 so I do not know for a fact.Q5sys wrote: Actually LHP64 can load all SFS into ram. You have the option to run them from disk or load to ram.
I just glanced at the code and although I can see COPYEXTRASFS2RAM I can not see how more that one SFS is loaded as UMNTRO.
I probably miss something, but can you actually see RAM usage increasing as much as the SFS size when more than 1 extra SFSs are loaded with the copy2am option? (I know you have the RAM for that test )
I knew I had seen this.
This is NOT Jeminah's model. It is one that is in place with LH64. ((I believe it may have been missed/overlooked as it is aimed for his 64bit platforms) See this pictorial for easy understanding.
It is NOT intended to shift current discussion, rather, to present one working concept.
Hope this helps and provides clarity.
This is NOT Jeminah's model. It is one that is in place with LH64. ((I believe it may have been missed/overlooked as it is aimed for his 64bit platforms) See this pictorial for easy understanding.
It is NOT intended to shift current discussion, rather, to present one working concept.
Hope this helps and provides clarity.
That's a good point - plus: a little guide or help for the less experienced of us - like me!gcmartin wrote:It is NOT intended to shift current discussion, rather, to present one working concept.
Ok.
Back to just a adrv, but still something is getting wrong. The sfs goes to the adrv, I can see the files and use the applications or whatever is in the sfs. I have loaded up to 39 sfs files using sfs_load 1.9.6 (shinobar) - also can unload.
But: after unloading an sfs I can't mount sfs files or iso files by the usual left-click action.
The same on my second edition, adrv & ddrv, which I do attach here, hoping someone will have a look and find my "bugs"?
Seems it's not clear to me , how to handle the tmpfs dirs and the loopX...
Thanks
- Attachments
-
- init.gz
- (90.43 KiB) Downloaded 938 times
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]
I really have a hard time understanding.R-S-H wrote: Back to just a adrv, but still something is getting wrong. The sfs goes to the adrv, I can see the files and use the applications or whatever is in the sfs. I have loaded up to 39 sfs files using sfs_load 1.9.6 (shinobar) - also can unload.
But: after unloading an sfs I can't mount sfs files or iso files by the usual left-click action.
The same on my second edition, adrv & ddrv, which I do attach here,
After you mount 39 sfs with sfs_load if you unmount (with sfs_load?) *anyone* of those 39 (not the adrv) then you can not mount sfs with sfs_load or you can not mount them with your "left-click"? But before you unload an SFS the left-click works?
What the left-click calls in your case? filemnt? other?
What the command "filemnt /path/name.sfs" reports?
BTW SFS-load also needs to be patched so will not unmount a/b/cdrv.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Hi mavrothal.
If I'm talking about mounting an sfs, I do mean the single left-click-action, loading an sfs means to me: using sfs_load.
Sorry, but I try my best...
Yes, the left-click works until I do unload an sfs (sfs_load) and, yes, it calls filemnt.
I will try the patch of sfs_load, but could you please have a look into my init script for the z,a,d(drv) and how I did arrange them (increasing its numbers etc. - btw: all needed dirs are in initrd.gz, I can see and use everything, even though I can not mount the iso, sfs with right-click, I can load more sfs files using sfs_load).
Thanks
If I'm talking about mounting an sfs, I do mean the single left-click-action, loading an sfs means to me: using sfs_load.
Sorry, but I try my best...
Yes, the left-click works until I do unload an sfs (sfs_load) and, yes, it calls filemnt.
I will try the patch of sfs_load, but could you please have a look into my init script for the z,a,d(drv) and how I did arrange them (increasing its numbers etc. - btw: all needed dirs are in initrd.gz, I can see and use everything, even though I can not mount the iso, sfs with right-click, I can load more sfs files using sfs_load).
Thanks
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]
So what is the "filemnt /path_to_sfs/name.sfs" output when typed in the terminal (after you have unloaded an sfs and left-click fails). ie what is the error? and why do you think that is realated to init? Is this the ONLY change between a working and an non-working version?R-S-H wrote: Yes, the left-click works until I do unload an sfs (sfs_load) and, yes, it calls filemnt.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
I'm currently using the no-adrv-initrd.gz, so I need to reboot to get the error message from terminal. Will post this later.mavrothal wrote:So what is the "filemnt /path_to_sfs/name.sfs" output when typed in the terminal (after you have unloaded an sfs and left-click fails). ie what is the error? and why do you think that is realated to init? Is this the ONLY change between a working and an non-working version?R-S-H wrote: Yes, the left-click works until I do unload an sfs (sfs_load) and, yes, it calls filemnt.
Yes, this is the only change, but I'm not sure yet, because of the not yet patched version of sfs_plus...
I will first do these patches, and after this, doing everything again, watching for the resuts...
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]
Would be easier then if you post a "diff -ur" between the adrv and the non-adrv initramfs folders.R-S-H wrote: Yes, this is the only change, but I'm not sure yet, because of the not yet patched version of sfs_plus...
Also the SFS_load patch is *only* for ydrv.
The latest sfs_load already has a provision for adrv and if you use b/c/d/e-drv must modify the ydrv patch accordingly.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Ok. Here it is!Would be easier then if you post a "diff -ur" between the adrv and the non-adrv initramfs folders.
- Attachments
-
- diff-out.txt.gz
- remove .gz
- (42.35 KiB) Downloaded 867 times
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]
Oh!!!
I have discovered right now, even though I'm using sfs_load 1.9.6, the adrv is not taken under sfs_load's provision for the adrv. This is because of sfs_load uses DISTRO_ADRVSFS, which I don't. I send the sfs for the use with the adrv from boot menu and LazY Puppy DISTRO_SPECS does not have the DISTRO_ADRVSFS.
Could this be a clue/reason for this weird behavior? I do believe so...
I have discovered right now, even though I'm using sfs_load 1.9.6, the adrv is not taken under sfs_load's provision for the adrv. This is because of sfs_load uses DISTRO_ADRVSFS, which I don't. I send the sfs for the use with the adrv from boot menu and LazY Puppy DISTRO_SPECS does not have the DISTRO_ADRVSFS.
Could this be a clue/reason for this weird behavior? I do believe so...
[b][url=http://lazy-puppy.weebly.com]LazY Puppy Home
The new LazY Puppy Information Centre[/url][/b]
The new LazY Puppy Information Centre[/url][/b]
mavrothal
here is a 3builddistro patch that works, manually adding adrive, so any custom adrive can be added, tested working.
it's against commit faca226129. (20130310)
here is a 3builddistro patch that works, manually adding adrive, so any custom adrive can be added, tested working.
it's against commit faca226129. (20130310)
- Attachments
-
- 3builddistro_adrv.patch.gz
- (1.72 KiB) Downloaded 869 times
Puppy Linux Blog - contact me for access
Looks good. Time to start lobbying01micko wrote:mavrothal
here is a 3builddistro patch that works, manually adding adrive, so any custom adrive can be added, tested working.
it's against commit faca226129. (20130310)
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
There is only one way to find out...R-S-H wrote:Could this be a clue/reason for this weird behavior? I do believe so...
This and running that filemnt command (preferably with a "set -x" in filemnt if problem persists)
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==