Date: Wed, 4 Sep 2013 09:49:43 +0200 From: Moritz Wilhelmy <moritz@wzff.de> To: freebsd-doc@FreeBSD.org, jhb@FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org, hrs@FreeBSD.org Subject: Re: docs/162354: Improve wording in rc.conf(5) regarding network-interfaces. Message-ID: <20130904074943.GA15730@barfooze.de> In-Reply-To: <20130904.132235.1295886508382839266.hrs@allbsd.org> References: <201111071709.pA7H9afH025856@phallus.wzff.de> <201309031426.34775.jhb@freebsd.org> <20130904.132235.1295886508382839266.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 04, 2013 at 13:22:35 +0900, Hiroki Sato wrote: > John Baldwin <jhb@freebsd.org> wrote > in <201309031426.34775.jhb@freebsd.org>: > jh> I don't think ifconfig_IF_aliasN is depreated, though you can now use > jh> ifconfig_IF_aliases as an alternate. Also, both ifconfig_IF_aliases > jh> and ifconfig_IF_aliasN handle both IPv4 and IPv6. See this commit for more > jh> details: > jh> > jh> http://svnweb.freebsd.org/base?view=revision&revision=252015 Thanks. Having both IPv6 and IPv4 in the same place with the ability to just configure an entire subnet sounds like a sane decision. > The sentence "Due to this difficult to manage behavior, the > ifconfig_IF_aliasN form is deprecated." was added back in 2005, when > ipv4_addrs_IF was added. I guess it was considered that > ipv4_addrs_IF was the replacement of ifconfig_IF_aliasN. > > I refactored it in a AF-independent manner and used > ifconfig_IF_aliases as the successor, but I did not change that part > in rc.conf(5) manual page. I think we can think both > ifconfig_IF_aliasN and ifconfig_IF_aliases are currently supported. > There is no immediate plan to remove ifconfig_IF_aliasN, at least. > > Is it reasonable to remove the sentence? I think it is. Thank you! I see the changes are already in 9.2 so I'm happy for now :) Moritz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130904074943.GA15730>