mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Shouldn't /etc/init.d/udev call udevadm trigger with --action=all ?
Date: Wed, 24 Aug 2016 16:52:44 +0200	[thread overview]
Message-ID: <CABDcavY62CkSe7qvE4ve52d6ROTJcjTNYL4KvSH5_XNfWk1kxA@mail.gmail.com> (raw)

Hello all,

I was just playing with some udev rules for automounting USB drives,
and noticed that the rules were working fine when the USB drive was
hot plugged, but not when it was already plugged at boot time.

After some investigation I found that the reason: At boot time, the
default udev init script in ptxdist (from projectroot/etc/init.d/udev)
calls udevadm trigger in order to "coldplug" devices that have already
been discovered by the time the udev daemon is started. However
udevadm trigger is called without arguments, which is equivalent to
--action=change. Thus udev rules for the "add" action are not
triggered.

Shouldn't this be changed to udevadm trigger --action=add ? I believe
most Linux distributions out there are using --action=add in their
udev init scripts.

Best,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2016-08-24 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 14:52 Guillermo Rodriguez Garcia [this message]
2016-08-25 11:42 ` Michael Olbrich
2016-08-25 13:27   ` [ptxdist] [PATCH] udev init script should pass --action=add to udevadm trigger Guillermo Rodriguez
2016-08-25 13:30   ` [ptxdist] Shouldn't /etc/init.d/udev call udevadm trigger with --action=all ? Guillermo Rodriguez Garcia

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=CABDcavY62CkSe7qvE4ve52d6ROTJcjTNYL4KvSH5_XNfWk1kxA@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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