It seems to me that dual boot made much more sense a few years back when drives were expensive. But at this point, if you want to run multiple OSs, why not just keep them on two separate drives so they don't wind up inadvertently stomping on each other? I remember I had problems with my dual-boot install getting things so that netbsd wouldn't corrupt the pre-existing TOS install. I also remember seeing some guidance saying to just avoid AHDI compatible partitioning if at all possible.
David Ross dross%pobox.com@localhost----- Original Message ----- From: "David Brownlee" <abs%NetBSD.org@localhost>
To: "David Ross" <dross%pobox.com@localhost>Cc: "T. Makinen" <tjamaloo%gmail.com@localhost>; <f.g.lukas%web.de@localhost>; <port-atari%netbsd.org@localhost>
Sent: Wednesday, February 04, 2009 1:58 PM Subject: Re: netbsd-5 install from unmounted gemdos filesystem
On Wed, 4 Feb 2009, David Ross wrote:Final question: Does prepare.fs.gz *do* anything that sysinst.fs.gz doesn't anymore? Disk partitioning / labelling / anything?I booted it up once just to see what it did. It looked potentially useful for disk partitioning, maybe for some AHDI related scenarios (dual boot) or something like that. But sysinst does everything I need. IMO, it's definitely worth considering removing it at this point if nobody sees a need to keep it around.Hmm, sysinst covers dual boot setup on other ports, so that functionality should ideally be moved across. I think we'll leave it for now. Maybe once NetBSD 5 is out and you have some spare time you could try testing a dual boot install to see what we need to fix there? :) -- David/absolute -- www.NetBSD.org: No hype required --