Apps :: Installing MyDSL



I have a frugal install with 40G HD partitioned thus:

hda1 - DSL/Knoppix image
hda5 - home, opt, & mydsl dirs.
hda6 - swap

I can download MyDSL apps to tmp and they are functional (MyDSL menu item, desktop icon, program runs), but when I shutdown or reboot, error message appears: Apps in ramdisk, save? Y/N  When I say yes, elfm opens, clicking on MyDSL I'm informed I must be user dsl to install. When I ask whoami in A term. I'm told: dsl!
So I figure there has to be another way: change dir to save MyDSL to hda5/opt - I'm told it's not mounted. Yet the boot sequence seems to automount both hda1 & 5 - and the mount tool reports both as mounted!
What to do, what to do?? Helllp!

Why would you be trying to load them upon shutdown?

The shutdown warning is opening emelfm as super user so that you may drag and drop the extensions downloaded into ramdisk to a permanent storage device.

The script usually tries to figure out the from and to based on boot options.
\
The only real use of this file manager prior to shutdown is to save (copy) your extensions; not to load them again!

What about a lua or bash script whose only function is to move the selected mydsl extensions to a target location? There would be no question about why a file manager was opened, and you wouldn't have the potentially harmful root file manager in use.

macadavy: The aterm is a different shell than the root emelfm...they are being run as different users.  If you open emelfm as root, all tasks done by it will be done by root.

Quote
What about a lua or bash script whose only function is to move the selected mydsl extensions to a target location? There would be no question about why a file manager was opened, and you wouldn't have the potentially harmful root file manager in use.

It is the purpose of a file manager to copy,move, rename files from easily selectable locations and via a simple drag and drop technique, why would I want to duplicate that functionality? It would seem to me that the use of a common file manager should already be very familiar and therefore easiest to use. I guess what seems common sense to me, using existing functionality to move (save) ramdisk located files to the target location of the users choice, is not obvious to others. To have to offer multiple versions of programs each with limited capabilities, training wheels, seems not only a waste of time but a waste of space. I believe in reuse of code or existing systems whenever possible. Seems no what I do. I cannot win. You can't please everybody.

Is there an entry in the wiki that addresses the use of the file manager at shutdown time?  I also have recieved that warning and did not know exactly what to do.  Your explanation was like a duh? to me.  Of course I should save the extensions in memory, but I didn't know how until now.  Thanks Roberts for hanging in there with us noobs!
Next Page...
original here.