Hallo, Goffredo, Du meintest am 20.06.12: [...] > Am not saying that we *should* move the kernel away from /boot. I am > only saying that having the kernel near /lib/modules *has* some > advantages. > Few year ago there are some gains to have a separate /boot (ah, the > time when the bios were unable to address the bigger disk), where > there are the minimum things to bootstrap the system. > 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 ? Where is the big problem? I use separate subdirectories for different kernels, p.e. "/boot/ 2.6.38.4" or "/boot/3.3.4" or "/boot/3.3.4-big". And these subdirs contain (p.e.) ".config", "vmlinuz", "initrd", "System.map". It's a very clear design. No incredibly long filenames. Viele Gruesse! Helmut -- 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
