From: AndrewL733 <And...@ao...> - 2006-01-04 13:49:37
|
Search on the web for Dan Wilga at Mount Holyoke University. He wrote a "symlink patch" for Netatalk. I have applied it to netatalk 2.03 with good results -- as good as what I got with Netatalk 1.64. Andy pr...@di... wrote: > I would break out the symlinks as separate "Volumes" to be shared. > Users would see each one in the list of available Volumes when > connecting to the server. This should be OK if there's a small amount > of them. If you have dozens, well, then it gets to be a tad unwieldy! > > $0.02, > ...ROMeyn > > > At 12:38 PM +0100 1/4/06, Bengt Nilsson scribbled: > Dear all, > > We have a tru64 system with several disks, file systems and nfs mounts > from other hosts. > We are using symlinks extensively to access the other disks and nfs > mounts directly from the user home, the user have access/ownership of > directories in various places. We see currently no problem with this, > and netatalk 1.9 can make use of this setup very nicely. > > Now the latest netatalk release 2.0xxx abandon symlinks altogether. > For variuous reasons I want to upgrade the netatalk installation, but > then the user would not have access to the other file systems anymore > when connecting via afp. Does anybody have a suggestion how to > re-organize things or in any way solve this problem? > > -- > Bengt Nilsson > Chalmers University of Technology, > SE-412 96 Göteborg, SWEDEN > e-mail: <mailto:ben...@mc...>ben...@mc... > tel: +46-31-7728480 > |