All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Razza" <rjames31@btopenworld.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: udev problem DVB-S/T Cards
Date: Wed, 02 May 2007 12:10:31 +0000	[thread overview]
Message-ID: <000301c78cb2$e2455390$a6cffab0$@com> (raw)
In-Reply-To: <000301c78982$db8615e0$929241a0$@com>

Bryan Kadzban wrote on 02 May 2007 12:08:
> Razza wrote:
> > I am specifically interested in what 'K' is at various points in this
> > rule -
> >
> >
> > BUS="pci", ID="0000:01:06.0", SYSFS{device}="0x7146",
> > SYSFS{vendor}="0x1131", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb};
> > printf dvb/adapter5/%%s $${K%%%%.*} $${K#*.}'", NAME="%c",
> MODE="0660"
> 
> Well, it starts out at %k (the kernel NAME, which should be available
> via udevinfo).  After that, you should be able to set K=<that name> in
> a normal shell, and then start running subsequent commands from the
> shell, while echoing $K from time to time.
> 
> (However, note that udev requires double dollar signs and double
> percent signs, so if you paste the various echos and printfs into a
> shell, you'll have to un-escape those characters.  I.e., %%s should be
> run through the shell as %s, and %%%% should be turned into %%.)
> 
> And actually, K only changes once (when it's set to ${K#dvb} just
> before the printf.  The rest of that rule is just formatting the
> output.
> 
> (Oh, and you hopefully already know this from the documentation, but
> NAME="%c" sets NAME to the output of the PROGRAM.)
Ah!
So a udevinfo yields kernels names such as - KERNEL="dvb1.frontend0"
So I guess I need to change the K=$${K#dvb} element to only return the
correct nodes so I end up with a correctly formatted tree?


-------------------------------------------------------------------------
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

  parent reply	other threads:[~2007-05-02 12:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 10:49 udev problem DVB-S/T Cards Razza
2007-05-02  8:47 ` Razza
2007-05-02 11:08 ` Bryan Kadzban
2007-05-02 12:10 ` Razza [this message]
2007-05-02 12:36 ` Matthias Schwarzott
2007-05-02 13:31 ` Matthias Schwarzott
2007-05-02 21:38 ` Razza
2007-05-02 22:20 ` Bryan Kadzban
2007-05-02 23:48 ` Razza
2007-05-03  1:56 ` Bryan Kadzban
2007-05-03  9:10 ` Razza
2007-05-03 11:12 ` Bryan Kadzban
2007-05-03 11:54 ` Razza
2007-05-03 12:13 ` Matthias Schwarzott
2007-05-07 17:18 ` Razza
2007-05-09 17:49 ` Razza
2007-05-30 10:35 ` Razza
2007-07-12  9:05 ` Razza

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='000301c78cb2$e2455390$a6cffab0$@com' \
    --to=rjames31@btopenworld.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.