Set correct terminology

[ronaldtse]

• Tebako: the packager
• Tebako package: the combined package that contains the Tebako image and the Tebako launch code
• Tebako image: a "pressed" image that is the DwarFS image
• Tebako init script / "entrypoint" (in Docker terms) script that a Tebako package calls initially

In the future if we support a stacked image, each of those layers is called a layer.

Anything to add @maxirmx ?

[maxirmx]

Tebako package contains:

• the Tebako image
• patched ruby
• original dwarfs library that supports inode-based interface and on-the-fly decompression of Tebako image
• dwarfs wrapper that implements POSIX interface to Tebako image

[ronaldtse]

• patched ruby

Packaged interpreter. Tebako's "packaged Ruby"?

• original dwarfs library that supports inode-based interface and on-the-fly decompression of Tebako image
• dwarfs wrapper that implements POSIX interface to Tebako image

If in the future we support other file system mechanisms, this would be:

• Tebako in-memory file system interface?
• Tebako file system driver?

I wonder if we should add an additional FS mechanism for not using DwarFS just for the sake of it. e.g. Zip file that expands to local temp for execution.

[maxirmx]

• Tebako in-memory file system interface?
• Tebako file system driver?

Agree, this sounds better

[maxirmx]

I wonder if we should add an additional FS mechanism for not using DwarFS just for the sake of it. e.g. Zip file that expands to local temp for execution.

We can easily have mechanism that extract existing image to local temp for execution like described here: #11

[ronaldtse]

Agree @maxirmx !