@ecmaos/kernel 0.9.3 → 0.9.4

package/dist/initfs.demo/usr/share/docs/@zenfs/core/devices.md

@@ -0,0 +1,58 @@
+---
+title: Devices and Device Drivers
+---
+
+> [!WARNING]
+> The device and device driver API is being upgraded into a broader "kernel" module API.
+> See [#262](https://github.com/zen-fs/core/issues/262) for more information.
+
+ZenFS includes support for device files. These are designed to follow Linux's device file behavior, for consistency and ease of use. You can automatically add some normal devices with the `addDevices` configuration option:
+
+```ts
+await configure({
+	mounts: {
+		/* ... */
+	},
+	addDevices: true,
+});
+
+fs.writeFileSync('/dev/null', 'Some data to be discarded');
+
+const randomData = new Uint8Array(100);
+
+const random = fs.openSync('/dev/random', 'r');
+fs.readSync(random, randomData);
+fs.closeSync(random);
+```
+
+## Device Drivers
+
+You can create your own devices by implementing a `DeviceDriver`. For example, the null device looks similar to this:
+
+```ts
+const customNullDevice = {
+	name: 'custom_null',
+	// only 1 can exist per DeviceFS
+	singleton: true,
+	// optional if false
+	isBuffered: false,
+	read() {
+		return 0;
+	},
+	write() {
+		return 0;
+	},
+};
+```
+
+Note the actual implementation's write is slightly more complicated since it adds to the file position. You can find more information on the docs.
+
+Finally, if you'd like to use your custom device with the file system:
+
+```ts
+import { addDevice, fs } from '@zenfs/core';
+
+addDevice(customNullDevice);
+
+fs.writeFileSync('/dev/custom', 'This gets discarded.');
+```

package/dist/initfs.demo/usr/share/docs/@zenfs/core/index.md

@@ -0,0 +1,192 @@
+# ZenFS
+
+ZenFS is a cross-platform library that emulates the [Node.js filesystem API](http://nodejs.org/api/fs.html).
+It works using a system of backends, which are used by ZenFS to store and retrieve data.
+ZenFS can also integrate with other tools.
+
+## Backends
+
+ZenFS is modular and easily extended. The core includes some built-in backends:
+
+- `InMemory`: Stores files in-memory. This is cleared when the runtime ends (e.g. a user navigating away from a web page or a Node process exiting)
+- `CopyOnWrite`: Use readable and writable file systems with [copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write).
+- `Fetch`: Downloads files over HTTP with the `fetch` API
+- `Port`: Interacts with a remote over a `MessagePort`-like interface (e.g. a worker)
+- `Passthrough`: Use an existing `node:fs` interface with ZenFS
+- `SingleBuffer`: A backend contained within a single buffer. Can be used for synchronous multi-threaded operations using `SharedArrayBuffer`
+
+ZenFS supports a number of other backends.
+Many are provided as separate packages under `@zenfs`.
+More backends can be defined by separate libraries by extending the `FileSystem` class and providing a `Backend` object.
+
+You can find all of the packages available over on [NPM](https://www.npmjs.com/org/zenfs). Below is a list of the backends included with some of them:
+
+- @zenfs/archives: `Zip`, `Iso`
+- @zenfs/cloud: `Dropbox`, `GoogleDrive`, `S3Bucket`
+- @zenfs/dom: `WebAccess` (Web [File System Access API](https://developer.mozilla.org/en-US/docs/Web/API/File_System_API)/OPFS), `IndexedDB`, `WebStorage` (`localStorage`/`sessionStorage`), `XML` (DOM elements)
+- @zenfs/emscripten: `Emscripten` and a plugin for Emscripten's file system API
+
+As an added bonus, all ZenFS backends support synchronous operations.
+Additionally, all of the backends included with the core are cross-platform.
+
+For more information, see the [docs](https://zenfs.dev/core).
+
+## Installing
+
+```sh
+npm install @zenfs/core
+```
+
+If you're using ZenFS, especially for big projects, please consider supporting the project.
+Thousands of hours have been dedicated to its development.
+Your financial support would go a long way toward improving ZenFS and its community.
+
+## Usage
+
+```js
+import { fs } from '@zenfs/core'; // You can also use the default export
+
+fs.writeFileSync('/test.txt', 'You can do this anywhere, including browsers!');
+
+const contents = fs.readFileSync('/test.txt', 'utf-8');
+console.log(contents);
+```
+
+#### Using different and/or multiple backends
+
+A single `InMemory` backend is created by default, mounted on `/`.
+
+You can configure ZenFS to use a different backend and mount multiple backends. It is strongly recommended to do so using the `configure` function.
+
+You can use multiple backends by passing an object to `configure` which maps paths to file systems.
+
+The following example mounts a zip file to `/zip`, in-memory storage to `/tmp`, and IndexedDB to `/home`. Note that `/` has the default in-memory backend.
+
+```js
+import { configure, InMemory } from '@zenfs/core';
+import { IndexedDB } from '@zenfs/dom';
+import { Zip } from '@zenfs/archives';
+
+const res = await fetch('mydata.zip');
+
+await configure({
+	mounts: {
+		'/mnt/zip': { backend: Zip, data: await res.arrayBuffer() },
+		'/tmp': InMemory,
+		'/home': IndexedDB,
+	},
+});
+```
+
+Note that while you aren't required to use absolute paths for the keys of `mounts`, it is a good practice to do so.
+
+> [!TIP]
+> When configuring a mount point, you can pass in
+>
+> 1. A `Backend` object, if the backend has no required options
+> 2. An object that has the options accepted by the backend and a `backend` property which is a `Backend` object
+> 3. A `FileSystem` instance
+
+Here is an example that mounts the `WebStorage` backend from `@zenfs/dom` on `/`:
+
+```js
+import { configureSingle, fs } from '@zenfs/core';
+import { WebStorage } from '@zenfs/dom';
+
+await configureSingle({ backend: WebStorage });
+
+if (!fs.existsSync('/test.txt')) {
+	fs.writeFileSync('/test.txt', 'This will persist across reloads!');
+}
+
+const contents = fs.readFileSync('/test.txt', 'utf-8');
+console.log(contents);
+```
+
+#### FS Promises
+
+The FS promises API is exposed as `promises`.
+
+```js
+import { configureSingle } from '@zenfs/core';
+import { exists, writeFile } from '@zenfs/core/promises';
+import { IndexedDB } from '@zenfs/dom';
+
+await configureSingle({ backend: IndexedDB });
+
+const exists = await exists('/myfile.txt');
+if (!exists) {
+	await writeFile('/myfile.txt', 'Lots of persistent data');
+}
+```
+
+> [!NOTE]
+> You can import the promises API using:
+>
+> 1. Exports from `@zenfs/core/promises`
+> 2. The `promises` export from `@zenfs/core`
+> 3. `fs.promises` on the exported `fs` from `@zenfs/core`.
+
+#### Mounting and unmounting, creating backends
+
+If you would like to create backends without configure (e.g. to do something dynamic at runtime), you may do so by importing the backend and calling `resolveMountConfig` with it.
+
+You can then mount and unmount the backend instance by using `mount` and `umount`.
+
+```js
+import { configure, resolveMountConfig, InMemory } from '@zenfs/core';
+import { IndexedDB } from '@zenfs/dom';
+import { Zip } from '@zenfs/archives';
+
+await configure({
+	mounts: {
+		'/tmp': InMemory,
+		'/home': IndexedDB,
+	},
+});
+
+fs.mkdirSync('/mnt/zip', { recursive: true });
+
+const res = await fetch('mydata.zip');
+const zipfs = await resolveMountConfig({ backend: Zip, data: await res.arrayBuffer() });
+fs.mount('/mnt/zip', zipfs);
+
+// do stuff with the mounted zip
+
+fs.umount('/mnt/zip'); // finished using the zip
+```
+
+> [!CAUTION]
+> Instances of backends follow the _internal_ API. You should never use a backend's methods unless you are extending a backend.
+
+### Devices and device files
+
+ZenFS includes support for device files. These are designed to follow Linux's device file behavior, for consistency and ease of use. Check out the [Devices and Device Drivers](https://zenfs.dev/core/documents/Devices_and_Device_Drivers) documentation for more information.
+
+## `node:*` emulation
+
+ZenFS also includes emulation of some other `node:` modules for various reasons, importable from `@zenfs/core/<name>`:
+
+- `node:path`
+- `node:readline`
+
+For example:
+
+```ts
+import * as path from '@zenfs/core/path';
+```
+
+## Bundling
+
+ZenFS exports a drop-in for Node's `fs` module, so you can use it for your bundler of preference using the default export.
+
+> [!IMPORTANT]
+> See [COPYING.md](./COPYING.md)
+
+## Sponsors
+
+A huge thank you to [deco.cx](https://github.com/deco-cx) for sponsoring ZenFS and helping to make this possible.
+
+## Contact and Support
+
+You can reach out [on Discord](https://zenfs.dev/discord) or by emailing jp@zenfs.dev

package/dist/initfs.demo/usr/share/docs/@zenfs/core/internal.md

@@ -0,0 +1,31 @@
+---
+title: Internal API
+category: Internals
+---
+
+## Overview
+
+The Internal API is the foundation of ZenFS, providing a standardized interface for managing file systems and file operations. All backends must instantiate a `FileSystem` implementation that conforms to this API, ensuring compatibility with the Virtual File System (VFS) and applications using ZenFS.
+
+## `FileSystem`
+
+The `FileSystem` class is the core of the internal API. It abstracts file storage operations, metadata management, and error handling. `FileSystem` does a few things:
+
+**Storage Abstraction:** Defines how files and directories are represented within a backend.
+
+**Usage Information (`UsageInfo`):** Tracks available storage, block sizes, and inode counts.
+
+**Metadata:** Various pieces of metadata, which are used by the VFS. This includes:
+
+- `attributes` is designed to keep track of simple values. This is analogous to options in [/etc/fstab](https://en.wikipedia.org/wiki/Fstab).
+- `name` is for the name of the file system type. For example, `tmpfs` is the name of `InMemory`. This is modeled after `file_system_type->name` in Linux
+- `id` is a unique 32-bit unsigned integer for the type of file system. It is currently unused internally but may in the future (one compelling use case is to resolve collisions of `name`). This is primarily designed for users, for example it could be used for partition tables.
+- `label` is an optional field that is designed to be used with instances. This is the same as labels in the context of normal partitions and file systems.
+
+**File Operations:** Implements core actions like creating, reading, writing, and deleting files.
+
+**Error Handling:** Standardizes file system errors.
+
+## Backends and the Internal API
+
+Backends in ZenFS do not implement file operations directly. Instead, they instantiate a `FileSystem` implementation that conforms to the internal API.

package/dist/initfs.demo/usr/share/docs/@zenfs/core/security.md

@@ -0,0 +1,64 @@
+---
+title: Security
+---
+
+> [!WARNING]
+> Since ZenFS exists purely client-side, this is **not** a true security boundary!
+
+## Overview
+
+Security in ZenFS is handled at the Virtual File System (VFS) level, ensuring that file operations comply with access control rules before interacting with storage backends. The primary mechanisms for enforcing security include permissions enforcement, user credential management, and execution contexts. ZenFS is designed to be used with a _single import per ES realm_.
+
+## Permissions Enforcement in the VFS
+
+The VFS is responsible for checking file permissions before executing operations. This ensures that unauthorized access attempts are blocked before reaching the backend storage system. Permissions are enforced based on the user ID (UID) and group ID (GID) associated with the process performing the operation.
+
+## `chroot`: Isolated Execution
+
+`chroot` in ZenFS is implemented as a shortcut for creating a new execution context or modifying an existing one. The effective uid or gid of the current set of credentials object _must_ be 0, which ensures untrusted code given a `chroot`ed environment cannot escape.
+
+```ts
+import { fs } from '@zenfs/core';
+
+const ctx = fs.chroot('/sandbox');
+ctx.writeFileSync('/file.txt', 'Restricted');
+console.log(ctx.readdirSync('/'));
+```
+
+## User and Group ID Management via `configure`
+
+ZenFS allows modifying user and group IDs (UID/GID) through configure. This allows you to use permissions, since by default the root user always has permission.
+
+Example Configuration
+
+```ts
+await configure({ uid: 1001, gid: 1001 });
+```
+
+## Credentials Management
+
+ZenFS maintains an internal credentials system, similar to the Linux `cred` struct, which defines the user and group ownership of operations.
+
+## Contexts: Secure Execution Environments (kind of)
+
+Contexts (`FSContext`/`BoundContext`) in ZenFS define isolated execution environments that enforce security constraints. Each context has:
+
+- A root directory (enabling `chroot`-like isolation).
+- Bound credentials that determine access permissions.
+- A present working directory for the context
+- A map of open files and their descriptors
+- References to the parent and children contexts
+
+**Example: Using a Context**
+
+```ts
+import { bindContext, fs } from '@zenfs/core';
+
+const ctx = bindContext({ root: '/secure', uid: 333, gid: 333 });
+
+ctx.writeFileSync('/data.txt', 'Restricted Access');
+
+console.log(fs.readdirSync('/secure')); // ['data.txt']
+```
+
+Contexts provide the fundamentals for building custom processes, the primary unit of execution in operating systems. By encapsulating a root directory and credentials, contexts allow for controlled access, process isolation, and flexible permission management. This design mirrors how modern OSes handle security and execution environments, enabling fine-grained control over filesystem interactions.

package/dist/initfs.demo/usr/share/docs/@zenfs/core/vfs.md

@@ -0,0 +1,35 @@
+---
+title: Virtual File System (VFS)
+---
+
+## Overview
+
+The Virtual File System (VFS) in ZenFS provides an abstraction layer that emulates the `node:fs` API, allowing applications to interact with files and directories in a unified manner. The VFS is responsible for handling path resolution, managing file system contexts, and mounting various storage backends.
+
+### Path Translation and Resolution
+
+The VFS converts user-provided paths into normalized absolute paths that the system can process. It also resolves which path corresponds to which mounted file system. This ensures compatibility with different storage backends and maintains a consistent structure across the system. Also, the VFS handles support for symlinks— which the internal API is unaware of.
+
+### `node:fs` Emulation
+
+The VFS provides a consistent API that mirrors Node.js's built-in file system module— down to full type compatibility!
+
+### Contexts and permissions
+
+_Main article: [Security](./security.md)_
+
+Contexts in ZenFS encapsulate file system operations within an execution scope. In addition to changing the uid/gid, this allows the ability to effectively `chroot`.
+
+### Mounts
+
+ZenFS allows mounting multiple storage backends, enabling seamless access to diverse storage implementations. A mounted backend can be a local filesystem, an in-memory store, a cloud providers storage system (e.g. Google Drive), etc. The limit is your imagination. Some nice features include hot-swapping mounts and per-mount configurations.
+
+### Files and File Descriptors
+
+The VFS is also responsible for handling open files and file descriptors.
+
+### Integration with Backends
+
+_Main article: [Backends](./backends.md)_
+
+The VFS does not directly interact with storage media but instead routes all file operations to the appropriate backend. This design ensures modularity and simplifies the addition of new storage backends.

package/dist/initfs.demo/usr/share/licenses/@ecmaos/kernel/LICENSE

@@ -0,0 +1,7 @@
+# Dual MIT/Apache-2.0 License
+
+Copyright (c) 2024-2026 Jay Mathis <code@mathis.network>
+
+Except as otherwise noted in individual files, this software is licensed under the MIT license (<http://opensource.org/licenses/MIT>), or the Apache License, Version 2.0 (<http://www.apache.org/licenses/LICENSE-2.0>).
+
+Downstream projects and end users may choose either license individually, or both together, at their discretion. The motivation for this dual-licensing is the additional software patent assurance provided by Apache 2.0.

package/dist/initfs.demo/usr/share/licenses/@ecmaos/kernel/LICENSE-APACHE

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+Copyright (c) 2024-2026 Jay Mathis <code@mathis.network>

package/dist/initfs.demo/usr/share/licenses/@ecmaos/kernel/LICENSE-MIT

@@ -0,0 +1,21 @@
+# MIT License
+
+Copyright (c) 2024-2026 Jay Mathis <code@mathis.network>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/initfs.demo/usr/share/licenses/@zenfs/core/COPYRIGHT.txt

@@ -0,0 +1,3 @@
+ZenFS, LGPL-3.0-or-later, Copyright © James Prevett and other ZenFS contributors
+https://github.com/zen-fs/core
+