From: Gontran Zepeda <gontran@gontran.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] IPv6 support in network initscripts
Date: Sat, 7 Jun 2003 05:27:26 +0100 [thread overview]
Message-ID: <20030607042726.GF1593@rythm.gontran.net> (raw)
In-Reply-To: <20030601125213.50136a59.xwred1@xwredwing.net>
% On 2003-06-01 at 12:52:13 -0700, Matt Thrailkill wrote:
> On Sun, 1 Jun 2003 08:49:14 -0400
> Peter Johanson <latexer@gentoo.org> wrote:
>
> > I've never seen anything which actually sources rc.conf and uses the
> > PROTOCOL variable in any way. I have no idea why that's there. anybody
> > enlighten me?
>
> # Set protocols to the protocols that you plan to use. Gentoo Linux will
> # only enable module auto-loading for these protocols, eliminating annoying
> # module not found errors.
IIRC variables from rc.conf are made available in the environment of the
running init.d scripts by /sbin/runscipt. ${PROTOCOL} _was_ used in the
very early days to determine whether servers like xinetd were to be run
with ipv6 support. Support for this seems to have been deprecated along
with the system-wide use of daemontools, that good work and the original
ipv6 integration having been done by A. Gottinger.
It would be nicely consistent if you were to use this variable for
determining when to initialize ipv6 interfaces and services in the init
scripts, IMHO.
--
Gontran
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-09 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 3:29 [gentoo-dev] IPv6 support in network initscripts Peter Johanson
2003-06-01 5:07 ` Matt Thrailkill
2003-06-01 5:56 ` Robin H.Johnson
2003-06-01 6:13 ` Seemant Kulleen
2003-06-01 7:50 ` Matt Thrailkill
2003-06-01 12:49 ` Peter Johanson
2003-06-01 19:52 ` Matt Thrailkill
2003-06-07 4:27 ` Gontran Zepeda [this message]
2003-06-13 19:42 ` Martin Schlemmer
2003-06-01 7:37 ` Dan Armak
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=20030607042726.GF1593@rythm.gontran.net \
--to=gontran@gontran.net \
--cc=gentoo-dev@gentoo.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