[OpenAFS-devel] proposal: removing mac prefs pane
Daria Brashear
shadow@gmail.com
Thu, 29 Jan 2015 12:00:44 -0500
--001a11331926cac9e4050dcd6dfe
Content-Type: text/plain; charset=UTF-8
On Thu, Jan 29, 2015 at 10:44 AM, Dave Botsch <botsch@cnf.cornell.edu>
wrote:
> Hi, Jeff.
>
> We can certainly move the pref pane portion over to openafs-info.
>
> See below...
>
>
> > The OSX client has a couple of huge holes in it at the moment:
> >
> > 1. The packaging is no longer current for Xcode that supports
> > Mavericks or Yosemite.
> >
>
> Can you clarify what you mean? As far as I know, the only thing required
> to build is an old packagebuilder script.
>
Can't sign it. Only flat packages can be signed
>
> > 2. Parts of the pref pane functionality no longer work because
> > of changes in Mavericks and Yosemite.
> >
>
> The preference pane, to my knowledge, has never worked for cross realm
> authentication. So, that also needs to be fixed to call it "working".
>
>
For you. Most users don't care.
> > 3. There is no support for Bulk Status RPCs which cause the
> > OSX client (especially when used through Finder) to be
> > extremely slow when evaluating directories with large
> > numbers of entries over high latency links.
> >
> > This same lack of support for Bulk Status RPCs also triggers
> > the file server throttling of clients when many of the objects
> > in the directory are unreadable by the user.
>
> Interesting. What would you consider "large numbers" out of curiosity?
> Is there a plan to fix this?
>
> I know how it could be fixed. I have no time to work on it currently.
I certainly would welcome the change.
> >
> > 4. There is no support for PAGs.
> >
>
> Always been that way. PAGs have their plusses and minuses (on our SunRay
> linux systems, I've actually disabled PAGs since certain processes get
> stuck in PAGs without authN).
>
>
It would be possible to do but there is limited benefit.
> > 5. Code signing for the installer, the userland binaries and
> > the kernel extension are necessary for improved firewall
> > access and installation behavior.
>
> Yeah, this sucks. It is workable aroundable pretty easily, but not
> something we want the end user to have to do.
>
> >
> > Of these, the easiest to address is fixing the Preference Pane.
> >
>
> Is there a plan in place to fix this? It'd be nice to have this fully
> working :)
>
>
> None that I am aware of.
--
D
--001a11331926cac9e4050dcd6dfe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Jan 29, 2015 at 10:44 AM, Dave Botsch <span dir=3D"ltr"><<a =
href=3D"mailto:botsch@cnf.cornell.edu" target=3D"_blank">botsch@cnf.cornell=
.edu</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Jeff.<br>
<br>
We can certainly move the pref pane portion over to openafs-info.<br>
<br>
See below...<br>
<span class=3D""><br>
<br>
> The OSX client has a couple of huge holes in it at the moment:<br>
><br>
> 1. The packaging is no longer current for Xcode that supports<br>
>=C2=A0 =C2=A0 Mavericks or Yosemite.<br>
><br>
<br>
</span>Can you clarify what you mean? As far as I know, the only thing requ=
ired<br>
to build is an old packagebuilder script.<br></blockquote><div><br></div><d=
iv>Can't sign it. Only flat packages can be signed<br>=C2=A0<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
#ccc solid;padding-left:1ex">
<span class=3D""><br>
> 2. Parts of the pref pane functionality no longer work because<br>
>=C2=A0 =C2=A0 of changes in Mavericks and Yosemite.<br>
><br>
<br>
</span>The preference pane, to my knowledge, has never worked for cross rea=
lm<br>
authentication. So, that also needs to be fixed to call it "working&qu=
ot;.<br>
<span class=3D""><br></span></blockquote><div><br></div><div>For you. Most =
users don't care.<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><sp=
an class=3D"">
> 3. There is no support for Bulk Status RPCs which cause the<br>
>=C2=A0 =C2=A0 OSX client (especially when used through Finder) to be<br=
>
>=C2=A0 =C2=A0 extremely slow when evaluating directories with large<br>
>=C2=A0 =C2=A0 numbers of entries over high latency links.<br>
><br>
>=C2=A0 =C2=A0 This same lack of support for Bulk Status RPCs also trigg=
ers<br>
>=C2=A0 =C2=A0 the file server throttling of clients when many of the ob=
jects<br>
>=C2=A0 =C2=A0 in the directory are unreadable by the user.<br>
<br>
</span>Interesting. What would you consider "large numbers" out o=
f curiosity?<br>
Is there a plan to fix this?<br>
<span class=3D""><br></span></blockquote><div>I know how it could be fixed.=
I have no time to work on it currently.<br></div><div>I certainly would we=
lcome the change.<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span c=
lass=3D"">
><br>
> 4. There is no support for PAGs.<br>
><br>
<br>
</span>Always been that way. PAGs have their plusses and minuses (on our Su=
nRay<br>
linux systems, I've actually disabled PAGs since certain processes get<=
br>
stuck in PAGs without authN).<br>
<span class=3D""><br></span></blockquote><div><br></div><div>It would be po=
ssible to do but there is limited benefit.<br>=C2=A0<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><span class=3D"">
> 5. Code signing for the installer, the userland binaries and<br>
>=C2=A0 =C2=A0 the kernel extension are necessary for improved firewall<=
br>
>=C2=A0 =C2=A0 access and installation behavior.<br>
<br>
</span>Yeah, this sucks. It is workable aroundable pretty easily, but not<b=
r>
something we want the end user to have to do.<br>
<span class=3D""><br>
><br>
> Of these, the easiest to address is fixing the Preference Pane.<br>
><br>
<br>
</span>Is there a plan in place to fix this? It'd be nice to have this =
fully<br>
working :)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br></font></span></blockquote><div>None that I am aware of.<br></div></div=
><br clear=3D"all"><br>-- <br><div class=3D"gmail_signature"><div dir=3D"lt=
r">D</div></div>
</div></div>
--001a11331926cac9e4050dcd6dfe--