hi. two points about the recent ability to use lladdr:
- the example of "bridge0" made sense when bridge was regarded as a separate entity and not integrated with ifconfig. plus a list of one example looks rubbish. now that we have a second example (lladdr) and bridge is not flagged as a special case, i think we can simply the text and reduce it to two examples - i'm not sure about using "lladdr". although we use this term in ifconfig(8), we explain it. and people may miss it if they are thinking of mac address. i've attempted to both write the term fully as "link layer local address" and add a "(MAC)". i suppose you could argue that people who think of the term as "lladdr" might miss that (!) but i don;t think that is a real worry. so here's my cut at tweaking... jmc Index: hostname.if.5 =================================================================== RCS file: /cvs/src/share/man/man5/hostname.if.5,v retrieving revision 1.80 diff -u -p -r1.80 hostname.if.5 --- hostname.if.5 5 Dec 2022 20:12:00 -0000 1.80 +++ hostname.if.5 9 Dec 2022 21:25:06 -0000 @@ -40,13 +40,12 @@ The .Nm hostname.*\& files contain information regarding the configuration of each network interface. -The interface can be referenced by name or lladdr, such as -.Pa hostname.fxp0 , -.Pa hostname.00:00:5e:00:53:af , +The interface can be referenced by name or link layer (MAC) address, such as +.Pa hostname.fxp0 or -.Pa hostname.bridge0 . +.Pa hostname.00:00:5e:00:53:af . One file should exist for each interface that is to be configured, -with priority given to configuration by interface name over lladdr. +with priority given to configuration by interface name over link layer address. A configuration file is not needed for lo0. .Pp The configuration information is expressed in a line-by-line packed format
