Quote:
Originally Posted by sam356
Ok, after much reading and suchlike, it appears that running the following in a terminal after puppy has fully started up fixes both problems:
modprobe -r psmouse
modprobe psmouse proto=imps
vmware-user-suid-wrapper
The problem now is how do you run something automatically in puppy after it has fully started up (ie. where do I put the above three lines so that they are run after puppy has fully started up)? In my previous (non puppy) linux I added such lines to ~/.desktop-session/startup, but that file doesn't exist in puppy linux...
|
@ sam356:-
Try putting them in /etc/init.d. This is where I put custom scripts for auto-mounting specific partitions at startup. If you want to make certain Puppy has fully started up before the commands are executed, add a 'sleep' statement. Like this:-
Code:
# /bin/sh
#
# Run commands below after a delay
#
sleep 90
#
modprobe -r psmouse
modprobe psmouse proto=imps
vmware-user-suid-wrapper
90 seconds should be more than enough to make sure everything has settled down.. Save to /etc/init.d as, oh, say 'vmware-delay.sh' (for example), and don't forget to make it executable. (Easiest way in Puppy - if you're running the default JWM/Rox-filer combo - is to rt-clk the file, ->Properties, tick the 3 'Exec' checkboxes, followed by hitting 'Refresh' at the bottom....then 'Close'.)
I know very little about VM's (don't use 'em, personally), but that should work for running those commands with a suitable delay.
Alternate locations include ~/Startup, or ~/.config/autostart (this is becoming more favoured, because ~/Startup is slowly being deprecated). The only snag being that anything placed in ~/.config/autostart
must be a .desktop file, or else it's ignored. With the older one, ~/Startup, you can put scripts in there, sym-link binaries.....you name it. If it's executable, it'll run.
Mike.