That is how the hard disk dock - modules directory works. I have
1.5GB of extra software in my hard drive modules directory that has
all been squashed with the SDK, and gets loaded (mounted in a loop
device) on each CD boot.

Or are you trying to be clever and put it into the nest image
without squashing? Does this perform better?

If performance is not gained as above, I prefer the /opt modules as
these give me somewhere to add the app to the menu.
Plus I can have different docks on other partitions or machines for
completely different overall functionality. I have these docks saved
on a DVD or multiple CDs so I can load them onto a /dyne folder on a
target machine.

Hope this helps.

andrea bertolasi wrote:
> On 12/3/06, Bryan <bryan@???> wrote:
>> I downloaded the source of some software, built it and installed it
>> locally. To run it, I have to cd to the directory in which I have it
>> installed and then type the name of the program.
>
> you can put the directory in the "path" or use the whole path
> when tou launch the app.
>
> for example:
> /opt/bin/myapp
>
>
> @jaromil:
> i think that could be useful if the db could load the (additional)
> dyne modules when it's booted from the cd and the modules are on the
> hd.
>
> for example you boot the dyne cd and load the OpenOffice.dyne wich is
> on the harddisk!
>
>
>
> bye
> andrea
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>