| 1 |
On Tue, Jul 24, 2018 at 12:06 PM Michael Orlitzky <mjo@g.o> wrote: |
| 2 |
> |
| 3 |
> On 07/24/2018 11:39 AM, Mike Gilbert wrote: |
| 4 |
> > |
| 5 |
> > You can run any system without udev, but you need to be very careful |
| 6 |
> > about what Linux features you utilize and how you have the system |
| 7 |
> > configured. |
| 8 |
> > |
| 9 |
> > Most Linux servers out in the wild are running udev; your |
| 10 |
> > configuration is an exception to the common case. |
| 11 |
> > |
| 12 |
> |
| 13 |
> udev itself works fine with the flag off. |
| 14 |
|
| 15 |
udevd works, but other software will not work optimally. If you are |
| 16 |
running udevd, it's usually good idea to have other stuff integrate |
| 17 |
with it, generally to prevent race conditions as devices are |
| 18 |
enumerated. |
| 19 |
|
| 20 |
For example, dhcpcd integrates with udevd via libudev to ensure that |
| 21 |
udev has finished renaming your network interfaces before dhcpcd |
| 22 |
attempts to configure them. I believe lvm2 uses libudev to prevent |
| 23 |
various races in block device setup and metadata gathering. |
| 24 |
|
| 25 |
Developers don't add udev support just for the hell of it; they do it |
| 26 |
to make their software play nice with hardware when udevd is running. |
Archives