write_files should not be curtin_hooks
Bug #1373964 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Confirmed
|
Low
|
Unassigned | ||
curtin (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
the 'write_files' portion of curtin is currently executed via curtin hooks.
That means that if a OS image provides its own curtin hooks, that would have to explicitly implement the write_files.
It seems like this might make sense to be always run after the extraction.
Changed in curtin (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in curtin: | |
status: | New → Confirmed |
importance: | Undecided → Low |
To post a comment you must log in.
also might make sense even to just have it available as a command:
curtin write-files
then the user could explicitly call it at a different stage fairly easily.
We also need to be clear about when it runs. Jtv asked me if he could use it to write /etc/network/ interfaces, and i'm not actually sure if tha twould stick or if the configure networking would overwrite it with OUTPUT_ NETWORK_ INTERFACES.