10 ms·
Pingfs: A filesystem where data is stored as ICMP Echo packets (2016)
- coolspot 9y agoThis needs IPO.
- zaptheimpaler 9y agoThis 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.
- techdragon 9y agoSounds like your looking for something like MangoDb https://github.com/dcramer/mangodb https://github.com/dcramer/mangodb Note: joke assumes parent poster was somewhat humorous
- emptyroads 9y agonsafs might be another good choice: https://github.com/freedomtools/nsafs https://github.com/freedomtools/nsafs
- metahost 9y agoThat's innovative!
- djsumdog 9y agoI didn't realize there were so many of these jokefs projects. It's like the software dev equivalent of those silly domain jokes: https://helenkellersimulator.org/ https://helenkellersimulator.org/ http://motherfuckingwebsite.com/ http://motherfuckingwebsite.com/ http://thingsididlastnight.com/ http://thingsididlastnight.com/
- LambdaComplex 9y agoI wrote a joke filesystem that does nothing but provide 1x1 PNG files[0] (I was bored and asked for dumb filesystem ideas on IRC) 0. https://github.com/sector-f/colorfs https://github.com/sector-f/colorfs
- empyrical 9y agoAnother good one: https://github.com/philipl/pifs https://github.com/philipl/pifs
- DarronWyke 9y agoObligatory: "Tokutek claims to improve MongoDB performance 20x. It is unclear if this also means losing 20x as many documents."
- dragonwriter 9y agoEventually inconsistent databases could save a lot of the effort developers faced with databases without inconsistency guarantees put into implementing eventual inconsistency at the application level.
- cvwright 9y agoThis is the perfect transport for GNU Terry Pratchett. http://www.gnuterrypratchett.com/ http://www.gnuterrypratchett.com/
- chillaxtian 9y agoJust had a quick look to see the general flow. Only looked at the read path, which is roughly: * filesystem receives read * blocks on a semaphore (https://github.com/yarrick/pingfs/blob/master/chunk.c#L141 https://github.com/yarrick/pingfs/blob/master/chunk.c#L141) * network thread wakes up semaphore when ICMP reply containing data is received * filesystem thread copies data into new buffer to return from syscall * filesystem relinquishes chunk back to network thread, which wakes up, sends it back to be echoed on the network via ICMP, and frees the in-memory buffer (https://github.com/yarrick/pingfs/blob/master/chunk.c#L107 https://github.com/yarrick/pingfs/blob/master/chunk.c#L107) How silly :)
- Annatar 9y agoLinux is the only intended target OS, portability is not a goal. Goodbye then.
- chrisper 9y agoYou can fork it and port it to something like dokany to make it work in Windows.
- Const-me 9y agoBased on Annatar's profile, he'd like it to work on FreeBSD.
- Annatar 9y agoillumos and it’s the programmer’s “Linux only” attitude which irritates me.
- Sir_Cmpwn 9y agoI get your sentiment in general but... you're upset because a tool for storing files in IMCP pings isn't available on your OS? Poor you, where else are you going to keep your files!
- Annatar 9y agoNo, I’m irritated because of the programmer’s attitude, which is quite systemic in programming and has been for a while.
- Sir_Cmpwn 9y agoWell, it's not merited, and you're being rude. I'm saying this as someone who references the POSIX standard several times a week to ensure portability. This kind of tool is a toy project and is by its nature highly dependent on non-portable interfaces.
- thsealienbstrds 9y agoredundancy == broadcast ping
- robin_reala 9y agoThis reminds me of delay line memory, storing information in the echo of a sound: https://en.wikipedia.org/wiki/Delay_line_memory 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.
- datenwolf 9y agoSame principle, but using slabs of glass, was used in PAL analog color television until digital memory got cheap enough to implement the delay line.
- avian 9y agoI 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.
- detaro 9y agoVery simplified, but assuming a 5000 km cable and 300 000 km/s speed of light (is slightly slower in fiber), light needs 0.01666... seconds for that. At 10 Gbit/s (fairly slow), that'd mean ~ 166 Mbit or ~ 20 Megabyte in flight. (I hope I didn't forget a factor 1000 somewhere)
- avian 9y agoYour calculation makes sense. However, for those 20 MB in flight, how much data is stored in buffers? I think that could be approximated by comparing ping time with speed of light. e.g. if a 5000 km long link at 10 Gbit/s has latency of 0.0166 s, then you have zero buffering. If you have latency of 0.2 s, then around 2 Gbit of data must be stored in buffers somewhere, making 20 MB in flight only 1% of all data stored in such a ping filesystem.
- thelomen 9y agoReminds me a little of PingTunnel :) https://www.cs.uit.no/~daniels/PingTunnel https://www.cs.uit.no/~daniels/PingTunnel
- catwell 9y agoThe author of PingFS is actually the same as iodine (IP over DNS: http://code.kryo.se/iodine/ http://code.kryo.se/iodine/).
- SwellJoe 9y agoCan't wait for the ICO.
- kelson 9y agoPrior art https://www.shysecurity.com/post/20120401-PingFS https://www.shysecurity.com/post/20120401-PingFS
- thoastbrot 9y agonot exactly new: https://hn.algolia.com/?query=pingfs&sort=byPopularity&prefix&page=0&dateRange=all&type=story https://hn.algolia.com/?query=pingfs&sort=byPopularity&prefi...
- dang 9y agoPrevious discussions: https://hn.algolia.com/?query=Pingfs%20points%3E3&sort=byDate&dateRange=all&type=story&storyText=false&prefix=false&page=0 https://hn.algolia.com/?query=Pingfs%20points%3E3&sort=byDat....
- mmjaa 9y agoCool .. all we need now is a host waaaaay out in space, and we can just use space itself to store all our data (not that we aren't already) ..
- speedplane 9y agoOf course the gut reaction to this is "why?" and the obvious answer is "because I can"... that's fine, but there's been plenty of filesystems built on protocols or things that weren't really supposed to be filesystems. I remember way back when gmail first announced giving away 1GB of storage, there were a bunch of hacky things to turn SMTP into a real filesystem. So, I get the answer to "why make this weird filesystem", but I'd really like to know: why is this weird filesystem, weirder or more intriguing than the others that have come before it.