The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Charles H. Sauer" <sauer@technologists.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Abstractions
Date: Tue, 23 Feb 2021 15:02:00 -0600	[thread overview]
Message-ID: <91696417-3233-232e-e1f4-3cb914202801@technologists.com> (raw)
In-Reply-To: <CMM.0.96.0.1614109077.beebe@gamma.math.utah.edu>

To add to the inventory below:
Dell SVR4 /bin is a symlink to /usr/bin
NEXTSTEP/486 3.3 /bin and /usr/bin are separate

On 2/23/2021 1:37 PM, Nelson H. F. Beebe wrote:
> The recent discussions on the TUHS list of whether /bin and /usr/bin
> are different, or symlinked, brought to mind the limited disk and tape
> sizes of the 1970s and 1980s.  Especially the lower-cost tape
> technologies had issues with correct recognition of an end-of-tape
> condition, making it hard to span a dump across tape volumes, and
> strongly suggesting that directory tree sizes be limited to what could
> fit on a single tape.
> 
> I made an experiment today across a broad range of operating systems
> (many with multiple versions in our test farm), and produced these two
> tables, where version numbers are included only if the O/S changed
> practices:
> 
> ------------------------------------------------------------------------
> Systems with /bin a symlink to /usr/bin (or both to yet another common
> directory) [42 major variants]:
> 
> 	ArchLinux		Kali			RedHat 8
> 	Arco			Kubuntu 19, 20		Q4OS
> 	Bitrig			Lite			ScientificLinux 7
> 	CentOS 7, 8		Lubuntu 19		Septor
> 	ClearLinux		Mabox			Solaris 10, 11
> 	Debian 10, 11		Magiea			Solydk
> 	Deepin			Manjaro			Sparky
> 	DilOS			Mint 20			Springdale
> 	Dyson			MXLinux 19		Ubuntu 19, 20, 21
> 	Fedora			Neptune			UCS
> 	Gnuinos			Netrunner		Ultimate
> 	Gobolinux		Oracle Linux		Unleashed
> 	Hefftor			Parrot 4.7		Void
> 	IRIX			PureOS			Xubuntu 19, 20
> 
> ------------------------------------------------------------------------
> Systems with separate /bin and /usr/bin [60 major variants]:
> 
> 	Alpine			Hipster			OS108
> 	AltLinux		KaOS			Ovios
> 	Antix			KFreeBSD		PacBSD
> 	Bitrig			Kubuntu 18		Parrot 4.5
> 	Bodhi			LibertyBSD		PCBSD
> 	CentOS 5, 6		LMDE			PCLinuxOS
> 	ClonOS			Lubuntu 17		Peppermint
> 	Debian 7--10		LXLE			Salix
> 	DesktopBSD		macOS			ScientificLinux 6
> 	Devuan			MidnightBSD		SlackEX
> 	DragonFlyBSD		Mint 18--20		Slackware
> 	ElementaryOS		MirBSD			Solus
> 	FreeBSD 9--13		MXLinux 17, 18		T2
> 	FuryBSD			NetBSD 6-1010		Trident
> 	Gecko			NomadBSD		Trisquel
> 	Gentoo			OmniOS			TrueOS
> 	GhostBSD		OmniTribblix		Ubuntu 14--18
> 	GNU/Hurd		OpenBSD			Xubuntu 18
> 	HardenedBSD		OpenMandriva		Zenwalk
> 	Helium			openSUSE		Zorinos
> 	
> ------------------------------------------------------------------------
> 
> Some names appear in both tables, indicating a transition from
> separate directories to symlinked directories in more recent O/S
> releases.
> 
> Many of these system names are spelled in mixed lettercase, and if
> I've botched some of them, I extend my apologies to their authors.
> 
> Some of those systems run on multiple CPU architectures, and our test
> farm exploits that; however, I found no instance of the CPU type
> changing the separation or symbolic linking of /bin and /usr/bin.
> 
> -------------------------------------------------------------------------------
> - Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
> - University of Utah                    FAX: +1 801 581 4148                  -
> - Department of Mathematics, 110 LCB    Internet e-mail: beebe@math.utah.edu  -
> - 155 S 1400 E RM 233                       beebe@acm.org  beebe@computer.org -
> - Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
> -------------------------------------------------------------------------------
> 

-- 
voice: +1.512.784.7526       e-mail: sauer@technologists.com
fax: +1.512.346.5240         Web: https://technologists.com/sauer/
Facebook/Google/Skype/Twitter: CharlesHSauer

  reply	other threads:[~2021-02-23 21:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 19:37 Nelson H. F. Beebe
2021-02-23 21:02 ` Charles H. Sauer [this message]
2021-02-23 21:15   ` Henry Bent
2021-02-24  2:47     ` Greg A. Woods
2021-02-24  3:20       ` Warner Losh
2021-02-24 20:05         ` Greg A. Woods
2021-02-24  1:51 ` Greg A. Woods
2021-02-24  2:23   ` Nelson H. F. Beebe
  -- strict thread matches above, loose matches on Subject: below --
2021-02-24  4:18 Rudi Blom
2021-02-21 10:47 Paul Ruizendaal
2021-02-20 23:09 M Douglas McIlroy
2021-02-21  8:15 ` Otto Moerbeek
2021-02-21 11:08 ` Rich Morin
2021-02-21 22:40 ` Dave Horsfall
2021-02-21 23:01   ` Steve Nickolas
2021-02-23  3:31     ` Andrew Warkentin
2021-02-22  0:13   ` Warren Toomey
2021-02-27  2:47     ` Dave Horsfall
2021-02-23  0:25   ` Wesley Parish
2021-02-23  0:38     ` Steve Nickolas
2021-02-23  2:50       ` Theodore Ts'o
2021-02-23  3:19         ` Warner Losh
2021-02-23  1:47     ` Theodore Ts'o
2021-02-21 22:54 ` Clem Cole
2021-02-15 19:56 Jon Steinhart
2021-02-15 21:52 ` Dave Horsfall
2021-02-16  7:13   ` arnold
2021-02-16  8:15 ` Tom Ivar Helbekkmo via TUHS
2021-02-16 10:04   ` Wesley Parish
2021-02-16 19:59   ` Jon Steinhart
2021-02-17  4:01     ` Theodore Ts'o
2021-02-17  6:50     ` Chris Hanson
2021-02-16 12:26 ` Rich Morin
2021-02-16 22:46 ` Steffen Nurpmeso
2021-02-17 12:09 ` David Arnold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=91696417-3233-232e-e1f4-3cb914202801@technologists.com \
    --to=sauer@technologists.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).