Re: [PATCH] ip4/6 jail enhancements

From: Meno Abels (meno.abels_at_gmail.com)
Date: 07/31/04

  • Next message: FreeBSD Tinderbox: "[current tinderbox] failure on amd64/amd64"
    Date: Sat, 31 Jul 2004 11:31:47 +0200
    To: Max Laier <max@love2party.net>
    
    

    Hello,

    I can, sorry my fault, I miss this every time I submit something to
    freebsd. In other projects where I working they don't like unified
    patches. So sometime I get confused.
    I put the patch as a followup to the gnats so everything is in its place.
    Watch out there are now to peaces of diff one for the kernel part and one
    for the userland.

    regards

    meno

    On Sat, 31 Jul 2004 04:47:26 +0200, Max Laier <max@love2party.net> wrote:
    >
    >
    > On Saturday 31 July 2004 01:05, Meno Abels wrote:
    > > Hello,
    > >
    > > i submit last week a patch to the jail code which enables
    > > the option to have multiple ip numbers (ip4 and ip6) assigned
    > > to a jail.
    > > Out of my view this patch isn't received any attention until today
    > > by any freebsd member or mailing list user.
    > > It could that I chosen the wrong channel to submit it by a
    > > standard pr.
    > > I worked in -CURRENT so it could be better to submit the
    > > work to these mailing list. What I now try.
    > > I'am not really familiar with the processes behind the scenes.
    > > So I try to point to my work, and asks if somebody is willing to
    > > try it. It would be nice to get a feedback-:)
    > > So I give the link to the orignal pr
    > > http://www.freebsd.org/cgi/query-pr.cgi?pr=69064
    > > this includes the patch to -CURRNT. What hopefully works until
    > > one week progress in -CURRENT.
    >
    > Can you re-produce this an unified diff, please? They are much more noise
    > protected than the plain diff format. Submitt it as a followup here or to
    > gnats. Just let's make sure that your work isn't lost!
    >
    > This is certainly something of great interest! Various developers have had
    > similar plans, not sure about their status, though.
    >
    > --
    > /"\ Best regards, | mlaier@freebsd.org
    > \ / Max Laier | ICQ #67774661
    > X http://pf4freebsd.love2party.net/ | mlaier@EFnet
    > / \ ASCII Ribbon Campaign | Against HTML Mail and News
    >
    >
    >
    _______________________________________________
    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: FreeBSD Tinderbox: "[current tinderbox] failure on amd64/amd64"

    Relevant Pages

    • Re: NetMos NM9805 1284 Printer port
      ... > Dear FreeBSD friends, ... When you have an addition to the sources, you need to create a diff ... patch won't get lost in the mailing lists. ... month if no-one has commited your patch, ...
      (freebsd-stable)
    • Re: [OT] Q: what would you choose for a VCS today
      ... FreeBSD as base that would allow better teams cooperation and easy code ... control fly out the window from, say, the 42nd floor. ... If you think you need a vendor branch, take a look at mercurial patch ... Patch queues are quite powerful, and even though you end up versioning ...
      (freebsd-hackers)
    • RE: For the love of God, is it even possible to make the Atheros ath.patch & updated HALactually
      ... > # mv ath_hal_20051212 ath ... in hopes that maybe the patch was FINALLY ... This FreeBSD installation is sitting here doing ... To June/July 2005 madwifi was very unstable, after merging cvs BSD tree of ...
      (freebsd-current)
    • Success! was Re: tvtime audio vs pcHDTV-3000 card and pvHDTV-1.6 software
      ... On Wednesday 16 March 2005 20:15, Gene Heskett wrote: ... > that a diff actually outputs only the src code differences, ... nor in that simple little 10 line patch that ... >Unforch, the 2.6.11 plain tree has not, in this case been built yet ...
      (Linux-Kernel)
    • Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv
      ... > There's no patch for these, and in the case of the embedded ... >>FreeBSD only: NO ... In a few instances in the resolver code, ... >>can spoof DNS messages) may produce a specially crafted DNS message ...
      (FreeBSD-Security)