>> can this error could be ignored?
>> is lwext4 port somhow usable in general on 21.11?
>
> Increasing a file via truncation is not supported by this version of
> the lwext4 library (I have not checked if this is addressed upstream by
> now). If your use-case depends on this feature, e.g. sparse
Hi Johannes,
thank you for clarification
>> [init -> /bin/bash -> 12] Error: ROM-session creation failed
>> (ram_quota=6144, cap_quota=3, label="/home/build/c") [init ->
>> /bin/bash -> 12] Error: Could not open ROM session for
>> "/home/build/c" [init -> /bin/bash -> 12] Warning: execve: executab
Hi Johannes,
thanks for clarification
>> Do you have something like ACL applied to file system?
>
> The VFS server has no notion of users or ACL, yet it is possible to
> provide different parts of the VFS to different clients/sessions. This
> is achieved by specifying a , which sets the root di
Hi Christian,
>> [init -> terminal] Error: bind to port failed
>
> 1. It seems your configured 1 port for 2 clients. This will not work.
> Please, configure different ports (or just one if you don't need
> the VFS component, which failed to setup its connection anyway.
this is exactly m
Hello Alexander,
> I am trying to run lwext4_fs.run from world repo
>
> it gives the following error on linux/x86_64
> ...
> [init -> test-libc_vfs] calling open(file_name4, O_CREAT | O_WRONLY)
> file_name=test4.tst
> [init -> test-libc_vfs] open(file_name4, O_CREAT | O_WRONLY) succeeded
> [init
Hi Alexander,
> if I try to execute it inside genode bash (eg in /home/build) - I do
> receive the following: in ssh client :
> bash-4.4# vim c
> bash-4.4# ls -la
> total 1
> -rwx-- 1 root 0 1004 Jan 1 2022 c
> drwx-- 1 root 0 144 Jan 1 1970 depot
> bash-4.4# ./c
> bash: ./c: No such
Hi Alexander,
> >
> >> in that case we need to have single VFS server with own cache/page
> >> mapping for files being shared between different instance of
> >> containers (subsystems), not only for children’s? is it true for
> >> current implementation of [single VFS+FS server] <=> [[multiple
>
Alexander,
I must admit I'm a bit confused by the information in your message.
On Wed, Jan 12, 2022 at 18:22:17 CET, Alexander Tormasov via users wrote:
> it helps to get rid of message, but does not help to solve the problem of
> attachment of bash to tcp_terminal (failed to create VFS node
>
