From owner-freebsd-current Tue Jan 4 14:21:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 8AD9614A08 for ; Tue, 4 Jan 2000 14:21:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA03645; Tue, 4 Jan 2000 14:26:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001042226.OAA03645@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas Zenker Cc: current@FreeBSD.ORG Subject: Re: Proposal: Removing doscmd from the source tree... In-reply-to: Your message of "Tue, 04 Jan 2000 22:57:41 +0100." <20000104225739.A865@peotl.tuebingen.netsurf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 14:26:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually i never used it under X11, but it is very important for > us to have it to run cross-compilers (which are only available as > DOS binaries) integrated with native development environment under > FreeBSD. > > I am not sure how many people use it this way. But if it is not > build in buildworld, it will break after kernel updates and I will > have strong wind blowing in my face defending our FreeBSD development > environment at work. It's actually quite unlikely that this would be the case; apart from the 4.x signal changes I don't recall a single other event that would have broken doscmd's binary compatibility. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message