Date: Tue, 16 Oct 2012 02:09:23 +0200 From: Polytropon <freebsd@edvax.de> To: Jos Chrispijn <kernel@webrz.net> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD9 - Fresh install (2) Message-ID: <20121016020923.68d15b3f.freebsd@edvax.de> In-Reply-To: <507C21EB.2040908@webrz.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Oct 2012 16:47:07 +0200, Jos Chrispijn wrote: > Polytropon: > > Per definition, you can only mark one slice bootable. If you manage to > > mark more than one slice bootable, the start loader (from BIOS) will > > boot into the first one it finds, and that will possibly be the one of > > the 1st slice. > I know, but I was referring to the update installation of a new BSD > version; if I have installed it on the empty slice, I only have to make > that slice bootable (and removing that function from the original one). > Does that make sense (still in Windows mode here J-) ? 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. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121016020923.68d15b3f.freebsd>