Date: Tue, 07 Jul 2015 15:57:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194077] Improper enumerate ada (da) device ID in 10.1-R Message-ID: <bug-194077-8-10KyatOZiF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194077-8@https.bugs.freebsd.org/bugzilla/> References: <bug-194077-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194077 --- Comment #3 from Alexander Motin <mav@FreeBSD.org> --- The new device naming scheme was introduced several years ago simply because previous one was not working for more complicated configurations with port multipliers, etc. People for whom old device<->port binding was critical can still manage it via loader tunables, as described in cam(4). Though better way to handle this is via using some kinds of on-disk metadata, such as partition labels, etc. There are GEOM providers with disk serial numbers, if you wish to go that way and mount file systems via disk serial numbers, though I personally don't like that. Requested wiring of boot device to ada0 is problematic, since there is no any relations between boot device numbering in BIOS and one detected by system. While it is odd, technically it is possible to boot from one device, while mount root from another. People in embedded environments do this sometimes. Wiring of device number to serial number is currently not supported, though it probably can be implemented. At this point FreeBSD has no any cross-reboot persistent database to store device mapping (is not count loader tunables). You may say that it is bad, but there are other opinions -- for example, that properly configured system will work fine independently of hardware it is booting on. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194077-8-10KyatOZiF>