Communicating FileSystem Structures b/w Two Machines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello All,

I am in the process of making a filesystem in a
client/server environment where there is a single
server having a storage attached and 2 to 3 clients
accessing that storage through a communication
mechanism. The client and server are using a
buffer(unsigned char array) to communicate.

In order for client and server to communicate, they
have to exchange different structures like
super-block, inode, dentry, vfsmount etc. We have to
use 2.6.x kernels but since different versions of
kernel will have differnt sizes for these structures,
I am getting problems in communicating these
structures b/w client and server. I therefore want a
machine and kernel independent way for communicating
these structures so as to handle the sizes problem.

Your comments and help are welcomed.

Thanks,
Uzair Lakhani

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux