🚀 go-pugleaf

Saurav Chatterjee wrote:
> 
> I have some software that uses the standard Unix I/O read()
> and write() calls. Normally, these will get linked with
> the system calls in libc.a.
> 
> I want to write my own read() and write() routines that
> will intercept certain file descriptors, while passing
> others to the standard read() and write() calls.
> 
> For example, if foo.c has this code:
> 
> {
>  ...
>  n = read (...);
>  ...
> }
> 
> I want to write a read() routine that will be called from
> foo.c. My read() routine will then need to call the read()
> routine in libc.a (this last part is what makes it tricky).
> 
> Constraints: I cannot modify the libc.a file. I don't want
> to modify the name of the read() function in foo.c
> 
> Any solutions?
> 


What about 
#define read __read__
in the header file that defines the interface to your RAM disk?

Dima.