Summary: | Installer does not fully identify discs in multiple-disc system | ||
---|---|---|---|
Product: | Base System | Reporter: | MMacD <scratch65535> |
Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed Not A Bug | ||
Severity: | Affects Some People | CC: | amd64, nwhitehorn |
Priority: | --- | ||
Version: | 10.3-STABLE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
MMacD
2016-06-25 14:27:58 UTC
It does show them, in detail, if you enter the partition editor. I always take option 1, the guided MBR thing. Which only shows the useless model numbers. 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 who 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 editor? 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 option even under boundary conditions. (In reply to MMacD from comment #2) There is no technical issue in showing anything we like. The issue is what to show: if you print the whole partition table, you just end up with the normal partition editor again and don't really solve anything. I can't think of something less than that that covers all the cases, however. In general, I would also imagine that most people going through the automatic mode only have one hard drive anyway. |