On 08-19-2024 05:26AM, Felix Miata wrote:
-pj composed on 2024-08-19 03:10 (UTC-0500):
On 08-19-2024 01:43AM, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing:
INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1
The first prevents multiple building of one single kernel's initrd during a zypper up or dup, deferring build until all transactions affecting initrd building and/or content have been applied.
"multiple building of one single kernel's initrd" I thought 1 initrd for each kernel no more? It rebuilds again with each installed kernel? Does this help prevent the machine from becoming non-bootable and requiring a chroot? Something going wrong with building initrd can cause grub_ blank.. and require chroot? Machine here line 579 and 580 in /etc/zypp/zypp.conf set to > ## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set multiversion.kernels = latest,latest-1,latest-2,latest-3,latest-4,latest-5,latest-6,latest-7,latest-8,latest-9,running,6.6.11-1
The second causes automatic initrd regeneration to be applied to one specific kernel, instead of all installed kernels, preventing inclusion of some possibly failing component to initrds that may have been usable when last generated.
"failing component" meaning part of initrd software included in snapshot? "applied to one specific kernel" < you mean the new kernel (included in the dup)? What can you tell me about the us of > 'dracut --regenerate-all --force' what I do think to know, is that it causes a regeneration of all the installed kernels' initrd's is that correct? Possible problem maker of sorts? Patrick Shanahan, says further in threads > subject file, environment, on tumbleweed is at /usr/etc/environment What do you think to place these variables in /usr/etc/environment and *not* in /etc/environment? Both of these directories are read during the boot process when created? -Regards