From owner-freebsd-questions@freebsd.org Wed Jun 26 13:32:32 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF16615C8AE2 for ; Wed, 26 Jun 2019 13:32:32 +0000 (UTC) (envelope-from freebsd01@dgmm.net) Received: from out4-server.securespamfilter.com (out4-server.securespamfilter.com [89.187.86.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED8AB6E3A9 for ; Wed, 26 Jun 2019 13:32:21 +0000 (UTC) (envelope-from freebsd01@dgmm.net) Received: from phantom.hostingseries.net ([89.187.86.9]) by server1.securespamfilter.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1hg81v-0006Te-4E for freebsd-questions@freebsd.org; Wed, 26 Jun 2019 14:32:17 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dgmm.net; s=default; h=Content-Type:Content-Transfer-Encoding:MIME-Version:References: In-Reply-To:Message-ID:Date:Subject:Reply-To:To:From:Sender:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=p2cSWOqlrPGetlvOx9+U5ukq7SQrc+A62Z684aK5rXE=; b=Mizs26yx5jE80IjnZGUw97idCO Vi+3IIdoUyKu30KbF4qXE53tS25vtmio9HnYEUAeVG0V9qRUfgxR7ERyNWUOF/7I2bu9gTHlDE0PZ Zb0SSTJ4IWk+5I3pO0VejKS4Hbv3RZmR7cs7Yz9SAu0VCu477UvCfIlvnHY55y7axrR+HWon/J4Ah jDCPV3f/An8Ob0I1++7DZ+mrZ2VLPiVkIW+D3HYRmYxM+ksfs2EM06jenuQGg7W9kXbe+Pj7jnHgR yxFSSjqW2UBgcRyly6gR9mHHcdzup5FSLHAb+eXI4auCAzBdUH68gk4HTxI0H+FEykn3onSPnd05C j8AHq7xg==; Received: from cpc138954-jarr14-2-0-cust73.16-2.cable.virginm.net ([92.236.194.74]:44382 helo=amd.asgard.uk) by phantom.hostingseries.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1hg81u-000WoM-7r for freebsd-questions@freebsd.org; Wed, 26 Jun 2019 14:32:06 +0100 From: Dave To: freebsd-questions@freebsd.org Reply-To: freebsd01@dgmm.net, freebsd01@dgmm.net Subject: Re: query re: dual-boot on two separate HDDs Date: Wed, 26 Jun 2019 14:32:05 +0100 Message-ID: <5146512.8gLySxXtyI@amd.asgard.uk> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-AuthUser: fbsd@dgmm.net X-Originating-IP: 89.187.86.9 X-SpamExperts-Domain: pickaweb.co.uk X-SpamExperts-Username: phantom X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.15) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0Q9DGisTdy29Heef28Cu3sipSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDlVo9zfgzQ4Wlm3+W3UHOX4Qa YpRhAYd86uWsk05meL64Dcwf+CZK8NXgy3In+fX7Sp1tcCTa6u6/r+fb51DXNv7Hrzz3S1b48+29 eERTSEtmGDnWynLP3lCOL1iSHb9JpeRe7rym3gJTauWmVTj9PSx/adqNMHahp5XtfA4ajmwm9bQU RyzcRopnGhnYmMEprg3E57r/Hq5lretslq4h6QJ4wOGdQcgc/WQa4yzUXumcXszKUcFfWEdlY+ph TUCGfOd0Lki8UcIop6ZvPjacVBxV4OtODaDwF9f4xH3I7i6wUeakzlSnqfLLyOr5H7FiHbVLduG7 PstHTe7h/7/D5mOQWqD2EgxIEt8t6SnCFqtWvr8JTlYtiVjMDmwO7HTyFMs5UMAjsy6cUdxf7Drg 4IgdtaR3o9khRoQLGgWg43DTIKZzwOAK1MPDwCdasCxRRCgIxW1i4SUk2QT29/WGoGiH1Wgh6RAe nBR+licROGYfkJnxOckQyokJVEa/BeYqqSFJ2+IaPfTEs0dVjxV+JI8gAPLMSZnYZDcIC4vudShH G/o9yvt8qKTZkCrxNwplAGTg1f/n0/UFbT969QCxzlruCM+6VEqIieGiY97fYuRzXSs4uthCmAS0 GZhfBJsF22Z0WyByCOn1LE0SDM+wV2Jz6HK/dap4WNDhfoBY0LWbLNyzY/V0GrDyrrXBLNo92b5E VhXl+0SAgT4HyNRqwk4vidrAbzPztKfs4s5XguIqNfH/BIlq5TJ+iSpBAmXGk63oZ0GOZkbhG8uj u0cK2bhjjiZ790zDPIl0wjnMaql714xGucFHZ+mqW7WV/465BM5ipbdT2ZlbyX+K4gbCt486A0Aq NLPkQzqqaeImyTcgzuuzwAxa49h0/4k6LZihuYn7Eiosaib2kKTvHX+aG0M3JUSyT+qpsy87yHsk upD3jMGGxCc2F5HG8A9hOo4X X-Report-Abuse-To: spam@server.securespamfilter.com X-Rspamd-Queue-Id: ED8AB6E3A9 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dgmm.net header.s=default header.b=Mizs26yx; spf=softfail (mx1.freebsd.org: 89.187.86.17 is neither permitted nor denied by domain of freebsd01@dgmm.net) smtp.mailfrom=freebsd01@dgmm.net X-Spamd-Result: default: False [-1.95 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd01@dgmm.net]; HAS_XOIP(0.00)[]; MX_INVALID(0.50)[greylisted]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[dgmm.net:+]; NEURAL_HAM_SHORT(-0.49)[-0.485,0]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-0.18)[ipnet: 89.187.86.0/24(-0.46), asn: 31708(-0.37), country: GB(-0.09)]; MIME_TRACE(0.00)[0:+]; CTE_CASE(0.50)[]; ASN(0.00)[asn:31708, ipnet:89.187.86.0/24, country:GB]; RECEIVED_SPAMHAUS_PBL(0.00)[74.194.236.92.zen.spamhaus.org : 127.0.0.11]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.986,0]; R_DKIM_ALLOW(-0.20)[dgmm.net:s=default]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[dgmm.net]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[17.86.187.89.list.dnswl.org : 127.0.10.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2019 13:32:33 -0000 On Wednesday, 26 June 2019 04:48:59 BST Frank Fenderbender wrote: > I am adding the FreeBSD 12 install to the 2nd hard drive. > Often, the dual-boot instructions appear to be for a same-drive, different partition configuration. > I give each OS its own [whole] drive, in an attempt to assist in the avoidance of segmentation faults, corruptions, performance hits, and the like, often used by data, applications, and OS slam-dancing, as in a crowded "mosh pit". > > So, with many well-meaning ways to botch this, I thought maybe someone had performed a similar sequence of steps that: > adds FreeBSD to a second drive > edits the GRUB/bootloader cfg file(s) > > I am uncertain if Grub gets called by the BIOS call to the bootloader, and so, is specific to Ubuntu? > I would expect it to be dealing with partition choices on one drive, rather than stipulating starting a boot on another drive. Since it's going to involve a keypress or two anyway, a quick'n'dirty "fix might be to use the BIOS boot menu, usually accessed from a Fn key at boot time when the BIOS logo/info screen is displayed.