From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 64D4A158041 for ; Fri, 23 Feb 2024 17:06:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 377272BC037; Fri, 23 Feb 2024 17:05:58 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8DA85E2A0B for ; Fri, 23 Feb 2024 17:05:57 +0000 (UTC) Received: from host86-152-228-249.range86-152.btcentralplus.com ([86.152.228.249] helo=[192.168.1.99]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1rdYzj-00000000CH0-3lIA for gentoo-user@lists.gentoo.org; Fri, 23 Feb 2024 17:05:56 +0000 Message-ID: Date: Fri, 23 Feb 2024 17:05:54 +0000 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [gentoo-user] Re: How to set up drive with many Linux distros? To: gentoo-user@lists.gentoo.org References: Content-Language: en-GB From: Wols Lists In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: beab98a5-4d68-4de1-8aa3-cfb57b91409f X-Archives-Hash: d194515f204cc518f9ffbbc4a423db93 On 23/02/2024 00:28, Grant Edwards wrote: > In my experience, 's bootloader does not boot other > installations by calling other bootloaders. It does so by rummaging > through all of the other partitions looking for kernel images, intird > files, grub.cfg files, etc. It then adds menu entries to the config > file for 's bootloader which, when selected, directly load the > kernel image and initrd from those other partitions. Sometimes, it > works -- at least until those other installations get updated without > the knowlege of the distro that currently "owns" the MBR's bootloader > config. Then it stops working until you tell that bootloader to re-do > it's rummaging about routine. IME distros that try that (SUSE, anyone!) generally get confused as to which kernel belongs to which root partition. Hence needing to boot with a live distro to edit the resulting mess and get the system to actually come up without crashing ... Cheers, Wol