--- fmdump.1m.orig	Mon Jan 28 10:48:23 2008
+++ fmdump.1m	Mon Jan 28 22:35:07 2008
@@ -9,9 +9,9 @@
      fmdump - fault management log viewer
 
 SYNOPSIS
      fmdump [-efvV] [-c	class] [-R dir]	[-t time] [-T time]
-	 [-u uid] [file]
+	 [-u uid] [-n name[.name]*[=value]] [file]
 
 
 DESCRIPTION
      The fmdump	utility	can be used to display	the  contents  of
@@ -366,9 +366,23 @@
 		 If the	-e option and -u option	are both present,
 		 the  error  events  that are cross-referenced by
 		 the specified diagnosis are displayed.
 
+     -n	name[.name]*[=value]
 
+		 Select fault log or error log events, depending on -e
+		 option, that have properties with a matching name (and
+		 optionaly a matching value).  For string properties
+		 the value can be a regular expression match. Regular
+		 expression syntax is described in the EXTENDED REGULAR
+		 EXPRESSIONS  section  of  the regex(5) manual page.
+		 Be careful using the characters  $, *, {, ^, |, (, ),
+		 and \   a regular expression, because  they are also
+		 meaningful to the shell. It is  saftest to enclose
+		 the  entire full regular expression in single quotes.
+		 For numeric properites, the value can be  octal, hex
+		 or decimal.
+
      -v		 Display verbose event detail. The event  display
 		 is enlarged to	show additional	common members of
 		 the selected events.
 
@@ -380,9 +394,48 @@
 		 includes  a  list  of	cross-references  to  the
 		 corresponding	errors	that were associated with
 		 the diagnosis.
 
+EXAMPLES
+     Example 1 Retriving given class from fmd log 
 
+        fmdump -Ve -c 'ereport.io.ddi.context'		or
+        fmdump -Ve -c 'ereport.*.context'			or
+        fmdump -Ve -n 'class=ereport.io.ddi.context'	or
+        fmdump -Ve -n 'class=ereport.*.context'
+
+        Oct 06 2007 11:53:20.975021712 ereport.io.ddi.context
+        nvlist version: 0
+        	class = ereport.io.ddi.context
+        	ena = 0x1b03a15ecf00001
+        	detector = (embedded nvlist)
+        	nvlist version: 0
+               		version = 0x0
+                	scheme = dev
+                	device-path = /
+        	(end detector)
+
+        	__ttl = 0x1
+        	__tod = 0x470706b0 0x3a1da690
+
+     Example 2 Retriving specific detector device-path from fmd log
+
+        fmdump -Ve -n 'detector.device-path=.*/disk@1,0$'
+
+        Oct 06 2007 12:04:28.065660760 ereport.io.scsi.disk.rqs
+        nvlist version: 0
+        	class = ereport.io.scsi.disk.rqs
+        	ena = 0x453ff3732400401
+        	detector = (embedded nvlist)
+        		nvlist version: 0
+                	version = 0x0
+                	scheme = dev
+                	device-path = /pci@0,0/pci1000,3060@3/disk@1,0
+        	(end detector)
+
+        	__ttl = 0x1
+        	__tod = 0x4707094c 0x3e9e758
+
 OPERANDS
      The following operands are	supported:
 
      file    Specifies an alternate log	file to	 display  instead
@@ -468,9 +521,9 @@
 
 
 SEE ALSO
      sh(1),   fmadm(1M),   fmd(1M),   fmstat(1M),    syslogd(1M),
-     libexacct(3LIB), attributes(5)
+     libexacct(3LIB), attributes(5), regex(5),
 
      System Administration Guide: Security Services
 
      http://www.sun.com/msg/