From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: fxload and udev 079
Date: Sun, 22 Jan 2006 15:28:11 +0000 [thread overview]
Message-ID: <200601221828.12301.arvidjaar@mail.ru> (raw)
In-Reply-To: <BAY113-F8F89AD70161124AF75CADAA250@phx.gbl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 22 January 2006 18:08, Robert Kennedy wrote:
> But with udev, should I use these directories? Or should I place the
> script and the firmware somewhere in /lib/udev?
>
You can use absolute pathname and have excutable anywhere; relative pathname
is now assumed to be in /lib/udev, right. FW may be anywhere your script
looks for it. I would use /etc/backpack or whatever.
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD06SMR6LMutpd94wRAmV6AJ9go2gRsW3NcgqHBt2QCUFMOwzhKQCeNzte
ft7eOnlmjglFMbHegmSm67Q=mXXh
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-01-22 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 15:09 fxload and udev 079 Robert Kennedy
2006-01-10 15:18 ` Moshe Yudkowsky
2006-01-10 15:20 ` Marco d'Itri
2006-01-22 15:08 ` Robert Kennedy
2006-01-22 15:28 ` Andrey Borzenkov [this message]
2006-01-22 16:07 ` Robert Kennedy
2006-01-22 22:00 ` Greg KH
2006-01-22 23:30 ` Robert Kennedy
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=200601221828.12301.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).