[OpenAFS] 1.1.0 client on RH 7.1

[Derek Atkins]

No, you do want /afs "owned", but it doesn't necessarily need to be
owned by the RPM system within the RPM database.  Another way of doing
it would be to have the openafs-client rpm mkdir /afs in the
postinstall:

[ -d /afs ] || mkdir /afs

And then in the post-uninstall script, something like this to remove
it:

[ $1 = 0 ] && rmdir /afs

Of course the pre-uninstall script should have something like this to
make sure AFS is stopped if you are unstalling the package:

[ $1 = 0 ] && /etc/rc.d/init.d/afs stop

-derek

"Patrick J. LoPresti" <patl@curl.com> writes:

> In a large installation, the logical place to keep a collection of
> RPMs is in AFS itself.  So it should be possible to upgrade AFS using
> packages living under /afs; that is, while AFS itself is running.
> 
> In my opinion, it would be better to have /afs unowned by any package
> than to need to stop AFS before performing an upgrade.  (Assuming
> those are the only options, of course; I do not know enough about RPM
> to be sure.)
> 
>  - Pat
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available