Date: Sun, 10 Oct 2010 10:23:04 -0700 From: Garrett Cooper <gcooper@FreeBSD.org> To: Sergey Kandaurov <pluknet@gmail.com> Cc: jhell <jhell@dataix.net>, Doug Barton <dougb@freebsd.org>, freebsd-rc@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: [RFC] ifconfig description support in rc.d Message-ID: <AANLkTimyHSkD=HVZKy4mXt9uMtCvTBZ687=2w-msx28h@mail.gmail.com> In-Reply-To: <AANLkTik77T2xjB2Gcmbh4z0EPu-%2BaQ1qwyKoQhGkHZPf@mail.gmail.com> References: <AANLkTinfOSQGnk0%2BPK6iM0=v5CZn2vcmJZbA8TvgGbfr@mail.gmail.com> <4C76CA06.5010001@FreeBSD.org> <AANLkTintgji3vzrb8XuUQHWp%2B7YDvHtd7ynP0MmV0oZr@mail.gmail.com> <4CB135F5.20804@DataIX.net> <AANLkTik77T2xjB2Gcmbh4z0EPu-%2BaQ1qwyKoQhGkHZPf@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 9, 2010 at 11:29 PM, Sergey Kandaurov <pluknet@gmail.com> wrote=
:
> On 10 October 2010 07:41, jhell <jhell@dataix.net> wrote:
>> On 08/27/2010 05:17, pluknet wrote:
>>> On 27 August 2010 00:09, Doug Barton <dougb@freebsd.org> wrote:
>>>> On 08/26/2010 12:53 PM, pluknet wrote:
>>>>>
>>>>> [cc'ing current@ as rc@ looks too quite]
>>>>>
>>>>> Hi.
>>>>>
>>>>> Since ifconfig has grown to label interfaces with
>>>>> ifconfig $ifname description "foobar", what about
>>>>> to give it more life and store i/face descriptions
>>>>> semi-permanently, so they will survive between reboots?
>>>>>
>>>>> This patch adds a functionality to rc.d to label
>>>>> interfaces at boot time.
>>>>>
>>>>> Comments are welcome.
>>>>
>>>> This seems like a good addition, thanks. Please also write a patch for
>>>> rc.conf.5 to describe this new functionality and I'll be happy to comm=
it it.
>>>
>>> Xin Li helped me with updating rc.conf.5 (thanks!).
>>> It's included in attached patch.
>>>
>>>> =A0One note below.
>>>>
>>>>
>>>>> --- etc/network.subr =A0 =A0(revision 211280)
>>>>> +++ etc/network.subr =A0 =A0(working copy)
>>>>> @@ -1187,6 +1187,24 @@
>>>>> =A0 =A0 =A0 =A0 return 0
>>>>> =A0}
>>>>>
>>>>> +# ifnet_descr
>>>>> +# =A0 =A0 =A0Add description to all requested interfaces.
>>>>> +#
>>>>> +ifnet_descr()
>>>>> +{
>>>>> + =A0 =A0 =A0 local _if _ifdescr
>>>>> +
>>>>> + =A0 =A0 =A0 # ifconfig_IF_descr
>>>>> + =A0 =A0 =A0 for _if in `ifconfig -l`; do
>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 _ifdescr=3D"`get_if_var $_if ifconfig_I=
F_descr`"
>>>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 if [ ! -z "$_ifdescr" ]; then
>>>>
>>>> This is probably better as [ -n "$_ifdescr" ]
>>>>
>>>
>>> This was blindly copy&pasted after ifnet_rename().
>>> So, it makes sense probably to change test expression there as well.
>>> [see ifnet_rename() proposed change below inline]
>>> This change to ifnet_rename() is not included in attached patch
>>> to not complicate things unnecessarily for now.
>>>
>>> Index: etc/network.subr
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> --- etc/network.subr =A0 =A0(revision 211280)
>>> +++ etc/network.subr =A0 =A0(working copy)
>>> @@ -1179,7 +1179,7 @@
>>> =A0 =A0 =A0 =A0 # ifconfig_IF_name
>>> =A0 =A0 =A0 =A0 for _if in `ifconfig -l`; do
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _ifname=3D`get_if_var $_if ifconfig_IF_=
name`
>>> - =A0 =A0 =A0 =A0 =A0 =A0 =A0 if [ ! -z "$_ifname" ]; then
>>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 if [ -n "$_ifname" ]; then
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ifconfig $_if name $_if=
name
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 fi
>>> =A0 =A0 =A0 =A0 done
>>
>> Was this ever committed ? If so does anyone have any referring svn
>> revisions ?
>>
>> Also if this is committed or planned to be committed is there a chance
>> it could be MFC'd ?
>>
>> Would be awesome if this was available on a production release without
>> patching ;)
>>
>
> Hi.
>
> I'm going to commit this after a proper review.
<offtopic>
I'm not sure it would get resolved after this commit, but one
minor annoyance is that restarting the netif rc.d script purges all
gateways set, so I have to do and restart the routing rc.d script (if
my connectivity doesn't get whacked). I think there was something else
with natd and ipfw that I've run into in the past where I've restarted
those scripts and things weren't all puppydogs and rainbows on my
CURRENT systems.
</offtopic>
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimyHSkD=HVZKy4mXt9uMtCvTBZ687=2w-msx28h>