From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:13:07 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A14516A4CF for ; Tue, 2 Mar 2004 13:13:07 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id D02EF43D39 for ; Tue, 2 Mar 2004 13:13:06 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 95135 invoked from network); 2 Mar 2004 21:13:06 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 21:13:06 -0000 Message-ID: <4044F8E1.F10CFD37@freebsd.org> Date: Tue, 02 Mar 2004 22:13:05 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: James Read References: <4043B6BA.B847F081@freebsd.org> <00d301c40089$8a035410$c000000a@jd2400> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: "Bjoern A. Zeeb" cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack (vimage) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 21:13:07 -0000 James Read wrote: > > > I still have in mind that I would like to see vimage[1] in HEAD one day > > ... I think it would be a pretty cool feature to have. If one can keep > > this in mind when doing greater modelling on the network stack it > > might help the one who will - at some time - find the time to > > ingtegrate it. > > > > > > [1] http://www.tel.fer.hr/zec/BSD/vimage/index.html > > > > > > In my opinion, this would be a _VERY_ good 'feature' to add into the system. > As it stands there is minimal 'networking' in a jail from a users point of > view, and also an administrators view aswell (granted this isnt exactly what > jail was designed to do, and so on). This could be more then an asset to the > whole jail architecture, by providing a clone-able network stack within > jails. For instance, you could then run programs/services like NFS etc from > jail to jail without having to lock down services offered from the jail > 'host'. Having a per-jail NFS is not dependend on a dedicated network stack but other things. NFS only uses the network for transport, there is on need to have it separated. > If this can in _any way_ be pushed/implemented (with minimal distruption) so > that is it in HEAD/CURRENT then its well on the way to complementing what > 'jail' does. The patch set is pretty extensive and intrusive and only for 4.x. Adding locking for 5.x would be a pretty nice challenge as well and not easy to get right for all cases. > This is one thing that I would like to use, without patching systems. But > then thats just my 'wish list' opinion of it. I think is makes more sense to get something like userland BSD. -- Andre