From: Robert Love <rml@ximian.com>
To: linux-hotplug@vger.kernel.org
Subject: automatic init.d script installation
Date: Tue, 02 Mar 2004 00:10:31 +0000 [thread overview]
Message-ID: <1078186231.10733.36.camel@localhost> (raw)
Looking at this TODO item:
- install the proper init.d script based on the distro we are
running on.
We can do this with something like:
if [ -f /etc/redhat-release ]; then
install redhat init script to redhat spot
elif [ -f /etc/SuSE-release ]; then
install LSB init script to suse spot
elif [ -f ... ]; then
...
fi
Is that cool? Such hard coding is not really my cup of tea, but it is a
Makefile and there is not much better way to do it. We have similar
logic in the D-BUS configure script and Makefile.
If it is cool, maybe Kay can swoop in and do it for me (KIDDING, KAY!
YOU ROCK!) ;-)
Robert Love
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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 reply other threads:[~2004-03-02 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 0:10 Robert Love [this message]
2004-03-02 0:22 ` automatic init.d script installation Kay Sievers
2004-03-02 0:23 ` Marco d'Itri
2004-03-02 0:24 ` Robert Love
2004-03-02 0:33 ` Kay Sievers
2004-03-02 0:37 ` Marco d'Itri
2004-03-02 0:38 ` Marco d'Itri
2004-03-02 0:45 ` Richard Troth
2004-03-02 0:47 ` Richard Troth
2004-03-02 0:54 ` Robert Love
2004-03-02 1:34 ` Greg KH
2004-03-02 1:35 ` Greg KH
2004-03-02 14:58 ` Richard Troth
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=1078186231.10733.36.camel@localhost \
--to=rml@ximian.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).