16 ms·

How do read-only filesystems align with your definition?

• yencabulator 3y ago
  You can't create new things on a read-only filesystem, you can in S3; not a good analogy.
  • akerl_ 3y ago
    I wasn’t making an analogy. I was asking how read-only filesystem works given the parent commenters description of what makes something a filesystem.
    • yencabulator 3y ago
      It's a filesystem where many operations return an error (historically, EROFS). There are many things you can't do with one. Is that interesting somehow? I don't agree with defining a filesystem as something that has to be backed by a block device, but the shape of a filesystem API is historically very different from the shape of the S3 API.
• paulddraper 3y ago
  All of the read stuff still applies (list, open, read, seek).
• mr_toad 3y ago
  You can read individual blocks on a read only file system. With S3 you’re stuck with range requests which are much larger.