I wouldn't advise it, because it might be possible to break the integrity of the snap system, or provide unexpected behavior where your application may not behave as intended because of the modification of the snap system itself. You could possibly experiment with remounting the protected read-only filesystems to read/write. But I can imagine it might be similar to designing Android, or Java programs, where the developer will use some type of export or publish method to run or to test the new version in an installed configuration. I'm not a snap programmer and can't give exact specifics of how the designing and export for use process works with snap. normally in your own personal space, then use the snap's development system for installing the new version. How can I resolve this?Īs I suggested in the comments, it would be safer and more common for you to design your program in a development environment as a normal user. So you would have to use the features of snap's programming configuration to decide which files will be placed where. Your question suggests that you are the app's programmer. Nsfs on /run/snapd/ns/vlc.mnt type nsfs (rw)īy your error message you are trying to make change on files that have been programmably protected by the programmer. Nsfs on /run/snapd/ns/hello-world.mnt type nsfs (rw) Tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,noexec,relatime,size=3293156k,mode=755) var/lib/snapd/snaps/vlc_190.snap on /snap/vlc/190 type squashfs (ro,nodev,relatime,x-gdu.hide)Ī command to see examples of snap's spaces that are not write protected: $ mount | egrep snap | egrep -v ro, var/lib/snapd/snaps/communitheme_246.snap on /snap/communitheme/246 type squashfs (ro,nodev,relatime,x-gdu.hide) var/lib/snapd/snaps/core_4571.snap on /snap/core/4571 type squashfs (ro,nodev,relatime,x-gdu.hide) var/lib/snapd/snaps/communitheme_124.snap on /snap/communitheme/124 type squashfs (ro,nodev,relatime,x-gdu.hide) var/lib/snapd/snaps/core_4407.snap on /snap/core/4407 type squashfs (ro,nodev,relatime,x-gdu.hide) If the attribute is not included, the :read-write pseudo class. If present on any of these input types and elements, the :read-only pseudo class will match. var/lib/snapd/snaps/hello-world_27.snap on /snap/hello-world/27 type squashfs (ro,nodev,relatime) The readonly attribute is supported by text, search, url, tel, email, password, date, month, week, time, datetime-local, and number types and thevar/lib/snapd/snaps/communitheme_185.snap on /snap/communitheme/185 type squashfs (ro,nodev,relatime,x-gdu.hide) var/lib/snapd/snaps/core_4486.snap on /snap/core/4486 type squashfs (ro,nodev,relatime,x-gdu.hide) You can verify the real location and how the spaces are linked with the following commands.Ī command to see examples of snap's protected mounts: $ mount | egrep snap | egrep ro, The process also has specific space for configuration data which includes the user's specific home space ( /home/user/snap) for data and configurations and a space for world-wide data ( /var/snap).Īll the world-wide snap files are readable and accessible via symbolic links to the /snap area. This is done by the process of mounting the protected files in their specific space as read only. Snap's program files are protected against change.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |