From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200505141859.j4EIxr013451@demeter.cs.utwente.nl> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] silly dhcpd question In-reply-to: Your message of "Sat, 14 May 2005 18:31:49 +0200." <06b601c558a2$6e533420$aafb7d50@kilgore> References: <72cca6a6583b9c78a245f4825fa65229@proxima.alt.za><14ec7b1805051401384dc36d2@mail.gmail.com><14ec7b18050514014012d4e1fe@mail.gmail.com> <06b601c558a2$6e533420$aafb7d50@kilgore> From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13447.1116097191.1@demeter.cs.utwente.nl> Date: Sat, 14 May 2005 20:59:52 +0200 Topicbox-Message-UUID: 4c10cdca-ead0-11e9-9d60-3106f5b1d025 > > I'm much happier requiring that the ndb entries be stored > > in canonical form than doing magical rewriting under the hood. > > this was my decision too, after a bit of squiz at the problem > and not wanting to break canonical interfaces or anything > else for that matter. Maybe some confusion could be avoided if anything that reports ethernet addresses to the user would use this same canonical format? Right now when I boot 9load reports the ether addres in lower case (via %E where it installed eipfmt from ip(2) which uses %.2lux%.2lux%.2lux%.2lux%.2lux%.2lux) ether#0: elnk3: port 0xDC00 irq 11: 00c0df15fb45 and a little later the kernel reports it in upper case (directly via %2.2uX%2.2uX%2.2uX%2.2uX%2.2uX%2.2uX) #l0: elnk3: 100Mbps port 0xDC00 irq 11: 00C04F15FB45 just my 0.02 whatever. Axel.