9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] silly dhcpd question
Date: Sat, 14 May 2005 20:59:52 +0200	[thread overview]
Message-ID: <200505141859.j4EIxr013451@demeter.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Sat, 14 May 2005 18:31:49 +0200." <06b601c558a2$6e533420$aafb7d50@kilgore>

> > 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.


  reply	other threads:[~2005-05-14 18:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 21:59 Ronald G. Minnich
2005-05-13 22:04 ` "Nils O. Selåsdal"
2005-05-13 22:28   ` Ronald G. Minnich
2005-05-14  2:36     ` boyd, rounin
2005-05-14  5:44 ` lucio
2005-05-14  8:05   ` lucio
2005-05-14  8:38     ` andrey mirtchovski
2005-05-14  8:40       ` andrey mirtchovski
2005-05-14 16:18         ` Russ Cox
2005-05-14 16:31           ` boyd, rounin
2005-05-14 18:59             ` Axel Belinfante [this message]
2005-05-14 19:11               ` Russ Cox
2005-05-16  4:04               ` Ronald G. Minnich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200505141859.j4EIxr013451@demeter.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).