https://bugs.kde.org/show_bug.cgi?id=426528
--- Comment #7 from Alexander Ewering <ae@seven.systems> --- (In reply to Nate Graham from comment #6) > kio-fuse is supposed to mount the FUSE path on demand, in response to > explicit user actions that require it. Its not meant to be a permanent > mount. Perhaps the real question is why you want to point apache as a > permanent CIFS mount. That's a highly unusual use case. :) Typically I see > this sort of thing done on a headless server (and I have done it myself back > in my sysadmin days). What exactly is the use case here? Can you explain it > in more detail? Maybe we can figure out a better alternative. I'm an absolute export at creating unusual use cases ;) I frequently do development on hybrid mobile apps (think Cordova, or whatever it's called these days...), and I test them in the browser and on the phone in parallel. XCode has (or at least used to have) the nasty habit of not being very cooperative when an XCode project is opened from a network share (which would be the proper way to do it). So instead, I opted for always putting the XCode project on the local hard drive in the Mac, and then instead mount that on my Linux machine, where the IDE (I'm not using XCode as an IDE, just for device deployment) and the browser (for testing) reside. So, Apache on the Linux machine has to mount the share from the Mac where the XCode project (and thus, the web part of it) is. I agree that's unusual, but I can't think I'm the only one who in some way wants Apache to host a "website" residing on a network share? :/ To derail this bug report further: I cannot emphasize enough how highly I respect the KDE developers and designers, it is by far the most powerful and useful desktop on the planet, on any platform. Thank you! -- You are receiving this mail because: You are watching all bug changes.
