From owner-freebsd-current@FreeBSD.ORG  Wed Apr  8 19:30:42 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 84A9C229
 for <freebsd-current@freebsd.org>; Wed,  8 Apr 2015 19:30:42 +0000 (UTC)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com
 [IPv6:2607:f8b0:4001:c03::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4B55DD15
 for <freebsd-current@freebsd.org>; Wed,  8 Apr 2015 19:30:42 +0000 (UTC)
Received: by iejt8 with SMTP id t8so11318869iej.2
 for <freebsd-current@freebsd.org>; Wed, 08 Apr 2015 12:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=WxAz3NqMNhQIOy7e52PSCly3tdnq7qg2JJ40lXn1X9Y=;
 b=cHFrmJWGtkhz7IEcjy97kC5kYf10saRvHNQV+i+ViFN84CwcPSKnfsVUL6ARzMTqpG
 ya6Ye2yrlblBOsvlh0FpMNBrduQ4Vjno5M36uBJDHx0OkFgMjHox6QwMsQh7sKot1V3n
 4VDA8Y0P3cxoI3u123BM+nICjmZk1578GLr3L4FA0NOnI8TTSDI7jhcPAvpQbThiB+Mb
 OOTu54n7vNBsBxKi20Tg36TGzjvU9+lezb4iXwrmbvKHsXEVxQoxgt3iQ9aq6xXkYWd0
 W9OXSbaMAj/D6XWkLUM6CTC8OJ8Lr5DWDuGVa0Ltk56vAL1bT19R4P0vt/HVmHsz/mnu
 n1/A==
MIME-Version: 1.0
X-Received: by 10.107.46.155 with SMTP id u27mr40133419iou.87.1428521441691;
 Wed, 08 Apr 2015 12:30:41 -0700 (PDT)
Received: by 10.107.156.75 with HTTP; Wed, 8 Apr 2015 12:30:41 -0700 (PDT)
Date: Wed, 8 Apr 2015 15:30:41 -0400
Message-ID: <CAFMmRNw=2fXw4ohn+xetuQtESEvMnmrNONi093Sz3FY2rQiAdQ@mail.gmail.com>
Subject: Dual booting FreeBSD and Win95
From: Ryan Stone <rysto32@gmail.com>
To: FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 19:30:42 -0000

No, this isn't a late April Fools joke. :(

I find myself in a situation where I need to integrate my employer's
manufacturing process with a third-party OEM's process.  My employer's
hardware tests are all FreeBSD-based while the OEM is Windows 95 based.  I
need to come up with a way to integrate them together.

We're looking at dual-booting FreeBSD and Win95.  We're thinking of booting
into Win95, the OEM can do their thing, switch to booting FreeBSD, run our
tests and produce a .csv file with the results, and then boot back into
Win95 for them to finish up.  Ideally we would like to switch the boot
slice without human interaction.

I've been playing around with trying to set one only slice as active to
make the loader boot it, but it appears that doesn't actually work.
boot0cfg would cover half of the use case (switching from FreeBSD back to
Win95), but I'm not sure how I could do the original switch from Win95 to
FreeBSD.

We've discussed just switching hard drives, but we really want to shoot for
a 100% automated process.  Anybody have any ideas?