[OpenAFS] 1.1.0 client on RH 7.1

[Derek Atkins]

What happens when afsd disappears out from under your running system?
I can see that being a Bad Idea (TM).  In the past, I even had the afs
RPM shut down AFS in the process of upgrading, to be sure you didn't
kill your system.  The reason is that I've seen systems crash hard
when they lose afsd out from under them.

-derek

Rudolph T Maceyko <rtm@cert.org> writes:

> The spec file for openafs-client lists /afs as a directory owned by the 
> openafs-client RPM:
> 
> %files client
> %defattr(-,root,root)
> %dir /afs
>   .
>   .
>   .
> 
> This precludes installing the RPM when AFS is running.  Our in-house 
> RPMs have not taken ownership of /afs, so we haven't run into this 
> prior to using the spec file from OpenAFS.
> 
> It seems like a good idea to have /afs listed in the RPM database, but 
> then again it seems (to us anyway) to be a good idea to be able to 
> update AFS on a running system.
> 
> I'm not sure what you can do about it...  Can you mark a %dir to also 
> be %config?  I haven't tried that yet...
> 
> -Rudy
> 
> --On Monday, July 23, 2001 10:58:57 -0400 jgood@umbc.edu wrote:
> 
> >    5:openafs-client         error: unpacking of archive failed on file
> > /afs: cpio: chown failed - Read-only file system
> 
> 
> _______________________________________________
> 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