[OpenAFS] the future

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC875626AD63A89D822D0958E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 10/1/2012 12:48 AM, Troy Benjegerdes wrote:
> On Sun, Sep 30, 2012 at 11:38:10PM +0200, Lars Schimmer wrote:
>> On 30.09.2012 21:10, Troy Benjegerdes wrote:
>>
>>> One-time deals (on linux) that require interaction will blow up all k=
inds
>>> of automated tools and leave the rank and file admins your enemy.=20
>>
>> Easy, user do call admins angry and stupid. And Admins change OpenAFS =
to
>> NFS/SMB/or anything else, which is free and easy to deploy.
>> Nearly everything is free, functional and already included.
>> Why hassle with more work, incompatible licenses and all the user supp=
ort?
>=20
> Having migrated from NFSv3 to AFS (and then OpenAFS), I'd have to say t=
hat
> NFS may be free, but it doesn't really fall into the 'functional' categ=
ory.
> But this was several years ago, so there might have been some magic tha=
t=20
> happened with NFS I haven't seen yet.
>=20
> Can anyone who has experience migrating to/from OpenAFS from/to anythin=
g=20
> else in the last 2-3 years please comment? If there's really something =

> free, functional, and already included then I'd like to know what the=20
> heck it is.

I will remind the community of OpenEFS <http://www.openefs.org/> which
was developed specifically to permit a large financial institution to
use NFSv3 for global software distribution via a firm-wide name space.
While it is true that AFS3 provides a large amount of administrator
functionality in the box that is not present in competing products, that
doesn't prevent organizations from spending money to replicate that
functionality at a higher layer.

Jeffrey Altman




--------------enigC875626AD63A89D822D0958E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJQakzDAAoJENxm1CNJffh4dFEIALy1fwF1e4pKXnjZ30KCzInZ
ex8iF9W9hu6HOzfkpzfixrKiXxcaQ2G+MLM/lUA3caDfltJgn0HcxAsdG24Irtbp
XXv1Bx+EoMugeqI1YBGekD3wjRLCG9Cvlsp6jQjRCnlEAxPV2dEA/HtQSeR5V4iZ
91sbeE7Bg7TaxNZpRK+GO+h/pzwA0v4CMUd5uuxeFPY4txupFf2SdBEmj0IForYM
1WF1yDqPQcsjXr7MxBtZji7Rwy8rhFyngY1W/GB95vUZUEjwklMySLFSYWXjeOF9
Mm8iN/2Mb2GvdQCFbfDLv++zB1uaov1jvpwtoANnA9HBzDQh7D2ikZVWwX/YV+k=
=51Aj
-----END PGP SIGNATURE-----

--------------enigC875626AD63A89D822D0958E--