[OpenAFS-port-darwin] consideration about Openafs installation

[Derrick Brashear]

On Nov 9, 2007 8:59 AM, Claudio Bisegni <Claudio.Bisegni@lnf.infn.it> wrote:
> On 09/nov/07, at 14:50, Derrick J Brashear wrote:
>
> > On Fri, 9 Nov 2007, Claudio Bisegni wrote:
> >
> >> Hi to all group,
> >> i' was thinking about installation on openafs on mac, now the
> >> installer put the startup script that launch all part of openafs
> >> kernel extension and /afs mount operation.
> >
> > It did so before, too.
> >
> >> can we considering the idea to install kernel extension directly on
> >> default path, and let system load it at startup time, and manage
> >> the mount of /afs volume according to user default choice(i think
> >> about AFSCommander could allow user to choiche automount or not).
> >
> > It used to be we could do this. Things changed 10.3->10.4. Before,
> > at start you'd run afsd -nomount, then mount later. Currently, you
> > either start it, or not. Until I fix a bug in the shutdown which
> > leaks resources it's not safe to unload AFS, which is what you need
> > to do (load module, run afsd, or umount, stop afsd, unload the
> > module), because in the memcache case you leak memory. As it happens
> > I hope to fix that bug today or over the weekend, but, basically,
> > this is not as simple as you propose.
>
> yes i know.
>
> >
> >
> >> What do you think about that?
> >
> > Why does it matter? With dynroot, there's no AFS traffic unless you
> > try to use it.
> >
> > In 10.5 the situation gets even murkier for the reason I am about to
> > post.
>
> My condition is that i have openafs folder in sidebar leopard,

I don't. Clearly you have "connected volumes" checked :)

> now i
> dont' have tried to work with afs mounted but without network, so i
> don't now if there are problem.

well, before you try to fix the problem this way, which is sort of
wretched, why not verify there is a real problem you're fixing?
especially since between 1.4.4 and 1.4.5 we added "rapid timeout when
there's no network" support.

> Anyway there is no problem if the user
> can choice to autosartup afs or not. This is can be don't using new
> osx launch methods, afscommander can be modified to make this.
> All this are only consideration:-)

well, before doing anything else, proposing something using launchd
instead of a StartupItems script is probably smarter. but, no real
interest here in doing work to support a solution to a problem that
doesn't exist, and if i'm going to do work to solve the problem i'd
rather solve it right.

consider that in the near future where you get disconnected afs
support you will actively not want to make it go away.