[OpenAFS] Strange Behavior of Openafs-1.1.1

Steven N. Hirsch shirsch@adelphia.net
Thu, 9 Aug 2001 07:59:01 -0400 (EDT)


On Wed, 8 Aug 2001, Derrick J Brashear wrote:

> On Tue, 7 Aug 2001, Derrick J Brashear wrote:
>
> > >  struct address_space {
> > > @@ -432,6 +442,7 @@ struct inode {
> > >  	unsigned long		i_blocks;
> > >  	unsigned long		i_version;
> > >  	struct semaphore	i_sem;
> > > +	struct rw_semaphore	i_truncate_sem;
> > >  	struct semaphore	i_zombie;
> > >  	struct inode_operations	*i_op;
> > >  	struct file_operations	*i_fop;	/* former ->i_op->default_file_ops */
> > struct inode is, making
> > i_truncate_sem
> > relevant
> >
> > i will do the necessary work
>
> it is in CVS and will be in the next release. it should make the nightly
> snapshot, if you care.

Ok, after a protracted battle I finally figured out which configuration
files needed to be patched up on my openafs-1.1.1 sources.  For the
record, what is the proper way to ensure that all the GNU configuration
bits get properly updated?  I updated acconfig.h, aclocal.m4 and
configure.in.  Then I ran the 'regen.sh' script.  For whatever reason,
this did not rebuild src/config/afsconfig.h.  Is there another step
required?

I note that the nightly snapshot does not have any of the config files
generated, so any advice on this would be appreciated.  I've always been
in awe of the GNU auto* suite, but it seems like voodoo and is abysmally
poorly documented (IMHO).

Steve