Mastodawn

On #Illumos, Joy vi is in /usr/src/cmd/vi:

https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi

On #OpenBSD, Bostic #nvi is in /usr/src/usr.bin/vi/vi; #NetBSD having it in /usr/src/external/bsd/nvi; and #FreeBSD in /usr/src/contrib/nvi:

https://cgit.freebsd.org/src/tree/contrib/nvi/

FreeBSD has an nvi2 in ports:

https://freshports.org/editors/nvi2/

OpenBSD has elvis in ports:

https://github.com/openbsd/ports/blob/master/editors/elvis/pkg/DESCR

Ritter's Heirloom vi is on SourceForge:

https://ex-vi.sourceforge.net

STEVIE was posted to comp.sources.unix in 1988:

https://sources.vsta.org/comp.sources.unix/volume15/stevie/

Unfortunately, Sven Guckes's vi Clones WWW site was never completed with some of this, notably lacking Heirloom vi, for example.

https://guckes.net/vi/clones.html

But it does mention oft-overlooked commercial clones such as Watcom's vi, a from-scratch implementation started in 1983 that is also now source-available:

https://github.com/open-watcom/owp4v1copy/tree/master/bld/vi

#vi #retrocomputing #ComputerHistory #STEVIE #elvis #VIM #NeoVIM #Watcom #OpenWatcom

illumos-gate/usr/src/cmd/vi at master · illumos/illumos-gate

An open-source Unix operating system -- this is a read-only mirror of the official repository at https://code.illumos.org/plugins/gitiles/illumos-gate - illumos/illumos-gate

GitHub

JdeBP 20h ago

People waxing lyrical about using 'original vi', both nowadays in 2026 and back in 2006, haven't a clue what that is.

There's only one family of operating systems where 'vi' will actually run the original vi program by Joy, Horton, et al.: #Illumos and its derivatives #Tribblix, #OmniOS, and #SmartOS.

*Everyone else* uses one of the ground-up clones.

On #FreeBSD, #OpenBSD, and #NetBSD, it's Bostic's early 1990s #nvi, which was derived from Kirkendall's elvis, a clone written some time around 1990.

On Linux-based operating systems, vi either is Bostic nvi, or is one of the derivatives of STEVIE (the middle-1980s vi clone for the Atari ST that inspired Kirkendall to write elvis in the first place): Moolenaar's VIM or NeoVIM.

On none of those will you get original Joy+Horton vi in base, or indeed packaged/in ports.

Yes, Heirloom vi exists, which is Ritter's 2002 fork of 1985 Joy+Horton vi. But it's not even available in Arch Linux nowadays.

#vi #retrocomputing #ComputerHistory

Show thread

David Cantrell 🏏3d ago

@bitprophet @daedalus @thomrstrom IME installing #IllumOS is dead easy. If you want to practice in a VM you'll need to use #Virtualbox as it makes #QEMU shit its pants.

Thomas Strömberg 3d ago

I'm procrastinating because I don't know if I'm more scared of rescuing data from this 13TB ZFS volume, or installing #illumos for the first time in forever.

Till Wegmüller 4d ago

Since some people have asked me if I they could collaborate on my rust IPS work, I decided to publish the Repo now on @Codeberg
https://codeberg.org/Toasterson/ips

Note: illumos is the main OS using this package manager but we should make this available for many operatingsystems as we can,

Happy if someone makes ipsOS based on linux aswell. (Please choose a better name though)

The Goal is to bring the IPS innovations to as many people as possible.

#illumos #Rust #Linux

ips

Rust IPS work

Codeberg.org

aru 4d ago

Just watched the recording of @Toasterson 's ips talk. Cool stuff all around

#illumos

Tionisla 4d ago

Just a shout out to everyone directly or loosly involved in *BSD world here on fedi and elsewhere.
Thanks for having me here. It's been a couple of years now since I migrated from Linux and really enjoying it.

be safe and keep up the excellent work,

#appreciation #bsd #kiss #unix #freebsd #openbsd #netbsd #dragonfly #runbsd #illumos

/usr/local/goth @ home 5d ago

Thinking about getting a new case for my old pc and some drives. I've been thinking about running an #illumos distro on there and building my lab off that.

Show thread

JdeBP 5d ago

@dgl @cks @lyda

In the majority of cases there actually is no separate inet_pton() manual page.

https://man.freebsd.org/cgi/man.cgi?query=inet_pton&sektion=3

https://man.netbsd.org/inet_pton.3

http://tribblix.org/man/man3c/inet_pton.html

https://man.omnios.org/man3c/inet.3c

http://uw714doc.xinuos.com/en/man/html.3N/inet.3N.html

Although most of those call out inet_pton(), SCO #UnixWare in fact documented the four human-readable IPv4 formats for inet_pton(), and did not even have an inet_aton().

In #NetBSD, the internal inet_pton4() function was indeed updated by Christos Zoulas from the old Paul Vixie code to support the four human-readable formats of inet_aton(), 22 years ago; although it's not clear where this additional IPv4 conversion functionality is actually used.

The old Paul Vixie code from 1996 is retained in GNU libc, #FreeBSD, & #OpenBSD; this being code from the BIND DNS client library.

It was superseded by a from-scratch reimplementation based around a str2inet_addr() function in #Solaris/ #Illumos/ #Tribblix/ #OmniOS. musl libc also has its own from-scratch version.

@ska