From owner-freebsd-rc@FreeBSD.ORG Mon Feb 6 02:01:01 2012 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B74F7106564A for ; Mon, 6 Feb 2012 02:01:01 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.13.206.130]) by mx1.freebsd.org (Postfix) with ESMTP id E25318FC0C for ; Mon, 6 Feb 2012 02:01:00 +0000 (UTC) Received: (qmail 77625 invoked from network); 6 Feb 2012 02:04:43 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with CAMELLIA256-SHA encrypted SMTP; 6 Feb 2012 02:04:43 -0000 Message-ID: <4F2F3459.3090401@erdgeist.org> Date: Mon, 06 Feb 2012 03:00:57 +0100 From: Dirk Engling User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Hiroki Sato References: <4F28B9D7.4010602@erdgeist.org> <4F2F209F.90309@erdgeist.org> <20120206.101800.1389796154758679137.hrs@allbsd.org> In-Reply-To: <20120206.101800.1389796154758679137.hrs@allbsd.org> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-rc@FreeBSD.org Subject: Re: Proposal ipv6_addrs_common X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2012 02:01:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06.02.12 02:18, Hiroki Sato wrote: > I also looked into an ipv6 counterpart of the ipv4_addrs_common, > and your patch looks good, but I am a bit concerned about adding > another independent knob to configure IPv6 addresses to rc.conf. I > feel this range specification can be integrated into > ifconfig_IF_aliasN and it will be simpler than adding another knob. > What do you think about it? Personally I do not like the fragile way of enumerating variables with the aliasN functions at all. It clutters the rc.conf with gazillion lines of config code, you always have to renumber the whole list when adding or removing one. It also broke and locked me out of my system in the past when I was just commenting out one IP address up in the address list, other users of systems with a lot of jails - and thus a lot of IP addresses - reported the same. The ipv4_addrs_common patch was a relief back then. But now v6 addresses start becoming common, so my configs fill up again. Since ipv6_addrs_common and ipv4_addrs_common share some code, especially handling v6 mapped v4 addresses, I could imagine just having one variable providing both v6 and v4 addresses and have an ip_addrs_common figure out which are which. There's other code in the rc system that uses the same enumeration scheme - the jail script and its _exec_afterstartN variables. My plans for the near future are proposing a new way of managing your jails, avoiding these error prone constructions. Regards and that you for your feedback, erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAk8vNFkACgkQuN1wFypsMNPrHQCeIDMIHeLVTbfR9MsSRpVjXOtc FnMAn3nB7053Rlt9G0GDbBiH6tO7fTQi =C0fE -----END PGP SIGNATURE-----