> Sometimes, diagnosing things need a leap of thought. It will always > require that. :)
Right. But once you've made the leap of thought, it's nice if you can save others from having to make the same leap themselves. The best thing is if the system can give a useful diagnostic, say something like "Can't execute file on noexec filesystem"; this would be much more useful than "Permission denied" or "Operation not permitted". However, I realize that performance considerations affect the number of possible error codes, so I don't know if this is feasible. (By the way, is the noexec mount option used for anything other than not allowing an executable file to run?) The next best thing, once you've figured out that the system says "permission denied" in this case, is to document the error and the possible causes for it. Perhaps I should have looked in a database of error codes. Is there such a thing? Just looked on Google and couldn't find one. So we're back to the manual. I can see why the writers of a manual think that mount options belong in a section about mounting. But a good manual will also include a cross-reference from the section on permissions, since mounting affects permissions in a non-trivial way; just look at the recent posts to see how non-trivial it is :-) Orna, it was one of the manuals that came inside my SuSE system; perhaps I'll write to them one of these days. -Ron. -------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
