From: Steve Nickolas <usotsuki@buric.co>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Abstractions
Date: Sun, 21 Feb 2021 18:01:34 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2102211758180.5567@sd-119843.dedibox.fr> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2102220924220.70858@aneurin.horsfall.org>
On Mon, 22 Feb 2021, Dave Horsfall wrote:
> I once worked for a place who reckoned that /bin and /lib etc ought to be in
> an EEPROM; I reckon that he was right (Penguin/OS dumps everything under
> /usr/bin, for example).
I have used distributions in the past that maintained the traditional
distinction.
While I've been stuck regarding bringing up a kernel, C compiler and libc
all together, (keeping in mind my desire to avoid gcc and glibc for the
project) the conceptual distribution I've been working on for some time
uses more or less the same abstraction as the BSDs, with distinct /bin and
/sbin vs. /usr/bin and /usr/sbin as I personally believe it should be,
that the stuff in /bin should be enough to bring up and/or run diagnostics
on a system, and everything else go in /usr.
-uso.
next prev parent reply other threads:[~2021-02-21 23:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2021-02-23 3:31 ` Andrew Warkentin
2021-02-23 17:29 ` [TUHS] /usr separation (was: Abstractions) Greg A. Woods
2021-02-23 18:28 ` [TUHS] /usr separation Grant Taylor via TUHS
2021-02-23 18:57 ` Theodore Ts'o
2021-02-23 20:29 ` Grant Taylor via TUHS
2021-02-24 14:14 ` Theodore Ts'o
2021-02-24 17:50 ` Grant Taylor via TUHS
2021-02-24 18:37 ` Theodore Ts'o
2021-02-24 18:48 ` Grant Taylor via TUHS
2021-02-25 3:38 ` Theodore Ts'o
2021-02-24 20:25 ` Steve Nickolas
2021-02-24 22:08 ` Steffen Nurpmeso
2021-02-24 3:12 ` [TUHS] /usr separation (was: Abstractions) Andrew Warkentin
2021-02-22 0:13 ` [TUHS] Abstractions 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
-- strict thread matches above, loose matches on Subject: below --
2021-02-24 4:18 Rudi Blom
2021-02-23 19:37 Nelson H. F. Beebe
2021-02-23 21:02 ` Charles H. Sauer
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
2021-02-21 10:47 Paul Ruizendaal
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=alpine.DEB.2.21.2102211758180.5567@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=dave@horsfall.org \
--cc=tuhs@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).