discover.conf(5)
π discover.conf β like, the whole vibe of the config file for discover(1) π
okay bestie, so this is the discover.conf page, and yeah it lives in the File Formats Manual section of the manual (section 5, for the record π). it's the lil guide to how you configure discover(1) and honestly it's giving main character energy. let's get into it π¦
β¨ NAME β¨
discover.conf β configuration file format for discover(1)
πΈ Description πΈ
so Discover goes looking for configuration files in a configuration directory, and that directory holds a bunch of files, okay? and those files are the ones that decide:
- which system buses get scanned by default π«Ά
- which ones should never be scanned, like absolutely not, not on our watch π
- and the URLs for hardware data files that go <em>beyond the local copy</em> that ships with the software β¨
the file format is XML β yes bestie, XML, we love a structured moment. the DTD is provided with the Discover software, and you can use it for informational or validation purposes. no cap, it's right there for you π
π Examples π
establishing default buses to scan π
<?xml version="1.0"?>
<!DOCTYPE conffile SYSTEM "conffile.dtd">
<conffile>
<busscan scan="default">
<bus name="ata"/>
<bus name="pci"/>
<bus name="pcmcia"/>
<bus name="scsi"/>
<bus name="usb"/>
</busscan>
</conffile>
a more complex example π¦
<?xml version="1.0"?>
<!DOCTYPE conffile SYSTEM "conffile.dtd">
<conffile>
<busscan scan="default">
<bus name="ata"/>
<bus name="pci"/>
<bus name="pcmcia"/>
<bus name="usb"/>
</busscan>
<!-- My ancient SCSI card locks up when probed -->
<busscan scan="never">
<bus name="scsi"/>
</busscan>
<data-sources>
<data-source url="http://www.example.com/discover/xfree86.xml"
label="Updated XFree86 hardware information">
</data-sources>
</conffile>
like, see how scsi is in the default list in the first example and then gets banished to scan="never" in the second one? because that ancient SCSI card locks up when probed π the comment in the XML says it and everything. iconic behavior honestly, protecting your own machine from itself π«Ά
π Authors π
Josh Bressers, John R. Daily, and G. Branden Robinson developed the current implementation of Discover for Progeny Linux Systems. absolute legends, we stan π
the Linux implementation of the system-dependent interfaces is derived from detect, by MandrakeSoft SA. giving credit where credit is due, periodt π
π See Also π
ok that's the whole page bestie, go forth and configure responsibly π β¨
discover.conf(5) β filed under the File Formats Manual, dated discover.conf(5) at the bottom of the page π mwah, thanks for reading, ily, bye π«Άπ
π¦ where this page comes from
- debian bookworm: libdiscover2 2.1.2-10
- debian trixie: libdiscover2 2.1.2-10.1
- ubuntu jammy: libdiscover2 2.1.2-10
- ubuntu noble: libdiscover2 2.1.2-10build1
- ubuntu questing: libdiscover2 2.1.2-10.1
- ubuntu resolute: libdiscover2 2.1.2-10.1build1
- ubuntu stonking: libdiscover2 2.1.2-10.1build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms