On Tue, Aug 25, 2009 at 13:58, Scott James Remnant<scott@xxxxxxxxxxxxx> wrote: > On Tue, 2009-08-25 at 13:32 +0200, Florian Zumbiehl wrote: > >> > reading some of the source of udev, I noticed what I would suspect to be a >> [...] >> >> could someone possibly explain to me why there is that special codepath >> for cases where the device node does already exist, so I can write a >> patch that's not gonna break other functionality? >> > For example, when using devtmpfs; in which case the device nodes already > exist. > > Or when updating devices like /dev/null which are created before udevd > is started by the init script when not using devtmpfs. > > Or when racing with devmapper which creates /dev/mapper/foo devices at > basically the same time as udev. Or having events not reset already applied ACLs by setting mode/perms. Or not changing the inode number of the node, and confuse some tools for no good reason. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
