Install and Use BusyBox on Windows
Windows-only skill for detecting CPU/OS and downloading the right BusyBox build to run Unix commands via a single binary.
Why it matters
Leverage the power of Unix command-line utilities directly on your Windows system. This asset automates the download and setup of BusyBox, enabling you to run essential Unix tools for system information gathering and task automation.
Outcomes
What it gets done
Download and install BusyBox.exe for Windows (32/64-bit, ANSI/Unicode).
Execute Unix commands like 'ls', 'grep', and 'find' on Windows.
Gather system information such as CPU details and OS version.
Access BusyBox help and list available commands.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-busybox-on-windows | bash Overview
Busybox On Windows
A Windows-only skill for detecting CPU/OS and downloading the matching BusyBox build to run Unix commands via a single binary. Use only on Windows when native Unix tooling isn't available; not applicable on UNIX/Linux/macOS systems.
What it does
This skill provides Unix command-line tools on Windows via BusyBox, a single binary that implements many common Unix utilities. It's Windows-only - on UNIX systems, the skill explicitly says to stop and not proceed. If busybox.exe isn't already present, it detects the CPU type (Get-CimInstance -ClassName Win32_Processor) and Windows version (Get-ItemProperty on the registry's CurrentVersion key) via PowerShell, then downloads the matching build: 32-bit x86 (ANSI), 64-bit x86 (ANSI), 64-bit x86 (Unicode), or 64-bit ARM (Unicode), each via a specific Invoke-WebRequest command.
Once downloaded, busybox.exe --list shows available commands, and any Unix command is run by prefixing it with busybox.exe (e.g. busybox.exe ls -1). Commands under a different working directory use the absolute path to busybox.exe.
When to use - and when NOT to
Use this only on Windows when Unix commands are needed but not natively available - detecting the correct CPU/OS combination and fetching the matching BusyBox build if one isn't already present.
Not applicable on UNIX/Linux/macOS systems, which already have native Unix tooling - the skill explicitly instructs to stop if not on Windows.
Inputs and outputs
Inputs: none beyond confirming the platform is Windows and checking whether busybox.exe already exists locally.
Outputs: a downloaded busybox.exe matching the system's CPU architecture and Windows version, and Unix commands executed by prefixing them with busybox.exe.
Integrations
BusyBox (frippery.org build for Windows), PowerShell (Get-CimInstance, Get-ItemProperty, Invoke-WebRequest).
Who it's for
Anyone working on Windows who needs Unix command-line tools available without installing WSL or a full Unix environment.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.