James Walmsley
James Walmsley
I noticed that one drive-d seems to constantly write 256kb/sec to disk between sync workers. Any ideas where this comes from?
Awesome project, I now have this running on an ARM based Readynas 204. I noticed that I killed the daemon halfway through a few images downloading, and I can see...
Kind of an experiment to see how versatile / simple meson really is. If I can configure and build BT with it, then it can probably do most things.
Implement the execve syscall. This allows a process to replace its own memory map with that of an executable image loaded from a storage medium.
Update the open() syscall to ensure that it is fully POSIX compliant.
Ensure read() syscall is fully POSIX compliant.
Ensure write() syscall is fully POSIX compliant.
We have a much better inline list structure which everything should be moved to.