On Wed, Aug 24, 2016 at 03:16:21PM +0200, Bertram Scharpf wrote: > > > But yet it was too late. The partition table was > > > overwritten. > > The bug is not a concrete misbehaviour but the trap it is > setting up.
This is beginning to sound ever more like lack of preparation for the task at hand. The FAQ entry somebody else posted earlier contains enough hints, had you read it, that you would have known that some preparation was necessary. But then you don't actually tell us what you did in any detail, only that whatever it was you attempted to do failed. If you expect any kind of help beyond what's already in the FAQ, you need to do better. As in, tell us exactly what you did, with all details and in the proper (actual) sequence. Otherwise you're just generating noise. And quite frankly, beyond some very limited and short-lived use cases, I don't see much point in multibooting at all, given the amount of work (developer resources) it tends to consume. Other OS projects possibly have other priorities and the resources to pour into making multibooting easier for the uninitiated, for OpenBSD it's pretty clear that multibooting is a special case that's not considered terribly useful to the majority of its users. OpenBSD runs surprisingly well on even dated hardware and under several of the common virtualization thingies that are available given recent-ish hardware. If what you want is to try out OpenBSD in some limited setting, I'd strongly recommend either getting some hardware you don't care about too much or spin up a VM in a virtualization setup you're comfortable with. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
