Has anyone know if it exists on the internet like Microsoft error db?

Debian Linux wrote:
> Has anyone know if it exists on the internet like Microsoft error db?

A general google for any issues usually turns up whatever answers are
needed.

A searchable archive of this mailing list is maintained at
http://lists.debian.org/search.html which essentially functions like the
Microsoft Knowledge Database does for Windows issues. I'm afraid I'm
unfamiliar with a "Microsoft error db", if that's something different,
so can't really address your question.

--
Kent West
Westing Peacefully - http://kentwest.blogspot.com



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Similar to the ones in the following

http://service1.symantec.com/SUPPORT...2?OpenDocument

http://msdn.microsoft.com/en-us/libr...86(VS.85).aspx

>From my understanding is that MS OS backbone errors are standardised coding
but the solution varies from one application client to another.

On 5/26/08, Kent West <westk@acu.edu> wrote:
>
> Debian Linux wrote:
>
>> Has anyone know if it exists on the internet like Microsoft error db?
>>
>
> A general google for any issues usually turns up whatever answers are
> needed.
>
> A searchable archive of this mailing list is maintained at
> http://lists.debian.org/search.html which essentially functions like the
> Microsoft Knowledge Database does for Windows issues. I'm afraid I'm
> unfamiliar with a "Microsoft error db", if that's something different, so
> can't really address your question.
>
> --
> Kent West
> Westing Peacefully - http://kentwest.blogspot.com
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>

On Mon, May 26, 2008 at 03:15:27PM +1000, Debian Linux wrote:
> Has anyone know if it exists on the internet like Microsoft error db?

I think you are looking for the Debian bug tracking system:

http://www.debian.org/Bugs/

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIOvYrqJyztHCFm9kRAmxcAJ0Vt09ZdVaSNNb+zcQYck zxmIERLgCfUCz7
RMzKZRy6DS+ZykViOOwfn6E=
=n5oV
-----END PGP SIGNATURE-----

On Mon, May 26, 2008 at 8:00 AM, Debian Linux <debianlinux34@gmail.com>
wrote:

> Similar to the ones in the following
>
>
> http://service1.symantec.com/SUPPORT...2?OpenDocument
>
> http://msdn.microsoft.com/en-us/library/ms681386(VS.85).aspx<http://msdn.microsoft.com/en-us/library/ms681386%28VS.85%29.aspx>
>
> From my understanding is that MS OS backbone errors are standardised coding
> but the solution varies from one application client to another.
>

I think it should be a good idea to create a site (¿wiki?) where you could
find possible solutions to a determined log error pattern. I don't think
bugs.debian.org is like that. "Debian Linux" user refers to a documentation
like oracle use.

The problem is how to sort the possible log errors, and how to bind the log
errors to specifics versions of packages.

So I think should be better to create a file like the FAQs in every
package/program where the autor/or contributors write the possible message
logs errors and their explication. It could be named "FLE" (Frequently Logs
Errors) or FLEW if warning messages are incluyed.

I know the best method is read and understand manuals and then the message
logs are sufficient to resolv the problem (but sometimes it take more time
that you have)

What do you think about it ?

Sorry for my english

I agree what you are saying. see my post at

http://forum.mysqlperformanceblog.com/s/t/763/

it does indicate that error log is even version sensitive. Whatever error
log or error db are fine to user as long as we newbies don't stuck with the
errors without solutions.


On 5/27/08, Javier Barroso <javibarroso@gmail.com> wrote:
>
>
>
> On Mon, May 26, 2008 at 8:00 AM, Debian Linux <debianlinux34@gmail.com>
> wrote:
>
>> Similar to the ones in the following
>>
>>
>> http://service1.symantec.com/SUPPORT...2?OpenDocument
>>
>> http://msdn.microsoft.com/en-us/library/ms681386(VS.85).aspx<http://msdn..microsoft.com/en-us/library/ms681386%28VS.85%29.aspx>
>>
>> From my understanding is that MS OS backbone errors are standardised
>> coding but the solution varies from one application client to another.
>>
>
> I think it should be a good idea to create a site (¿wiki?) where you could
> find possible solutions to a determined log error pattern. I don't think
> bugs.debian.org is like that. "Debian Linux" user refers to a
> documentation like oracle use.
>
> The problem is how to sort the possible log errors, and how to bind the log
> errors to specifics versions of packages.
>
> So I think should be better to create a file like the FAQs in every
> package/program where the autor/or contributors write the possible message
> logs errors and their explication. It could be named "FLE" (Frequently Logs
> Errors) or FLEW if warning messages are incluyed.
>
> I know the best method is read and understand manuals and then the message
> logs are sufficient to resolv the problem (but sometimes it take more time
> that you have)
>
> What do you think about it ?
>
> Sorry for my english
>

Hi Mister Unknown,

On Tue, 27 May 2008, Debian Linux wrote:

> I agree what you are saying. see my post at
>
> [1]http://forum.mysqlperformanceblog.com/s/t/763/
>
> it does indicate that error log is even version sensitive. Whatever error
> log or error db are fine to user as long as we newbies don't stuck with
> the errors without solutions.

please do not speak for others.

In the MS World, there are maybe Error Codes from Applications, but those are nearly always
completely useless. And I do not want a "Error Code" so i can search for it, a see .. many other
people discussing what those numbers mean.


--
Florian Reitmeir


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org