From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 11:09:22 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 D454316A531; Tue, 2 Mar 2004 11:09:22 -0800 (PST) Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4395F43D1F; Tue, 2 Mar 2004 11:09:22 -0800 (PST) (envelope-from james@physicalsegment.com) Received: from [81.174.238.178] (helo=mail.physicalsegment.com) by ptb-relay02.plus.net with esmtp (Exim) id 1AyFGa-000KAe-L4; Tue, 02 Mar 2004 19:09:20 +0000 Received: from [10.0.0.192] (helo=jd2400) by mail.physicalsegment.com with smtp (Exim 4.20) id 1AyFGV-0004Ya-Jx; Tue, 02 Mar 2004 19:09:15 +0000 Message-ID: <00d301c40089$8a035410$c000000a@jd2400> From: "James Read" To: "Bjoern A. Zeeb" , References: <4043B6BA.B847F081@freebsd.org> Date: Tue, 2 Mar 2004 19:06:59 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@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 19:09:23 -0000 > 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'. 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. This is one thing that I would like to use, without patching systems. But then thats just my 'wish list' opinion of it. Regards, James. ( I apoligise for the cross post, it's my first time posting to -current & -net, I just thought it would be worth my 2c ) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Mailscanner thanks transtec Computers for their support.