Is *_kver=$(ls /usr/lib/modules) OK?

Scimmia · 2025-12-19 14:04:35

jebez wrote:

In computer science, in general, when a setting is not set, there must be a default.

Wrong. Just plain wrong. Don't take your personal bullshit and think it applies 'in general'.

seth · 2025-12-19 14:21:44

◉ rm                    
rm: missing operand
Try 'rm --help' for more information.

So would you suggest that rm should always default to "-rf /" because there is generally a default?
The default position in computer science is EBKAC.
In this case it happens to be your chair.

I assume you're trying to achieve *something* here, but even your local attempt is based on a weak assumption and poorly executed so there's an epic chance for a classical https://en.wikipedia.org/wiki/XY_problem
Walk ten steps back and take another look at the fork where you branched into this dead end.

jebez · 2025-12-19 15:21:43

Seeing the shell script /usr/bin/mkinitcpio &
/etc/mkinitcpio.d/linux.preset with a wrong *_kver value:

ALL_kver=*
PRESETS=
_uki=/efi/efi/boot/bootx64.efi

[a@archlinux ~]$ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: ''
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k * -U /efi/efi/boot/bootx64.efi
==> ERROR: '/lib/modules/*' is not a valid kernel module directory

: mkinitcpio searches in /usr/lib/modules , so why not a default?

There's the option *_uki .

Anyway ALL_kver=$(ls /usr/lib/modules) works for me.

I feel the same crap of Feature request: F2FS support for the BIOS https://bbs.archlinux.org/viewtopic.php?id=302708 with the same useless (but lot of posts) guy pretending F2FS is a bad idea so well bye, before this topic goes to Dustbin.

loqs · 2025-12-19 15:31:24

jebez wrote:

I feel the same crap of Feature request: F2FS support for the BIOS https://bbs.archlinux.org/viewtopic.php?id=302708 with the same useless (but lot of posts) guy pretending F2FS is a bad idea so well bye, before this topic goes to Dustbin.

Please consider common to both threads is your contention that your use case should be used to define the default.

seth · 2025-12-19 15:36:54

ALL_kver=*

And what's that supposed to be? And why?

I feel the same crap of Feature request: F2FS support for the BIOS

a) why would you direct such request for the BIOS at any OS instead of your board vendor? (Though this would require changes to the EFI standard about the ESP)
b) who is "pretending" that "F2FS is a bad idea"? Scimmia told you that

The extra features of f2fs are already taken care of by the controller on SSDs, it's only beneficial on dumb flash storage like USB flash drives or SD cards.

jebez · 2025-12-19 15:48:08

Read entirely my previous post, it's just a test.

a) as my config in my signature, the BIOS UEFI of my PC supports FAT (the EFI standard) & NTFS, I can boot NTFS! So why not F2FS, I think the BIOS memory has space for this, or replace NTFS of micro$oft by F2FS...
b) "There is no benefit to f2fs on SSDs that other major linux filesystems don't already do."

Last edited by jebez (2025-12-19 15:48:38)

loqs · 2025-12-19 15:52:20

jebez wrote:

a) as my config in my signature, the BIOS UEFI of my PC supports FAT (the EFI standard) & NTFS, I can boot NTFS! So why not F2FS, I think the BIOS memory has space for this, or replace NTFS of micro$oft by F2FS...
b) "There is no benefit to f2fs on SSDs that other major linux filesystems don't already do.

Already answered in detail in the dust binned thread.

Arch Linux

#26 2025-12-19 14:04:35

Re: Is *_kver=$(ls /usr/lib/modules) OK?

#27 2025-12-19 14:21:44

Re: Is *_kver=$(ls /usr/lib/modules) OK?

#28 2025-12-19 15:21:43

Re: Is *_kver=$(ls /usr/lib/modules) OK?

#29 2025-12-19 15:31:24

Re: Is *_kver=$(ls /usr/lib/modules) OK?

#30 2025-12-19 15:36:54

Re: Is *_kver=$(ls /usr/lib/modules) OK?

#31 2025-12-19 15:48:08

Re: Is *_kver=$(ls /usr/lib/modules) OK?

#32 2025-12-19 15:52:20

Re: Is *_kver=$(ls /usr/lib/modules) OK?

Board footer