From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: "Eric S. Raymond" <esr@thyrsus.com>,
Doug McNaught <doug@wireboard.com>,
linux-kernel@vger.kernel.org, greg@kroah.com,
felix-dietlibc@fefe.de
Subject: Re: initramfs programs (was [RFC] klibc requirements)
Date: Wed, 9 Jan 2002 23:07:04 +0100 [thread overview]
Message-ID: <20020109230704.A25786@devcon.net> (raw)
In-Reply-To: <200201092005.g09K5OL28043@snark.thyrsus.com> <m3n0zn6ysr.fsf@varsoon.denali.to> <20020109154425.A28755@thyrsus.com>
In-Reply-To: <20020109154425.A28755@thyrsus.com>; from esr@thyrsus.com on Wed, Jan 09, 2002 at 03:44:25PM -0500
On Wed, Jan 09, 2002 at 03:44:25PM -0500, Eric S. Raymond wrote:
>
> You're right, I don't need this to be done at kernel level. I do need it to
> be done *everywhere*. I'm not sure how else to guarantee this will happen.
Then add an init script and include installation of it to the
installation steps of your autoconfigurator (it has to be installed
anyway). If a distributor packages your program, he will include the
init script into his package and enable it according to his init
policy, or write an own init script, if your provided one doesn't
fit.
That's the way it works for network daemons etc. for years.
Andreas
--
Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
---------------------------------------------------------
+49 521 1365800 - af@devcon.net - www.devcon.net
next prev parent reply other threads:[~2002-01-09 22:07 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 20:05 initramfs programs (was [RFC] klibc requirements) Eric S. Raymond
2002-01-09 20:43 ` Doug McNaught
2002-01-09 20:44 ` Eric S. Raymond
2002-01-09 21:01 ` Doug McNaught
2002-01-09 22:07 ` Andreas Ferber [this message]
2002-01-09 21:56 ` Eric S. Raymond
2002-01-09 23:26 ` H. Peter Anvin
2002-01-09 23:30 ` Andreas Ferber
2002-01-12 5:31 ` Pavel Machek
2002-01-09 20:55 ` Patrick Mochel
2002-01-09 20:47 ` Eric S. Raymond
2002-01-09 22:41 ` Matthew Kirkwood
2002-01-09 22:46 ` Eric S. Raymond
2002-01-09 23:28 ` H. Peter Anvin
2002-01-10 0:21 ` Alan Cox
2002-01-10 11:21 ` Dave Jones
2002-01-09 23:29 ` Matthew Kirkwood
2002-01-09 23:29 ` Eric S. Raymond
2002-01-09 23:54 ` H. Peter Anvin
2002-01-10 10:35 ` Matthew Kirkwood
2002-01-12 5:36 ` Pavel Machek
2002-01-12 18:11 ` Oliver Xymoron
[not found] <fa.gs2ktfv.1r00h12@ifi.uio.no>
[not found] ` <fa.kj79fuv.1angmqd@ifi.uio.no>
2002-01-10 17:13 ` Giacomo Catenazzi
2002-01-10 17:28 ` Dave Jones
2002-01-10 17:32 ` H. Peter Anvin
2002-01-10 17:43 ` Dave Jones
2002-01-10 17:44 ` H. Peter Anvin
2002-01-10 17:47 ` Dave Jones
2002-01-10 17:37 ` Alan Cox
2002-01-10 17:27 ` H. Peter Anvin
[not found] <fa.d7rnnnv.1l1gnri@ifi.uio.no>
[not found] ` <fa.p5gg3pv.1iiscrg@ifi.uio.no>
2002-01-10 11:22 ` Giacomo Catenazzi
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 20:25 Torrey Hoffman
2002-01-10 0:02 ` Tom Rini
2002-01-09 17:54 Torrey Hoffman
2002-01-09 18:06 ` Tom Rini
2002-01-09 18:28 ` Greg KH
2002-01-09 18:49 ` Tom Rini
2002-01-08 19:24 [RFC] klibc requirements Greg KH
2002-01-09 4:23 ` Felix von Leitner
2002-01-09 4:34 ` initramfs programs (was [RFC] klibc requirements) Greg KH
2002-01-09 6:10 ` Greg KH
2002-01-09 7:23 ` H. Peter Anvin
2002-01-09 9:33 ` Kai Germaschewski
2002-01-09 10:00 ` Erik Andersen
2002-01-09 10:38 ` Anton Altaparmakov
2002-01-09 15:56 ` Pavel Machek
2002-01-09 16:04 ` Patrick Mochel
2002-01-09 16:26 ` Greg KH
2002-01-09 16:29 ` Pavel Machek
2002-01-09 16:48 ` Andreas Ferber
2002-01-09 21:15 ` Alex Bligh - linux-kernel
2002-01-09 21:34 ` Anton Altaparmakov
2002-01-09 21:40 ` Greg KH
2002-01-09 21:55 ` Anton Altaparmakov
2002-01-09 22:15 ` Andreas Ferber
2002-01-10 0:25 ` Tom Rini
2002-01-10 0:38 ` Andreas Ferber
2002-01-10 2:42 ` Tom Rini
2002-01-10 14:09 ` Rob Landley
2002-01-10 22:24 ` Tom Rini
2002-01-11 0:15 ` H. Peter Anvin
2002-01-09 22:12 ` Alex Bligh - linux-kernel
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=20020109230704.A25786@devcon.net \
--to=aferber@techfak.uni-bielefeld.de \
--cc=doug@wireboard.com \
--cc=esr@thyrsus.com \
--cc=felix-dietlibc@fefe.de \
--cc=greg@kroah.com \
--cc=linux-kernel@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