Ancient NFS patch sought
Greets,
I'm looking for a few terms that I can use to STFW with google, to find the patch (or code) for a wierd ancient NFS feature.
Many years ago I was using someone else's Linux box with NFS. This version of NFS had the feature that:
On the server you could copy a file to it's own name followed by a '#' followed by the MAC address of one of the clients, and then that client would see this copy of the file as though it were the original. The two files would typically be different, and the server and the client get their own versions each. The process could be continued for any number of different clients.
Can anyone give me some search terms (or an URL) to help me find the code for this feature on the web?
TIA,
chippo
PS: What I really want to know (which I'll hopefully glean from the code/URL when located) is:
- was this a user-space or kernel-space implementation of NFS
- how much mission it'll be to get the same (or similar) functionality on a 2.4 kern.
Quoted 15 lines · On Sunday August 11, [email protected] wrote:
Greets,
I'm looking for a few terms that I can use to STFW with google, to find the patch (or code) for a wierd ancient NFS feature.
Many years ago I was using someone else's Linux box with NFS. This version of NFS had the feature that:
On the server you could copy a file to it's own name followed by a '#' followed by the MAC address of one of the clients, and then that client would see this copy of the file as though it were the original. The two files would typically be different, and the server and the client get their own versions each. The process could be continued for any number of different clients.
Quoted 2 lines
Can anyone give me some search terms (or an URL) to help me find the code for this feature on the web?
ClusterNFS on sourceforge. So
http://clusternfs.sourceforge.net/
Quoted 7 lines
TIA,
chippoPS: What I really want to know (which I'll hopefully glean from the code/URL when located) is:
- was this a user-space or kernel-space implementation of NFS
UserSpace
Quoted 2 lines
- how much mission it'll be to get the same (or similar) functionality
on a 2.4 kern.
Not if I can help it. All the functionality you need already exists.
Each client mounts a common root filesystem.
A very early rc script mounts a per-client filesystem on e.g. /perclient.
The rc script can use hostname or IP address or MAC address or whatever it wants to choose the actual filesystem to mount:
mount -t nfs -o nolocks server:/clientfilesys/hostname /perclient
Then any file that needs to be per-client becomes a symlink into /perclient.
About the only thing that this doesn't work for is files the are unlinked and re-created often. I suspect if there are any of those there is a workable solution.
NeilBrown
Quoted 6 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/