Date: 26 Jan 2002 13:25:45 -0800 From: swear@blarg.net (Gary W. Swearingen) To: David Schultz <dschultz@uclink.Berkeley.EDU> Cc: freebsd-chat@FreeBSD.ORG Subject: Re: Why dual boot? Message-ID: <y4wuy46bza.uy4@localhost.localdomain> In-Reply-To: <20020126003431.A77505@HAL9000.wox.org> References: <3C4FBE5C.2AE8C65@mindspring.com> <20020123114658.A514@lpt.ens.fr> <20020123223104.SM01952@there> <3C4FBE5C.2AE8C65@mindspring.com> <4.3.2.7.2.20020124213809.00e6e5d0@localhost> <20020125131659.GB7374@hades.hell.gr> <3C51CD33.4E69B204@mindspring.com> <001b01c1a635$636a4170$0a00000a@atkielski.com> <20020126003431.A77505@HAL9000.wox.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'd be great to have an automatic multiple-booterizer, but I think there are better things to develop, mainly because I think the number of people who should use it would be small. Few (mostly laptop users) with M$Win installed can't easily buy a cheap, small, even used, second disk for a dedicated FreeBSD install. Few of them should risk loosing their M$Win when moving it around on the disk. Very few of them would be willing to back up or able to restore their M$Win. Even those who ARE willing will spread the news that FreeBSD blew out their M$Win when it happens due to bugs or drained battery or other hardware failure. Most of those few who can't use a dedicated disk can at least get a good taste of FreeBSD by booting off a CDROM into a memory-based FreeBSD. That experience could be greatly improved if someone would make one of those systems that puts FreeBSD filesystems into M$Win files (which has likely already been done), esp. if they could write some M$Win code to pre-size the fs files and run the defragger before making the FS in the file during the FreeBSD install. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y4wuy46bza.uy4>