ehmry/genode
ehmry
/
genode
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
genode/repos/os/src/server/fs_rom
History
Ehmry - 3d68a520cb Tag release 19.11 
-----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCgAdFiEEsIWqvdxEKaxX80hspyRgNBfs1rcFAl3fpmAACgkQpyRgNBfs
 1rcezQ//ZoYChufO6m2CByuPUbITql12b6oyOjmvcw16NW+Nsf2EodwMeCk/9yyM
 kWIxqOtXp1yFPGNf8ebEkTu5YXYMkHrUds4V6nQ4nQnyk7VnQmR3XTnqP8Sr27Hp
 fHi7Dddjxufexeyb6bwis04mK4PeFWXk/D6H4nh6ZeaR30g/GQ+Wt4N64a+HcQ1g
 kLMKuLlooOoq0L9q8IVLAtQoKNR1LP6x0FKGH8B6elwns8rXna2fRSlCB+W7qLwl
 K/pQadaIkwQNj8TEXuQxdGOR1GIrTbUz9ExS6U1yPXjqK06CunDZqsn+Cv5G7p+5
 ybMaViXwDGilZjhNLTjAbPhqhoOVu+yDB5gwzKiYt6/gTKP8N+VUpXKhGpzu/0ya
 wEt2b/43vmPm1NsBQQFU6vmjyW0W0iOl+a1tetv/qFo4mzQNesbVlu6t91b0EAjp
 C0JzZj9UHj/QkKgLIPkWMVWyz+VtODUeFhMLV6+86wzFmqSNhbaL0K/1LvX3AHZR
 5M/sjMRdtRL9U7Xv/LTn/Sgisk5wT2wfI9dpkAZALZjm22751mSTv9XhdLC/+XpA
 0F7cfSg36DphYsyPmSQ9+Q79rpU+bvuuTbqAsLdYcflMaW4bsIOd4j5Lk3adIPbN
 EE0uu+CD1GbqpKy+vLr+2EIlYpVNRTQKLklmkmhb+ZBuvUo00cU=
 =4dhl
 -----END PGP SIGNATURE-----

Merge tag '19.11'

Tag release 19.11
 		2019-11-28 13:21:13 +01:00
..
README Move repositories to 'repos/' subdirectory 2014-05-14 16:08:00 +02:00
Tupfile Refactor Tup, flatten output directories 2019-10-28 11:32:29 +01:00
main.cc fs_rom: adaptation to added file-modification time 2019-11-19 14:17:30 +01:00
target.mk Move repositories to 'repos/' subdirectory 2014-05-14 16:08:00 +02:00

README 

The 'fs_rom' server translates the 'File_system' session interface to the
'ROM' session' interface. Each request for a ROM file is handled by looking
up an equally named file on the file system. If no such file could be found,
the server watches the file system for the creation of the corresponding file.
Furthermore, the server reflects file changes as signals to the ROM session.

Limitations
-----------

* Symbolic links are not handled
* The server needs to allocate RAM for each requested file. The RAM is always
  allocated from the RAM session of the server. The RAM quota consumed by the
  server depends on the client requests and the size of the requested files.
  Therefore, one instance of the server should not be used by untrusted clients
  and critical clients at the same time. In such situations, multiple instances
  of the server could be used.