| Summary: | RFE: Allow multiple systemd.unit= directives on the kernel cmdline, and support systemd.mask= to runtime mask a unit for one boot | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Orion Poplawski <orion> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
| Severity: | enhancement | ||
| Priority: | medium | CC: | mbiebl |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Orion Poplawski
2013-07-19 20:05:55 UTC
I am not convinced it is a good to allow them to be enabled/disabled via the command line. But I think it would make sense to optionally runtime *mask* units (this feature has been on the TODO list for a while) and to add them to the initial transaction. This should be equally useful, but in its effect it more comprehensive. Yeah, I wasn't asking for the ability to permanently enable/disable - just for the initial boot process. What about allowing multiple systemd.start= and systemd.mask=? Yes, allowing multiple systemd.unit= and systemd.mask= would be the way I'd like to see this implemented! What we have now in place in git is: systemd.mask= as described and: systemd.wants= which adds additional units into the initial transaction. THis is different from starting multiple units in one transaction, as systemd.unit= is still clearly the primary one, and systemd.wants= just integrates into its dependency tree. Anyway, this should be fixed. Closing. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.