On Jan 21, 2011, at 3:45 AM, "Rod Widdowson" <r...@steadingsoftware.com> wrote:
>>> 1) Redirect IO through the afs_XXXX operations.
>>
>> Not OS_OPEN &co?
>
> Good point. I'll do that.
>
> Meantime I've also spelunked through the code some more...
>
> What is the expectation about afs_open and friends - such as afs_stat which
> is used in some places to mean both the function and the
> struct..
>
> I would like to leave afs_open defined as "use the c run time library" and
> reserve it logging and so forth; then use OS_XXX for
> [meta]data IO. Converting logging to Win32 CamelCase code would be tedious
> to say the least and would not affect the issues that we
> have between mixing io between the c run time library and the windows one.
>
> Equally I'm slightly nervous about wholesale conversion of afs_open to
> OS_OPEN. Maybe it safest to just do it in the paths which
> are compiled for the Windows build?
>
> Also, for my information, why are OS_XXXX defined in ihandles.h? historical?
>
OS, IH, and FDH was done to abstract I/O so the fileserver could have multiple
backends first, and then, run on multiple types of platform.
All are thus conflated in the vol package
>
_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel
