Apps :: mysdl-load

Quote (roberts @ Feb. 26 2007,01:27)

Then this thread is mis-titled, as this has nothing to do with mydsl-load.

Are there really that many new extenions that do not even offer an menu item?

The problem only occurs when "mydsl-load /path/app" is written to bootlocal.sh; otherwise there is a menu item. No apt that I have tried got a mydsl menu item when installed from bootlocal using mydsl-load. If the app has an icon, that does appear.

There is no reason to use /opt/bootlocal.sh for mydsl loading.
/opt/bootlocal.sh is run as root user.

The fact that X has not even started is the reason for such observed behavior!

Read Getting Started to learn about the proper way using a mydsl directory or the mydsl boot option for proper way to load extensions at boot time.

Quote (roberts @ Feb. 26 2007,10:06)

There is no reason to use /opt/bootlocal.sh for mydsl loading.

True.....seems more simple to just load a bash script from xterm with all frequently used apts listed:

#!/bin/bash
mydsl-load /path/apt1
mysdl-load /path/apt2
...

Now I can run whatever I want from the mydsl menu.
But why keep things simple when there are more creative approaches?

There is the easy way (place extensions in a directory and type one thing) and then there is the manual way, create a list and manually type each and every extension name.

Whatever. No matter what I suggest you are apparently not going to accept.

Quote (roberts @ Feb. 27 2007,00:31)

"There is the easy way (place extensions in a directory and type one thing)"

Sounds good to me......

"Whatever. No matter what I suggest you are apparently not going to accept."

?? hm...... (guess I neglected to include a smiley face on my previous post)

Next Page...
original here.