From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (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 finch.gentoo.org (Postfix) with ESMTPS id 95C6B1581F0 for ; Fri, 24 Jan 2025 18:44:51 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 7F74434356F for ; Fri, 24 Jan 2025 18:44:51 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 6C8AE110436; Fri, 24 Jan 2025 18:44:07 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id A8D3411042D for ; Fri, 24 Jan 2025 18:44:06 +0000 (UTC) Received: from [IPV6:2a02:a45a:ca9b::aa5] (2a02-a45a-ca9b--aa5.fixed6.kpn.net [IPv6:2a02:a45a:ca9b::aa5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: nowa) by smtp.gentoo.org (Postfix) with ESMTPSA id 19C703434FE for ; Fri, 24 Jan 2025 18:44:05 +0000 (UTC) Message-ID: <048be8f3-47ba-4022-b9c7-d5f2d51b0a63@gentoo.org> Date: Fri, 24 Jan 2025 19:44:04 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: [gentoo-dev] 2025-xx-yy-dracut-hostonly: new news item Content-Language: en-US, nl-NL References: <053f1ce9-7afb-4d29-94fa-fb122bd398a8@gentoo.org> To: gentoo-dev@lists.gentoo.org From: Nowa Ammerlaan Organization: Gentoo Linux In-Reply-To: <053f1ce9-7afb-4d29-94fa-fb122bd398a8@gentoo.org> X-Forwarded-Message-Id: <053f1ce9-7afb-4d29-94fa-fb122bd398a8@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: e6c15736-2d3f-4d7e-85c8-077fb8f12bae X-Archives-Hash: 1073290ca42006a8935bd2633d5bd77e To be published whenever the next version of Dracut is released and pushed into ::gentoo. Upstream has changed the default setting for hostonly in the kernel-install hook. I do not expect huge problems, but there might be some weirdness on more unusual systems. I do anticipate some confusion since the default has only changed in the kernel installation hooks, and not when Dracut is invoked directly. I hope that this situation will be resolved in the future, in the meantime this news item should help clarify what is going on. Enabling hostonly was already our (and upstreams) recommendation on the wiki. Please let me know if the below is clear. See-also: https://github.com/dracut-ng/dracut-ng/pull/1158 Best regards, Nowa Title: Dracut changed default for hostonly setting Author: Nowa Ammerlaan Posted: 2025-xx-yy Revision: 1 News-Item-Format: 2.0 Display-If-Installed: sys-kernel/installkernel[dracut] Dracut is an initramfs generation tool. It may be invoked via the installkernel mechanism in order to automatically generate a new initramfs when the kernel is installed. If you are reading this then sys-kernel/installkernel is configured to use Dracut and the below is relevant for you. What changed? ==================== Starting with version 106 of sys-kernel/dracut the default for the "hostonly" setting has changed from disabled to enabled when Dracut is invoked via installkernel[1]. "hostonly" is a setting for Dracut that controls how much is included in the generated initramfs image. When it is disabled Dracut aims to generate an initramfs image that is bootable on any hardware. On the other hand, when this setting is enabled, Dracut aims to generate an initramfs image containing only what is needed to boot the current system. The advantage is a significantly smaller initramfs images, but this comes with the cost of losing portability. Example: When the "hostonly" setting is disabled, Dracut's drm module will cause all GPU drivers to be included in the initramfs. When it is enabled, only the drivers for GPUs that are currently present in the system are included in the initramfs. Enabling the "hostonly" setting was and is our recommendation for most use cases. This however was not the default behaviour in versions prior to 106. Note, the default value for the "hostonly" setting has changed only when Dracut is invoked via installkernel. Disabled remains the default behaviour when Dracut is invoked directly. User Action Required ==================== If your system is already configured to enable "hostonly" setting via /etc/dracut.conf.d/ then effectively nothing has changed for you. However, if Dracut has previously not been configured to enable the "hostonly" setting, then starting with version 106 the behaviour of Dracut will change for you. Though we do not expect major problems, we recommend ensuring a backup booting option remains available before rebooting the system after the first kernel upgrade following the upgrade of Dracut. This is usually the case unless the old kernels are manually removed by the user. If you do experience a booting problem with the "hostonly" enabled initramfs images, then please report this problem to Dracut[2]. The "hostonly" setting may be disabled via /etc/dracut.conf.d/ configuration snippets. For example: echo "hostonly=no" >> /etc/dracut.conf.d/95-no-hostonly.conf [1] https://github.com/dracut-ng/dracut-ng/pull/1158 [2] https://github.com/dracut-ng/dracut-ng/issues