... although having scripted the fdisk on openbsd quite nicely so I can't screw it up, proceeed to forget that windows numbers partitions starting at 1, not 0, in diskpart, and am now digging for a usb stick and kicking myself in the ass..
Someone good at windows could take pity on me and mail me a batch fie to activate partition *3* on disk 0 with diskpart :) I might even buy them a beer or 13 for it. On Fri, Mar 7, 2014 at 11:43 AM, Bob Beck <b...@obtuse.com> wrote: > Why I hadn't thought of going back to that I don't know.. It actually > works better for me since I don't then normally have to wait for the > windows bootloader screen... as at least in my case 90% of the time > the laptop runs OpenBSD.. > > Of course now after testing it I have to wait for windows to finish > installing update because I haven't booted it in too long.. > > On Fri, Mar 7, 2014 at 11:27 AM, Kenneth Westerback > <kwesterb...@gmail.com> wrote: >> On Mar 7, 2014 1:10 PM, "Wade, Daniel" <dw...@meridium.com> wrote: >>> >>> I've been dual booting for years and never once use dd to copy the >> openbsd.pbr >>> If I'm in windows world and want to boot into OpenBSD I run diskpart and >> flip the active partition. >>> Same in the other direction, fdisk -e and flip the active back to windows. >> >>> I am my own boot manager. >> >> Dude, we need a Daniel mode in mg just to keep that line alive! :-) >> >> .... Ken >> >>> >>> >>> >>> -----Original Message----- >>> From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf Of >> Bob Beck >>> Sent: Friday, March 07, 2014 12:15 PM >>> To: Theo de Raadt >>> Cc: Mark Kettenis; Stuart Henderson; Jean-Philippe Luiggi; OpenBSD >> technical list >>> Subject: Re: 5.5 and dual-boot >>> >>> It will affect everyone who needs windows on a laptop for work - or >>> filling out pdf forms for foundations, things like that. >>> >>> It is a good way to ensure snaps get tested less on real hardware. >>> >>> On Fri, Mar 7, 2014 at 10:13 AM, Theo de Raadt <dera...@cvs.openbsd.org> >> wrote: >>> >> actually more painful than having to boot windows is to always have >>> >> something handy to boot the snap from in order to dd the bootblock off >>> >> in case you forget to do it before rebooting, or you're fucked. >>> > >>> > The new installboot was enabled around a month ago. The issue is only >>> > being talked about now. >>> > >>> > Apparently... this dual-boot issue is only seen now, indicating that >>> > these people don't upgrade very often, or participate in the test >>> > cycles leading up to release. >>> > >>> > Hey, I get it. Just let's not over-estimate how many people this will >>> > affect. >>> >>>
