Re: [OpenAFS] Documentation project update

2005-06-03 Thread Esther Filderman
On 6/3/05, ted creedon <[EMAIL PROTECTED]> wrote: > All, > > The documentation project is finished except for hyperlinks. That's a very nice planet you live on. > The conversion from IBM htm to tex is stable and the conversion from tex to > html, dvi or pdf is also stable. Oh, you mean the proj

[OpenAFS] Documentation project update

2005-06-03 Thread ted creedon
All, The documentation project is finished except for hyperlinks. The conversion from IBM htm to tex is stable and the conversion from tex to html, dvi or pdf is also stable. Hyperlinks use Latex reserved characters such as #. The tex to html, dvi and pdf converters all interpret the reserved ch

Re: [OpenAFS] oopses with openafs 1.3.83 and linux 2.4.31

2005-06-03 Thread Derrick J Brashear
Pruned linux-kernel. There's basically no point in copying them unless you like hearing the same tired 'oh my god why are you doing xyz horrible thing' unproductive comments. On Sat, 4 Jun 2005, Dimitris Zilaskos wrote: After moving to linux 2.4.31 and openafs 1.3.83 , I still get oop

[OpenAFS] Locking issues, Solaris & AFS, kernel panic stated to be due to AFS vs Solaris thread locking order

2005-06-03 Thread Dexter 'Kim' Kimball
We have had a panic/core on A Sun Solaris box -- the Sun kernel engineer who examined the core determined that there was lock contention for a page of memory -- and that the kernel and AFS (IBM AFS 3.6 2.53) use different locking order and that this results in lock contention which is subsequentl

[OpenAFS] oopses with openafs 1.3.83 and linux 2.4.31

2005-06-03 Thread Dimitris Zilaskos
(resending due to size , sorry mods) Hi , After moving to linux 2.4.31 and openafs 1.3.83 , I still get oopses once per day. Usually this causes the system to either freeze totally (only replies to ping) or all processes segfault. Exacly the same happened with 2.4.29 and 2.4.30