Hi, I'm the developer of spacefm. I replied to archie's msg but I just wanted to clarify a few of the build options so you can get this working as you want on PCLinuxOS.
spacefm uses the kernel inotify API directly so it should work okay, but I don't know what pclinuxos/inotify issues he was refering to. Unless it's not detecting directory changes I wouldn't disable it. Otherwise as you found you can disable it and use gamin instead. But gamin is less good in general. (afaik gamin also uses inotify btw, at least in some modes) The inotify vs gamin support has no relationship to the udisks/hal or device management issues.
By default, spacefm builds with udisks support, which is recommended. The alternative is to build with --enable-hal. This will disable udisks support and will seriously limit the functions of the device manager - you'll miss out on a lot of what spacefm can do with devices. You can tell if you have a udisks build by right-clicking on the devices list. If you see a Settings submenu, it's udisks. Otherwise it's a hal build. If you're being prompted for a root password to mount a device, that's a hal indicator as well.
I recommended to Archie that PCLinuxOS provide both spacefm and space-hal packages, because there are quite a few users still using hal. Regardless, you can also make use of spacefm's self-extracting installer to create your own build with a minimum of hassle.
Thanks for testing.