At 9:08 PM -0500 9/3/02, Vidiot wrote:
>  >    I'm clear on the concept of symbolic linking, but in practice
>>I seem to be having a problem ...
>>
>>      I've got a client that screwed up some print advertising and
>>listed the wrong directory name. Instead of "/abc", they called it
>>"/ABC" (all caps). My "fix" is to create a new (all caps) directory
>>and symbolically link that new directory to the correct (all
>>lower-case) one. However, I'm doing something wrong.
>>
>>      I've tried the following command:
>>
>>              ln -s   abc/index.html   ABC
>>
>>      The resulting output (ls -l ABC) is ...
>>
>>              lrwxrwxrwx    1 root     client       14 Sep  3 17:59
>>index.html -> abc/index.html
>>
>>      The creation of the symbolic link seems to have created the
>>"index.html" file in "ABC". However, the browser doesn't render this
>>link properly. I still get a "Parent Directory" screen when accessing
>>"www.client.com/ABC/".
>>
>>      What am I doing wrong??
>
>You created the directory.  Bad.  Makes things not work as expected :-)
>
>Do the following:
>
>       rm -r ABC
>       ln -s abc ABC
>
>Do this in the path that contains the "abc" directory.



        YES!  ... thank you!!  I knew what it needed to look like ...

lrwxrwxrwx    1 root     client       3 Sep  3 21:01 ABC -> abc

        ... but I couldn't figure out HOW to get there.  Thanks very 
much for helping me twist my brain the correct direction.   ;-)




Patrick Beart
-- 
------------------------------------------------
Web Architecture  &  "iWeb4Biz"         503-774-8280       Portland, OR
Internet Consulting, Intelligent Web site Development & Secure site Hosting.
http://www.WebArchitecture.com/

"This is an era when nonsense has become acceptable and sanity is 
controversial."
                                      - Thomas Sowell
------------------------------------------------



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to