From: Jerry Peters on
John Hasler <jhasler(a)newsguy.com> wrote:
> Jerry writes:
>> If IBM couldn't manage this in a timely fashion, how the heck are FOSS
>> developers expected to?
>
> Especially considering that Linux has orders of maginitude more
> software.
>
> In any case, it makes no sense to give people an error number and tell
> them to go look up the message when you can just give them the message.
> Mass storage isn't expensive any more.

In fact for MVS (and I assume Z/OS) there's a non IBM product that is
used with SDSF; IIRC you put the cursor in the message number, hit a
PF key and it gives you the message text. Entering *all* of the
messages must have been a real chore!

Even with the mmessages manual, you still needed at least some basic
knowledge of whatever subsystem or program produced the error.

Jerry
From: Robert Riches on
On 2010-04-08, Curt <curty(a)free.fr> wrote:
> 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?

Ummm, you said you "googled the entire quote", which implies that
you searched for the phrase.

>> 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.

Without quotation marks around the phrase, you're searching for
the words in any order, not the quote. That's how Google
works--Google and most other search engines/facilities I have
seen.

> "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.

Only if you choose to refuse to learn.

--
Robert Riches
spamtrap42(a)verizon.net
(Yes, that is one of my email addresses.)
From: Curt on
On 2010-04-09, Robert Riches <spamtrap42(a)verizon.net> wrote:
> On 2010-04-08, Curt <curty(a)free.fr> wrote:
>> 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?
>
> Ummm, you said you "googled the entire quote", which implies that
> you searched for the phrase.

I searched the entire phrase--quote--as in a repeated passage. But if I
could go back in time and choose another formulation without the
admitted ambiguity, I would.

>>> Searching for the individual words in any order yields 53,300
>>> hits. I suspect you forgot to put quotation marks around the
>>> phrase.

Your claim is meaningless because modifying the word order
of an unquoted search string modifies the number of hits obtained:

file or such No directory ls access cannot (yields 6,230,000 hits)

cannot file such or ls No directory access (yields 5,640,000 hits)

cannot No file such ls directory access or (yields 876,000 hits)

>> The individual words in any order? I'm sure I'm not following you
>> here.
>
> Without quotation marks around the phrase, you're searching for
> the words in any order, not the quote. That's how Google
> works--Google and most other search engines/facilities I have
> seen.

If you're saying that without the quotation marks, you're searching for
any random permutation of the words in the string, without any
additional weight or value given to one combination or another, you're
wrong

http://www.google.com/support/websearch/bin/answer.py?hl=en&answer=136861
From: Marten Kemp on
Sidney Lambe wrote:
> On comp.os.linux.misc, Marten Kemp <marten.kemp(a)thisplanet-link.net> wrote:
>> From: Marten Kemp <marten.kemp(a)thisplanet-link.net>
>> Newsgroups: comp.unix.bsd.misc,comp.os.linux.misc
>> Subject: Re: Are there any man pages for any of the system error messages?
>> Date: Tue, 06 Apr 2010 19:56:52 -0400
>> Organization: Aioe.org NNTP Server
>> Lines: 40
>> Message-ID: <hpghoa$1kj$1(a)speranza.aioe.org>
>> References: <565n87-uta.ln1(a)neptune.markhobley.yi.org>
<ick4smlpil.fsf(a)verizon.net> <tico87-m7b.ln1(a)neptune.markhobley.yi.org>
<iczl1hjqtm.fsf(a)verizon.net> <hols87-vfc.ln1(a)neptune.markhobley.yi.org>
>> Reply-To: marten.kemp(a)thisplanet-link.net
>> NNTP-Posting-Host: XeMTe4goQluOzT6zZui20Q.user.speranza.aioe.org
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>> Content-Transfer-Encoding: 7bit
>> X-Complaints-To: abuse(a)aioe.org
>> X-Notice: Filtered by postfilter v. 0.8.2
>
>> User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>> Path: x-privat.org!news.mixmin.net!aioe.org!not-for-mail
>> Xref: newsfeed.x-privat.org comp.unix.bsd.misc:173
>> comp.os.linux.misc:81542
>>
>> Mark Hobley wrote:
>>
>>> In comp.os.linux.misc despen(a)verizon.net wrote:
>>>
>>>> home> ls -l nonsuchfile /bin/ls: cannot access nonsuchfile:
>>>> No such file or directory
>>>>
>>>> Do you really think a message number would help?
>>> It might help a user who has that error pop up on the screen
>>> during operation, because they can reference the message
>>> number against the documentation.
>>>
>>> If on the other hand, they google for the message as output
>>> above, the only documentation that they get, is a single hit
>>> to your post.
>>>
>>> Lets, look at another example. A user opens up their internet
>>> browser, starts browsing the web, and the following error
>>> message appears:
>>>
>>> (gecko:nnnn): Pango-WARNING **: Error loading GPOS table 5503
>>>
>>> Who the hell knows what means? An end user may have a real
>>> hard time trying to resolve that error, if they cannot relate
>>> the message to appropriate reference documentation. Numbering
>>> the messages so that this can be related to reference
>>> documentation is just a good idea IMHO.
>> On googling for mesage output - I've run into a 'display limit'
>> when running Debian's aptitude and the only hits I've ever
>> gotten are posts that I've made asking for clarification.
>>
>> I come from an IBM mainframe environment where messages have
>> numbers (see my earlier post). They make life immeasurably
>> simpler, even in environments without as steep a learning curve
>> as Linux does.
>>
>> This is one of the differences between a
>> professionally-designed and -written OS and something else.
>
> Try slackware without KDE/Gnome, etc. and you'll change your mind
> about what Linux can be. It is modeled after the Unix OSes not
> the fumblings of the folks at GNU as they try desperately and
> foolishly to be different from Unix.
>
>> IMHO, of course.
>
> Says a guy running Windows.
>
> ROTFL!
>

c/professional/intelligent/ then, if it makes you happier.
The main point is _designed_ , with malice aforethought
<grin>.

I use Windows on this machine because it meets the needs
I have for it and, frankly, I started with Windows. I have
another machine running Windows because my school runs
Adobe products. My web and general-purpose server runs
command-line Debian (I've tried Gnome and it hasn't been
worth the trouble). My _other_ workstation is for trying
various GUI-enabled Linux distros - I haven't found one
that I really cared about keeping yet.


--
-- Marten Kemp (Fix ISP to reply)
You can't help being ignorant 'cause there's always
something you don't know; what you can't be is stupid.
From: Robert Bonomi on
In article <565n87-uta.ln1(a)neptune.markhobley.yi.org>,
Mark Hobley <markhobley(a)hotpop.donottypethisbit.com> wrote:
>Does anyone know of any repositories containing man pages for system error
>messages? I am looking for pages that document error messages and resolution.
>
>Manual pages for each of the error messages produced by the C library would
>be a good starting point for me. Has anyone written any such pages?

With very *rare* exceptions, the library doesn't produce _any_ error
MESSAGES. Message reporting is left to the higher-level code.

'man 2 intro' covers the error _codes_ returned by system calls and the
standard C library. It also has a 'generic' text string associated with
each code. Which something reporting the error may, or *MAY*NOT* use

See also 'man 3 intro' and the manpages referenced therein.


Beyond that, you'll need to read through all the core kernel and loadable-
kernel-module sources, looking for anything sent to syslog(2), or output
to 'stdout'/'stderr' (as well as any other file pointers that have been
assigned their value therefrom), *OR*, more likely, stuff written to file
descriptors 1 and 2 (either literally, or a variable with that value).

The 'good news' is that probably no message output is going to occur from
any of the modules that are native assembler code.