6 ms·
Interesting project. Out of curiosity, when/why would someone want to use something like this? SQLite is a file database, in that the database is literally a
by Alupis 12y ago
Interesting project.
Out of curiosity, when/why would someone want to use something like this?
SQLite is a file database, in that the database is literally a file, which means it will reside on another already existing filesystem - so you would have:
`
Abstract Filesystem
-------------------
SQLiteDB
-------------------
OS Filesystem
- liveoneggs 12y agoIt could be very convenient as an alternative to tarfs where you want to package up an entire X into a mount point to distribute.
- fiatmoney 12y agoIt looks like they wanted to implement a encrypted userspace filesystem, presumably in an environment without something like EncFS.
- craigching 12y agoThis was exactly how I thought it might be interesting too.
- eighthave 12y agoYup, exactly, it is used in IOCipher to provide encrypted virtual disks that don't need root access or special permissions to mount.
- shawn-butler 12y agoA portable, encrypted, transactional "abstract" filesystem that works with existing POSIX semantics and code. Would be useful where you have legacy codebase and want to deploy it new scenarios where POSIX filesystem access is not guaranteed.
- koenigdavidmj 12y agoDMG (a disk image that can be mounted) is the main way to distribute OS X applications, and something this could have fulfilled the same use case if Linux wasn't as fond of centrally distributed packages.
- icebraining 12y agoIt's not like Linux lacks disk image formats, though, like cloop (used by Knoppix). It's just that when you don't have to distribute weird metadata like resource forks, what's the point of using a whole filesystem versus a tar file?
- mikeash 12y agoEven when you do have weird metadata, it's easy enough to retrofit archive formats to handle it, which Mac OS X did years ago. Disk image distribution is a complete anachronism now, and it's odd how persistent it is.
- lvillani 12y agoDMGs still have the advantage that you can customise the Finder windows that opens when you double click one [1]. So, from an UX standpoint, they still make a lot of sense to distribute application bundles since it compels users to "install" the application by dragging the bundle icon to the appropriate directory, which is conveniently symlinked in that Finder window. It's also easier to produce than a self-installing package. With a .zip or .tar.gz users would be left with an app bundle and no idea of where to put it. Generally they would just throw it somewhere random across the filesystem. At least, that's what non-technical Mac users I know happen to do. [1]: https://support.cdn.mozilla.net/media/uploads/gallery/images/2012-01-26-17-04-06-2b7732.png https://support.cdn.mozilla.net/media/uploads/gallery/images...
- mikeash 12y agoI think the proper solution to that, if there's actually a problem with "somewhere random", is to have apps that move themselves on first launch. It's pretty easy to do, and IMO easier than creating a consistent build process for a good-looking dmg.
- bane 12y agoI could see this being a ridiculously easy way to distribute portable applications.