search for: nautlius

I have a quick question - I have been starting to test if bugs are still in the current git of wine. When trying to test a DirectX bug I came across this weird behavior and I am trying to figure out why/if there is a problem or I'm doing something wrong/different. Here's the scenario: 1. Make and install current git of wine (did with 1.1.23-xxx and 1.1.24 and currently trying with

...kmark, but it looks like Nautilus will actually try to access the location before that, so that the filesystem pretty much stays mounted at all times. If the disk is available, that is, I haven't tested yet what happens when it isn't, but others with different Linux variants report that Nautlius will lock up completely because it can't get data for the location. So, does anyone have any idea how to best set up the system do to what I want (see above)? I guess I might create special "mount" and "unmount" launchers, but I'd prefer a solution that's more in...

Looks like Nautilus is periodically 'stat'-ing the bookmark location. How about making a softlink to the target dir in your home directory, then bookmarking the link in nautilus. Hopefully Nautilus will stat the link and not the target then. K