Re: [atomic-devel] nominate pciutils for inclusion in base atomic tree

[Jeremy Eder <jeder redhat com>]

----- Original Message -----
> From: "Colin Walters" <walters verbum org>
> To: atomic-devel projectatomic io
> Sent: Thursday, October 30, 2014 11:58:17 PM
> Subject: Re: [atomic-devel] nominate pciutils for inclusion in base atomic	tree
> 
> On Wed, Oct 29, 2014, at 11:50 AM, Jeremy Eder wrote:
> > lspci is useful for determining what hardware is installed in a system, and
> > what it's capabilities are.
> > Information such as if a device is installed in a slot with the most
> > performant bus width, model numbers, PCI ids.
> > 
> > Would it be possible to include the pciutils package in the atomic-host
> > base tree ?
> 
> It is pretty small.  However, this also works:
> 
> docker run centos /bin/sh -c 'yum -y install pciutils; lspci'

Yeah, right now our debug container pulls all this stuff in.  I still have to re-orient my thinking because even these low-level utils aren't _truly_ required in the atomic base image.

> Which actually gets into an interesting topic; right now with containers we
> expose most of the host's /proc - pid namespacing aside, you get pretty much
> everything else, just read-only for most of it.  So containers see the
> host's hardware listing, though they still have a filtered /dev by default.

Yes, we ran into performance problems before /proc was exposed ;)