From: Steven Scholz <steven.scholz@imc-berlin.de>
To: linux-ide@vger.kernel.org
Subject: hotplug event on fdisk?
Date: Tue, 12 Jul 2005 17:57:52 +0200 [thread overview]
Message-ID: <42D3E880.6060902@imc-berlin.de> (raw)
Hi,
I noticed that /sbin/hotplug is called by the kernel when I am doing
fdisk -l /dev/hda
to do a "remove" and then do "add" again:
~ # fdisk -l /dev/hda
kobject_hotplug
kobject_hotplug: /sbin/hotplug block seq=574 HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=remove DEVPATH=/block/hda/hda1
SUBSYSTEM=block
hda: hda1
kobject_hotplug
kobject_hotplug: /sbin/hotplug block seq=575 HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add DEVPATH=/block/hda/hda1
SUBSYSTEM=block
Disk /dev/hda: 512 MB, 512483328 bytes
16 heads, 63 sectors/track, 993 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 993 500440+ 6 FAT16
Why is it so? And what is the system suposed to do? Actually remove the device?
--
Steven
next reply other threads:[~2005-07-12 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 15:57 Steven Scholz [this message]
2005-07-16 17:24 ` hotplug event on fdisk? Sergey Vlasov
2005-07-18 6:49 ` Steven Scholz
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=42D3E880.6060902@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).