Re: dev.* analogue for interfaces

John-Mark Gurney <jmg@xxxxxxxxxxxx> writes:
My case is perfectly clear. We already have dev.* for this, and you
want to add a second, confusing, place to put similar/same information...
Yes, this is specific for network interfaces, but what makes a network
interface special that it's configuration can't live in dev.*? You
stated that you were fine w/ some items being in dev.* and others in
net.if.* for the same device, which is why I objected.

If you can't tell the difference between a struct ifnet and a device_t,
I'm afraid we're going to have to agree to disagree.

DES
--
Dag-Erling Smørgrav - des@xxxxxx
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: dev.* analogue for interfaces
    ... want to add a second, confusing, place to put similar/same information... ... Yes, this is specific for network interfaces, but what makes a network ... interface special that it's configuration can't live in dev.*? ... I recently handled something like this for the cryptosoft driver by arbitrarily attaching it to nexus and it worked out very well. ...
    (freebsd-arch)
  • Re: dev.* analogue for interfaces
    ... Your case was very unclear. ... something that you made up in your head which was completely different ... We already have dev.* for this, ... Yes, this is specific for network interfaces, but what makes a network ...
    (freebsd-arch)