The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] /bin vs /sbin
Date: Tue, 21 Jul 2020 21:27:59 -0600	[thread overview]
Message-ID: <b5ba60e5-c602-602b-db83-1bc64bba3db8@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20200722011603.GA1536749@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

On 7/21/20 7:16 PM, tytso@mit.edu wrote:
> Yeah, that's definitely not right.  /sbin had been around for 
> "essential system binaries" long before Linux, and Linux took it 
> from there.

I'm sorry, I think there has been a misunderstanding.  I did not mean to 
imply that Linux influenced the larger Unix community with /sbin. 
Rather the other way around, that that's the time that Linux had been 
influenced about /sbin.

> You can see this from the Linux Filesystem Hierarchy Standard (earlier 
> named fsstnd, which specified /sbin as "essential system binaries").

I should revisit that, particularly in light of an older name and use.

> SunOS used that nomenclature and the GNU tools all used /sbin for 
> that purpose.

Did Solaris follow in SunOS's foot steps?  Or did Solaris do something 
different?

> The other thing I'd again urge is that you not take HJ Lu's boot/root 
> disks as being influencial after early 1992.

Okay.  I naively thought that HJ Lu's boot/root was falling out of favor 
in '93, a year later.  Thank you for clarifying Warner.



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]

  reply	other threads:[~2020-07-22  3:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 17:55 Grant Taylor via TUHS
2020-07-21 18:15 ` Warner Losh
2020-07-21 22:42   ` David Arnold
2020-07-22  3:33     ` Warner Losh
2020-07-21 18:22 ` arnold
2020-07-21 18:33   ` Warner Losh
2020-07-21 18:43     ` Larry McVoy
2020-07-22  1:16     ` tytso
2020-07-22  3:27       ` Grant Taylor via TUHS [this message]
2020-07-22  3:35         ` Warner Losh
2021-01-27  5:56         ` Greg A. Woods
2021-01-27 19:06           ` Grant Taylor via TUHS
2021-01-27 22:22             ` Warner Losh
2021-01-27 22:35             ` Greg A. Woods
2021-01-28  5:24               ` Grant Taylor via TUHS
2020-07-22  1:44     ` Dan Cross
2020-07-22  2:17       ` Jon Forrest
2020-07-22  2:20         ` Adam Thornton
2020-07-22 13:30           ` Clem Cole
2020-07-22 13:43             ` Richard Salz
2020-07-22  2:27       ` Kurt H Maier
2020-07-21 19:24   ` Clem Cole
2020-07-22 13:39     ` Clem Cole
2021-01-29 23:50   ` Chris Hanson

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=b5ba60e5-c602-602b-db83-1bc64bba3db8@spamtrap.tnetconsulting.net \
    --to=tuhs@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    /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).