From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1ICId1-0006BI-5R for garchives@archives.gentoo.org; Sat, 21 Jul 2007 17:20:27 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l6LHJNrT004766; Sat, 21 Jul 2007 17:19:23 GMT Received: from mail.marples.name (rsm.demon.co.uk [80.177.111.50]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l6LHHORF002423 for ; Sat, 21 Jul 2007 17:17:24 GMT Received: from [IPv6:fee1::f20b:aaff:fe00:2] (uberpc.marples.name [IPv6:fee1::f20b:aaff:fe00:2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.marples.name (Postfix) with ESMTP id 4BD4E190038 for ; Sat, 21 Jul 2007 18:17:24 +0100 (BST) Subject: Re: [gentoo-dev] baselayout-2 stablisation plans From: Roy Marples To: gentoo-dev@lists.gentoo.org In-Reply-To: <46A23815.60704@gentoo.org> References: <1185028563.2490.22.camel@uberpc.marples.name> <46A23108.5030006@gentoo.org> <1185035193.2490.25.camel@uberpc.marples.name> <46A23815.60704@gentoo.org> Content-Type: text/plain Organization: Gentoo Date: Sat, 21 Jul 2007 18:17:23 +0100 Message-Id: <1185038243.2490.27.camel@uberpc.marples.name> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 Content-Transfer-Encoding: 7bit X-Archives-Salt: f2a62c47-dc20-4b4d-ac75-34b51969f658 X-Archives-Hash: cf19c71fc7c4f1322cdcd2d69100aa70 On Sat, 2007-07-21 at 12:45 -0400, Daniel Drake wrote: > Roy Marples wrote: > > I don't actually know how to set those up or what the migration path > > would be. Maybe devzero and strerror could document this as I understand > > they do this. > > I manage systems with a single RAID 0 stripe (not dmraid) managed by > device-mapper. When upgrading baselayout, we also have to upgrade to a > recent device-mapper version which provides the device-mapper init > script. Then we must run: > > # rc-update add device-mapper boot > > If we don't, we get an unbootable system. Probably a good idea to add that to the ebuild output too? Roy -- gentoo-dev@gentoo.org mailing list