Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

apache puzzler...

On 12/19/2010 05:29 PM, David Kramer wrote:
> On 12/19/2010 04:47 PM, Stephen Adler wrote:
>> Guys,
>> This is a weird one. I finished building compiz and I wanted to
>> share my work with everyone. So I put a bunch of tar balls on my web
>> site. So I created and area on my web server, made it so that people and
>> see the area from the internet and put the tar ball files there and a
>> text file name README.txt. The weird thing is this. The .tar.gz files
>> show up, but not the README.txt file. I created a tarball with just the
>> README.txt called README.tar.gz but it does not show it. Can you guys
>> confirm this?
>> The directive gave the apache server is this....
>> [root at telacode conf.d]# more compiz.conf
>> alias /compiz /telacode/base/www/compiz
>> <Directory /telacode/base/www/compiz>
>> Options +Indexes
>> </Directory>
>> [root at telacode conf.d]#
> There are various directives that can hide files by wildcard, etc.  I
> would start by doing a "grep -i readme" on *all* your config files,
> including in conf.d, as a sledgehammer approach.
> See this thread:
> If you name it READ_ME.txt does it show up?
renaming to READ_ME.txt does make it visible... uggg...

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /