I just set the sysname to whatever I want it to be. Cfengine sticks a "/usr/bin/fs sysname -newsys" command in the /etc/init.d/openafs-client script in the startup) section
On Thu, Mar 08, 2012 at 02:44:28PM -0500, Dan Scott wrote: > Hi, > > I'm running into a small annoyance managing our OpenAFS files with the > most recent kernels (3.X). When I was running a 2.6 kernel, the > sysname didn't change very often and I didn't need to perform much > maintenance on my software installation volume. Recently, some > workstations have started using the 3.1 and 3.2 kernels and I've had > to create a lot of symlinks so that the @sys directories resolve > correctly. I'll have to do this whenever a new kernel version is > released. > > Is there a way to have a 'fallback' directory for @sys? i.e. If > amd64_linux32 doesn't exist, then it should use the amd64_linux31 > directory instead. Or maybe we can have a amd64_linux3 sysname for all > 3.x linux kernels? > > I can see the advantages of having different names for 2.4,2.6 and 3. > kernels, but do we really need a new sysname every 3 months or so? > > Thanks, > > Dan > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > -- ******************************** David William Botsch Programmer/Analyst CNF Computing bot...@cnf.cornell.edu ******************************** _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info