On 06/21/2012 01:46 PM, Martin Steigerwald wrote: > 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? > For which ? If you want to point the bootloader subvolume (where the 2nd stage relies), I suggest subvolid=. If you need to point to the kernel (bzImage/initrd) *for my setup* it would be useful to use the path. Unfortunately these two requirements are in contrast. > I tend to lean towards subvolid. > > Ciao, Ciao Goffredo -- 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
