From: Joe <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] segmentation fault running kismet
Date: Thu, 07 Feb 2008 18:16:28 +0100 [thread overview]
Message-ID: <47AB3CEC.2050206@gmail.com> (raw)
In-Reply-To: <A1286843C9B74E46B0063D92B7844C2802DE7E8A@azindbaex01.aztec.soft>
Do you really want an answer? So get rid of this. Some other MLs would
have you banned on the spot.
> This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.
> The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address.
Greetz Joe
--
Sepp "ZaP" Holzmayr
please reply to: zentrale.at.work at gmail.com
"Never underestimate the bandwidth of a freight train full of DAT tapes.
Only the round-trip is a little suboptimal."
next prev parent reply other threads:[~2008-02-07 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 16:31 [Buildroot] segmentation fault running kismet Saurav Kumar Barik
2008-02-07 17:16 ` Joe [this message]
2008-02-08 5:05 ` Yogesh Kumar Sharma
2008-02-08 7:08 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 6:51 saurav barik
2008-02-08 8:08 ` Joe
2008-02-08 8:51 ` saurav barik
2008-02-12 7:04 ` saurav barik
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=47AB3CEC.2050206@gmail.com \
--to=zentrale.at.work@gmail.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox