dCore Import Debian Packages to Mountable SCE extensions > dCore X86
Wiki tentatively complete
sm8ps:
I have completed my proposed work for the wiki with the extensions page. As predicted, I got it done by the end of the month; luckily I do not remember which one exactly I had been talking about. ;) I would be glad if you all could look it over because I certainly learned a lot about extensions and so I may have missed one point or an other.
Furthermore, I have polished the entire set of pages so that they hopefully are easy to navigate through. When I find time, I shall want to add a page about the new ISO installation but that will not happen very soon. Maybe somebody else will beat me before the finishing line (maybe even you!). It is exciting to see how dCore comes along!
I think it is time now to "publish" the dcore-section of the wiki more openly. Specifially, I suggest adding the dcore:welcome-page to the navigation panel but this has to be done by a moderator. However, I have not been successful in contacting that person. Can anybody help?
sm8ps:
While writing about extensions, I explored and learned a lot. In the course of this process, I stepped over some technical questions:
1. ) What is the logic behind sce-import asking to select a deb-package among list when the very same package is in the list? E.g. sce-import libphonon4 gives
--- Code: ---Select Package for libpulse-mainloop-glib0_4.0-0ubuntu11_i386.deb
(...)
26. libpulse-mainloop-glib0_4.0-0ubuntu11_i386.deb
(...)
--- End code ---
among dozens of other candidates. That is the exact package so why do I need to select it? Which other packages would fit and how can I know?
2.) What are the data.extensions for (-data.tar.gz)? I see .deb-packages, prebuilt tar.gz extensions from the Tinycore repository and -data.tar.gz files in my tce/sce/ directory. How do they relate?
3.) What is the tce/import/ directory for? I see some sub-directories but cannot make out any specific logic. Ditto for '/tce/sce/update/'.
4.) I learned that the deb2sce files under /usr/local/tce.installed/ are dCore-specific start scripts. Is it possible to browse the repository they come from so as to get an over-view?
5.) What about the memory consumption of mounted SquashFS? Is the full file un-packed in RAM or only the used files/blocks? That is crucial for the urge to create dependencies among extensions in order to keep their size small. I hit Google search with any kind of search phrase I could imagine but could not find anything.
6.) sce-load calls 'depmod -a' but that command is not available (on my system at least). Is this a problem in general?
7.) What is the difference of the two files .installed and .debinstalled under /tmp?
Thanks for your consideration!
Jason W:
Hi.
1. What you saw there is what happens when the Debian or Ubuntu Packages list is updated ahead of ours. Does not happen often, but it can. That menu comes up when the filename from our DEBINX is not found, that is has been updated and Debian always changes their deb file names upon any updates.
2. Data extensions are extra files the package needs or benefits from to operate. The Core specific things that make the window managers work are in the data.tar.gz files.
3. tce/import is for downloaded debs and the working area of sce-import. sce/update is for updated extensions that get coped over on reboot.
4. Those startup scripts are created by us as needed, there is no upstream.
5. Mounted squashfs takes very little ram at all. Symlinking takes some, but nothing like what copying to filesystem would take. i have 1.7GB of squashfs SCEs mounted, uncompressed to file system that would be about twice that or more. But I can sit at a command prompt with all that installed and just 286MB of used RAM. A huge savings, and this is the same as with Core and it's TCZ mounted extensions.
6. If depmod command was not available, then any new kernel modules installed would not be usable, so I am quite sure you have it.
7. /tmp/.installed is for already run startup scripts, /tmp/.debinstalled is for already installed deb or custom packages. Not really meant to be directly used by the user under normal circumstances.
Hope this helps.
sm8ps:
Thanks for your extensive answers! They do make things more clear but I still have a few that I do not quite understand.
1. Do the package lists not get fetched directly from the Ubuntu/Debian repos? What other ("ours") is there in play? If the debinx.-files come from the Core-repos then how are repos under debextra handled?
2.&4. Is there a URL where one can look at these files ans scripts? I have been unsuccessful trying so.
6. You are right, depmod is available, of course. What I meant (but did not read out of my notes) is that depmod -h does not show the option -a. Presumably it does work nevertheless.
Jason W:
Our DEBINX files are in the link below, we have our own as we prune them to speed up searching that large file.
http://tinycorelinux.net/dCore/x86/
Below is the startup scripts and data files:
http://tinycorelinux.net/dCore/x86/import/
http://tinycorelinux.net/dCore/import/
depmod -a is the default behavior, the -a switch does not error even though no longer needed a current option since they apparently have that option grandfathered in as to not break scripts like ours.
Navigation
[0] Message Index
[#] Next page
Go to full version