Are there any man pages for any of the system error messages?
in [General Linux]
|
Prev: Live CD to scan windows pc for a virus
Next: where is CentOS storing my hostname that it resets it on each reboot?
From: Mark Hobley on 7 Apr 2010 23:17 despen(a)verizon.net wrote: >> Error: C2: No such file or directory: fred > > So where is the message number from "ls"? That will be the message from ls. > You have perror producing a C2 prefix, I don't have at the moment, but I would just to see this happen. I will implement this on mglibc, if it does not happen upstream. > What happened to "/bin/ls cannot access"? Developers of ls commands can still output that, if they want to. The benefit of using the C2 prefix though, is that software that uses different file not found messages can still use the C2 reference documentation, without the need to write separate documentation for their versions. So "File not found", "file not found", "file cannot be found", "File ne found pas", etc, can all be prefixed with C2, to indicate that the C2 reference documentation applies to this message. > When IBM embarked on it's mission to number all it's messages, > they realized that applications running on their systems needed to > pump out messages too. So they started out reserving messages > starting with "I" to IBM. > ISPF is designed to first produce a short (20 character or so) > message, then if you don't understand, you press PF1 (the help key) and > get a long message (usually > 80 characters but it can be more), then if you press help once more and > you get the actual full documentation. > Now, that's my idea of a solution. Actually, Metawindows supported the F1 key too, although I never got round to writing the documentation for it to display. Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/
From: Curt on 8 Apr 2010 05:01 On 2010-04-08, Robert Riches <spamtrap42(a)verizon.net> wrote: >> I googled the entire quote, fred included, and got 53,800 hits. > > Searching for the whole phrase/sentence/message (including fred), > with quotation marks around it, Google returns _FOUR_ hits. Who said anything about quotation marks? > Searching for the individual words in any order yields 53,300 > hits. I suspect you forgot to put quotation marks around the > phrase. The individual words in any order? I'm sure I'm not following you here. "ls: cannot access: No such file or directory" yields 695 hits (with or without semicolons, with quotation marks). Anyway, talk about an exercise in futility.
From: John Hasler on 8 Apr 2010 08:28 Mark Hobley writes: > Error: C2: No such file or directory: fred despen writes: > So where is the message number from "ls"? Mark Hobley writes: > That will be the message from ls. So you are not going to identify the failing program? That is the primary defect in the Pango message. -- John Hasler jhasler(a)newsguy.com Dancing Horse Hill Elmwood, WI USA
From: despen on 8 Apr 2010 09:36 markhobley(a)hotpop.donottypethisbit.com (Mark Hobley) writes: > despen(a)verizon.net wrote: >>> Error: C2: No such file or directory: fred >> >> So where is the message number from "ls"? > > That will be the message from ls. > >> You have perror producing a C2 prefix, > > I don't have at the moment, but I would just to see this happen. I will > implement this on mglibc, if it does not happen upstream. > >> What happened to "/bin/ls cannot access"? > > Developers of ls commands can still output that, if they want to. The benefit > of using the C2 prefix though, is that software that uses different > file not found messages can still use the C2 reference documentation, without > the need to write separate documentation for their versions. > > So "File not found", "file not found", "file cannot be found", > "File ne found pas", etc, can all be prefixed with C2, to indicate that > the C2 reference documentation applies to this message. Currently, ls does not handle "File not found" as a special case. It just takes the output of perror and wraps its own text around the result. For example: home> ls /var/log/samba/* /bin/ls: cannot access /var/log/samba/*: Permission denied Exact same logic, ls doesn't know it's Permisson denied instead of File not found. All it knows is that it can't access the file.
From: Mark Hobley on 8 Apr 2010 11:58
John Hasler <jhasler(a)newsguy.com> wrote: > So you are not going to identify the failing program? Yes of course. Programs will be able to provide this as a parameter. Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/ |