Dan/Jay - thanks for the idea. I tried hard linking, but I get an "Operation not permitted" error. Here's the context I'm using: # ln -d /path/to/target /path/to/link -Erik Jay Kline wrote: > Would hard links be an option? They can sometimes be a bit more difficult to > administer, however. > > Jay > > On Wednesday 06 November 2002 3:26 pm, Erik Anderson wrote: > >>Hi all - I'm trying to set up an ftp server to allow our customers to >>download softwarem, updates, yada yada, >> >>The idea is to, upon login, dump the users into their chrooted home dir, >>which would contain some of our custom software, writted specifically >>for them. This was easy to do.....now comes the catch: >> >>We want to also give them access to a "Common" directory as well. Any >>ideas? >> >>I've thought about structuring the ftp tree as follows: >> /Common >> /cust1 >> /cust2 >> /cust3 >>giving the customer only read access to their folder and the Common >>folder....however, the management doesn't like the idea of presenting >>our list of customers to the whole world. Soooo... >> >>Here was my second strategy: >> /Common >> /cust1 >> >> |_ symlink to Common >> >> /cust2 >> >> |_ symling to Common >> >>etc etc.....well that didn't work since the users were chrooted to their >>home dirs. >> >>I'm stumped! >> >>Thanks- >>Erik Anderson >> >>_______________________________________________ >>Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, >>Minnesota http://www.mn-linux.org tclug-list at mn-linux.org >>https://mailman.mn-linux.org/mailman/listinfo/tclug-list > > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list -- Erik Anderson - erik at andersonfam.org