/usr/share mutability
Hi All~!
I'm trying to use sbctl to sign the kernel image for Secure Boot after it's generated in each update.
Unfortunately sbctl hardcodes the path at which it stores it's database and keys as /usr/share/..., which is mounted as RO in blend.
I can modify the source to store it elsewhere, but where can I put the
a) modified binary
b) secureboot keys and sbctl database
such that I can access it from a
commands entry in system.yaml that runs after the system is buillt?Solution:Jump to solution
If there isn’t an existing mechanism would we be willing to add something like this to akshara? Maybe as a
/persist directory that gets moved into the new root early in the build23 Replies
@Rudra
use
mount
just remount /usr as rw
or add a commands: entryyou mean a commands entry to remount it?
no, do it in your shell right now
Also I tried remounting as rw, did not work. Not sure if I am doing it wrong:
that might work
:(
run the creation commands through system.yaml
is it not rw during build?
if you need to move files add them as commands too
all of it
but I need to move files from /home, which build does not seem to have access to
store them elsewhere
try a flash drive
Hence my question in the original post - store them where - that is both writable at run time and readable at build time?
oh
that I have to keep plugged in forever?
mounted as root
just temporarily
oh just to get it into /usr/share the one time?
/etc
I remember now
that is writeable
should be there during buildooooh
scrap the drive
build does not seem to see the same /etc as I do
during build:
Before/After build:
right it's staring at
/.new_etc
generated during build
you could also use network storage
with wget/curl
to the build env that is /etc
you'd have to copy them in yourself mid-buildThere's gotta be a less sketchy way to share some files between builds (that the build also has access to)
0x0.st is self hostable BTW https://git.0x0.st/mia/0x0
I was half joking
Ah
it's sketchy because I don't think it was designed for these kinds of file operations
it would work
even under the main instance
Solution
If there isn’t an existing mechanism would we be willing to add something like this to akshara? Maybe as a
/persist directory that gets moved into the new root early in the build