Skip to content

Conversation

@ahesford
Copy link
Member

@ahesford ahesford commented Jan 9, 2026

This is a rough sketch for now. It could use a bit of refining, and zfsbootmenu-preview is unaware of the selected kernel, which means that the kernel version never updates in the header and, now, neither does the KCL.

I think I've worked out the kinks, and everything respects the changing kernel.

@ahesford ahesford marked this pull request as draft January 9, 2026 03:59
@ahesford ahesford force-pushed the who_jacked_da_fuckin_truck branch 5 times, most recently from 5d0c302 to b316a82 Compare January 10, 2026 18:03
@ahesford ahesford marked this pull request as ready for review January 10, 2026 23:26
@ahesford ahesford force-pushed the who_jacked_da_fuckin_truck branch from b316a82 to d1576b1 Compare January 11, 2026 15:58
Copy link
Member

@zdykstra zdykstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the new /zfsbootmenu/$environment/kcl directory structure, should the value derived from OS initramfs defaults/ZFS property that's currently stored as /zfsbootmenu/$environment/cmdline be moved under the kcl/ directory to have them all in a single place? There's no way that filenames will conflict.

cat <<EOF
ENTER A NEW KERNEL COMMAND LINE
- Interrupt with Ctrl+C or specify an empty line to cancel input
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is sorta unrelated to the PR, but how do we handle the user wanting an empty KCL so that the internal default for the detected initramfs is used? Ideally an empty line should be accepted and not used to cancel input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants