linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Matching something against an environment-variable
Date: Fri, 27 Apr 2007 11:39:04 +0000	[thread overview]
Message-ID: <200704271339.04976.zzam@gentoo.org> (raw)

Hi!

I just have noticed that comparisons like this are not possible with udev:

something=ENV{MY_VAR}
or
something="$env{MY_VAR}"

The reason I want to use that is: creating /dev/root without executing a 
program for every blockdev.

With some rule like this:
SUBSYSTEM="block", ATTR{dev}=ENV{ROOT_DEV_NR}, SYMLINK+="root"


with variable ROOT_DEV_NR be either set by 
A. SUBSYSTEM="block", IMPORT{file}+="/dev/.udev/root_dev_nr"
and that file is created by udev-startscript

B. injecting the env-var with
udevcontrol env ROOT_DEV_NR=$(get_root_dev)
after udevd has been started

I think the variant  something=ENV{MY_VAR} should not be too complicated to 
realize.

Matthias

-- 
Matthias Schwarzott (zzam)

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2007-04-27 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 11:39 Matthias Schwarzott [this message]
2007-04-30 13:43 ` Matching something against an environment-variable Kay Sievers
2007-04-30 14:06 ` Andrey Borzenkov
2007-04-30 14:09 ` Matthias Schwarzott

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=200704271339.04976.zzam@gentoo.org \
    --to=zzam@gentoo.org \
    --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 NNTP newsgroup(s).