Re: What populates /proc/partitions ?

It has something to do with devtmpfs that causes it. If I could set this GENHD_FL_HIDDEN flag on it, it would solve the problem on those system that say the have a floppy but doesn't really exist.Is something built-in to allow that or it's up to the driver itself? On Mon, Sep 30, 2019 at

Re: What populates /proc/partitions ?

Well, it's not straightforward. No direct calls, it must be somehow when kmod is used to load the module. The only difference I see in the udevadm output is the old system has attribute differences capability new==11, old==1, event_poll_msec new=2000, old=-1. I figured if i could set the

Re: What populates /proc/partitions ?

Thanks for the replies. I'll see if I can figure this out. I know with the same kernel and older udev version in use that it didn't add it, but with the new udev (eudev) it does (one big difference is the new one requires and uses devtmpfs and the old one didn't). I tried making the floppy a

Re: What populates /proc/partitions ?

On 9/30/19 3:47 PM, David F. wrote: > Hi, > > I want to find out why fd0 is being added to /proc/partitions and stop > that for my build. I've searched "/proc/partitions" and "partitions", > not finding anything that matters. /proc/partitions is produced on demand by causing a read of it. That

Re: What populates /proc/partitions ?

On Mon, Sep 30, 2019 at 03:47:21PM -0700, David F. wrote: > Hi, > > I want to find out why fd0 is being added to /proc/partitions and stop > that for my build. I've searched "/proc/partitions" and "partitions", > not finding anything that matters. It looks like it is done in block/genhd.c with

What populates /proc/partitions ?

Hi, I want to find out why fd0 is being added to /proc/partitions and stop that for my build. I've searched "/proc/partitions" and "partitions", not finding anything that matters. If udev is doing it, what function is it call so I can search on that? TIA!!