Dual boot multiple fedora verions
poma
pomidorabelisima at gmail.com
Sun Nov 23 21:05:56 UTC 2014
On 23.11.2014 21:57, poma wrote:
> On 23.11.2014 21:47, Chris Murphy wrote:
>> On Sun, Nov 23, 2014 at 1:40 PM, poma <pomidorabelisima at gmail.com> wrote:
>>
>>> Sure,
>>> shared single /boot with a extlinux/extlinux.conf
>>
>> That's a good idea also. Single /boot means one grub.cfg or
>> extlinux.conf. And the kernels each have distinct naming conventions
>> between distro versions so no conflicts there. Grubby will update the
>> menu entries when new kernels are installed.
>>
>
> /boot/extlinux/extlinux.conf
> ui menu.c32
> menu title The EXTLINUX bootloader
> timeout 50
>
> label Fedora (3.17.3-300.fc21.x86_64) 21 (Twenty One)
> kernel /vmlinuz-3.17.3-300.fc21.x86_64
> append root=UUID=...
> initrd /initramfs-3.17.3-300.fc21.x86_64.img
>
> label Fedora (3.17.3-300.fc21.i686) 21 (Twenty One)
> kernel /vmlinuz-3.17.3-300.fc21.i686
> append root=UUID=...
> initrd /initramfs-3.17.3-300.fc21.i686.img
>
> label CentOS Linux (3.10.0-123.9.3.el7.x86_64) 7 (Core)
> kernel /vmlinuz-3.10.0-123.9.3.el7.x86_64
> append root=UUID=...
> initrd /initramfs-3.10.0-123.9.3.el7.x86_64.img
>
> label Memtest86+ 5.01
> kernel /memtest86+-5.01
>
> label BFO boot.fedoraproject.org - iPXE
> kernel /ipxe.lkrn
>
> Yeah,
> of course should be done for each new installation - the initial entry point and that's it, the rest is covered via grubby.
>
The initial *manual* entry, not via anaconda.
Anaconda's bootloader tampering with each new installation is expressly excluded!
More information about the users
mailing list