[OpenAFS-devel] fs sysname assignment problem

[Eric Sturdivant]

On Thu, 23 Jun 2005, John A. Goebel wrote:

> ++ 22/06/05 00:11 -0400 - <Tom Keiser>:
>
> Hey,
>
> Tom, I hear an unfortunately deafening silence on this issue.
>
> So another bit of information: I build 1.2.13 (after apply a patch
> <https://lists.openafs.org/pipermail/openafs-info/2004-September/014951.html>
> for a 2.4 kernel (RHEL3) with the same results. I'm not able to get
> multiple sysnames and there is not sysname (@sys) expansion.
>
> Has anyone have a Opteron system running RHEL that _can_ make this work? Any
> suggested magic?
>
> Thanks,
> John
>

This works just fine for me on RHEL3 running 1.3.80 on an opteron 
system...

foo:~# uname -a
Linux foo.umd.edu 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:46:36 EDT 2005
x86_64 unknown

foo:~# fs sysname
Current sysname is 'amd64_rel30'

foo:~# fs sysname foo bar amd64_rel30
fs: new sysname list set.

foo:~# fs sysname
Current sysname list is 'foo' 'bar' 'amd64_rel30'




-- 
Eric Sturdivant
University of Maryland
Office of Information Technology
Distributed Computing Services
(301) 405-8473
sturdiva@umd.edu
http://www.oit.umd.edu/dcs