Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Mar 1998 07:57:35 -0800
From:      "Jordan K. Hubbard" <jkh@time.cdrom.com>
To:        Eivind Eklund <eivind@yes.no>
Cc:        hackers@FreeBSD.ORG
Subject:   Re: cvs commit: src/release/sysinstall disks.c 
Message-ID:  <22018.890323055@time.cdrom.com>
In-Reply-To: Your message of "Thu, 19 Mar 1998 16:54:39 %2B0100." <19980319165439.56949@follo.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
> 1. Install a disk using dangerously dedicated mode.
> 2. Reboot.
> 3. Select custom install.
> 4. 'fdisk' the disk, doing nothing.
> 5. Watch sysinstall come up with a full-screen request with 3 choices
>    - IIRC, "Install booteasy", "Install standard MBR", and "Do nothing
>    to my bootblock".  The default choice is either a standard MBR or
>    booteasy; I forget which.  If you don't change the default, your
>    disk is toast on 'Commit'.

Erm...  But that's exactly what I'd expect to have happen?

> I've been caught by this myself, and I've seen quite a few people
> being caught by it since.  You need to be alert and have a good
> understanding of the FreeBSD disk-layout to not get caught.

Well, yes..  But I'm not sure that this one's fixable using methods
that wouldn't in themselves be worse than the problem.

						Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22018.890323055>