Fatdog64-630:Click/mount icon WITHOUT rox window?(Solved)

[jtwdyp]

I had a similar question for my Precise & Slacko puppies in:

http://murga-linux.com/puppy/viewtopic.php?t=89745

Which was solved to my satisfaction when I learned to eliminate {actually #comment out} any/all commands in the

Code: Select all

/usr/local/bin/drive_all

file that looked like:

Code: Select all

rox -x /mnt/$xONEDRVNAME -d /mnt/$xONEDRVNAME

zap the contents of

Code: Select all

/root/.pupevent

«Which don't seem to exist in fatdog. Thus I can't delete it's contents...»

Then save the ram layer, and reboot. Then the rox filer would stop jumping in my way while I'm already hitting a keyboard shortcut to open a terminal window, running mc (the ONLY good file manger in the known universe ) {opening it of course with the working directory preset to /mnt ...}

I use the keyboard (never ever the mouse) to navigate through my filesystem. If I need rox for something I can't do with mc {a rare event I assure you}, I navigate {or cd} to the appropriate directory with mc and type

Code: Select all

rox . 

I only click on the icon because it's easier than checking the available devices with fdisk, then using mkdir to create a mount point {if it doesn't already exist} and finally typing in a mount command... But I never want rox to open a window for it just because I mounted it.

But in Fatdog, I can't find the mojo to keep rox from auto-opening a window.

How can I do this in fatdog:?::?::?:

[jamesbond]

But in Fatdog, I can't find the mojo to keep rox from auto-opening a window.

How can I do this in fatdog:?::?::?:

That's because the mojo lives in another dimension. Try /usr/sbin/fatdog-drive-icon-action-handler.sh and search for the function named "open_rox_folder".

Good luck.

[jtwdyp]

But in Fatdog, I can't find the mojo to keep rox from auto-opening a window.

That's because the mojo lives in another dimension. Try /usr/sbin/fatdog-drive-icon-action-handler.sh and search for the function named "open_rox_folder".

Thanks BTW: I'm starting to like this alternate universe Fatdog lives in... A lot! Just wish there were more pets :sigh:

I decided the simplest fix would be to disable the function itself rather than to try to figure out any of the calling code segments...

{I mean I'd rather navigate mc to anyplace I might {on rare occasion} actually want a rox window and type the shell command "rox . " than to have to click on something with the durned rodent to open rox anyway, and I've got a keybinding to open a terminal with mc. }

But I wasn't sure if the function had to actualy DO something, to avoid some error trap, so when I commented out the rox command I added a dummy variable assignment... The fix started working instantly...