From owner-freebsd-current@FreeBSD.ORG Mon Sep 1 12:19:06 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 8BDEF16A4BF for ; Mon, 1 Sep 2003 12:19:06 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E54943FFD for ; Mon, 1 Sep 2003 12:19:05 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h81JIqi8035642; Mon, 1 Sep 2003 21:18:57 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Nicole From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 01 Sep 2003 12:12:48 PDT." Date: Mon, 01 Sep 2003 21:18:52 +0200 Message-ID: <35641.1062443932@critter.freebsd.dk> cc: current@freebsd.org Subject: Re: 5.2-RELEASE TODO 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, 01 Sep 2003 19:19:06 -0000 In message , Nicole writes: > > Is anyone going to be fixing the sysinstall problem of not being able to >re-slice a drive? For those who are not technical whizes this IS a big problem. >We do still care about them.... right? If you are talking about using sysinstall to modify drives in use, then the answer is probably no. For that job you want to use the correct tools: fdisk(8) and bsdlabel(8) (tacitly assuming i386 here). If you are talking about a problem during initial install of FreeBSD you need to provide more details about it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.