On Wed, 2012-03-21 at 09:11 -0700, Adam Williamson wrote:
> On Wed, 2012-03-21 at 09:02 -0700, Phil Dibowitz wrote:
> > On 03/21/2012 08:30 AM, Adam Williamson wrote:
> > > On Wed, 2012-03-21 at 09:23 -0400, Scott Talbert wrote:
> > >> On Tue, 20 Mar 2012, Phil Dibowitz wrote:
> > >>
> > >>> + $(install_sh_DATA) start_concordance_dhcpd.sh \
> > >>> + $(DESTDIR)$(sysconfdir)/udev/
> > >>> + $(install_sh_DATA) start_concordance_dhcpd_wrapper.sh \
> > >>> + $(DESTDIR)$(sysconfdir)/udev/
> > >>>
> > >>> These shouldn't go in /etc/udev - they're executable scripts. These
> > >>> should go
> > >>> in $sbindir. You'll of course need to update the udev rule itself as
> > >>> well when
> > >>> you move these.
> > >>
> > >> The reason for putting these in $(sysconfdir)/udev was so that udev
> > >> could
> > >> find them without having to hard-code the path to them. This directory
> > >> seems to be the place where udev-related scripts get stored. If we move
> > >
> > > On my up-to-the-minute F17, where presumably stuff is in the location
> > > udev authors intend, such scripts seem to be in /usr/lib/udev (note:
> > > _not_ $libdir/udev - they're in /usr/lib/udev on 32-bit and 64-bit).
> >
> > Scott, good point.
> >
> > Adam, I think that's because Fedora has unified / and /usr... For me,
> > they're
> > in /lib/udev which should be true for a wider variety of users. And Fedora
> > should have a symlink from /lib to /usr/lib.
>
> Ah yeah, good catch. I just checked a pre-/usrmove machine and they are
> indeed in /lib/udev there.
>
> I definitely think sbindir is wrong, though, as they're not meant to be
> used interactively, they're helper scripts for a system component. /etc
> also seems wrong as they're not configuration. So /lib/udev seems like a
> good candidate to me. I think we had a big bikeshedding session about
> this on fedora-devel-list recently, where the use of /usr/libexec was
> universally excoriated as a fedora-ism but there was lots of exciting
> debate on where else this kind of thing should go.
udev man page states:
RUN
Add a program to the list of programs to be executed for a specific
device. This can only be used for very short running tasks. Running
an event process for a long period of time may block all further
events for this or a dependent device. Long running tasks need to
be immediately detached from the event process itself.
If no absolute path is given, the program is expected to live in
the directory provided at compile-time to configure via
--libexecdir (this is usually /lib/udev), otherwise the absolute
path must be specified. The program name and following arguments
are separated by spaces. Single quotes can be used to specify
arguments with spaces.
which supports /lib/udev.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
