Dan Nicholson wrote: > Randy just reverted the update to pciutils-2.2.4 because it can > potentially break HAL. The reason is that when zlib support is built > into pciutils, it will prefer using pci.ids.gz in both the library and > update script. However, HAL simply tries to open pci.ids and will bomb > if it doesn't find it. I think we might be able to find some middle > ground here to allow the update in and not have it break HAL or > anything else that's just trying to access pci.ids. > > 1. As Randy suggested, add a note about unzipping pci.ids if you're using HAL. > > 2. Disable the zlib support with `make ZLIB=no' in pciutils. > > 3. Patch the update-pciids script so that you can enable/disable > compressing the updated data. > > The details are that with zlib support, the code in libpci looks for > the most recent pci.ids.gz and falls back to the most recent pci.ids > if none is found. HAL, on the other hand, just looks for pci.ids where > you said it would be at build time and does the standard file opening > calls to read it. I think hald will quit if it can't find the file. > > Any other ideas? What do you guys think?
Well since update-pciids is a script, we could just modify that to unpack the pci.ids file. The difference between the compressed data and the uncompressed is about 330K. That's not much saving on a modern system unless it is some kind of embedded device. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
