On Nov 30, 2003, at 2:41 PM, Robert Watson wrote:
if_tap is actually quite useful, and in the same general class of
synthetic interfaces as if_tun. I've used both in building tunneling
and
topology-manipulation tools, as well as for debugging routing, etc.
if_tap simulates an 802 device, and
Hi all,
As per Sam's suggestion, I've been working on refactoring ifconfig(8),
which has grown increasingly large and unwieldy. Part of the effort has
been to get a handle on all of the options we currently support; so I've
written a YACC grammar for it.
This is my first serious bit of work with
Bruce M Simpson wrote:
Hi all,
As per Sam's suggestion, I've been working on refactoring ifconfig(8),
which has grown increasingly large and unwieldy. Part of the effort has
been to get a handle on all of the options we currently support; so I've
written a YACC grammar for it.
This is
On Sun, Nov 30, 2003 at 01:12:42PM +0100, Andre Oppermann wrote:
What I've thinking about a lot is to make the networking system and
ifconfig sort of class-based like newbus and geom.
Look at: http://people.freebsd.org/~bms/dump/nifconfig/nifconfig-design.txt
There is a pending change to
On Sun, 30 Nov 2003, Bruce M Simpson wrote:
On Sun, Nov 30, 2003 at 01:12:42PM +0100, Andre Oppermann wrote:
What I've thinking about a lot is to make the networking system and
ifconfig sort of class-based like newbus and geom.
Look at:
On Sun, Nov 30, 2003 at 02:20:50PM -0500, Robert Watson wrote:
if_type seems like it will work for high level classes of interfaces, but
something more fine-grained will be required for interfaces that implement
multiple classes or subclasses (i.e., 802 generally, and also 802.11b).
The idea
On Sun, 30 Nov 2003, Bruce M Simpson wrote:
On Sun, Nov 30, 2003 at 02:20:50PM -0500, Robert Watson wrote:
if_type seems like it will work for high level classes of interfaces, but
something more fine-grained will be required for interfaces that implement
multiple classes or subclasses
Robert Watson wrote:
On Sun, 30 Nov 2003, Bruce M Simpson wrote:
I have to find an abstraction to comfortably deal with this stacking of
properties/methods, simple polymorphism (a la Java 'implements
interface') springs to mind.
I think that would be a reasonable approach, although it
8 matches
Mail list logo
