From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 02:33:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5BAB37B401 for ; Mon, 7 Jul 2003 02:33:38 -0700 (PDT) Received: from saltmine.radix.net (saltmine.radix.net [207.192.128.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1428B43F75 for ; Mon, 7 Jul 2003 02:33:38 -0700 (PDT) (envelope-from dickey@saltmine.radix.net) Received: from saltmine.radix.net (localhost [127.0.0.1]) by saltmine.radix.net (8.12.2/8.12.2) with ESMTP id h679XU1o029740; Mon, 7 Jul 2003 05:33:31 -0400 (EDT) Received: (from dickey@localhost) by saltmine.radix.net (8.12.2/8.12.2/Submit) id h679XShI029734; Mon, 7 Jul 2003 05:33:28 -0400 (EDT) Date: Mon, 7 Jul 2003 05:33:28 -0400 From: Thomas Dickey To: Juan Rodriguez Hervella Message-ID: <20030707093328.GA29208@saltmine.radix.net> References: <3F08B199.3050409@comcast.net> <20030707002347.GC5141@aurema.com> <20030706203440.D89894@vhost101.his.com> <200307071022.04273.jrh@it.uc3m.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307071022.04273.jrh@it.uc3m.es> User-Agent: Mutt/1.3.27i cc: "Myron J. Mayfield" cc: freebsd-current@freebsd.org cc: dickey@herndon4.his.com Subject: Re: /dev/shm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 09:33:39 -0000 On Mon, Jul 07, 2003 at 10:22:02AM +0200, Juan Rodriguez Hervella wrote: > > (still waiting for FreeBSD to "complete" a sysinstall program that doesn't > > look as if it was an assignment for high-school interns). > > What's the matter with "sysinstall" ? > I very much like "sysinstall" as it is now. :) to be perfectly fair, the 5.x version of sysinstall is slightly improved from 4.x (it finally - took 5 years - does not overwrite my boot loader when requested not to). however. it still has some odd use of the state information which makes me ask (and this means it's defective) why did it do _that_ (for instance installing something _twice_ because I visited the targets menu twice). if someone set out to test it systematically, it wouldn't require the snide remarks, "well, submit patches". -- Thomas E. Dickey http://dickey.his.com ftp://dickey.his.com