A .CI extension question

Forum: myDSL Extensions (deprecated)
Topic: A .CI extension question
started by: dare2dreamer

Posted by dare2dreamer on July 20 2005,07:14

Is there any way to get a .ci/.uci to mount someplace other than /opt?

I'm working on converting the nxclient.dsl I hacked up to a .ci extension, but from the looks of it the damned thing is hardcoded to run only from the /usr/NX directory.

As everything in the client is otherwise self-contained, I figured it would be an excellent candidate for the compressed filesystem styled extensions. If .uci/.ci could mount itself to /usr/NX, I think we'd be in business (and saving loads of aging hardware RAM).

Posted by SuperLou on July 20 2005,13:19

I'm not so good as this kinda stuff myself, but I'm pretty sure it's a requirement of a .ci to run under opt, or it appears that way to me from < http://www.damnsmalllinux.org/talk/node/85. > If it's hard coded that way you may have to open up the source code and go a-changin' things.

Posted by cbagger01 on July 20 2005,13:19

Such a restriction usually means that you should turn it into a *.dsl extension instead of a *.uci extension.

However, you could get creative and make it into a *.uci extension and then build a small sidekick *.dsl extension that would be used to create symlinks back to the *.uci files that are in /opt

ie:

/usr/NX --> /opt/NX

Posted by mikshaw on July 20 2005,13:43

You could probably mount it to /usr/NX manually rather than through mydsl-load, but I'd say cbagger's suggestion would be simplest.

Posted by ke4nt1 on July 20 2005,15:21

If it is truly a self-contained app, then recompiling it using the option
./configure --prefix=/opt/NX
should be an easy task, if the program is easily compilable.
Then creatng a .uci from it should be no problem.

73
ke4nt

Posted by hawki on July 20 2005,16:57

Hi
If you are building custom .uci extensions I think you could put your symlinks in the user.tar.gz file. Then it would auto-magically point to /opt.

/usr/NX --> /opt/NX

good luck

Posted by SaidinUnleashed on July 20 2005,17:10

if you are going to put things into /usr. etc, you might as well make it a normal .dsl, since it will be running mkwritable on those directories anyway.

Posted by ke4nt1 on July 20 2005,18:18

Technically,
the user.tar.gz file is ONLY for the items needed in /home/dsl,
and /tmp/mydsl.menu, to support the myDSL system.

Someone could get creative, and add files to ANOTHER dir in /opt,
and place them inside the user.tar.gz.
The dir in /opt used by the .uci image is read-only.

These areas are already writable. Minimal ram usage.

73
ke4nt

Posted by cbagger01 on July 20 2005,19:13

Or if you REALLY wanted to get creative,

you could make a small nxlinks.dsl file and place it inside

/opt/NX

and then use your user.tar.gz menu item to perform this command:

mydsl-load /opt/NX/nxlinks.dsl

and you are in business.

You can then wrap the whole thing up into one *.uci file.

However, keep in mind that your uci file would need to be color coded yellow or red because it indirectly creates a writable file system.

Of course, the RIGHT way to do it is to take ke4nt's suggestion and recompile it with prefix /opt

Posted by clivesay on July 20 2005,19:38

SU is correct. The only true benefits would be to have remastered all the symlinks into the filesystem so it doesn't have to be opened up at all. If you are familiar with Knoppix remastering you can do this. I've done it before with success.

Chris