<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX Processors中的主题 Risks to removing udev-hwdb</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1414571#M187070</link>
    <description>&lt;P&gt;I have generated an image and have enabled build history. One interesting file I get from this is the installed-package-sizes.txt. It lists all packages installed along with their size in KiB. By far the largest is udev-hwdb.&lt;/P&gt;&lt;P&gt;This can easily be removed by adding&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;BAD_RECOMMENDATIONS += "udev-hwdb"&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to a bb file.&lt;/P&gt;&lt;P&gt;What are the risks to removing this package? This question was asked in a &lt;A href="https://community.nxp.com/t5/i-MX-Processors/How-disable-hwdb-files-in-Yocto/m-p/1015278" target="_self"&gt;previous question&lt;/A&gt; after an answer to the initial question was found.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 16 Feb 2022 16:12:12 GMT</pubDate>
    <dc:creator>MichaelBMiner</dc:creator>
    <dc:date>2022-02-16T16:12:12Z</dc:date>
    <item>
      <title>Risks to removing udev-hwdb</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1414571#M187070</link>
      <description>&lt;P&gt;I have generated an image and have enabled build history. One interesting file I get from this is the installed-package-sizes.txt. It lists all packages installed along with their size in KiB. By far the largest is udev-hwdb.&lt;/P&gt;&lt;P&gt;This can easily be removed by adding&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;BAD_RECOMMENDATIONS += "udev-hwdb"&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to a bb file.&lt;/P&gt;&lt;P&gt;What are the risks to removing this package? This question was asked in a &lt;A href="https://community.nxp.com/t5/i-MX-Processors/How-disable-hwdb-files-in-Yocto/m-p/1015278" target="_self"&gt;previous question&lt;/A&gt; after an answer to the initial question was found.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 16:12:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1414571#M187070</guid>
      <dc:creator>MichaelBMiner</dc:creator>
      <dc:date>2022-02-16T16:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: Risks to removing udev-hwdb</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1414994#M187098</link>
      <description>&lt;P&gt;HWDB is a database of devices for udev diagnostic output.&lt;BR /&gt;So I suppose everything should be running fine after udev-hwdb removing except the diagnostic may become unclearю&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 05:59:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1414994#M187098</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2022-02-17T05:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Risks to removing udev-hwdb</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1415470#M187148</link>
      <description>&lt;P&gt;Would I still be able to insert a USB device and have it enumerate? If I understand correctly the answer is yes, but if there was an error I could not easily find out why.&lt;/P&gt;&lt;P&gt;Is there a way to trim the udev-hwdb so it does not take so much space in my image?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 16:49:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Risks-to-removing-udev-hwdb/m-p/1415470#M187148</guid>
      <dc:creator>MichaelBMiner</dc:creator>
      <dc:date>2022-02-17T16:49:51Z</dc:date>
    </item>
  </channel>
</rss>

