From owner-freebsd-stable@FreeBSD.ORG Tue Jul 26 15:34:04 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB95E106566C for ; Tue, 26 Jul 2011 15:34:04 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout026.mac.com (asmtpout026.mac.com [17.148.16.101]) by mx1.freebsd.org (Postfix) with ESMTP id D31628FC12 for ; Tue, 26 Jul 2011 15:34:04 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from [10.1.2.163] ([173.200.178.70]) by asmtp026.mac.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LOY00G0D5WRQ570@asmtp026.mac.com> for freebsd-stable@freebsd.org; Tue, 26 Jul 2011 08:34:04 -0700 (PDT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813,1.0.211,0.0.0000 definitions=2011-07-26_05:2011-07-26, 2011-07-26, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1012030000 definitions=main-1107260110 From: Chuck Swiger In-reply-to: <1311693565.1799.81.camel@xenon> Date: Tue, 26 Jul 2011 08:34:03 -0700 Message-id: References: <4E2E9F24.1040108@dichotomia.fr> <1311681539.1799.54.camel@xenon> <4E2ECEFE.5030302@dichotomia.fr> <1311693565.1799.81.camel@xenon> To: Michal Varga X-Mailer: Apple Mail (2.1084) Cc: freebsd-stable@freebsd.org Subject: Re: Making world but no kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 15:34:05 -0000 On Jul 26, 2011, at 8:19 AM, Michal Varga wrote: > Well, that depends. Probably every single time I've seen someone > touching sysinstal in a post-install environment, that OS was instantly > rendered as much as good for a complete reinstall. It's just "one of > those things" that shouldn't be present in any rescue scenario. I've been using sysinstall at dozens of customer sites since the 1990's without ever once running into a problem resembling what you've described. Considering the absence of specific details, I think you're exaggerating well past the point of credibility. Anyway, if someone does something bad using sysinstall and needs to fix it, restoring from backups should be all that is needed. When people talk about doing a complete reinstall, it implies to me that they don't have backups in the first place. Regards, -- -Chuck