From owner-freebsd-isdn Mon Feb 18 0:22:15 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mailhost2.dircon.co.uk (mailhost2.dircon.co.uk [194.112.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 630B237B425 for ; Mon, 18 Feb 2002 00:21:48 -0800 (PST) Received: from dircon.co.uk (webmail.dircon.net [194.112.32.35]) by mailhost2.dircon.co.uk (Postfix) with SMTP id 11D3B63000; Mon, 18 Feb 2002 08:21:47 +0000 (GMT) Date: Mon, 18 Feb 2002 08:21:47 -0000 To: "Steven Looman" , "ISDN Mailinglist" Subject: Re: subaddr implementation From: "Clem Dye" X-Mailer: Webmail 2.6.2 In-Reply-To: <001001c1b7e2$5c594250$0200a8c0@coyote> Reply-To: clem@bastet.com Message-Id: <20020218082147.11D3B63000@mailhost2.dircon.co.uk> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I boot FreeBSD 4.1 using the Windows 2000 bootloader. I used a utility called BootPart from Gilles Vollant to create the FreeBSD boot sector file. My config has FreeBSD as the second partition on my system's first disk. I haven't tried using it in any other configuration. HTH Clem Steven Looman said: > The partition didn't die, I just cannot boot from it anymore (boot0 > (in the mbr) "runs", and then has to load boot1 from the freebsd > partition. This doesn't work, just a mere beep. I can use it when I > use the fixit disk (actually booting from a 4.4-RELEASE cd, I am > running -CURRENT btw). Everythings runs normally (the console > has some problems tho, but i guess that is is normal). > > I hadden't thought of the about booting freebsd from the NT > bootloader. It is a dirty fix, but what the hell, if it works it works ;) > > Steven > > ----- Original Message ----- > From: "Gerhard Sittig" > To: "ISDN Mailinglist" > Sent: Sunday, February 17, 2002 12:16 PM > Subject: Re: subaddr implementation > > > > [ OT for -isdn, feel free to ignore this, to not reply or > > to reply by means of PM. Thank you! ] > > > > On Sat, Feb 16, 2002 at 23:10 +0100, Gary Jennejohn wrote: > > > > > > "Steven Looman" writes: > > > > > > > > [ FreeBSD "gone" (not bootable) after installing Win* ] > > > > > > You installed winxp _after_ you installed FBSD ? BIG mistake !!! > > > I did something similar once. Winblows merrily overwrites all the > > > partition information. I think I ended up having to reinstall > > > FBSD. > > > > Wait! It doesn't have to be this bad! > > > > Although MS is known for the "every PC runs Win" and the "Win > > installations are the only system on a computer, there cannot > > be anything else to make sense" attitudes, only the "smaller" > > Windows versions are really sick in this respect. But the NT > > versions somehow could vaguely imagine that there can be > > something else. And they can even be taught to cooperate with > > a second, third, ... system. :) > > > > To cut it short: most MS installations "only" overwrite your > > boot sequence (because you don't want to choose when you install > > MS software, do you?). So I suggest you start a live system or > > a rescue (fixit) floppy/image and run "fdisk", "disklabel -r", > > "mount -o" and the other navigation commands to check if your > > partitions are still there and hold the data you would like > > them to. > > > > Hooking an OpenSource UNIX into the NT boot loader always has > > been as easy as "dd bs=512 count=1" your UNIX' boot partition > > to a regular file on the MS partition and adding another menu > > option to the boot.ini file. Only when you insist in running > > LILO you either have to mirror this boot block again after > > running the lilo command (i.e. rebuilding and installing your > > kernel) or you have to point lilo.conf to the mirrored file > > instead of the MBR / partition boot record on disk (that would > > be what I would call more natural, since you boot Linux from > > the NT loader and not from BIOS). I've never seen a machine > > with both NT and FreeBSD on them (all of my machines are > > dedicated to FreeBSD only), but I guess there's no difference > > here. It doesn't seem to matter how you get to the partition's > > boot record, as long as you finally do somehow. After that > > FreeBSD should startup fine as it usually does. > > > > > > But if you "installed" from an OEM recovery CD that's a totally > > different matter: These don't install something but merely > > mirror back an image to your harddrive just like they do in > > their plant when filling an empty disk with what comes bundled > > when you unpack your PC after the purchase. That's when all hope > > is lost (even "fixing" your running Windows this way makes you > > lose all your data and applications which didn't come with the > > recovery media, i.e. from the hardware vendor). But you wouldn't > > confuse a recovery CD with an installation or rescue system, > > would you? > > > > > > virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 > > Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net > > -- > > If you don't understand or are scared by any of the above > > ask your parents or an adult to help you. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isdn" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message