Replies: 1 comment 2 replies
-
|
I have actually been playing with nfs in elks! at least a pale imitation of it, "homebrewed" Thanks for sharing VFS, i need a few weeks to understand vfs, will take a look myself :) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
One of the most useful tools I've encountered for working with vintage 8088 hardware is etherdfs. Often the old hard drive is dead, but with etherdfs and a 3COM card I'm able to boot from a floppy and then pivot to the emulated C: drive just by setting a few environment variables. In this setup most of the software lives on the remote server, which is super handy when old equipment fails.
Since ELKS has a nice VFS layer, has anyone discussed hooking in some sort of remote filesystem capability?
Nothing fancy like NFS2, but maybe a raw Ethernet frame protocol that provides a block device. I presume the current filesystem layer was written with the assumption that it is the only thing changes bytes on a block device. Invalidating the current buffers would need to be part of the protocol, but even a read-only remote device would provide some support for disk-less clients. This would only provide link-local remote drives, but that's more than good enough to have fun with an old machine.
If anyone knows of any links to old discussions on this topic I'd would like to read them.
Also, I'm curious to know if the current structure of the network and filesystem modules are sufficiently compatible to provide a platform for a network based block devices.
Beta Was this translation helpful? Give feedback.
All reactions