hasse69

Interesting use-case instead. I quickly checked `dl-error.c` in glibc but it was not obvious what would cause this error to be thrown. Actually, the error message itself looks a bit...

>I encounter another problem: When I tried to import pyc file in rarfs from python program, It told me RuntimeError: Bad code object in .pyc file The problem is most...

You can try this patch on master/HEAD. __But you need to tweak your I/O buffer for this to work.__ By default the history size is 50% of the I/O buffer,...

I think you need to explain in more detail what you see. And also provide the command line arguments you gave to rar2fs etc.

Btw, it is expected to get 'defunct' processes if your I/O buffer is large and RAR extraction to it completes before the file is actually closed by the application. My...

Again. The defunct processes are there because the application using the file has not closed it properly (the I/O error is due to that the I/O buffer is not big...

Let me get back to your questions later, but first try this patch instead. [patch2.txt](https://github.com/hasse69/rar2fs/files/1116073/patch2.txt)

>I improved the I/O buffer,Bus error is disappeared and my program can be started . Can you elaborate a bit on this? Improved, how? A bus error can not just...

>1. After the first process have finished importing modules, the python modules in rar archive should have been extracted and I/O buffered, then the subsequent cloned subprocesses will import/read these...

Btw, I need to look deeper into how to publish my last few changes and if they in any way could affect other more common use cases negatively. So an...