From: "Marco d'Itri" <md@Linux.IT>
To: linux-hotplug@vger.kernel.org
Subject: Re: Location of firmware files
Date: Thu, 20 May 2004 17:25:36 +0000 [thread overview]
Message-ID: <20040520172536.GA9891@wonderland.linux.it> (raw)
In-Reply-To: <40ACDCE3.5040500@us.ibm.com>
On May 20, Marcel Holtmann <marcel@holtmann.org> wrote:
> I won't vote for checking two places. Let's see what the LSB says and
> choose the best place.
Why not? If a firmware file is needed at boot time before /usr is
available then it has to go in /lib, else it has to go in /usr/share.
It's not like using test -e is hard...
> Btw I don't think that we need a subdirectory
> called "hotplug" in the path.
Good point.
--
ciao, |
Marco | [6382 scHvMf/nwXQTM]
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
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:[~2004-05-20 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 16:29 Location of firmware files Brian King
2004-05-20 16:53 ` Marco d'Itri
2004-05-20 17:19 ` Marcel Holtmann
2004-05-20 17:25 ` Marco d'Itri [this message]
2004-05-20 18:16 ` Marcel Holtmann
2004-06-22 20:50 ` Brian King
2004-06-22 21:17 ` Marco d'Itri
2004-06-22 21:36 ` Marcel Holtmann
2004-06-22 21:51 ` Brian King
2004-06-22 22:02 ` Marcel Holtmann
2004-06-22 22:27 ` Brian King
2004-06-22 22:37 ` Marcel Holtmann
2004-06-22 23:09 ` Greg KH
2004-06-23 8:14 ` Marcel Holtmann
2004-09-20 21:23 ` Greg KH
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=20040520172536.GA9891@wonderland.linux.it \
--to=md@linux.it \
--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).