From: https://me.yahoo.com/hanki_pank#f42c5 Date: Fri, 20 Jan 2012 06:01:30 +0000 (-0800) Subject: add section 2.23 X-Git-Url: http://git.openafs.org/?p=openafs-wiki.git;a=commitdiff_plain;h=f41cecaf99797365a1a2413650f6584e3ea58aed add section 2.23 --- diff --git a/AFSLore/UsageFAQ.mdwn b/AFSLore/UsageFAQ.mdwn index 4db14ab..ee3f50c 100644 --- a/AFSLore/UsageFAQ.mdwn +++ b/AFSLore/UsageFAQ.mdwn @@ -30,6 +30,7 @@ The Usage Section of the [[AFSFrequentlyAskedQuestions]].
  • 2.20 How do you set up IP-based ACLs?
  • 2.21 What meaning do the owner, group, and mode bits have in AFS?
  • 2.22 What are "dropboxes"?
    • +
  • 2.23 Can I access a RW-Volume using the RO-Path ?
    • @@ -499,3 +500,21 @@ In practice, the "not modify them once deposited" part is not enforced by the fi Also, note that system:anyuser=irl has additional problems: because dropbox semantics are based on pts identities (see question 2.21), the fileserver cannot distinguish between two unauthenticated users. So, not only can a user come back days later and modify the "dropped" file, but **any** user can modify a file dropped by an unauthenticated user, at any time. +### 2.23 Can I access a RW-Volume using the RO-Path ? + +Depends. Once, you have RO-Volumes released, a mountpoint pointing to the RO, will bring you to the RO-Volume.
    +To change that behaviour, you have to change the corresponding mountpoint.
    +However, for some situations, like software installations, it might be useful to +reach the RW-Volume through the RO-path.
    + +You can do that for a single client with a special setup.
    + +The trick is to break the convention described in 2.17 for a single client :
    +You mount the RW volume "root.cell" as /afs/cellname.
    + +This can be done by creating an alternative "root.afsrw" - Volume ( in contrast to root.afs), +where you do the RW-mount.
    +Then you must disable on this special client the "dynroot" -option and use this alternative root.afsrw +as root volume, by adding "-rootvol root.afsrw". + +