Ramdisk and network file sharing

[Kamisama]

Scenario:

Box 1 (Live OS with a ramdisk of 256 MB)
Box 2 (Live OS)

Box 1 is connected to Box 2 via ethernet cable.
Box 1 is running NFS (Network file sharing).

How can Box 2 access the ramdisk of Box 1 and use it for storing files, data, etc.?

For what I've read, it's not possible. I don't believe that's completely the case.
Does anyone here know how to do it?
The few ideas to come to mind were to use FTP.
I don't want to use FTP.

One Puppy Linux user recently developed something similar to NFS. However, I haven't had a chance to fully look at it and understand it. I'm curious if any of you think that could be used like NFS, or very closely resemble, in order to give the feel of it.

[Prometheum]

Network File System, you mean?

You should be able to export the ramdisk just like any other part of the file system, the machine just has to be running an NFS server.

[Kamisama]

C6. Which local file systems can I export with the Linux NFS server?

A. We expect the following local file systems to work, as they are tested often: ext2, ext3, jfs, reiserfs, xfs.

These local file systems may work or may have a few minor-ish issues: iso9660, ntfs, reiser4, udf. Ask on the NFS mailing list for details.

Any file system based on FAT or not having the ability to provide permanent inode numbers will have trouble with NFS versions 2 and 3 (see question C4).

Local file systems that are known not to work with the Linux NFS server are: procfs, sysfs, tmpfs (and friends).

http://nfs.sourceforge.net/#section_c

Yeah, Network file system, or whatever. I remember it as NFS.

I first noticed there was a problem when I created this scenario:

Box 1 (Live-CD Ubuntu)
Box 2 (Live-CD ubuntu)
Box 1 connected to Box 2 via ethernet cable.
Box 1 is running NFS.

I created a share folder on Box 1, and Box 2 wasn't able to access it. I installed all the dependencies and so forth. It appeared to not want to work while inside a live environment. I think live environments use squashfs, ausfs, and tmpfs. Some assortment of those things.

When I created an NFS server on a HDD install with box 1, box 2 was able to access the NFS share.
So, it seems like the NFS protocols wanted a HDD environment. I don't know why, though.

I will admit I haven't tried actually mounting /ramdisk and trying what I'm requesting.

But I assume if I were to take the next thirty minutes to do so, I'd still get no progress.

The idea with the scenario using two live-cds has to do with the fact that they use RAM as storage. I mean, if I could create an NFS, there would be no need for creating a ramdisk mount. As I move files from Box 2 to Box 1, the RAM on Box 1 would be eaten up.


################################################## ########################
# <file system> <mount point> <type> <options> <dump> <pass>
none /ramdisk tmpfs size=1G,user,noauto,rw 0 0

[Prometheum]

The error you got when trying to mount the export might help.

Also, it might be possible that those filesystems can't be exported (I think I've heard of issues like this, but I can't be certain).

[Kamisama]

I want it to be possible.
I figure it's possible.
I was wondering if some totsean knew or knew and wasn't willing to say.

I've been playing with the idea of RAMFS. Basically, it's like spill-over memory but it has to do with RAM. A central computer acts as the table, and says where each file is amongst the computers. Since ethernet can give about 5MB ups and downs, it seems like a neat idea. If the RAM starts filling to a certain amount on one computer, you can have files transferred to another computer's RAM.