-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop-in directory for initialization scripts companion to /rw/config/rc.local #8690
Drop-in directory for initialization scripts companion to /rw/config/rc.local #8690
Comments
Although no dicsussion was made about it, not in favor or opposing to it, it follows the same methods used in for parsing I would like to ask for the label |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
How to file a helpful issue
The problem you're addressing (if any)
Currently when orchestrating QubesOS deployment, most files I change are intended for packages as they have drop-in configuration directory,
/etc/qubes/policy.d/*.policy
,/etc/ssh/sshd_config.d/*.conf
,/etc/apt/sources.list.d/*.(sources|list)
, including/rw/config/qubes-bind-dirs.d/*.conf
, but/rw/config/rc.local
does not have an equivalent.When orchestrating qubes deployment, initialization calls have to be written to
/rw/config/rc.local
, but the file can't be replaced, because there is a possibility of having user modifications in it on multiple packages managing the same file.Currently I am using Salt module
file.append
for rc.local, the only file that I am currently using this module in all my states is rc.local.The solution you'd like
I know I can create my own sourcing mechanism in rc.local
But it would be much better if this was the upstream default for packagers to not mess with user configuration.
The value to a user, and who that user might be
The value to a user is not having their configuration overriden by a packages.
The value to a packager is not having to mess with user configuratio, with an easy drop-in configuration to apply at qube boot.
The text was updated successfully, but these errors were encountered: