From: Chris Hanson <cmhanson@eschatologist.net>
To: arnold@skeeve.com
Cc: tuhs@minnie.tuhs.org, gtaylor@tnetconsulting.net
Subject: Re: [TUHS] /bin vs /sbin
Date: Fri, 29 Jan 2021 15:50:23 -0800 [thread overview]
Message-ID: <40DAE471-0FDF-4891-8E66-817E1B7059C7@eschatologist.net> (raw)
In-Reply-To: <202007211822.06LIMBJ4018831@freefriends.org>
On Jul 21, 2020, at 11:22 AM, arnold@skeeve.com wrote:
>
> This is also when /var came into being for log files and such;
> again - it was per machine space, so it lived either on a small disk
> in the workstation or on a per-client chunk of space on the server
> if the client was totally diskless.
And then NeXT went a little further, making /etc, /var, and /tmp symlinks to entries in /private, so each netbooted system only needed two main mount points:
/ could be read-only, served from any number of servers for load-balancing, and shared among all systems running NEXTSTEP (even across architectures, thanks to multi-arch binaries).
/private could be per-machine and could come from a server near that machine to manage load.
It meant your admins just needed the MAC address of a new system (to create the NetInfo /machines entry for it) and it would be immediately usable on the network.
All of our NeXT-derived operating systems still follow this filesystem layout, though only a tiny number (relatively speaking) are netbooted these days. (I don't even remember whether netboot is supported any more…)
-- Chris
prev parent reply other threads:[~2021-01-30 0:00 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
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 [this message]
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=40DAE471-0FDF-4891-8E66-817E1B7059C7@eschatologist.net \
--to=cmhanson@eschatologist.net \
--cc=arnold@skeeve.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).