From: Frank K. <fbk...@ve...> - 2008-04-03 20:18:25
|
H. Peter Anvin wrote: > Frank Kotler wrote: > >>I also found a way to subject this list to "emergency moderation", which >>I have done. I don't know if that'll help - this is kind of a "test >>message" to see what it does... > > The easiest is to set the list to "subscriber post only". This means > that only registered list members can post, which filters out virtually > all spammers. That's the option I was looking for. I'll look again. What I've done seems to be asking me for approval after the fact... On a completely different topic, but still "talk", I'm wondering if you, or someone, can help me. There's an issue come up on alt.lang.asm (yeah, I know...) under the subject "Why is my nasm program killing itself". A guy has got Slackware 12.0 - kernel 2.6.21.5, apparently, and is having apparently good programs being "killed". Looks like they're killing the loader, actually... His disassembly suggests it's not a Nasm or ld problem... We saw something in kernels 2.6.10 - 2.6.16 (approximately) where programs without a writeable section last were causing a SIGSEGV in the loader (fs/binfmt_elf.c, IIRC) - original patch threw SIGKILL. I suspect something similar here. I "should" learn my way around the kernel well enough to be able to find something like this myself, but I'm hoping someone more familiar can bail me out and suggest some workaround for this guy - an "align" directive or ???? - that'll make his programs work without having to reinstall. He's getting the impression that asm is difficult! TIA for any help or suggestions! Best, Frank |