Also the Parts-of-file File System: https://www.usenix.org/conference/2005-usenix-annual-technic...
The File Filesystem (2021)
11–20 of 105 posts
Re: The File Filesystem (2021)
#12I would gently suggest naming it filefs or something; ffs already means https://man.freebsd.org/cgi/man.cgi?ffs(7) That said - good idea/approach; seems like an excellent way to cleanly extend the unix approach to structured file formats:)
Op’s ffs do not target FreeBSD and it l seems like referenced system is FreeBSD only. Claiming naming rights is a stretch here
Re: The File Filesystem (2021)
#13I would gently suggest naming it filefs or something; ffs already means https://man.freebsd.org/cgi/man.cgi?ffs(7) That said - good idea/approach; seems like an excellent way to cleanly extend the unix approach to structured file formats:)
There's another expansion to that acronym that I can think of. I think the joke is implied.
Re: The File Filesystem (2021)
#14For fuck's sake! Not everything needs to be a file! (This is a joke. I love the idea and execution.)
I see what you did there.
Re: The File Filesystem (2021)
#15For fuck's sake! Not everything needs to be a file! (This is a joke. I love the idea and execution.)
Daniel Stenberg, of cURL fame, co-write an Amiga-editor called FrexxEd where the open buffers were exposed as files in the filesystem.
Meaning you could write any shell script to manipulate an open buffer (not that important as it also exposed all editor functionality both via IPC via Arexx and via FPL - a C-like scripting language), and that you could e.g. compile without saving (that was very helpful on a system where a lot of people might only even have a single floppy drive, and where being able to have the compiler in the drive and compile straight from the in-memory version in RAM so you didn't have to keep swapping floppies was highly useful (just remember to save before actually trying to run the program - no memory protection...)
Re: The File Filesystem (2021)
#16I would gently suggest naming it filefs or something; ffs already means https://man.freebsd.org/cgi/man.cgi?ffs(7) That said - good idea/approach; seems like an excellent way to cleanly extend the unix approach to structured file formats:)
Op’s ffs do not target FreeBSD and it l seems like referenced system is FreeBSD only. Claiming naming rights is a stretch here
That's ahistorical. FFS is the berkeley Fast File System, from BSD 4.2, in 1983.
Re: The File Filesystem (2021)
#17You can also mount your git commits as a filesystem: https://jvns.ca/blog/2023/12/04/mounting-git-commits-as-fold... (previously: https://news.ycombinator.com/item?id=38527866 )
All you need now is a giant pile of rules for which revisions to select and you have the unholy demon that is Rational ClearCase
What!? you didn't add a versioned database layer on a server with code stored in clearcase that stored those ClearCase config specs to manage the configuration of your config specs to manage the configuration of your version control system that had your application configuration in it?! How did you even operate? /s
Re: The File Filesystem (2021)
#18No XML, Excel,PDF or CSV support yet.
Re: The File Filesystem (2021)
#19I would gently suggest naming it filefs or something; ffs already means https://man.freebsd.org/cgi/man.cgi?ffs(7) That said - good idea/approach; seems like an excellent way to cleanly extend the unix approach to structured file formats:)
Op’s ffs do not target FreeBSD and it l seems like referenced system is FreeBSD only. Claiming naming rights is a stretch here
FFS predates FreeBSD and is in some capacity supported by all 3 major BSDs. I'm fairly confident that Linux actually supports it through the ufs driver ( https://github.com/torvalds/linux/tree/master/fs/ufs ); whether the use of different names in different places makes it better or worse is an exercise for the reader.
Re: The File Filesystem (2021)
#20[deleted]