Yes and these functionalities make the config very versatile at a minimal cost to the language they are written in. I would gladly volunteer the time to do it but I'm heavily stretched right now.
Duplicate the _name functionality and rename to description ? And tie her down... -- Jason Hellenthal JJH48-ARIN On Jul 28, 2015, at 15:16, Ryan Stone <ryst...@gmail.com> wrote: > On Jul 28, 2015 11:07 AM, "Sergey Kandaurov" <pluk...@freebsd.org> wrote: > > On 28 July 2015 at 20:55, Alexander V. Chernikov <melif...@freebsd.org> wrote: >> 28.07.2015, 15:32, "Arseny Nasokin" <eir...@gmail.com>: >> >> Separate ifconfig_IF_description will be simpler to use. >> >> I was also insisting on this.. >> +pluknet@ >> Sergey, maybe we could reconsider this stuff and add separate _description >> field? > > No, thanks. > > That means that we should also build up ifconfig_IF_group, > ifconfig_IF_name and suchalikes for parity. > I wouldn't object strongly though if someone will come up with a patch. > > -- > wbr, > pluknet > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" Doesn't ifconfig_*_name already exist? _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
