From owner-freebsd-questions@FreeBSD.ORG Wed Oct 17 18:50:19 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B18EB80A for ; Wed, 17 Oct 2012 18:50:19 +0000 (UTC) (envelope-from kernel@webrz.net) Received: from webrz.xs4all.nl (webrz.xs4all.nl [82.95.248.216]) by mx1.freebsd.org (Postfix) with ESMTP id 5DFF78FC12 for ; Wed, 17 Oct 2012 18:50:19 +0000 (UTC) Received: from webrz.xs4all.nl (localhost [127.0.0.1]) by webrz.xs4all.nl (Postfix) with ESMTP id 89B0850889; Wed, 17 Oct 2012 20:48:07 +0200 (CEST) Received: from [10.10.10.44] (chimea.webrz.net [10.10.10.44]) by webrz.xs4all.nl (Postfix) with ESMTPA id 637175086E; Wed, 17 Oct 2012 20:48:07 +0200 (CEST) Message-ID: <507EFDED.5040303@webrz.net> Date: Wed, 17 Oct 2012 20:50:21 +0200 From: Jos Chrispijn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Polytropon Subject: Re: FreeBSD9 - Fresh install (2) References: <5079ABFA.8050607@webrz.net> <20121013210513.80676821.freebsd@edvax.de> <507AFEEC.2030609@webrz.net> <201210142129.24479.jmc-freebsd2@milibyte.co.uk> <507BC823.9060606@webrz.net> <20121015120321.21ff48f4.freebsd@edvax.de> <507C21EB.2040908@webrz.net> <20121016020923.68d15b3f.freebsd@edvax.de> In-Reply-To: <20121016020923.68d15b3f.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV using ClamSMTP @triton.webrz.net Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2012 18:50:19 -0000 Thanks for this very informative suggestion. I think I need to study it thouroughly, but will certainly head for that solution. kind regards, Jos Chrispijn Polytropon: > That would work, and could be performed easily even using > the slice editor of the sysinstall program. > > Of course, make sure that all partition references work > properly for _each_ slice. Using labels is a comfortable > way to achieve this. But it would be no problem to use > the device names (as long as the disk won't be moved). > > For example: > > Slice 1: Installation OS 8.2 > -> boots to /dev/ad0s1a (kernel is in ad0s1a:/boot/kernel) > -> performs root mount of /dev/ad0s1a > -> mounts OS partitions /dev/ad0s1[defg] > -> mounts data partition /dev/ad0s3 > > Slice 2: Installation OS 9.0 > -> boots to /dev/ad0s2a (kernel is in ad0s2a:/boot/kernel) > -> performs root mount of /dev/ad0s2a > -> mounts OS partitions /dev/ad0s2[defg] > -> mounts data partition /dev/ad0s3 > > Slice 3: Users' home directories > > You also use the fdisk command to set the active partition manually, > or write a short skript that "flips the switch" to boot from "the > other slice" the next time (comparable to the nextboot command in > relation to kernels); see "man fdisk" for details. > > That won't work in "Windows" mode, as you cannot click on the slice. :-) > >