On 04/26/2013 09:03 PM, Tejun Heo wrote: > hey, > > On Thu, Apr 25, 2013 at 05:12:20PM -0500, scame...@beardog.cce.hp.com wrote: >> It looks like these are called from a function called init_device_map() >> that is called from grub_stage2() at least in the version of grub I looked >> at (0.97, from rhel6). >> >> So my assumption is that adding a new block driver with yet another name >> space >> would require adding another bit of code into grub like those above. When I >> asked about "best practices" for new block driver device names on the grub >> devel >> mailing list to minimize required changes to grub, nobody argued against that >> assumption. > > I think we kinda need to get down to the root cause of the issue. > Nothing against giving common names to devices in itself but there's a > non-insigificant chance that we end up with something half-way if the > original problem isn't properly understodd. > Oh, the problem _is_ well understood.
It's the design of grub :-) grub requires you to re-implement _every_ device naming scheme which is present in the kernel. And no, you cannot use the kernel itself as grub is run _prior_ to the kernel. As there is no common naming scheme for block devices each and every block device driver has implemented it own. So grub need to re-implement each and every device naming for these drivers. The approach from Stephen would solve that. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
