From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 20:00:29 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A78E12D for ; Wed, 8 Apr 2015 20:00:29 +0000 (UTC) Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) (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 13BA2C2 for ; Wed, 8 Apr 2015 20:00:28 +0000 (UTC) Received: by obbfy7 with SMTP id fy7so156106692obb.2 for ; Wed, 08 Apr 2015 13:00:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+bsY7NnIuyGQ3E9Rv/yB+X7bs1Low1A0X8kBvyAUmJU=; b=aWnod7s3LhnSGpngjw3r+/XmIriwrHXhhcSjNE/dGY/8PCA4l9IFeRUQsi8sMjruom 4SnAGc6ig2LGo/XcZBW9ntKiu1ZqtfCrSrtsNiczuGWHbuK1lxSrz0NHwri5ODI/LMlW qErmXZf2nUM3etL2DZPtPDznU9UL8w4zhAVOSKpMv8zkNYpgyRyte2xeQ12YJwJCMgZJ fBtBJPAj/2zW/5krbZ7Ti03SASYhp2Ik3aK+H/3FWFhNLGIeqcQPxNRyhWNEfuptClHo 92hCG9tPuEeTH4VenZk1ZruJzecWx35HNYeUgRCd1h7wI+Asf4cWugzu8RkYLfxlQrFf lcJw== X-Gm-Message-State: ALoCoQmCpvMsL/7HdksUfSNfm6yNaWKjCOfncrwSXCfLot5ZorCLOyf7oW6rtWgDxNK5xHnjW05w MIME-Version: 1.0 X-Received: by 10.60.70.40 with SMTP id j8mr7873122oeu.59.1428523221813; Wed, 08 Apr 2015 13:00:21 -0700 (PDT) Received: by 10.202.80.6 with HTTP; Wed, 8 Apr 2015 13:00:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 8 Apr 2015 22:00:21 +0200 Message-ID: Subject: Re: Dual booting FreeBSD and Win95 From: Oliver Pinter To: Ryan Stone Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2015 20:00:29 -0000 As dirty hack, try to save two state of MBR, one when FreeBSD selected (MBR.FBSD) , and one when Win95 selected (MBR.W95). When the windows booted up properly, then write the MBR.FBSD to the disc, on the same schema do the reverse on freebsd with dd. http://www.fccps.cz/download/adv/frr/wipembr.html Or just do what Adrian has said, flip the active bits with a custom tool. On Wed, Apr 8, 2015 at 9:30 PM, Ryan Stone wrote: > 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? > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"