[OpenAFS] any experiences with OpenAFS client on the upcoming MacOS 10.10 (yosemite) release?
Tue, 21 Oct 2014 15:33:41 +0200
I shouldn't try to provide that text, but this bit from =
http://www.openafs.org/credits.html may help:
"Several institutions have funded internal development of AFS code which =
has been contributed for inclusion in OpenAFS distributions.=20
=95 Apple Computer, Inc - MacOS 10.3 client/server port
On 2014-10-20, at 21:58, Dave Botsch <firstname.lastname@example.org> wrote:
> I can request it on our account, but I need a *clear* explanation, for
> Apple, of ... "what your kernel extension does and why your customers
> are required to install it".
> If someone who knows the internals better than I can provide this =
> that'd be great.
> On Mon, Oct 20, 2014 at 03:48:11PM -0400, Dave Botsch wrote:
>> I used the git head, and first had to create the various darwin-140
>> files as those were not there.
>> My attempt to compile the git head on a fresh install of Yosemite =
>> failed with the following:
>> I don't know if Cornell's developer level allows signing of kernel
>> extensions or not. I can certainly check.
>> On Mon, Oct 20, 2014 at 03:40:49PM -0400, Benjamin Kaduk wrote:
>>> On Mon, 20 Oct 2014, Mattias Pantzare wrote:
>>>> I have tried to compile 1.6.10 on OS X 10.10.
>>>> The first problem is that it will not compile with xcode 5 or 6. I =
>>>> checked if there is a way to change the compiler to gcc on xcode 6, =
>>>> might be possible (the command gcc starts c-lang).
>>> The git master compiles just fine with xcode 6 on my Mavericks =
>>> if there are build failures, they are probably just small patches =
>>> need to be merged from the master branch to the 1.6 branch. (I =
>>> think you can get "real" gcc from xcode 6 or higher.)
>>>> 10.10 requires all kernel extensions to be signed. They ship a list =
>>>> hashes for old kernel extensions, that is why some versions of =
>>>> work on an upgraded system. But new openafs versions have to be =
>>> Some individual or organization will need to step forward to do that
>>> signing; I do not believe that there is an "OpenAFS" organization
>>> currently able or prepared to do so. (Perhaps the Foundation could, =
>>> am not sure.) The Windows installers that OpenAFS distributes are =
>>> by Secure Endpoints or YFSI (I forget which), who have graciously =
>>> using their codesigning certificates for this purpose. I do not =
>>> they will be willing to perform the same service for OS X =
DESY - DV -
15738 Zeuthen, Germany