From: Warner Losh <imp@bsdimp.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] /bin vs /sbin
Date: Tue, 21 Jul 2020 21:35:56 -0600 [thread overview]
Message-ID: <CANCZdfpT1NOCk=B1J-+PRRs9ovUZzX14SkK+ep-Cd=ZnBv3nNQ@mail.gmail.com> (raw)
In-Reply-To: <b5ba60e5-c602-602b-db83-1bc64bba3db8@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Tue, Jul 21, 2020, 9:30 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
wrote:
> 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.
>
I think it was Ted clarifying me :)
Warner
>
> --
> Grant. . . .
> unix || die
>
>
[-- Attachment #2: Type: text/html, Size: 2070 bytes --]
next prev parent reply other threads:[~2020-07-22 3:37 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
2020-07-22 3:35 ` Warner Losh [this message]
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='CANCZdfpT1NOCk=B1J-+PRRs9ovUZzX14SkK+ep-Cd=ZnBv3nNQ@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=gtaylor@tnetconsulting.net \
--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).