partitions?

Asked Sep 30 '19 at 00:47

Active Sep 30 '19 at 02:27

Viewed 138 times

I'm updating udev to eudev, the issue I am having is now fd0 shows in /proc/partitions which causes hang delays by things that process items from that file.

I would imagine it's some "rule" but I have no clue what the rules actually do. For instance, udisks2 rules sets some environment variable ID_DRIVE_FLOPPY to 1 via KERNEL==”fd*”, ENV{ID_DRIVE_FLOPPY}=”1″ but what they heck does that do? I look for anything using an environment variable named ID_DRIVE_FLOPPY and find nothing, even in the udev source. If I set that to "0", fd0 still shows up in /proc/partitions.

Any idea on what to do? I still would like /dev/fd0 to work if manually mounted, but don't want it showing in /proc/partitions (used by fdisk -l, mdadm xxx --scan, and others). That's how the old udev 175 I was using was doing it, now using udev 228.

edited Sep 30 '19 at 02:27

Jeff Schaller

66,199
35
114
250

asked Sep 30 '19 at 00:47

user3161924

Are you comparing udev 175 and 228 on the same kernel? Could you clarify what eudev has to do with your question? – Stephen Kitt Sep 30 '19 at 05:05
same kernel. Just different udev. /proc/partitions is only populated after the `udevadm trigger` call. Just that the version used is eudev, doesn't rely on systemd. – user3161924 Sep 30 '19 at 06:26
1

Which [release of `eudev`](https://github.com/gentoo/eudev/releases) are you using? 228 is a `udev` release, not `eudev`. – Stephen Kitt Sep 30 '19 at 06:43
It's 3.2.8 but it still prints out 228. – user3161924 Sep 30 '19 at 23:06

How to prevent udev from adding fd0 to /proc/partitions?

0 Answers0