How do I install oksh on Ubuntu?

You can use the unofficial Ubuntu PPA listed in the README or build from source with ./configure && make. For other Debian-based systems, check Repology for package availability or compile manually.

Is oksh better than bash for scripting?

oksh excels in portability and consistency across platforms, making it ideal for heterogeneous environments. However, bash has more features and is the de facto standard on many systems, so choose based on your need for compatibility versus functionality.

Does oksh support vi editing mode?

Yes, as it's based on OpenBSD ksh, oksh includes vi and emacs editing modes by default. You can configure this in your shell settings, similar to other ksh implementations.

Can I use oksh on Android without Termux?

oksh is primarily tested and used with Termux on Android, as mentioned in the README. For other methods, you'd likely need to cross-compile it, which is more complex and less documented.

How to cross-compile oksh for ARM Linux?

Set CC to your cross-compiler, specify CFLAGS and LDFLAGS, and run ./configure with --no-thanks. Then, you may need to manually edit the generated Makefile and pconfig.h before running make, as per the cross-compilation instructions.

What's the difference between oksh and pdksh?

oksh is a portable version of OpenBSD ksh, based on pdksh but with updates from OpenBSD and a focus on maximum portability. Pdksh is an older, public domain implementation, while oksh adds modern support and compatibility across more systems.

Open-Awesome

oksh

Coksh-7.9

A portable, self-contained implementation of the OpenBSD Korn Shell (ksh) that runs across many operating systems and compilers.

GitHub

447 stars46 forks0 contributors

What is oksh?

oksh is a portable implementation of the OpenBSD Korn Shell (ksh) that brings the reliable OpenBSD shell experience to many other operating systems. It solves the problem of shell inconsistency across platforms by providing a single, well-tested ksh that works everywhere from traditional Unix systems to modern environments like Android and WSL.

Target Audience

System administrators, developers, and users who need a consistent Korn Shell experience across multiple operating systems, particularly those managing heterogeneous environments or working on less common platforms.

Value Proposition

Developers choose oksh because it offers genuine OpenBSD ksh functionality with exceptional portability, supporting more platforms and compilers than other ksh ports while maintaining upstream compatibility and a self-contained, dependency-minimal design.

Overview

Portable OpenBSD ksh, based on the Public Domain Korn Shell (pdksh).

Use Cases

Best For

Using OpenBSD's ksh on Linux or macOS systems
Maintaining consistent shell scripts across heterogeneous server environments
Shell development on less common platforms like Haiku, SerenityOS, or IBM i PASE
Testing shell compatibility with multiple C compilers
Cross-compiling shells for embedded or specialized systems
System administration on AIX, Solaris, or HP-UX with modern shell features

Not Ideal For

Environments where bash is the standard and script compatibility with GNU extensions is critical
Users who want modern shell features like real-time syntax highlighting or extensive plugin ecosystems out of the box
Projects requiring rapid adoption of new shell features beyond OpenBSD's release schedule

Pros & Cons

Pros

Maximal Portability

Supports over 20 operating systems, from Linux and BSD variants to niche platforms like Haiku and SerenityOS, as listed in the README, ensuring a consistent shell experience across diverse environments.

Compiler Agnostic

Builds with a wide range of C compilers including clang, gcc, pcc, and even specialized ones like CompCert, enhancing flexibility in development and cross-compilation scenarios.

Self-Contained Design

Includes all necessary portability code, eliminating dependencies on external ksh implementations and simplifying deployment, as emphasized in the project philosophy.

Cross-Compilation Support

Provides configure flags like --no-thanks for easy cross-compilation, useful for targeting embedded or specialized systems, though it requires manual tweaks.

Cons

Upstream Bottleneck

Patches that change behavior must first be submitted to OpenBSD, as noted in the README, potentially slowing the adoption of non-portability enhancements and new features.

Cross-Compilation Complexity

Using --no-thanks for cross-compiling requires manual adjustments to Makefile and pconfig.h, which can be error-prone and less user-friendly compared to automated tools.

Limited Modern Features

Focuses on compatibility over conveniences, lacking built-in advanced features like autocompletion or theming found in shells like zsh, which might require additional configuration.

Frequently Asked Questions

Related Projects

nushell

A new type of shell

Stars39,839

Forks2,165

Last commit10 hours ago

murex

A smarter shell and scripting environment with advanced features designed for usability, safety and productivity (eg smarter DevOps tooling)

Mirror of https://gitlab.redox-os.org/redox-os/ion

Stars1,651

Forks140

Last commit2 months ago

ngs

Next Generation Shell (NGS)

Stars1,522

Forks49

Last commit9 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub