[Bug 274174] kdump(1): list trace points directly instead of pointing to ktrace(1)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274174

            Bug ID: 274174
           Summary: kdump(1): list trace points directly instead of
                    pointing to ktrace(1)
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Manual Pages
          Assignee: bugs@FreeBSD.org
          Reporter: naddy@FreeBSD.org
                CC: doc@FreeBSD.org

Created attachment 245332
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=245332&action=edit
list trace points directly in kdump(1)

It's always the same:
* foobar doesn't behave as expected.
* I ktrace foobar.
* I run kdump... too much information.
* I check the kdump(1) man page, since I can't remember which letter represents
which trace point.
* "See the -t option of ktrace(1)."

Sigh.  Yes, duplication is frowned on, but would it really be so bad to also
list the trace points directly in kdump(1) instead of pointing to ktrace(1)?

Patch attached.

-- 
You are receiving this mail because:
You are on the CC list for the bug.