From: Greg <softcode@telus.net>
To: linux-hotplug@vger.kernel.org
Subject: udev syntax and features
Date: Wed, 17 Oct 2018 20:06:35 +0000 [thread overview]
Message-ID: <04a28467-5e2d-238f-8812-29ba4f34311c@telus.net> (raw)
Hello all.
I have a few questions about udev.
I have tried the net for several hours/days, but much of the udev
documentation out there is over 5 years old and I have had no lucuck
with the following questions:
Udev. Q1. is it case sensitive? i.e. is kernel="sd?*" allowed as a
synonym for KERNEL="sd?*"
Udev Q2. What does UDEV define as a "long running process"? Are there
some docs or a udevadm cmd that will report udev compile time options? A
config file that specs that? a systemd unit file that specs that?
Udev. Q3. Would a command like: systemctl set-environment GKH="Gregory
the Great" qualify as long running? (it takes about 0.132 secs)
Udev Q4. Could ANY list variable that can be modded with += have TWO (or
more) new terms added to it?
such as say SYMLINK+="/media/%k","/mnt/%k" ?
Udev Q5. Similar to the above I would like to have
RUN+="/path/to/Somecmd %k %n","/path/to/Someothercmd $foo" in some rule.
is that OK?
Udev. Q6. Is RUN guaranteed to be last? so that PROGRAM will set the var
RESULT before RUN starts its stuff?
Udev. Q7. At what point does SYSTEMD_WANTS take effect? How would I
ensure that say my PROGRAM had set RESULT before
the SYSTEMD_WANTS magic happened?
Udev. Q8. IMPORT and RUN and PROGRAM all have a "type" option one of
which is "builtin" which refers to bultin cmds.
where do I get a list of such builtins? there is nothing in man udev.
Thank you.
Greg Morse
--
Sent from My Linux Mint Desktop
next reply other threads:[~2018-10-17 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 20:06 Greg [this message]
2018-10-19 4:27 ` udev syntax and features Andrei Borzenkov
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=04a28467-5e2d-238f-8812-29ba4f34311c@telus.net \
--to=softcode@telus.net \
--cc=linux-hotplug@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 read-only IMAP folder(s) and NNTP newsgroup(s).