I'll be able to finally get around to doing this on the 2nd, sorry for the delay.
But just a quick overview of the code in my sight I do see it DTRT. -- Jason Hellenthal Voice: 95.30.17.6/616 JJH48-ARIN > On Jan 1, 2014, at 1:26, "Teske, Devin" <[email protected]> wrote: > > >> On Dec 31, 2013, at 10:14 PM, Jason Hellenthal wrote: >> >> >> >>>> On Dec 31, 2013, at 23:20, Darren Pilgrim <[email protected]> >>>> wrote: >>>> >>>> On 12/27/2013 9:53 PM, [email protected] wrote: >>>> Looking at _alias'N' sequentialy feels like a neucense. >>> >>> It is. It's also very easy to overlook a gap and have the system break on >>> a reboot. I thought ipv4_addrs_* was a good solution. >> >> Ipv4_addrs var while nice can get very lengthy very quick and then more >> prone to humanized errors. If you add ipv6 in there it grows horizontally >> tenfold. >> >> There just isn't an easy way around this unless we were to for say . . . >> /etc/ifconfig_ipv4 >> /etc/ifconfig_ipv6 >> >> And then read in the lines one by one as . . . >> $INTERFACE $ADDR $OPTS >> >> >> Personally I like the way Debian handles this but I really only see a need >> for handling it the initial way I wrote about non-sequentially which puts it >> fairly close to how they do it. > > Which I bet my patch would implement it the way you want. > Any chance to get around to testing it yet? > -- > Devin > > _____________ > The information contained in this message is proprietary and/or confidential. > If you are not the intended recipient, please: (i) delete the message and all > copies; (ii) do not disclose, distribute or use the message in any manner; > and (iii) notify the sender immediately. In addition, please be aware that > any message addressed to our domain is subject to archiving and review by > persons other than the intended recipient. Thank you.
smime.p7s
Description: S/MIME cryptographic signature
