From owner-freebsd-questions@freebsd.org Fri Jun 28 06:10:06 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 1A23415D9276 for ; Fri, 28 Jun 2019 06:10:06 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0941F8B612 for ; Fri, 28 Jun 2019 06:10:04 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id 2D9391A1145; Fri, 28 Jun 2019 02:10:03 -0400 (EDT) Subject: Re: query re: dual-boot on two separate HDDs Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Frank Fenderbender In-Reply-To: <5146512.8gLySxXtyI@amd.asgard.uk> Date: Thu, 27 Jun 2019 23:09:57 -0700 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <37655A7A-FD94-42C2-AC53-6F6EC7F2F38E@council124.org> References: <5146512.8gLySxXtyI@amd.asgard.uk> To: freebsd01@dgmm.net X-Mailer: Apple Mail (2.1085) X-Rspamd-Queue-Id: 0941F8B612 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of frankfenderbender@council124.org designates 216.92.231.69 as permitted sender) smtp.mailfrom=frankfenderbender@council124.org X-Spamd-Result: default: False [-0.90 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:cegray.mail.pairserver.com]; HEADER_FORGED_MDN(2.00)[]; MIME_GOOD(-0.10)[text/plain]; MV_CASE(0.50)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[council124.org]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mailwash31.pair.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.88)[-0.878,0]; IP_SCORE(-0.21)[asn: 7859(-1.01), country: US(-0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7859, ipnet:216.92.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Fri, 28 Jun 2019 06:10:06 -0000 Thanks Dave. The methods I used on the older BIOSes (for boot sequence re-ordering) = on HP/Dell systems no longer works with the UEFI-based BIOS that new = DEll system deploy. It's like when I could no longer work on my car w/o factory- and = dealership-only tools. There is a push to make working on your own computer "off limits", as = noted in emails I received from by FreeGeek.org (Portland, OR) in their = "Right to Repair Campaign" (https://repair.org/stand-up).=20 FreeGeek converts donated PCs (and components) to minimum-leveled = Debian-based systems and sells them for $50, donates them to free-access = busineses, and gives them to people who volunteer 20-hours for work in = one or more phases of the whole process.=20 I do not know if this is one of those cases, but the result is the same = when documentation does not explain workarounds. If the goal is security, then telling a workaround defeats the securing, = right? However, if the change makes purchased system owners insecure, well, = then, I'd say that that had inadequate QA, Beta testing, and = owner-viewable documentation. Whatever, it is an unnecessary barrier to = what once was working and easy to achieve. Just what is being secured? = Is me actually using "my" system considered a security breach or threat?=20= Anyway, the F5, F11, and F12 keys now all go to an EUFI-secured BIOS = that has hard-to-enable (disabled) "legacy" BIOS optioning ROMs. Even following the cyber-acorns of some who claim success, the process = gets messed-with by the default UEFI ROMs, which, prevent both USB and = disk boot-ups. The mindfulness of this "securing" is not very = well-documented by Dell, and so, it will take some support-call research = to discover the currently-secret success at adding a second OS to either = the same or a second internal or external HD. thanks again, chris On 26-June-2019, at 06:32 AM, Dave wrote: > 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". >>=20 >> 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) >>=20 >> 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.=20 >=20 > 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. >=20 >=20 >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" >=20 Frank frankfenderbender@council124.org