From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: Re: wireshark
Date: Fri, 31 Oct 2014 16:20:26 -0400 [thread overview]
Message-ID: <20141031202026.GG17580@fieldses.org> (raw)
In-Reply-To: <20141027220848.GB32743@fieldses.org>
On Mon, Oct 27, 2014 at 06:08:48PM -0400, bfields wrote:
> I've been getting frequent crashes with the latest wireshark. I think
> it's fixed in:
>
> git://linux-nfs.org/~bfields/wireshark.git master
>
> I'll probably try to add seek and allocate support while I'm there, and
> pass it to wireshark upstream when I've got it better figured out.
Done, but not upstream yet. Till then, something like:
git clone git://linux-nfs.org/~bfields/wireshark.git
cd wireshark
./autogen.sh
./configure
make
should work. (And you may discover you need to install some -devel
packages after the next-to-last step.)
--b.
prev parent reply other threads:[~2014-10-31 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 22:08 wireshark J. Bruce Fields
2014-10-31 20:20 ` J. Bruce Fields [this message]
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=20141031202026.GG17580@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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