From owner-freebsd-questions@freebsd.org Sun Jul 12 20:16:46 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCA4499BB1B for ; Sun, 12 Jul 2015 20:16:46 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8937C12C0 for ; Sun, 12 Jul 2015 20:16:46 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-74-114.dynamic.qsc.de [92.195.74.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 689D93CD36; Sun, 12 Jul 2015 22:16:42 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t6CKGfmq002107; Sun, 12 Jul 2015 22:16:41 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 12 Jul 2015 22:16:41 +0200 From: Polytropon To: reg@dwf.com Cc: FreeBSD questions Subject: Re: FreeBSD install. Message-Id: <20150712221641.69f81f00.freebsd@edvax.de> In-Reply-To: <201507120402.t6C427Dg001385@deneb.dwf.com> References: <201507120402.t6C427Dg001385@deneb.dwf.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 20:16:47 -0000 On Sat, 11 Jul 2015 22:02:07 -0600, reg@dwf.com wrote: > I have been trying for several months to put PCBSD 10.1 and FreeBSD 10.1 > on one disk. I finally gave up, and am installing FreeBSD over > the top of my previous PCBSD. sigh. It should be no big problem to allocate two slices, put FreeBSD in one, PC-BSD in the other, and add the FreeBSD boot manager to select which OS to boot. This has been possible for decades now, and it isn't "special". > After several attempts to put FreeBSD in a partition on the disk > I gave up, and let it have the full 500GB disk. Mumph. Did you use MBR or GPT partitioning? As far as I remember, the GPT approach doesn't support boot manager use yet. > The install seems to go well, I give it an IP address, hostname, > etc, and get down to the point where you reboot. > > I say yes to the reboot, and instead of rebooting from disk, I > get the bios messages (Im using a mbr) that say its trying to > boot from the ethernet. This indicates that you've missed to add a boot record for the disk, so obviously the BIOS doesn't find anything that screams "Here! Here! I'm bootable!" :-) > I went back and did this a 2nd time, just to be sure, but got > the same result. So you missed the boot part a second time. > What gives? > I dont remember having this sort of problem when I ran FreeBSD > 20 years ago? Yes, this kind of problems seems to happen now that many parts of FreeBSD are in a "transition phase"... :-( > And why isnt the installer smart enough to install to a partition, > every other OS in existence can do that. Depends on how "every other OS in existence" defines what "partition" means. :-) But you're right - what you plan to do is possible with MBR slices (commonly called "DOS primary partitions"). Let's say you have 500 GB and want to use it as 50/50. Then you prepare the disk as follows: ada0 <- for boot manager ada0s1 <- for FreeBSD ada0s2 <- for PC-BSD You can do this either with gpart (using MBR partitioning) or with fdisk, the "old" tool for dealing with MBR. Use boot0cfg to add the boot manager. The slices can be formatted to carry _one_ file system (no further subpartitioning a la disklabel), it has to be an 'a' partition (bootable partition): ada0s1a ada0s2a Use bsdlabel to create it, spanning the whole disk size. Use newfs to initialize it, or leave that task to the installers of FreeBSD and PC-BSD. Result: The BIOS will now see ada0 bootable. It will continue to transfer control to the boot manager. The boot manager then will see two slices carrying a bootable file system each, and will let you decide which one to boot. As soon as control is transfered to one of the slices, the kernel loader will load the kernel, mount the root file system, and continue booting the OS. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...