You weren't paying attention at the AFS/Kerberos workshop, were you? :-) The AFS community isn't able to get aligned with the distros, for political more than technical reasons. Because the openafs license "taints" the Linux kernel, AFS will remain on the outside for the forseeable future, for most of the Linux distros. Some license nazis are actively trying to make it harder and harder for code like openafs to access the internals of the kernel it requires. There's a long, sordid history here, with no short term resolution.
This is why people like Derrick hate Linux so much, and why he runs everything on FreeBSD and MacOS X. This is why the OpenAFS logo is an Orca: because Derrick googled "what eat penguins", and this was the first thing that came up :-P The exception would be Debian, and by extension perhaps Ubuntu, and that's largely because of the work of Russ Allbery at Stanford. He does a great job of providing integrated OpenAFS packages for Debian. I haven't tried to set this up on the other OSes yet, so I'm not sure what the state is there. For my purposes, it's moot anyway, because I want to be on the leading edge with OpenAFS, so I need to be able to deploy from source. Like I said, there's a few things I intend to patch myself, and I want to be able to take critical patches and integrate them without waiting for the distro's to catch up. On Fri, Oct 8, 2010 at 2:55 PM, David A. Desrosiers < [email protected]> wrote: > On Fri, Oct 8, 2010 at 1:31 PM, Phillip Moore <[email protected]> > wrote: > > When you try to tun efs_virtual_machine on a couple of the platforms, you > > have to first install a couple of packages anyway (perl on Debian, IIRC, > and > > a few things on FreeBSD). I think it makes sense to create VM templates > > with minimally installed software, but my point is that the way we do it > now > > is *too* minimal. > > I’ve built my templates from scratch with additional software I know I > was going to use later (vim, emacs, flex, make, bison, glibc-devel, > etc.) > > We could just create a meta-package that contains the necessary > repositories and dependencies, and require those to be installed, to > satisfy the AFS deps, until the AFS community gets aligned with the > distros and a distro packager takes on the task of including AFS as an > installable package in the core repositories. > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev >
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
