Sebastien Roy wrote:
On Mon, 2009-11-02 at 07:19 -0500, James Carlson wrote:
The only thing blocking the removal of snoop in the past has been the
lack of wireshark/tshark integration as a replacement. Has that finally
been fixed? If so, then just do it.
Wireshark and tshark are in SFW, but there is IMO much work to be done
to call it a suitable alternative/replacement. For one, we have a large
number of Solaris networking test suites that depend on the snoop CLI
and output format (both the snoop file format and the terminal output),
and one would need to evaluate how to handle those dependencies. I have
no doubt that similar dependencies exist for user scripts and tools.
For that reason, I'm not sure that we'll be able to exclude snoop from a
Solaris distribution anytime soon.
I agree.
But a Solaris distribution already includes components from SFW, not
just ON.
And our test suite already depends on bits from SFW.
So there is no Rubicon that needs crossing here.
Why shouldn't snoop become SFW?
Do we need to have a PSARC case or something to announce the EO-whatever
for snoop in order to unbundle it from ON?
So the idea I'm proposing is not to "rip snoop out" but to change the
location and the home of its source code so that it is no longer
considered an integral part of Solaris like it is now. It becomes just
another tool for sniffing packets, alongside tcpdump and wireshark, that
we bring in from the outside.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
