UCI extensions to UNC extensions


Forum: Other Help Topics
Topic: UCI extensions to UNC extensions
started by: meo

Posted by meo on Dec. 05 2006,17:10
Hello everybody!

Is it possible to convert UCI extensions to UNC extensions? If it is and someone knows how I'm very eager to know. Thanks in advance!

Have fun with DSL,
meo

Posted by ^thehatsrule^ on Dec. 05 2006,17:42
I haven't used UNC's yet, but maybe this can help.

There are probably several ways of doing it, but you can
- mydsl-load ext.uci
- files will be in /opt/ext
- ie. find /opt/ext > ext_files.txt <-- don't include user.tar.gz
- you can add the files in user.tar.gz (if it exists), which is treated like a regular mydsl extension
This should get you all the data and filelists needed to build a new extension.

Following the guide in creating uci extension on the section of updating/editing them should help.

Posted by roberts on Dec. 05 2006,19:16
There would be no point to convert UCI to UNC.
UCI type extensions enjoy a feature that UNC cannot.
Both are mountable extensions, but UCI by definition is totally self-contained.
Being so, means it can be mounted and umounted at will. That is why we have a ucitool as a right click option under the MyDSL icon.

Since .tar.gz is also self contained under /opt, it would make sense to convert .tar.gz to UCI.  And .dsl to UNC.

In due time, this will likely happen. It took along time for users to begin to use UCI, so too for UNC.

I posted instructions on how to make a .dsl into a .unc and WDef took those instructions and posted a script < dsl2unc >

Currently the repository has separate sections for UCI and UNC, so it will take some reorganiztion to move forward.



Posted by meo on Dec. 05 2006,20:34
Hi again!

Thanks for fast feedback. Anyway UNC-files are imperative for my purposes. I'll investigate further.

Have fun,
meo

Posted by meo on Dec. 06 2006,12:38
Hi there!

If you check out my last remastering HOWTO you'll understand my interest in unc-files instead of uci-files.

Have fun,
meo

Posted by mikshaw on Dec. 06 2006,15:13
I don't get it.
If you're just putting the gcc/gnu-utils unc files next to the KNOPPIX file, that can be done with mkmydsl.
If you're remastering KNOPPIX, you have no need for unc because you can install files directly to the base filesystem.

I agree with roberts...there is no apparent reason to convert uci to unc.  A uci file is already built to run from a mounted location, without the extra work of linking it into the base system with unionfs. Just about any other package type (deb, rpm, dotpup) will be more appropriate to convert to unc than a uci would be.

Posted by meo on Dec. 06 2006,15:35
Hi mikshaw!

Have you checked the latest Remastering HOWTO (page 62)? The point is that it all ends up INSIDE the KNOPPIX file and it can be done very fast and easy. Furthermore it's intended for use with USB pendrives or as in my case a CF-card. Where you can swap to another KNOPPIX file easily and then just reboot and fire up your remastered version of DSL.

As always have fun,
meo

Posted by ^thehatsrule^ on Dec. 06 2006,16:31
Apparently the unionfs implementation "supermounts" on the /KNOPPIX cloop, which was previously uneditable.  Not that I understand the implementation itself (yet) - but I can see how this can be handy if you are making remaster a lot without scripts.

Unfortunately doing it this way doesn't seem to work in all cases.  My first test was with the XFree86.unc.  It looks like a uci in the fact its also mounted in /opt, with a user.tar.gz - but I think unionfs kicks in here and the XF86 usr data is accessible through /KNOPPIX.  However, user.tar.gz is mydsl-loaded 'normally' and only goes into /ramdisk , but unionfs doesn't touch it (therefore not in /KNOPPIX).

In addition, trying to remove a file from this... such as /usr/X11R6/bin/XFree86 (which would be on /ramdisk) results in a segfault, and consequent things, such as ls /usr/X11R6/bin will results in the program hanging.  I assume you can only modified those loaded by unionfs to be modified through that interface.

This is how I understand it so far... feel free to explain, etc.

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.