From owner-svn-src-all@FreeBSD.ORG Mon Jan 19 16:50:31 2009 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9CD31065677; Mon, 19 Jan 2009 16:50:31 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9CB8FC12; Mon, 19 Jan 2009 16:50:31 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.2/8.14.2) with ESMTP id n0JGoUPh018643; Mon, 19 Jan 2009 08:50:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.2/Submit) id n0JGoUgR018642; Mon, 19 Jan 2009 08:50:30 -0800 (PST) (envelope-from obrien) Date: Mon, 19 Jan 2009 08:50:30 -0800 From: "David O'Brien" To: Robert Watson Message-ID: <20090119165030.GA18409@dragon.NUXI.org> References: <200901161547.n0GFlZ4C012008@svn.freebsd.org> <20090117142021.92d5a40b.stas@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Stanislav Sedov , svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Ed Schouten Subject: Re: svn commit: r187332 - head/tools/regression/usr.bin/jot X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 16:50:32 -0000 On Sat, Jan 17, 2009 at 02:00:55PM +0000, Robert Watson wrote: > > On Sat, 17 Jan 2009, Stanislav Sedov wrote: > >> Was this discussed somewhere? I don't understand why we should restrict >> our filesystem naming because of limitation of auxilary filesystems. >> There're even more restrictive filesystems available, we couldn't support >> them all. While previous modifications looked harmless this one seems >> questionable to me. >> >> I understand, this is a bikesched, but I really don't see a reason. You >> can't build FreeBSD on windows anyway. > > Many of us would *very* much like to be able to cross-build FreeBSD from > both Windows and Mac OS X, which would be highly desirable for embedded > systems and appliance shops. Run VMware. Seriously. Or raise a serious discussion on developers@ about this and get conciseness that cross building on MacOS X and MS-Windows is a goal. Juniper Networks creates VM's of FreeBSD build machines when they are upgraded (or decommissioned) so it can build old EOL'ed JUNOS versions if really needed on the same exact FreeBSD version as when the JUNOS version was in full production. If Juniper can do it - FreeBSD developers cannot? For changes like this to be reasoned because of building FreeBSD on Windows there should consensus. For MacOS X - there is a case sensitive FS. > The first obstacle to making that work is > that you can't even check out our source code correctly on those platforms, > so fixing that is an important priority so that the remainder can be worked > on. See above for MacOS X users. -- -- David (obrien@FreeBSD.org)