linux-hotplug.vger.kernel.org archive mirror
 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: Thu, 03 May 2007 11:54:29 +0000	[thread overview]
Message-ID: <000701c78d79$cef3c570$6cdb5050$@com> (raw)
In-Reply-To: <000301c78982$db8615e0$929241a0$@com>

Bryan Kadzban wrote on 03 May 2007 12:13:
> Razza wrote:
> > I have located path_id which is in /sbin on Fedora core 5
> Hmm; it should be in /lib/udev AFAIK.  But maybe this doesn't matter.
Wouldn't be the first time something is in a completely different place in
Fedora!

> > there are some pretty long case statements in there (one I counted had
47 lines!),
> Yeah, it's complicated.  But I don't think we can do much about that...
:o) Agree - The user (me) needs to get more intelligent!

----------8< snip! >8----------

> That should be the right case, but that doesn't look like the current
> version of the script.  The script from udev-110 looks like this:
> 
> case "$TYPE" in
>     block)
>         handle_device
>         echo "ID_PATH=$d"
>         ;;
>     scsi_tape)
>         handle_device
>         echo "ID_PATH=$d"
>         ;;
>     input)
>         handle_device
>         echo "ID_PATH=$d"
>         ;;
>     *)
>         RESULT=1
>         ;;
> esac
> 
> And then it's followed by:
> 
> exit $RESULT
> 
> But I don't think it's safe to modify the script that you have unless
> it has a case that matches this layout (because the script you have is
> quite different from mine, so I don't think my modifications are valid
> for your system).  Is it possible to get an updated udev?  I know that
> the path_id script from udev-105 should work with the changes I posted
> last night, and I know -110 should too, so I assume anything between
> those two should also work.

Interestingly also in the commented out section of path_id it states (and
remember this is Fedora 5) :
# Copyright (C) 2005 SUSE Linux Products GmbH
# Author: Hannes Reinecke <hare@suse.de>

> (But use a distro version of udev, not the sources.  The sources will
> put the path_id script in /lib/udev, and it sounds like your distro
> already has that script somewhere else.  There will probably be other
> issues too.)

----------8< snip! >8----------

I have looked at the (rpm) version of udev, running my system:
udev-084-13.fc5.2.i386
Which appears to be the latest, see -
http://rpmfind.net/linux/rpm2html/search.php?query=udev-persistent
The build date is "Build date: Wed Aug 16 17:19:57 2006" - could try forcing
the FC6 or 7 rpm's? 


-------------------------------------------------------------------------
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-03 11:54 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
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 [this message]
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='000701c78d79$cef3c570$6cdb5050$@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 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).