I've already put "root/my-applications" in every XAMPP configuration file I can find. Doesn't seem to help. It seems to involve something about the Document Root, but that's only a guess at this point.
In fact, I realized it didn't make much sense to do in the first place, because XAMPP is obviously following the main symlink or it wouldn't find the PHP application ( minus style sheets and images ). However, multi-session makes it so easy to tamper with the system internals that it's hard to resist tampering tempation to do wild things that I'd never dream of doing anywhere else. After an extended config file orgy, all I have to do is "just say "no". The best of both worlds, like a morning-after pill.
![Smile :-)](./images/smilies/icon_smile.gif)
As I understand it, there is a symlink from /opt to the root/my-applications directory. Is there somethig about symlinks and XAMPP on multi-seesion CD that is different from a disk install ? It works fine on hard disk.
I've looked at some of the other threads on the subject and other people have had problems with XAMPP as well, but I didn't understand some of their comments, particularly about how XAMPP treats symbolic links.
Does anyone have any suggestions for next steps ? Would it help to install a more recent version of XAMPP ?
- Bill Breitmayer
BTW, I've been hacking away at Puppy multi-session CDs since pre version 2 and think they are the most alpha top dog in the linux universe. The remastering process in 2.16 is soooo easy that it's become a personal priority ( some might say obsession ) to get the beast to behave itself. I really want to get XAMPP running. Are there debugging files or montioring tools I should be looking at to try to catch the varmint in the act ?