public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Thrailkill <xwred1@xwredwing.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] IPv6 support in network initscripts
Date: Sun, 1 Jun 2003 00:50:23 -0700	[thread overview]
Message-ID: <20030601005023.07cb48c5.xwred1@xwredwing.net> (raw)
In-Reply-To: <20030531231311.027ad8ad.seemant@gentoo.org>

I was thinking about that earlier and figured it must not do anything if Peter is working on ipv6 init scripts.

Another subject though... why are only a handful of random things in /etc/rc.conf?  Why not do most all init-script configuration there like under the bsds?  Why have it at all if its just a handful of random settings that could have been parted out to other things in conf.d?

On Sat, 31 May 2003 23:13:11 -0700
Seemant Kulleen <seemant@gentoo.org> wrote:

> there's something which occurs to me -- in /etc/rc.conf there is a way to specify which protocols you allow.  Do our net scripts already have ipv6 support, I wonder? or is that stuff in rc.conf for some other purpose?
> 
> 
> -- 
> Seemant Kulleen
> Developer and Project Co-ordinator,
> Gentoo Linux					http://www.gentoo.org/~seemant
> 
> Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
> Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E
> 


-- 

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-01  8:00 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 [this message]
2003-06-01 12:49     ` Peter Johanson
2003-06-01 19:52       ` Matt Thrailkill
2003-06-07  4:27         ` Gontran Zepeda
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=20030601005023.07cb48c5.xwred1@xwredwing.net \
    --to=xwred1@xwredwing.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