From: Clem Cole <clemc@ccc.com>
To: M Douglas McIlroy <m.douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Abstractions
Date: Sun, 21 Feb 2021 17:54:19 -0500 [thread overview]
Message-ID: <CAC20D2MoRbm09TSgA5URU+pQdgbUzJJTyazPkxC12S3Sey-U8w@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiXW80gL1Hy7nVTrZ1Wm-zbKZGUj8+T8Ui4cjWdW=vV1LA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
On Sat, Feb 20, 2021 at 6:10 PM M Douglas McIlroy <
m.douglas.mcilroy@dartmouth.edu> wrote:
> > - separation of code and data using read-only and read/write file
> systems
>
> I'll bite. How do you install code in a read-only file system? And
> where does a.out go?
>
The best way I have seen this done is with overlay and union file system
support. The 'writeable' versions are the file in /bin are overlayed as
needed. To do this properly you need the stackable file system stuff we
worked on at LCC and Sun. If you can interpose at the inode level it's
very cool and flexible (Sun played with - but makes the Sun symlink
nightmare seem like an easy night at the movies), at the filesystem switch
layer (Locus and UCLA - scheme that was in BSD at one point - easier to
manage/admin).
ᐧ
[-- Attachment #2: Type: text/html, Size: 1892 bytes --]
next prev parent reply other threads:[~2021-02-21 22:55 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
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 [this message]
-- 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=CAC20D2MoRbm09TSgA5URU+pQdgbUzJJTyazPkxC12S3Sey-U8w@mail.gmail.com \
--to=clemc@ccc.com \
--cc=m.douglas.mcilroy@dartmouth.edu \
--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).