florian_kc has quit [Read error: Connection reset by peer]
<sotaoverride>
vvn: is there a way to just restrict a selected few directories to be readly only?
florian has joined #yocto
florian__ has quit [Ping timeout: 250 seconds]
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
<smurray>
sotaoverride: unless you cut the filesystem into multiple ones, pretty much doing read-only and then overlays on top is what comes to mind, look at the overlayfs and overlayfs-etc classes for the out of the box options
<vvn>
sotaoverride: as smurray said. If you're using systemd, you could also use systemd.volatile= (man kernel-command-line)
jclsn_ has joined #yocto
jclsn_ has quit [Client Quit]
<vvn>
if you manage multiple machines for your product, I assume it is common to end up with a container layer for your BSPs, e.g. meta-<company>/meta-<product>-bsp holding several machine configuration files, in addition to meta-<company>/meta-<distro>
<vvn>
(as a place to centralize machine-level recipes and customizations)
<sotaoverride>
vvn: so mount points defined with overlayfs.bbclass persist over system updates?
<vvn>
sotaoverride: depends on what you mean by system update (this is very product-specific)
<sotaoverride>
I mean when I just write a new rootfs to a partition
<sotaoverride>
and the current and the new rootfs has OVERLAYFS_MOUNT_POINT[data] = "/data", so data directory would persist?
<sotaoverride>
so im guessing systemd-machine-units recipe is different from the systemd recipe
<vvn>
what does that mean
Guest23 has joined #yocto
<sotaoverride>
overlayfs.bbclass has a comment "# The class assumes you have a data.mount systemd unit defined in your"
<sotaoverride>
# systemd-machine-units recipe and installed to the image.
jclsn has quit [Ping timeout: 246 seconds]
<sotaoverride>
trying to figure whats what in he systemd land. this systemd-machine-uints is a recipe on top of the systemd recipe?
<vvn>
sotaoverride: this means that the class assumes that you have a systemd-machine-units_%.bbappend file in the distro layer which install a data.mount unit file.
<amahnui[m]>
Hello everyone 👋
jclsn has joined #yocto
<vvn>
sotaoverride: systemd-machine-units is a package, empty by default, meant to hold machine-specific unit files
<vvn>
sotaoverride: so instead of appending the systemd recipe directory, your bsp or distro layer can append this recipe
<sotaoverride>
vvn: so my system-machine-unit_%.bbappend would have a do_install block, which takes care of data.mount?
zen_coder has quit [Ping timeout: 276 seconds]
<vvn>
sotaoverride: yes, you would append FILEEXTRAPATHS, SRC_URI, do_install and FILES:${PN} to include your data.mount file as part of the systemd-machine-units package
florian has quit [Ping timeout: 246 seconds]
zen_coder has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
amitk has quit [Ping timeout: 240 seconds]
Guest23 has quit [Quit: Connection closed]
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
florian has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
zen_coder has quit [Ping timeout: 250 seconds]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
mvlad has quit [Remote host closed the connection]
GNUmoon has quit [Remote host closed the connection]
amahnui has quit [Quit: Connection closed for inactivity]
sakoman has quit [Ping timeout: 256 seconds]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
sakoman has joined #yocto
bluelightning has joined #yocto
florian has quit [Ping timeout: 276 seconds]
florian has joined #yocto
GNUmoon has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
leon-anavi has quit [Quit: Leaving]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<hushmoney>
so here's a weird one: a layer i'm using has several recipes that support PACKAGECONFIG="tcp". rather than setting it for every recipe individually, i thought i'd set PACKAGECONFIG_append?="tcp" in my distro.conf. now when i try to bake my image, i get "Nothing PROVIDES 'virtual/update-alternatives-native'" error
<hushmoney>
now i removed it and set PACKAGECONFIG_append_pn-foo?="tcp" for each recipe and the error has cleared
<RP>
hushmoney: you probably want " tcp"
<hushmoney>
ah shit i forgot about that thanks. you're right that fixed it
florian has quit [Ping timeout: 276 seconds]
nsbdfl has quit [Ping timeout: 256 seconds]
goliath has quit [Quit: SIGSEGV]
codavi has quit [Read error: Connection reset by peer]