News for hackers. Stuff that matters.
Re:Non-Posix File Systems by LeoPanthera on Tuesday September 08, 2020 @06:24PM (#24414288)
Acorn's "ADFS", as used in RISC OS, uses "." as the directory separator. Fully qualified paths look like this:

fs::drive_id.$.directory.directory.filename

Where "$" means "root directory". (On network filesystems, you can also use "&" which means "home directory".)

The top level identifier is the filesystem type, usually "adfs", which is a slightly unusual way of doing it.

Bringing in files from other systems, which invariably have filename extensions, involves converting the . to a /, so you end up with filenames like "readme/txt". ADFS stores the file type not as a filename extension, but as a three-character hex ID in the filesystem instead. (Text, for example, is FFF.)

Re:Non-Posix File Systems by fanf2 on Tuesday September 08, 2020 @09:51PM (#24415898)
On the BBC Micro-era pre-hierarchial DFS, there was a single level of single character directories, so files were called things like “d.file”. $ was the default directory rather than the root.

The Acorn/Norcroft ARM C compiler used c and h directories which effectively swapped the file extension around, so sources were named like c.main, and #include would try swapping name and extension for compatibility. It was about as Unix-flavoured as was possible on the Archimedes...