This needs IPO.
You mean ICO, right?
Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
11–20 of 45 posts
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#12Linux is the only intended target OS, portability is not a goal. Goodbye then.
You can fork it and port it to something like dokany to make it work in Windows.
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#13Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#14Can't wait for the ICO.
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#15This reminds me of delay line memory, storing information in the echo of a sound: https://en.wikipedia.org/wiki/Delay_line_memory . LEO had long tubes of mercury for this, not sure I would have wanted to work in that office.
Same principle, but using slabs of glass, was used in PAL analog color television until digital memory got cheap enough to implement the delay line.
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#16Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#17This is exactly what I needed - not a lot of people are doing eventually inconsistent databases yet. If theres a network partition, shits probably fucked anyways so its best to throw away all your data. Unfortunately the metadata (list of files) is stored in memory, not network. Not quite as unreliable as I would like.
Sounds like your looking for something like MangoDb https://github.com/dcramer/mangodb Note: joke assumes parent poster was somewhat humorous
nsafs might be another good choice: https://github.com/freedomtools/nsafs
Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#18Re: Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
#19This reminds me of delay line memory, storing information in the echo of a sound: https://en.wikipedia.org/wiki/Delay_line_memory . LEO had long tubes of mercury for this, not sure I would have wanted to work in that office.
I think very few bits here are actually stored in-flight on the copper/fiber/radio at any time. Most of them are probably stored in various buffers of networking equipment (which are ordinary semiconductor RAM). It would be interesting to see someone do an actual breakdown for, say, a transatlantic link.
My gut feeling says that only geostationary satellite links have any significant number of bits in-flight.