From owner-freebsd-fs@FreeBSD.ORG Tue Apr 26 23:49:44 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 9D2F81065672; Tue, 26 Apr 2011 23:49:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 4390D179B84; Tue, 26 Apr 2011 23:49:22 +0000 (UTC) Message-ID: <4DB75A02.9050600@FreeBSD.org> Date: Tue, 26 Apr 2011 16:49:22 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9 MIME-Version: 1.0 To: lev@FreeBSD.org References: <4DB70949.6090104@FreeBSD.org> <4DB70F97.1070809@FreeBSD.org> <4DB71311.7080203@FreeBSD.org> <4DB71654.5060008@FreeBSD.org> <5710150841.20110427004608@serebryakov.spb.ru> In-Reply-To: <5710150841.20110427004608@serebryakov.spb.ru> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-fs@FreeBSD.org, "Andrey V. Elsukov" , Alexander Motin Subject: Re: Why not just name the cam-ata devices the same as the old names? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 23:49:44 -0000 On 04/26/2011 13:46, Lev Serebryakov wrote: > Hello, Andrey. > You wrote 26 апреля 2011 г., 23:00:36: > >>> files, but there is precedent for doing so for changes like this, and as >>> long as we are not relying on mergemaster to _fix_ the problem, I'm Ok >>> with doing it that way. So I will stay tuned to see how this develops. >> mergemaster usually used a bit later than it can help, i mean that we >> recommend run it after installing kernel and first reboot. > There is special option `-p', am I right? mergemaster is not the answer to fixing this problem for the user. Please read the whole thread for the answer to "why not?" -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/