summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorguy <guy>2000-12-23 20:48:13 +0000
committerguy <guy>2000-12-23 20:48:13 +0000
commit8d35bf0e1cf45929761c0b20480a91fc4be9f0a5 (patch)
tree2b309a2aa74e36979aba3335fc1f22d55bc5e677
parent16011e473a5e169132fe4573ddcd22fca20e37ce (diff)
downloadtcpdump-8d35bf0e1cf45929761c0b20480a91fc4be9f0a5.tar.gz
Fix some comments to reflect current reality.
-rw-r--r--print-fddi.c10
-rw-r--r--print-token.c10
2 files changed, 10 insertions, 10 deletions
diff --git a/print-fddi.c b/print-fddi.c
index f8a2ffdd..8911dea1 100644
--- a/print-fddi.c
+++ b/print-fddi.c
@@ -21,7 +21,7 @@
#ifndef lint
static const char rcsid[] =
- "@(#) $Header: /tcpdump/master/tcpdump/print-fddi.c,v 1.49 2000-12-22 22:45:11 guy Exp $ (LBL)";
+ "@(#) $Header: /tcpdump/master/tcpdump/print-fddi.c,v 1.50 2000-12-23 20:48:13 guy Exp $ (LBL)";
#endif
#ifdef HAVE_CONFIG_H
@@ -279,10 +279,10 @@ fddi_if_print(u_char *pcap, const struct pcap_pkthdr *h,
*/
snapend = p + caplen;
/*
- * Actually, the only printer that uses packetp is print-bootp.c,
- * and it assumes that packetp points to an Ethernet header. The
- * right thing to do is to fix print-bootp.c to know which link
- * type is in use when it excavates. XXX
+ * Actually, the only printers that use packetp are print-arp.c
+ * and print-bootp.c, and they assume that packetp points to an
+ * Ethernet header. The right thing to do is to fix them to know
+ * which link type is in use when they excavate. XXX
*/
packetp = (u_char *)&ehdr;
diff --git a/print-token.c b/print-token.c
index 1a0cc693..3f1f44ba 100644
--- a/print-token.c
+++ b/print-token.c
@@ -25,7 +25,7 @@
*/
#ifndef lint
static const char rcsid[] =
- "@(#) $Header: /tcpdump/master/tcpdump/print-token.c,v 1.10 2000-12-22 22:45:12 guy Exp $";
+ "@(#) $Header: /tcpdump/master/tcpdump/print-token.c,v 1.11 2000-12-23 20:48:13 guy Exp $";
#endif
#ifdef HAVE_CONFIG_H
@@ -136,10 +136,10 @@ token_if_print(u_char *user, const struct pcap_pkthdr *h, const u_char *p)
*/
snapend = p + caplen;
/*
- * Actually, the only printer that uses packetp is print-bootp.c,
- * and it assumes that packetp points to an Ethernet header. The
- * right thing to do is to fix print-bootp.c to know which link
- * type is in use when it excavates. XXX
+ * Actually, the only printers that use packetp are print-arp.c
+ * and print-bootp.c, and they assume that packetp points to an
+ * Ethernet header. The right thing to do is to fix them to know
+ * which link type is in use when they excavate. XXX
*/
packetp = (u_char *)&ehdr;