On Thu, Mar 15, 2018 at 05:15:37PM -0000, Oliver Grawert wrote:
> nontheless, we need the "content:" directive on a "role: system-data"
> partition working for a customer project soon where some udev rules (and
> other files) need to be pre-installed in the system-data partition.
I agree that this is a useful feature to have, and this has come up before.
However, it doesn't follow from the spec (which is admittedly ambiguous),
and it's new feature work. If this is a requirement for a customer project
"soon", you might need to look at contributing that feature.
In any case, if there is a deadline for this please communicate this to us
so we can try to schedule it appropriately.
> While I could apply hacks to do this from i.e. a customized hacked
> initrd I would really prefer if we could give something clean to the
> customer for their production images instead.
For a possibly-reusable example of this from the joule images, see:
On Thu, Mar 15, 2018 at 05:15:37PM -0000, Oliver Grawert wrote:
> nontheless, we need the "content:" directive on a "role: system-data"
> partition working for a customer project soon where some udev rules (and
> other files) need to be pre-installed in the system-data partition.
I agree that this is a useful feature to have, and this has come up before.
However, it doesn't follow from the spec (which is admittedly ambiguous),
and it's new feature work. If this is a requirement for a customer project
"soon", you might need to look at contributing that feature.
In any case, if there is a deadline for this please communicate this to us
so we can try to schedule it appropriately.
> While I could apply hacks to do this from i.e. a customized hacked
> initrd I would really prefer if we could give something clean to the
> customer for their production images instead.
For a possibly-reusable example of this from the joule images, see:
git+ssh: //git.launchpad .net/~vorlon/ tuchuck/ +git/uc16- build-script