<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in README</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2025</copyright>
    <generator>Java</generator><item>
        <title>92f251f36b31519ed336ac67b768d39b62ebf896 - cam: Dtrace scripts to help diagnose weird things</title>
        <link>http://opengrok.net:8080/history/src/tools/cam/README#92f251f36b31519ed336ac67b768d39b62ebf896</link>
        <description>cam: Dtrace scripts to help diagnose weird thingsThese are sample dtrace scripts that likely need to be modified forwhatever problem you are chasing. Unfortuneately, you have to read thedriver extensively to understand them or how to use them. But studyingthe completion routine of mpr/mps will help understand many of the errorand recovery paths.Sponsored by:		Netflix

            List of files:
            /src/tools/cam/README</description>
        <pubDate>Fri, 09 Jan 2026 06:11:10 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>cd1aa5f9917cc7de255e854954c818e5ef3e9c9b - tools/cam: Start to add the testing tools for CAM</title>
        <link>http://opengrok.net:8080/history/src/tools/cam/README#cd1aa5f9917cc7de255e854954c818e5ef3e9c9b</link>
        <description>tools/cam: Start to add the testing tools for CAMCreate a directory for testing tools arond CAM. These are snippets ofwhat will eventually be camio. At the moment, it was written using fbttraces. This is OK, but fragile, so they need to be re-written with thecam provider. cam_all_but_scsi.d is the first step. It shows how to dothis with the new cam dtrace provider.Sponsored by:		NetflixReviewed by:		adrianDifferential Revision:	https://reviews.freebsd.org/D54472

            List of files:
            /src/tools/cam/README</description>
        <pubDate>Thu, 08 Jan 2026 06:20:34 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>92f251f36b31519ed336ac67b768d39b62ebf896 - cam: Dtrace scripts to help diagnose weird things</title>
        <link>http://opengrok.net:8080/history/src/tools/cam/README#92f251f36b31519ed336ac67b768d39b62ebf896</link>
        <description>cam: Dtrace scripts to help diagnose weird thingsThese are sample dtrace scripts that likely need to be modified forwhatever problem you are chasing. Unfortuneately, you have to read thedriver extensively to understand them or how to use them. But studyingthe completion routine of mpr/mps will help understand many of the errorand recovery paths.Sponsored by:		Netflix

            List of files:
            /src/tools/cam/README</description>
        <pubDate>Fri, 09 Jan 2026 06:11:10 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>cd1aa5f9917cc7de255e854954c818e5ef3e9c9b - tools/cam: Start to add the testing tools for CAM</title>
        <link>http://opengrok.net:8080/history/src/tools/cam/README#cd1aa5f9917cc7de255e854954c818e5ef3e9c9b</link>
        <description>tools/cam: Start to add the testing tools for CAMCreate a directory for testing tools arond CAM. These are snippets ofwhat will eventually be camio. At the moment, it was written using fbttraces. This is OK, but fragile, so they need to be re-written with thecam provider. cam_all_but_scsi.d is the first step. It shows how to dothis with the new cam dtrace provider.Sponsored by:		NetflixReviewed by:		adrianDifferential Revision:	https://reviews.freebsd.org/D54472

            List of files:
            /src/tools/cam/README</description>
        <pubDate>Thu, 08 Jan 2026 06:20:34 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>92f251f36b31519ed336ac67b768d39b62ebf896 - cam: Dtrace scripts to help diagnose weird things</title>
        <link>http://opengrok.net:8080/history/src/tools/cam/README#92f251f36b31519ed336ac67b768d39b62ebf896</link>
        <description>cam: Dtrace scripts to help diagnose weird thingsThese are sample dtrace scripts that likely need to be modified forwhatever problem you are chasing. Unfortuneately, you have to read thedriver extensively to understand them or how to use them. But studyingthe completion routine of mpr/mps will help understand many of the errorand recovery paths.Sponsored by:		Netflix

            List of files:
            /src/tools/cam/README</description>
        <pubDate>Fri, 09 Jan 2026 06:11:10 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>cd1aa5f9917cc7de255e854954c818e5ef3e9c9b - tools/cam: Start to add the testing tools for CAM</title>
        <link>http://opengrok.net:8080/history/src/tools/cam/README#cd1aa5f9917cc7de255e854954c818e5ef3e9c9b</link>
        <description>tools/cam: Start to add the testing tools for CAMCreate a directory for testing tools arond CAM. These are snippets ofwhat will eventually be camio. At the moment, it was written using fbttraces. This is OK, but fragile, so they need to be re-written with thecam provider. cam_all_but_scsi.d is the first step. It shows how to dothis with the new cam dtrace provider.Sponsored by:		NetflixReviewed by:		adrianDifferential Revision:	https://reviews.freebsd.org/D54472

            List of files:
            /src/tools/cam/README</description>
        <pubDate>Thu, 08 Jan 2026 06:20:34 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
