--v9Ux+11Zm5mwPlX6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 14, 2005 at 09:54:56PM +0900, Izumi Tsutsui wrote:
> kiyohara@kk.iij4u.or.jp wrote:
>=20
> > > FreeBSD's eui64.[ch] is in libc.  eui64.[ch] is used by fwctl(8).
> >=20
> >   FreeBSD's eui64.c is in libc.
>=20
> I don't think "just following FreeBSD" is a good reason.
> We would like to know the reason why FreeBSD guys put them into libc.
>=20
> > fwctl(8) is control utility for IEEE1394. I renamed from fwcontrol(8)
> > to fwctl(8).
>=20
> According to description of their eui64(3), theses functions are
> "IEEE EUI-64 conversion and lookup routines," so we should think
> which other utility could use such functions.
> http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/net/eui64.3
>=20
> I don't know what is EUI64, but netinet6/in6_ifattach.c contains
> some EUI64 definitions. So could other network programs use it?

I'm not sure. It looks like firewire doesn't use arp and these routines=20
take its place. Other firewire tools may well need these routines too.

I bet one reason that these routines are in libc is that they will look in=
=20
NIS maps if the /etc/eui64 file is configured right.

Take care,

Bill

--v9Ux+11Zm5mwPlX6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFCru5fWz+3JHUci9cRArPiAJ443ybsWsEmR2Sf5hNruq5CCzhPHwCgkwxd
x4d/hWlMlTrcTeo4pvmjPEQ=
=WkxG
-----END PGP SIGNATURE-----

--v9Ux+11Zm5mwPlX6--