OK. Sorry for bothering. This is the dynroot feature which ignores the root.afs volume contents cf. Email dated 27 Feb 2003 by Derek Atkins, and which is turned on by default on the rpm distro.

I removed -dynroot from the /etc/sysconfig/openafs config file, and everything now works like before.

Many congratulations to the development team for making 1.4 happening and working close to out of the box on 2.6 kernels (linux) on 64 bit SMP architectures. This is really a great achievement.

Kind regards,

Christophe.

On Tue, 20 Dec 2005, Christophe BERNARD wrote:

Hello.

I installed a long awaited RPM openafs distro on a 64 bit fedora core 4 client. The server is still running 1.2.13 on a fedora core 1.

Works mostly well (krb5/aklog/afs access). Just one problem I do not how to solve:

The cell name is (say) abc.com, and I used to put a symbolic link abc -> abc.com in /afs:

/afs/abc -> /afs/abc.com

Bad luck, the abc symbolic link does not show up any more on the latest
fedora core 4 / openafs 1.4.0 client. I tried to replace the abc symlink
with an actual "fs mkmount" mountpoint abc -> root.cell. Nothing is showing up, as if the new client was completely ignoring was is lying in root.afs? Did something change in the classical directory and volume hierarchy to explain this?

The hierarchy I am used to is:

/afs -> root.afs volume

in root.afs, I have a RO mount point abc.com to root.cell, and either a symbolic link abc to abc.com or a RO mount point abc to root.cell. In either case, the abc link/mountpoint is invisible in the 1.4 client.

Any hints?

I would like to keep the /afs/abc paths running, as they are used in the standard paths for user home directories and plenty of other stuff.

With my best regards,

Christophe.
---
Christophe BERNARD
Ecole des Mines de Paris
77305 Fontainebleau cedex

_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to