Skip to content

feat: compile time config parity for existing runtime settings - #33

Merged
RoyalOughtness merged 5 commits into
secureblue:livefrom
RoyalOughtness:morealreadydisabledstuff
Sep 30, 2026
Merged

RoyalOughtness merged 5 commits into
secureblue:livefrom
RoyalOughtness:morealreadydisabledstuff

Conversation

@RoyalOughtness

Copy link
Copy Markdown
Contributor

No description provided.

@RoyalOughtness RoyalOughtness changed the title Morealreadydisabledstuff feat: compile time config parity for existing runtime settings Sep 28, 2026

@HastD HastD left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

These modules being disabled is something users can opt out of, while the modules being compiled out of the kernel is not. Are any of these modules something that there could reasonably still be a use-case for on a secureblue image?

@RoyalOughtness

Copy link
Copy Markdown
Contributor Author

These modules being disabled is something users can opt out of, while the modules being compiled out of the kernel is not. Are any of these modules something that there could reasonably still be a use-case for on a secureblue image?

reasonably? no, not really. These ports either don't have a desktop use or haven't been manufactured in 3 decades

@RoyalOughtness
RoyalOughtness merged commit 5da6a6f into secureblue:live Sep 30, 2026
3 checks passed
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