I'd like to report an AFS malfunction on my machine here, in
POSTECH, Korea. And also would like to hear any similar behaviors or
solutions experienced out there.
I just failed to install AFS client on an Ultra Sun machine running
on Solaris 2.5. When I executed '/usr/sbin/modload /kernel/fs/afs' as the
manual described, 'bad trap' messages appeared on the colsole and then CPU
turned to be panic and rebooted. :(
According to the README file in the latest release (AFS.3.4.ports)
from Transarc, 'sun4x_55' binaries can support sun4u CPU architecture but
now I can't say it's true. The following is the results of 'uname -a' from
my machine 'ys'.
ys[ jay{3} ~ ] uname -a
SunOS ys 5.5 Generic sun4u sparc SUNW,Ultra-1
Any comments or suggestions can be welcomed. Thanks in advance.
Jay Kim
___________________________________________________________________________
_____ ___ __ __
__/\__ |_ _| / _ \ \ \_/ / Remember Yesterday, Dream about Tomorrow
\ / | | | /_\ | \ / but ... LIVE TODAY !!!
/_ _\ | | | _ | | |
\/ __| | | | | | | | [EMAIL PROTECTED] (Jae-young Kim)
|___/ |_| |_| |_| Researcher, Computer Center/POSTECH, KOREA
___________________________________________________________________________
