On Mon, Nov 26, 2012 at 12:11 PM, Andres Perera <andre...@zoho.com> wrote:
> don't know about OP, but yesterday i was surprised when rtlabel had to
> be specified after inet
just double checked; s/after/before
ifconfig(8) section on rtlabel bears no mention about the order
before rearranging, lines were just C sorted:
cat hostname.ral0
inet 192.168.2/24
rtlabel egress
afterboot:
route -vn show -inet | awk '{$2="";print}' | column -t
...
Destination Flags Refs Use Mtu Prio Iface Label
default UGS 4 557 - 12 ral0
10.0.0/24 UC 1 0 - 4 re0
10.0.0.11 UHLc 3 1100 - 4 re0
127/8 UGRS 0 0 33152 8 lo0
127.0.0.1 UH 2 24 33152 4 lo0
192.168.2/24 UC 1 0 - 4 ral0
192.168.2.1 UHLc 1 0 - 4 ral0
224/4 URS 0 0 33152 8 lo0
>
> i haven't fully researched the relationship between the two, but at
> least during boot's run of netstart, this is a case where order of
> lines and thus ifconfig commands do matter
>
> On Mon, Nov 26, 2012 at 11:56 AM, Jason McIntyre <j...@kerhand.co.uk> wrote:
>> On Mon, Nov 26, 2012 at 04:30:47PM +0200, Paul Irofti wrote:
>>> Be more specific about the order of interpretation. Okay?
>>>
>>> diff --git share/man/man5/hostname.if.5 share/man/man5/hostname.if.5
>>> index b07459f..aa8446f 100644
>>> --- share/man/man5/hostname.if.5
>>> +++ share/man/man5/hostname.if.5
>>> @@ -49,6 +49,8 @@ A configuration file is not needed for lo0.
>>> The configuration information is expressed in a line-by-line packed format
>>> which makes the most common cases simpler; those dense formats are
>>> described
>>> below.
>>> +The order of the configuration lines matters, they are interpreted from the
>>> +top down.
>>> Any lines not matching these packed formats are passed directly to
>>> .Xr ifconfig 8 .
>>> The packed formats are converted using a somewhat inflexible parser and
>>>
>>
>> if we say this, then we should provide guidance to folks about how to
>> order the lines. what is the specific problem, or the general rule, that
>> you are addressing?
>>
>> jmc
