From owner-freebsd-bugs@freebsd.org Mon Jun 27 20:31:50 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C53E7B85003 for ; Mon, 27 Jun 2016 20:31:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B505B2C99 for ; Mon, 27 Jun 2016 20:31:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5RKVoGH085248 for ; Mon, 27 Jun 2016 20:31:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210572] Installer does not fully identify discs in multiple-disc system Date: Mon, 27 Jun 2016 20:31:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: scratch65535@att.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 20:31:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210572 --- Comment #2 from MMacD --- I always take option 1, the guided MBR thing. Which only shows the useless model numbers.=20=20 I do that in part that's because my field is human factors, so I do what new people do because that's where the problems show up quickest. The people w= ho wrote the installer are experts, and it's pretty much impossible without a = lot of training for an expert to remember how it was to be a novice. So they do things that seem perfectly sensible to them, but which confuse and derail anyone new. (For broadly the same reason, whenever I'd do QA, I'd always go after the boundary conditions because I'd invariably find bugs, which would enrage the dev and product managers. But I was the program manager so they didn't say too much) Would it really be hard to migrate the information from the part table edit= or?=20 It doesn't seem like it would be - the code already exists and it's not as = tho the installer has to fit in rom - but I've not looked at the code. It really is a bug, if you want people to be able to reliably use that opti= on even under boundary conditions. --=20 You are receiving this mail because: You are the assignee for the bug.=