Colin Watson wrote: > > binfmt_misc isn't his problem, it's trying to execute random other files > for some reason, at which point the kernel constructs a module name > based on the first two bytes of the file and tries to modprobe it; it > only goes near binfmt_misc if that module has specifically registered > itself as knowing about the binary format in question. I haven't worked > out exactly what's causing it for him yet. >
The activity seems to have gone dead around my post. Has anything else occurred to you that might help? This may be trivial, but I just hate having unexplained error messages floating around... Thanks, Jonathan -- /* Jonathan Gift [EMAIL PROTECTED] */
