Am Donnerstag, 21. Juni 2012 schrieb Goffredo Baroncelli: > > > > > >> Now we have the possibility to move the kernel near the modules, and > >> this could lead some interesting possibility: think about different > >> linux installations, with an own kernel version and an own modules > >> version; what are the reasons to put together under /boot different > >> kernel which potential conflicting names ? de facto standard ? > >> historical reasons ? Nothing wrong here; but also the idea to moving > >> the kernel under /lib/modules is not so wrong. > > > > > > > > No, it is completely, totally and very very seriously wrong. > > When a bootloader (and the bioses) will be able to address the whole > diskS, this will change.. Not now Why not the other way around? /boot/modules-3.4 or so. But either way, these are different discussions. H. Peter´s question was, if I understood correctly, whether to use subvolid or path? I tend to lean towards subvolid. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
