Hi,
I am going to release the initial version of the afs module for php
where pioctl is wrapped (and a couple of helpers are provided to decode
responses for interesting opcodes, as well as a trivial ACL class for easy
manipulation of permissions in php).
Finally, there is in the code a rudimentary attempt to provide access
to vldb (i.e. I'm trying to mimic vos examine, needs work).

Actually, I have a couple of questions:
(I hope the first one is not off-topic)

1. there are license issues ?
    i.e. what kind of license is ``compatible`` with openafs ?
    (a)GPL ? BSD ? apache ? ... ?

2. the most complex part of writing the code was ``choosing libraries``;
   there is a best practice ?
   or better: there is somewhere documentation about the libraries
   generated building openafs and their ``purpose`` ?

3. pioctl opcode VIOCGETVOLSTAT gives a VolumeStatus where
   ``Type`` is always 1;
   a bug, a feature or, my misunderstanding ?

Sincerly,
                        Alberto.



On Thu, 11 Dec 2008, Alberto Mancini wrote:

Hi,
I wrote, mostly to understand the difficulties, a tiny php extension wrapping a couple of pioctl calls.

Actually WHEREIS,GETACL,GETVOLSTAT are in the code and I think that
writing the extension is less problematic than processing  'fs'
output.

The code (that is really a quick-and-dirty test) can be downloaded
at the URL:
         http://ununtrio.math.unifi.it/PHP/

where a working test (test.php) is available.
Most of the code is from fs.c.

Any criticism will be apreciated.

I'd like to ear ideas on the general layout of the extension (OO ?) and on the "operations" that may be useful to implement.

The code is going to be part of a web-afs-access system
(something similar to filedrawers, and based on mod_waklog)
we are planning/developing for our users.

Alberto.











_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel


_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel

Reply via email to