Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 05 May 2010 14:10:06 +0200
From:      Jan Henrik Sylvester <me@janh.de>
To:        Benjamin Kaduk <kaduk@MIT.EDU>
Cc:        afs-list freebsd <freebsd-afs@freebsd.org>
Subject:   Re: AFS on FreeBSD 8?
Message-ID:  <4BE1601E.1010809@janh.de>
In-Reply-To: <alpine.GSO.1.10.1005041225120.29136@multics.mit.edu>
References:  <558186334.2619.1271175586732.JavaMail.root@thunderbeast.private.linuxbox.com> <alpine.GSO.1.10.1004131220540.29136@multics.mit.edu> <4BC4A5F1.6050406@janh.de> <alpine.GSO.1.10.1004131314070.29136@multics.mit.edu> <4BC5EEB5.5050109@janh.de> <alpine.GSO.1.10.1004141242470.29136@multics.mit.edu> <4BE01AF0.3080309@janh.de> <alpine.GSO.1.10.1005041225120.29136@multics.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On 05/04/2010 18:45, Benjamin Kaduk wrote:
> On Tue, 4 May 2010, Jan Henrik Sylvester wrote:
>> The machine is a Core2Quad (four cores) currently running on a GENERIC
>> FreeBSD-8.0-RELEASE i386. I plan to test amd64 in a few weeks. (All
>> the other machines I could use for testing are i386, too, one 8-STABLE
>> and the others 8.0-RELEASE.)
>
> Thanks! I suspect that we are not quite safe for the SMP case, yet.

Unfortunately, I do not have a real single processor machine anymore. My 
Atom based "netbook" (single processor, hyper-threading) comes closest. 
Maybe I find some time to bring it to a similar configuration. With the 
improved packaging list, I probably can just make a package...

>> The port has 1.5.73.3 hard coded, but if I understand it correctly, it
>> pulls the latest git (currently something beyond 1.5.74) -- or am I
>> wrong?
>>
>> I just tried to build it again, but it did not succeed:
>>
> [snip errors]
>
> There was some refactoring that went into git master a couple days ago;
> it looks like the freebsd-specific code needs a few tweaks to compile.
> You coul revert back to the 1.5.74 release branch, but it looks like
> Derrick has committed a fix since you reported this, so why don't you
> 'make clean' and try again?

As of today, the error remains.

> (I do not expect the hangs experienced previously to have been fixed,
> though.)

Ok. If you think it might be improved in any way, you can send me an 
email and I will repeat my testing. Unfortunately, I do not think that I 
can do any real work like debugging.

Thanks,
Jan Henrik



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BE1601E.1010809>