[OpenAFS] Re: sysname for 3.x linux kernel

Andrew Deason adeason@sinenomine.net
Thu, 8 Mar 2012 14:26:54 -0600

On Thu, 8 Mar 2012 15:05:33 -0500
Dan Scott <danieljamesscott@gmail.com> wrote:

> Thanks. So it should 'fallback' by default?

Well, by 'default' only one is set. If you look up something called
@sys, the client will try all of the elements in the sysname list in
order until it finds something that works. So, if you set the list to
'amd64_linux32 amd64_linux3', then that would fall back as you describe.

> Would be nice if there was a default amd64_linux3 though... :)

Well, I think you may just want to avoid amd64_linux3* sysnames in

> This is on Fedora 16+RPMFusion:
> djscott@n6:~$ fs sysname
> Current sysname list is 'amd64_fedora_16' 'amd64_linux32'
> I don't know if the default sysname comes from upstream OpenAFS or if
> it's set in the RPMFusion packages.

Well that's definitely not coming from us; we're not going to set a
sysname like 'fedora' (though setting a distribution-specific sysname
does make sense). A brief look at the rpmfusion packaging suggests it
may be coming from SYSNAMELIST in /etc/sysconfig/openafs .  And the
default config file sets it to

SYSNAMELIST="${_ARCH}_${_DIST}_${_REL} ${_ARCH}_linux${_KERN}"

Which is not correct, or at least doesn't seem like a reasonable default
to me, since most sites will be using amd64_linux26 by default. File a
bug with the rpmfusion packaging, or tell me where I should.

Andrew Deason