public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: linux-kernel@vger.kernel.org
Subject: block till hotplug is done?
Date: Tue, 05 Oct 2004 21:52:07 +0200	[thread overview]
Message-ID: <1097005927.4953.4.camel@simulacron> (raw)

Hi,

is there any way to block till all hotplug events are handled/
the hotplug processes terminated?

For example
	fdisk
	mkfs
fails, because after fdisk create a partition, and the kernel
reread the partition table, called hotplug, hotplug called udev
and udev created the matching /dev file, all of that might be
too slow and mkfs might fail in the mean time.

even
	fdisk
	sleep 2
	mkfs
sometimes failes with machines I'm installing.

so I can either randomly increase the delay everytime the installation
fails because the device isn't created in time, or I can create the
devices myself with mkdev, which defeats the whole purpose of hotplug
and udev. Or - preferable - I would want to wait till something
tells me the device is there. some way to sleep till not kernel
triggered hotlug process is running any more, that would be nice.
does the kernel keep track of it's hotplug processes? is there such
a way to wait till they are all done? 

(and would that work, if hotplug spawned some child process/daemon, i.e.
not wait for the daemon to end?)

Regards, Andreas


             reply	other threads:[~2004-10-05 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 19:52 Andreas Jellinghaus [this message]
2004-10-05 20:13 ` block till hotplug is done? Harald Dunkel
2004-10-05 20:38   ` Valdis.Kletnieks
2004-10-05 22:16     ` Jon Masters
2004-10-05 22:04   ` Andreas Jellinghaus
2004-10-06 14:19 ` Alexander E. Patrakov
2004-10-08 14:23 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1097005927.4953.4.camel@simulacron \
    --to=aj@dungeon.inka.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox