OpenAFS-1.3.85 has changed locations of many files, and there are lines in the ebuild to move files from their old places to new ones. But it appears that a new OpenAFS-1.3.85, as opposed to an upgrade, does not put at least some files into anyplace, at all. From what I can see, there is supposed to be a "/etc/openafs", which in my case was not created. Nor am I sure if CellServeDB, ThisCell, and cacheinfo, pulled from another working machine (1.3.84 non-Gentoo-supplied ebuild) should go there, or "/etc/openafs/server", which seems an odd place for client files, but seems to be what the ebuild is directing. Reproducible: Always Steps to Reproduce: 1. Either start with a new install, or remove ALL TRACES of OpenAFS from a current install. 2. Emerge openafs-1.3.84. 3. Attempt to configure. (I've been using afs for almost 15 years on AIX and 4 years on Linux.) Actual Results: /etc/openafs is missing, and so are the files that belong there. I did my best guesses at manual configuration, and: (get many of these Create/doSweep errors, these are the last) CreateCacheFile: Can't create '/usr/vice/cache/D23/V49999', error return is -1 (28) doSweepAFSCache: Can't create '/usr/vice/cache/D23/V49999' /etc/init.d/afs: line 36: 8863 Segmentation fault /sbin/start-stop-daemon --quiet --start --exec /usr/sbin/afsd -- ${AFSD_OPTIONS} [ !! ] Expected Results: Previous OpenAFS ebuilds have given me a mostly-set-up installation, and I only needed to set up a /usr/vice/cache partition and get my site's CellServDB and ThisCell files to be fully functional. This install appears to be incomplete, so I'm guessing it has only been tested in upgrade mode. Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r1, 2.6.12-gentoo-r6 i686) ================================================================= System uname: 2.6.12-gentoo-r6 i686 Intel(R) Pentium(R) M processor 1500MHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -pipe -mfpmath=sse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -pipe -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://kimon.btv.ibm.com/gentoo-portage" USE="x86 X acpi afs alsa apm avi berkdb bitmap-fonts caps crypt cups curl dbus eds emboss encode foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 imagemagick imlib java jpeg libg++ libwww mad mikmod mmx motif mozilla mp3 mpeg ncurses nls nptl ogg oggvorbis opengl oss pam pdflib perl png posix python qt quicktime readline sdl spell sse ssl svg tcltk tcpd tetex threads tiff truetype truetype-fonts type1-fonts usb verbose vorbis xml2 xmms xv zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
(In reply to comment #0) I removed OpenAFS-1.3.85, and installed the OpenAFS-1.3.84 that I had received through the forums, and got it working. Then I upgraded to OpenAFS-1.3.85, with following results: The mount point "/afs" was somehow missing, I needed to recreate it. I needed to add "CACHESIZE=nnn" to /etc/conf.d/afs. To be perfectly honest, I should have removed /etc/openafs first. On my first round I installed cacheinfo, CellServDB, and ThisCell there. I had cacheinfo pointing to an ext2 partition mounted a /usr/vice/cache. It appears that the installation also copied CellServeDB and ThisCell from /usr/vice/etc to /etc/openafs/server. (Personally, I don't like putting client or client/server config files in a directory labeled "server". That should be for server-only stuff, IMHO. Anyway, though fresh install still needs work, I've got a workaround.
Actually, this was done more or less intentionally. I'll explain my reasoning for this: In /etc/openafs, you need: - CellServDB, which you need to set up for your own cell. The previous default installation put a public CellServDB there, which is harmful for any setup that uses other servers. Therefore you need to manually create it with your server information, or unpack a default one from /usr/share/doc/openafs-1.3.x/CellServDB.gz to /etc/openafs/CellServDB (this is roughly explained in the gentoo openafs-documentation, but the paths mentioned there are obsolete now, so I guess: TODO) - ThisCell, simply containing the name of your cell (also explained in the same documentation) - CacheInfo, which you need to create yourself, currently not mentioned in the gentoo openafs-documentation (but is explained in the (quite old) openafs documentation). Previous installations created this file using defaults or parameters in the afs.conf file. As this method stored identical information in more than one config file, limited the user to using a whole partition for the cache, used a default of /usr/vice/cache for the cache mountpoint, ... it has been obsoleted. Also as I think it's the user's choice where to put the cache, especially when a previous cache already existed, I think I'll again leave it to the documentation to explain this. (btw: I'm inclined to recommend the debian default /var/cache/openafs for the cache-location) And that's it. Bottom line, I think that in any reasonable installation the user needs to read installation documentation anyway, and that for "default" world-read installations, there should be files available, but they shouldn't be installed automatically. So maybe the "einfo" at the end of the installation should be shortened to "go to http://www.gentoo.org/doc/en/openafs.xml for information on first-time installations", and all the information I've given should be contained there. Any comments, even if of a totally different opinion, are welcome. I recognize the new ebuilds require some transition effort :)
Please check bug #100837 for updated ebuilds. It contains an attempt to detect at installation time whether a default configuration should be installed or not, thus it should install something ready to jump-start on a system that didn't have openafs installed previously.
Fixed in openafs-1.4.0_rc2
