| Lists: | pgsql-hackers |
|---|
| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Hackers List <pgsql-hackers(at)postgresql(dot)org>, Larry Rosenman <ler(at)lerctr(dot)org>, Alex Pilosov <alex(at)pilosoft(dot)com> |
| Subject: | New MAC OUI capabilities |
| Date: | 2000-08-23 06:17:40 |
| Message-ID: | 39A36C84.38A39563@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
I've committed changes to the main tree which update the pg_proc system
catalog, so initdb is required.
As discussed recently, I've added some contrib/mac/ routines to support
generating a table, macoui, which contains current manufacturers'
identification fields for hardware MAC addresses. I've made a few other
changes, including dropping the macaddr_manuf() built-in function.
Note that I did *not* add a current copy of the oui.txt file from IEEE,
since it is over half a meg uncompressed. But we could add it to cvs if
it is advisable.
The contrib/mac directory does not yet have a README, but should.
More details below...
- Thomas
The CVS log:
Add functions to convert to and from text, and to truncate to MAC OUI.
Remove hardcoded macaddr_manuf(), which had really old, obsolete info.
Replace this with some contrib/mac/ code to maniag OUI info from IEEE.
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org>, Larry Rosenman <ler(at)lerctr(dot)org>, Alex Pilosov <alex(at)pilosoft(dot)com> |
| Subject: | Re: New MAC OUI capabilities |
| Date: | 2000-08-23 14:03:37 |
| Message-ID: | 27741.967039417@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> Note that I did *not* add a current copy of the oui.txt file from IEEE,
> since it is over half a meg uncompressed. But we could add it to cvs if
> it is advisable.
Then we'd have to worry about keeping it up to date. That's also
more distribution-bloat than I think is advisable for a relatively
little-used feature. I vote for just providing a README that tells
where to get the current oui.txt file.
regards, tom lane
| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org>, Larry Rosenman <ler(at)lerctr(dot)org>, Alex Pilosov <alex(at)pilosoft(dot)com> |
| Subject: | Re: New MAC OUI capabilities |
| Date: | 2000-08-23 16:01:22 |
| Message-ID: | 39A3F552.D5D0E574@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
> Then we'd have to worry about keeping it up to date. That's also
> more distribution-bloat than I think is advisable for a relatively
> little-used feature. I vote for just providing a README that tells
> where to get the current oui.txt file.
We do even better than that: there is an "updateoui" routine which uses
wget to go out and fetch the file for you.
- Thomas