Include EyeSDN USB S0 trace files in the list of file formats we read.

svn path=/trunk/; revision=10040

4 files changed, 24 insertions, 24 deletions

diff --git a/doc/editcap.pod b/doc/editcap.pod
index 5b65a62325..2f1ed717d3 100644
--- a/doc/editcap.pod
+++ b/doc/editcap.pod
@@ -41,12 +41,12 @@ the B<DBS Etherwatch> VMS utility, traffic capture files from Visual
 Networks' Visual UpTime, the output from B<CoSine> L2 debug, the output
 from Accellent's 5Views LAN agents, captures in Endace Measurement
 Systems' ERF format, Linux Bluez Bluetooth stack B<hcidump -w> traces,
-and captures from Network Instruments Observer version 9.  There is no
-need to tell B<Editcap> what type of file you are reading; it will
-determine the file type by itself.  B<Editcap> is also capable of
-reading any of these file formats if they are compressed using gzip. 
-B<Editcap> recognizes this directly from the file; the '.gz' extension
-is not required for this purpose.
+captures from Network Instruments Observer version 9, and traces from
+the EyeSDN USB S0.  There is no need to tell B<Editcap> what type of
+file you are reading; it will determine the file type by itself. 
+B<Editcap> is also capable of reading any of these file formats if they
+are compressed using gzip.  B<Editcap> recognizes this directly from the
+file; the '.gz' extension is not required for this purpose.
 
 By default, it writes the capture file in B<libpcap> format, and writes
 all of the packets in the capture file to the output file.  The B<-F>
diff --git a/doc/ethereal.pod b/doc/ethereal.pod
index 730ef8aa41..96e1adf199 100644
--- a/doc/ethereal.pod
+++ b/doc/ethereal.pod
@@ -59,12 +59,12 @@ the B<DBS Etherwatch> VMS utility, traffic capture files from Visual
 Networks' Visual UpTime, the output from B<CoSine> L2 debug, the output
 from Accellent's 5Views LAN agents, captures in Endace Measurement
 Systems' ERF format, Linux Bluez Bluetooth stack B<hcidump -w> traces,
-and captures from Network Instruments Observer version 9.  There is no
-need to tell B<Ethereal> what type of file you are reading; it will
-determine the file type by itself.  B<Ethereal> is also capable of
-reading any of these file formats if they are compressed using gzip. 
-B<Ethereal> recognizes this directly from the file; the '.gz' extension
-is not required for this purpose.
+captures from Network Instruments Observer version 9, and traces from
+the EyeSDN USB S0.  There is no need to tell B<Ethereal> what type of
+file you are reading; it will determine the file type by itself. 
+B<Ethereal> is also capable of reading any of these file formats if they
+are compressed using gzip.  B<Ethereal> recognizes this directly from
+the file; the '.gz' extension is not required for this purpose.
 
 Like other protocol analyzers, B<Ethereal>'s main window shows 3 views
 of a packet.  It shows a summary line, briefly describing what the
diff --git a/doc/mergecap.pod b/doc/mergecap.pod
index c7d104256e..da77ea0fa0 100644
--- a/doc/mergecap.pod
+++ b/doc/mergecap.pod
@@ -37,12 +37,12 @@ the B<DBS Etherwatch> VMS utility, traffic capture files from Visual
 Networks' Visual UpTime, the output from B<CoSine> L2 debug, the output
 from Accellent's 5Views LAN agents, captures in Endace Measurement
 Systems' ERF format, Linux Bluez Bluetooth stack B<hcidump -w> traces,
-and captures from Network Instruments Observer version 9.  There is no
-need to tell B<Mergecap> what type of file you are reading; it will
-determine the file type by itself.  B<Mergecap> is also capable of
-reading any of these file formats if they are compressed using gzip. 
-B<Mergecap> recognizes this directly from the file; the '.gz' extension
-is not required for this purpose.
+captures from Network Instruments Observer version 9, and traces from
+the EyeSDN USB S0.  There is no need to tell B<Mergecap> what type of
+file you are reading; it will determine the file type by itself. 
+B<Mergecap> is also capable of reading any of these file formats if they
+are compressed using gzip.  B<Mergecap> recognizes this directly from
+the file; the '.gz' extension is not required for this purpose.
 
 By default, it writes the capture file in B<libpcap> format, and writes
 all of the packets in both input capture files to the output file.  The
diff --git a/doc/tethereal.pod b/doc/tethereal.pod
index db97351823..aa20d76baf 100644
--- a/doc/tethereal.pod
+++ b/doc/tethereal.pod
@@ -61,12 +61,12 @@ the B<DBS Etherwatch> VMS utility, traffic capture files from Visual
 Networks' Visual UpTime, the output from B<CoSine> L2 debug, the output
 from Accellent's 5Views LAN agents, captures in Endace Measurement
 Systems' ERF format, Linux Bluez Bluetooth stack B<hcidump -w> traces,
-and captures from Network Instruments Observer version 9.  There is no
-need to tell B<Tethereal> what type of file you are reading; it will
-determine the file type by itself.  B<Tethereal> is also capable of
-reading any of these file formats if they are compressed using gzip. 
-B<Tethereal> recognizes this directly from the file; the '.gz' extension
-is not required for this purpose.
+captures from Network Instruments Observer version 9, and traces from
+the EyeSDN USB S0.  There is no need to tell B<Tethereal> what type of
+file you are reading; it will determine the file type by itself. 
+B<Tethereal> is also capable of reading any of these file formats if
+they are compressed using gzip.  B<Tethereal> recognizes this directly
+from the file; the '.gz' extension is not required for this purpose.
 
 If the B<-w> flag is not specified, B<Tethereal> prints a decoded form
 of the packets it captures or reads; otherwise, it writes those packets