From owner-freebsd-isdn Sun Feb 17 10:39:14 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.wish.net (server1.wish.net [212.123.130.19]) by hub.freebsd.org (Postfix) with ESMTP id CB02237B400 for ; Sun, 17 Feb 2002 10:39:07 -0800 (PST) Received: from coyote (p10342.nl.wish.net [212.123.178.102]) by mail.wish.net (8.11.4/8.11.4) with SMTP id g1HId0x07461 for ; Sun, 17 Feb 2002 19:39:01 +0100 Message-ID: <001001c1b7e2$5c594250$0200a8c0@coyote> From: "Steven Looman" To: "ISDN Mailinglist" Subject: Re: subaddr implementation Date: Sun, 17 Feb 2002 19:38:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 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