Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Dec 29, 2005, at 4:30 PM, Tom Metro wrote: > David Kramer wrote: >> I ran into one bit of trouble already where the commands worked >> fine on the >> CLI, but running it through apache gave strange results, and I >> finally figured >> out the build working directory had to be somewhere under the >> DocumentRoot >> (prolly an selinux thing. Gawd I hate selinux.). Moved the build >> dir, and >> got past that problem. > > If it was an selinux thing, shouldn't you also be able to solve > that by setting the right security context on the original directory? You could try temporarily disabling selinux with "setenforce 0" I think.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |