Date: Thu, 19 Mar 1998 09:44:58 -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: <22578.890329498@time.cdrom.com> In-Reply-To: Your message of "Thu, 19 Mar 1998 17:15:25 %2B0100." <19980319171525.25110@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Give the poor users a break! They just select a disk, go through > everything selecting the defaults (which work, until the install is > complete). Then they reboot, and nothing work - their disklabel is > hosed. > > This isn't even close to satisfying POLA. I didn't say it was a good thing, simply that the problem has been known for some time and it's not hard to see how and where it would happen. This has been around since at least 2.2.1, so if it doesn't get fixed for 2.2.6 (which is coming up very soon here, in case nobody noticed ;) then I'm not going to get especially choked up over it. > Uhm? As far as I can tell, this just requires not writing the > bootblock if a disk is dangerously dedicated. This is information > that should be easily available from libdisk - unfortunately, I > couldn't find an easy way to get it. Is there some interaction here > that I'm overlooking? I couldn't find any easy way to get at it either. If Poul-Henning has some suggestions? 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?22578.890329498>