[9fans] Definitinon list of the # filesystems

[dlm-9fans]

Is there a relatively concise list of the # filesystems (#s, #|, etc)
and what each of them is/contains hiding somewhere?  I've been poking
around for one and not having much luck.  I suppose one could be
derived by grepping through man3, but that doesn't seem to give a
complete list (I only get 10 hits, and I know there are more than ten
shades of #).

Thanks.

Dworkin

--
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/Tc21478a4dc8e2df1-M53e7a145d7e726e30dd4bbed
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] mk results in rc: suicide:

[dlm-9fans]

o...@eigenstate.org wrote:
ori: asm()/casm() shows assembly. The PC you crashed on
ori: is 0xb5d9, which happens to be in the middle of
ori: this comparison instruction:
ori: 
ori: > Readdir+0x2c 0xb5d8 CMPLdir+0x8(SB)(CX*1),AX
ori: > Readdir+0x33 0xb5df JNE Readdir+0xd8(SB)
ori: 
ori: which tells me whatever jumped into the code here
ori: is junk; either a bad function pointer, a flipped
ori: bit in your binary, or something else.

At this point, this is really sounding like a hardware issue.  I'm
betting it only happens after the build's been going for a while.  My
bet would be it's heat-related, and could be in the CPU or in memory,
leaning towards CPU.  Check your case and CPU fans, blow out dust,
make sure everything's firmly seated, etc.  If you built the machine
yourself, in particular installing the CPU, did you use thermal paste
between the CPU and the heatsink?  Reseat anything that's socketed,
including cables.  Also, make sure that there's a free air path to and
from all vents in the case.

Also, check the BIOS logs and such for temperature excursions,
assuming your BIOS reports such things.

Dworkin

--
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-Mc77820658e37f59385b949d6
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription