From mboxrd@z Thu Jan 1 00:00:00 1970 From: Piotr Karbowski Date: Fri, 02 Mar 2012 00:46:44 +0000 Subject: Re: udev and existing /dev (devtmpfs) Message-Id: <4F501874.1000503@gmail.com> List-Id: References: <4F15CB13.1000703@gmail.com> In-Reply-To: <4F15CB13.1000703@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On 01/23/2012 06:00 PM, Kay Sievers wrote: > On Mon, Jan 23, 2012 at 17:41, Gabor Z. Papp wrote: > > It was always 'add' which was suggested. It was the default action, > but it was changed to 'change' because 'add' must not be used anywhere > else than once after bootup. > > Triggering 'change' has some valid use cases, not many though, and > most of them are workarounds for broken things. > > Settle is only needed to block until broken subsystems catch up with > reality during bootup, and with reality how hotplug systems work > today. It is not pulled-in for systems which do not run broken or > legacy tools. > o > > Yes, that changed May 2010 with udev 154. I just upgraded to udev-181 and the issue still is there. I believe the=20 /dev/mapper/ nodes are created by kernel's devtmpfs but the /dev/dm-*=20 are created by cryptsetup and lvm running in initramfs where is no udev=20 running. Even if I umount devtmpfs on initramfs level and let udev mount=20 it again, the changes will be still there. (I do mount --move to=20 /newroot/dev). Maybe the 'action=ADd' should care about already-created=20 nodes as well? -- Piotr.