(I am having problems with the list and don't know if this message got through, I am sorry if it did).
I am porting Recover to 4e. Recover is a filesystem which speaks 9P with two ends, a server and a client. When a connection falls down it pushes the state and restarts the pending requests, so you don't see a hung channel any more if your connection falls down. I am now working on the authentification part. The problem I have is that after doing the Tauth, I have to do the authentification RPC's over the afid. auth_proxy would be just fine, except that it takes a real file and does not speak 9P. I only have is a fid on a 9P conversation. I could use fauth, but then there would be no way to recover the fid which I need for the attach later. I imagine four solutions for this: First, which is what I would currently take rewrite auth_proxy to use 9Pread and 9Pwrite which read and write from a fid using 9P over a connection. The second would be to take out the system call fauth() which I dont like and replace it with new one (fauth can be a library function) which maps an fd with a fid so the kernel does the 9P talking. This may require more changes for the attach, I don't know. Third, writing a kernel filesystem, srvlike were you could post a connection, give it a fid and get a file where you could read from. Fourth, posting fids for file on /proc/xx/fd, this is the simplest one, probably, though it requires changes all around. What do you think about this?. What is the right approach?. Is there a simpler way of doing this I have not thought of?. TIA, G. -- - curiosity sKilled the cat
