Re: "linux6.5: configured successfully" without initramfs

[Jipok <Jipok@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

New comment by Jipok on void-packages repository

https://github.com/void-linux/void-packages/issues/46006#issuecomment-1712952544

Comment:
> the current release of ZFS doesn't support 6.5

I know. This question is not about ZFS, but about the frustration associated with the inability to boot into the system after a “successful kernel update”. It’s not just the ZFS that can produce an error.

> it is kinda important to know what your system is doing, especially for updates. 

You can't say this seriously. I have my PC and home server. Both with void, both are updated on average once every couple of weeks. The number of logs you propose to view exceeds my ability to meaningfully read the logs. There are much more interesting and productive things in life than reading the logs of the next update simply because somewhere there may be a hint of a malfunction. And I'm sure that about 99.9% of void users, if they look at the update logs, then only briefly and conspicuous things. For example, a message that the kernel is not installed due to errors. At the end of the logs and preferably highlighted in red.

> having a hook fail and causing an xbps operation to stop in the middle would be much worse, leading to issues with lots of half-configured packages

I believe there may be specific cases where ignoring errors is useful. Well then you need at least an exception for the kernel.