From: Wolfgang Pfeiffer <roto@gmx.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linuxppc-dev@ozlabs.org, billfink@mindspring.com,
linux1394-devel@lists.sourceforge.net
Subject: Re: Broken Firewire 400/SCSI on ppc Powerbook5,8
Date: Fri, 25 Aug 2006 00:56:26 +0200 [thread overview]
Message-ID: <20060824225626.GA4100@localhost> (raw)
In-Reply-To: <44EE0173.9060403@s5r6.in-berlin.de>
On Thu, Aug 24, 2006 at 09:43:47PM +0200, Stefan Richter wrote:
> Wolfgang Pfeiffer wrote:
> ...
> >Because i hate to burden my lousy memory with what I did to produce
> >the logs above, I scrambled together my admittedly marginal bash
> >knowledge and ran the tests with 4 scripts to produce the logs.
> >
> >All the following below is to give you control on how these logs were
> >created.
> ...
>
> Thanks, I will look at them as soon as I have my lookup table for the
> hex codes and the mental capacity available. :-) BTW, a convenient way
> to annotate the syslog is the command "logger". E.g.
> $ logger "hello world"
> $ ./hello_world 2>&1 | logger -t hi_world
I'll keep that on my radar for the next time I could use 'logger' ...
But after reading the - how do I say that without becoming offensive,
- err .. possibly slightly esoteric explanations in "man logger" I'm
not that much enthusiastic to use the tool ... but let's see .. :)
Note: Please ignore most of the ugly explanations on how I created the
logs for ieee1394 in my previous mail. Some should be nothing more
than a reference if (and only if) the ieee logs I put on my home page
don't help to debug the FW issue ...
Thanks
Best regards
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
next prev parent reply other threads:[~2006-08-24 22:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 23:03 Broken Firewire 400/SCSI on ppc Powerbook5,8 Wolfgang Pfeiffer
2006-08-18 5:28 ` Bill Fink
2006-08-18 10:17 ` Wolfgang Pfeiffer
2006-08-19 9:32 ` Stefan Richter
2006-08-20 0:18 ` Bill Fink
2006-08-22 8:58 ` Stefan Richter
2006-08-18 23:49 ` Wolfgang Pfeiffer
2006-08-19 9:13 ` Stefan Richter
2006-08-20 1:31 ` Wolfgang Pfeiffer
2006-08-21 7:56 ` Stefan Richter
2006-08-21 0:29 ` Wolfgang Pfeiffer
2006-08-21 0:40 ` Wolfgang Pfeiffer
2006-08-23 0:28 ` Wolfgang Pfeiffer
2006-08-23 0:36 ` Wolfgang Pfeiffer
2006-08-23 1:50 ` [Correction #2] " Wolfgang Pfeiffer
2006-08-24 19:22 ` Wolfgang Pfeiffer
2006-08-24 19:43 ` Stefan Richter
2006-08-24 22:56 ` Wolfgang Pfeiffer [this message]
2006-09-02 19:18 ` Stefan Richter
2006-09-02 23:08 ` Wolfgang Pfeiffer
2006-09-02 23:28 ` Stefan Richter
2006-09-02 23:26 ` Wolfgang Pfeiffer
2006-09-04 16:58 ` Stefan Richter
2006-08-19 8:10 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060824225626.GA4100@localhost \
--to=roto@gmx.net \
--cc=billfink@mindspring.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=stefanr@s5r6.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.