Date: Mon, 31 Jan 2005 14:21:16 +0400 From: Rakhesh Sasidharan <rakhesh.s@gmail.com> To: "Loren M. Lang" <lorenl@alzatex.com> Cc: Joe Kraft <hishadow@netcabo.pt> Subject: Re: Booting FreeBSD-5.3 from NTLDR Message-ID: <38b3f6e405013102211008416f@mail.gmail.com> In-Reply-To: <20050131101152.GA8619@alzatex.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> <20050131101152.GA8619@alzatex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
So that means I should install boot0 to the MBR of my second disk, using boot0cfg with the "-o noupdate" flag, and then extract that MBR (using "dd" for instance) to a file like c:\bootsectbsd? That should work? Or wait, maybe there's no need to extract. When I install boot0 to the MBR, possibly the boot0 file modified also, and so I just need to copy that to c:\bootsect.bsd and then boot using NTLDR. Right? On Mon, 31 Jan 2005 02:11:52 -0800, Loren M. Lang <lorenl@alzatex.com> wrote: > On Mon, Jan 31, 2005 at 11:59:11AM +0400, 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? > > > > You can disable this behavior of boot0 when you install the MBR on the > second disk using the "-o noupdate" argument to boot0cfg. > > > > > -- > > Rakhesh > > rax@rakhesh.com > > -- > 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 > > -- -- Rakhesh rax@rakhesh.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38b3f6e405013102211008416f>