Is Block-Persistence Possible on non-Linux base? - users

26 Oct 2025


      Hi,
Is there a way to achieve functionality similar to lx_fs on non-base-linux? My best guess is something like:
```xml
<start name="ahci">
    <resource name="RAM" quantum="1M" />
    <provides><service name="Block" /></provides>
    <config atapi="no">
    	<report ports="yes"/>
    	<policy label="isomem -> " device="0" writeable="yes" />
    	<policy label="vfs -> " device="1" writeable="yes" />
    </config>
    <route>
    	<service name="Report"> <child name="ahci_report_rom"/> </service>
    	<any-service> <parent/> <any-child/> </any-service>
    </route>
</start>
<start name="vfs" ram="200M" caps="200">
  <provides><service name="File_system"/></provides>
  <config>
    <vfs>
      <dir name="dev">
        <block name="block" block_buffer_count="128"/>
      </dir>
      <dir name="snapper">
        <rump fs="ext2fs" ram="64M" writeable="yes"/>
      </dir>
    </vfs>
    <policy label_prefix="snapper" root="/snapper" writeable="yes"/>
  </config>
  <route>
    <service name="Block"> <child name="ahci"/> </service>
    <any-service> <parent/> <any-child/> </any-service>
  </route>
</start>
```
However, with this ACHI complains that device=1 is already taken. If I remove the following from the vfs_component:
```xml
     <dir name="dev">
        <block name="block" block_buffer_count="128"/>
      </dir>
```
Then the error goes away, but I am unable to read and write to the file-system. From what I have read it's not possible to have persistent storage without lx_fs, necessitating the use of base-linux. Please let me know if I missed something in my research.
Best,
Rumen