Re: Network stack cloning / virtualization patches

From: Peter Jeremy (peterjeremy_at_optushome.com.au)
Date: 05/31/03

  • Next message: Wes Peters: "Re: Collision on NIC" 
    Date: Sat, 31 May 2003 08:26:19 +1000
To: Marko Zec <zec@tel.fer.hr>

    On Fri, May 30, 2003 at 10:07:07PM +0200, Marko Zec wrote:
    >I plan to start porting the cloning code to -CURRENT once it becomes -STABLE
    >(that means once the 5.2 gets out, I guess).

    FreeBSD has a policy that all new features must be added to -CURRENT
    before they can be added to -STABLE (4.x or 5.x). This means that
    you are going to have to port the code to -CURRENT at some point in
    order to get it added to the main tree.

    That said, now is actually a relatively good time to look at porting
    code to -CURRENT. It has been in a 'semi-frozen' state since about
    last November and will stay in this like this until 5.x is branched
    (ie work is focused on bug-fixes and performance enhancements with
    minimal new features). Once 5-STABLE is branched, 6-CURRENT will go
    through a period of rapid change and instability as everyone gets 9
    months or so of pent-up API changes and 'interesting new ideas'
    committed. In other words, the longer you leave it, the more effort
    you'll probably need to invest.

    Peter
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Wes Peters: "Re: Collision on NIC"

    Relevant Pages

    • Re: Network stack cloning / virtualization patches
      ... FreeBSD has a policy that all new features must be added to -CURRENT ... months or so of pent-up API changes and 'interesting new ideas' ...
      (freebsd-hackers)
    • Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3
      ... This whole discussion is really interesting as it clearly showcases two common trends in computing (rapid development vs stability) On the one side we got people who are more interested in development than stabilization of the existing code base. ... They really do not care about "new features", but they do care about maximum stability of the existing code, security, and nonstop business continuity even in the face of natural disasters. ... There are definitely points of conflict along these lines, but much of the time the reason that people use FreeBSD is precisely because there *is* agreement on these points. ... If FreeBSD developers only hung around to do adventurous new feature development, we wouldn't have -STABLE branches, errata/security branches, freebsd-update, and so on. ...
      (freebsd-stable)
    • Re: XP in 2000 Domain
      ... Specifically what features are you trying to get on Win2K? ... > The Local Security is not controlled by the ADM files. ... You might consider installing Group Policy ...
      (microsoft.public.windows.group_policy)
    • Re[2]: FreeBSD and i386 VM hardware
      ... the Intel microprocessors provide some very elaborate features ... MD>:for management of virtual memory, I/O operations, and security, allowing total ... How much of this is used by FreeBSD? ... MD> use most of the major MMU/VM features of the processor. ...
      (FreeBSD-Security)
    • Future of FreeBSD
      ... As an active FreeBSD user, I'm ever so interested about the future ... plans of FreeBSD and direction of developement. ... strive for new features driving developers past their limits, ...
      (freebsd-current)