> Oh Yes. You are correct. I did not look in to that aspect at all. I just did
> a comparison of whatever we have at *testcases/kernel/syscalls* and what
> they have in *Crackerjack*. I am listing down my comments here:

O.k. I'll focus on *testcases/kernel/syscalls*. So the porting task becomes 
much simpler.

> 91) lstat64
> Comments: We have lstat at *testcases/kernel/syscalls/lstat**. *You may need
> to include/port lstat64 on similar lines to sendfile64 and fadvise64.
> 
> 92) setfsuid16
> Comments: We have setfsuid at *testcases/kernel/syscalls/setfsuid**. *You
> may need to include/port setfsuid16 on similar lines to sendfile64 and
> fadvise64.


Really grate list.

BTW,

> 92) setfsuid16
> Comments: We have setfsuid at *testcases/kernel/syscalls/setfsuid**. *You
> may need to include/port setfsuid16 on similar lines to sendfile64 and
> fadvise64.

You wrote "sendfile64 and fadvise64".
I think you mean setfsuid instead, don't you?
 
I coundn't understand why you wrote "sendfile64 and fadvise64" here.

Masatake

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to