No description
  • Go 99.5%
  • Shell 0.3%
  • Makefile 0.2%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
nobody 7e917f9c3a
All checks were successful
CI / build (push) Successful in 28m34s
chore: cap the CI job at GOMAXPROCS=4, take gosec from the CI image
I do not want a build to take every core of the machine that hosts
my runner. The job sees all 8 cores, and every Go process in it
sized itself for 8. One run pushed the load average past 30 while it
compiled golangci-lint, but the build used only about 3 cores; its
other threads waited to run. I have not found what limits a build to
3 cores in the sandbox, so I arbitrarily picked 4.

`make security-check-deps` compiled gosec from source on every push.
The CI image now has gosec at a pinned version, and the Security
scan step depends on that. The make target is unchanged and still
installs @latest.

golangci-lint is still compiled on every push. That is most of the
CPU time of the job.
2026-11-13 09:21:27 -08:00
.forgejo/workflows chore: cap the CI job at GOMAXPROCS=4, take gosec from the CI image 2026-11-13 09:21:27 -08:00
assets Screenshot 2023-09-03 16:23:39 +01:00
cmd fix: a USB passthrough id above ffff was truncated, not rejected 2026-11-13 09:11:39 -08:00
constants Bump the version to v0.2.0 2023-09-28 11:04:23 +01:00
examples feat: add zfs and up commands to share ZFS pools from the VM 2026-11-04 07:11:58 -08:00
imgbuilder chore: fix the remaining problems that gosec reported 2026-11-13 09:12:30 -08:00
job chore: fix the remaining problems that gosec reported 2026-11-13 09:12:30 -08:00
keys Add a GPG key 2023-09-04 09:41:44 +01:00
nettap chore: fix the remaining problems that gosec reported 2026-11-13 09:12:30 -08:00
osspecifics chore: fix the problems that make lint reported 2026-11-13 07:50:20 -08:00
qemucli Fix aarch64 runtime issues 2023-09-03 16:19:39 +01:00
serious-bug-disclosures Add missing "or" in serious bug disclosure "unless" field 2023-09-30 12:23:16 +01:00
share chore: fix the problems that make lint reported 2026-11-13 07:50:20 -08:00
sshutil chore: fix the problems that make lint reported 2026-11-13 07:50:20 -08:00
storage chore: fix the remaining problems that gosec reported 2026-11-13 09:12:30 -08:00
third_party/aslint chore: get the linter working on Go 1.27 2026-11-13 07:31:19 -08:00
tools/golangci-lint chore: get the linter working on Go 1.27 2026-11-13 07:31:19 -08:00
utils Optional run 2-3 args + -c flag 2023-09-27 15:37:28 +01:00
vm chore: fix the remaining problems that gosec reported 2026-11-13 09:12:30 -08:00
.gitignore chore: run CI on my Forgejo runner instead of GitHub Actions 2026-11-13 07:41:35 -08:00
.golangci.yml chore: fix the problems that make lint reported 2026-11-13 07:50:20 -08:00
AGENTS.md chore: run CI on my Forgejo runner instead of GitHub Actions 2026-11-13 07:41:35 -08:00
build-binaries.sh build-binaries.sh updates 2023-09-28 11:22:25 +01:00
CONTRIBUTING.md chore: get the linter working on Go 1.27 2026-11-13 07:31:19 -08:00
go.mod feat: add zfs and up commands to share ZFS pools from the VM 2026-11-04 07:11:58 -08:00
go.sum feat: add zfs and up commands to share ZFS pools from the VM 2026-11-04 07:11:58 -08:00
INSTALL_MACOS.md Fix go install command 2023-10-09 14:44:28 +01:00
INSTALL_WINDOWS.md Fix go install command 2023-10-09 14:44:28 +01:00
LICENSE Licensing & Copyright 2023-09-02 20:03:44 +01:00
LINUX_DEV_ENV.md More progress writing .md files 2023-09-03 15:01:13 +01:00
main.go Licensing 2023-09-02 20:11:25 +01:00
Makefile chore: get the linter working on Go 1.27 2026-11-13 07:31:19 -08:00
README.md Add missing "or" in serious bug disclosure "unless" field 2023-09-30 12:23:16 +01:00
SHELL.md SHELL.md updates 2023-09-03 16:00:29 +01:00
TROUBLESHOOTING.md More progress writing .md files 2023-09-03 15:01:13 +01:00
USAGE_MACOS.md Update usage guides 2023-09-27 17:17:57 +01:00
USAGE_WINDOWS.md Update usage guides 2023-09-27 17:17:57 +01:00

Linsk

Linsk is a utility that allows you to access Linux-native file system infrastructure, including LVM and LUKS on Windows and macOS. Unlike other solutions created to access Linux filesystems on unsupported operating systems, Linsk does not reimplement any file system. Instead, Linsk utilizes a lightweight Alpine Linux VM (~130 MB only) combined with network share technologies like SMB, AFP, and FTP.

Because Linsk uses a native Linux VM, there are no limitations on what you can access. Anything that works on Linux will work under Linsk too (hence the Linux+Disk name).

To show your thanks, please star this repository if you found it useful.

Screenshot of Linsk running

💻 Supported platforms

CPU architectures

Linsk natively supports both x86_64 (aka amd64, Intel, AMD, etc.) and aarch64 (aka arm64, Apple M1/M2, and others).

Although Linsk uses a virtual machine, the CPU is never emulated but the hardware accelerators like HVF (macOS), WHPX (Windows), and KVM (Linux) are used.

Operating systems

  • Windows
  • macOS
  • Linux (for development purposes, mostly)

Network file share backends

Linsk relies on network file shares to expose files to the host machine. Below are the types of network shares Linsk supports:

  • SMB - The default for Windows.
  • AFP - The default for macOS.
  • FTP - An alternative backend.

💿 Installation

🔧 Usage

⚠️ Serious bug disclosures (Obsolete versions)

Linsk versions below v0.2.0 are considered obsolete UNLESS:

  • The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size; or
  • The experimental USB passthrough was used.

More information: serious-bug-disclosures/README.md

👨‍💻 Contributing

Please see CONTRIBUTING.md.

©️ Copyright and License

Copyright (c) 2023 The Linsk Authors.

Provided under the GNU General Public License v3. The copy of the license is included in the LICENSE file.

Use this git command to view the list of Linsk Authors:

git log --format='%aN <%aE>' | sort -uf