Date: Mon, 31 Jan 2005 02:35:23 -0800 From: "Loren M. Lang" <lorenl@alzatex.com> To: rax@rakhesh.com Cc: Mark Ovens <marko@freebsd.org> Subject: Re: Booting FreeBSD-5.3 from NTLDR Message-ID: <20050131103523.GC8619@alzatex.com> In-Reply-To: <38b3f6e40501310216de768e@mail.gmail.com> References: <38b3f6e40501292247696b96b@mail.gmail.com> <38b3f6e4050129231132f8e743@mail.gmail.com> <41FCA314.3070602@netcabo.pt> <38b3f6e4050130033551e43818@mail.gmail.com> <20050130120618.GA21695@alzatex.com> <38b3f6e4050130235957c049c2@mail.gmail.com> <41FDEFE7.1090204@freebsd.org> <38b3f6e40501310216de768e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 31, 2005 at 02:16:25PM +0400, Rakhesh Sasidharan wrote: > Thanks for that link! I had read that part of the handbook a long time > ago, and that's how my ideas of boot0 and boot1 and etc etc had gotten > clear. Glad to see it once again -- in the context of my question! :)) > > So what I understand now is -- copying boot0 over to c:\bootsect.bsd > will *not* work. Which explains why my MBR got messed up when I tried > booting FreeBSD this way. :( > > But I'm still confused. How do I install boot0 using sysinstall? As > far as I remm, sysinstall gives three options -- (a) leave the MBR > untouched, (b) put a standard MBR, and (c) install BootEasy. My > understanding is that option (b) copies boot0 to the MBR, and this > that is what I had chosen while installing FreeBSD. How does one copy > boot0 to a file using sysinstall?? I think option b is actually /boot/mbr and BootEasy refers to /boot/boot0. They are two different boot loaders, mbr being a very simple one with no configuration. I think fdisk -B is used to install /boot/mbr to the mbr of a harddisk and boot0cfg is used to install BootEasy. > > > On Mon, 31 Jan 2005 08:44:23 +0000, Mark Ovens <marko@freebsd.org> wrote: > > Rakhesh Sasidharan wrote: > > >> No, boot0 is just a normal file that is 512 bytes long. There is > > >> nothing special about it. In it is a bootloader program that can be > > >> used to boot FreeBSD, and if you run it during boot, it will read the > > >> partition table and look for all OSes. I think it will modify the > > >> partition table, though, marking the last OS you booted into, but that's > > >> the program running doing that, the file itself is harmless. > > > > > > Ok. I must have used some other command then, which resulted in my > > > first disk MBR getting over-written ... strange. :-/ > > > > > > By the way, does the fact that NTLDR is on my first disk, while > > > FreeBSD (and hence its MBR boot0) is on my second disk complicate > > > matters? I mean, you mention boot0 will modify my partition table to > > > reflect which OS was booted last -- will it by any chance modify the > > > partition table on the first disk and hence mess it? > > > > > > > > > > Yes and yes, > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER > > > > Regards, > > > > Mark > > > > --- > > avast! Antivirus: Outbound message clean. > > Virus Database (VPS): 0504-4, 28/01/2005 > > Tested on: 31/01/2005 08:44:24 > > avast! - copyright (c) 2000-2004 ALWIL Software. > > http://www.avast.com > > > > > > > -- > -- Rakhesh > rax@rakhesh.com > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050131103523.GC8619>