TEST PLEASE: if_tun patch

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 09/27/03

  • Next message: Vitalis: "Re: Can't hear audio CDs (Asus P4P800 / Soundmax)"
    To: current@freebsd.org
    Date: Sat, 27 Sep 2003 23:57:19 +0200
    
    

    Please test this patch:

            http://phk.freebsd.dk/patch/if_tun.patch

    There is a slight change in semantics in that the interface will disappear
    entirely when the /dev/tun%d device is closed.

    If no objections this will be committed in some days.

    | Remove the bogus tunbasedev, instead record the dev_t in our softc.
    |
    | Rely on the new an cloning friendlier semantics of make_dev().
    |
    | Properly dismantle and remove the interface and destroy the dev_t
    | at last close of the device.
    |
    | Remove code from MOD_UNLOAD to dismantle things.
    |
    | Remove the list used to hang the tunnels from, it is no longer needed.

    -- 
    Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
    phk@FreeBSD.ORG         | TCP/IP since RFC 956
    FreeBSD committer       | BSD since 4.3-tahoe
    Never attribute to malice what can adequately be explained by incompetence.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Vitalis: "Re: Can't hear audio CDs (Asus P4P800 / Soundmax)"

    Relevant Pages

    • Re: Static vs. Dynamic typing
      ... > If you call methods with an expectation of their semantics (ie: ... > GunFighter interface? ... I want a type which specifies exactly that handful and no ...
      (comp.object)
    • Re: Static vs. Dynamic typing
      ... > If you call methods with an expectation of their semantics (ie: ... > GunFighter interface? ... I want a type which specifies exactly that handful and no ...
      (comp.programming)
    • Re: Interface freeloading on a superclass - is it good practice?
      ... > Who's talking about changing any method signatures? ... > the subject of any interface contracts written by the same authors of the ... any future changes to the *precise semantics* of the methods ... Because Sun don't know or care about your interface's rigid semantic ...
      (comp.lang.java.programmer)
    • Re: Tell, Dont Ask
      ... The whole point was for Range to ensure its own invariant. ... Here my solution was constrained by separate setHigh and SetLow interface methods in the original example. ... If that is all of the semantics of Range that is relevant to the problem in hand, then I would probably provide setValueand let Range determine whether its internal High or Low gets set based on the invariant. ... The 'require' in Range enforces an invariant that is implicit in the semantics of a 'range'. ...
      (comp.object)
    • Re: Classes as units of reuse
      ... One can see this in something as simple as a String class where different libraries will provides somewhat different interfaces for basically the same semantics. ... This is manifested during reuse when a client in a new reuse context wants to access the object semantics using a different interface than the one provided by the object's class. ... However, such overhead is usually not excessive at larger scales, such as subsystems because it is small compared to the subsystem functionality. ... The high level view enabled us to deal with high level control in a quite elegant fashion because at that level of abstraction we didn't care what the individual data element values were; we just needed to manipulate the aggregate. ...
      (comp.object)