From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>,
Grant Taylor <gtaylor@tnetconsulting.net>
Subject: Re: [TUHS] Pre-init initialization
Date: Thu, 8 Aug 2019 12:59:23 -0600 [thread overview]
Message-ID: <CANCZdfqksWFQ-vMZtZjaQO0agCrdrDL0HeMEwjD1mLnBC9+CVA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Pu0Jwfs=qFc2gVAzDpyuR4gvPepo8RVuC-=YsPM4keoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On Thu, Aug 8, 2019 at 7:43 AM Clem Cole <clemc@ccc.com> wrote:
>
>
> On Wed, Aug 7, 2019 at 12:40 PM Warner Losh <imp@bsdimp.com> wrote:
>
>> This obviated the need to copy a filesystem to a new disk's swap space
>> and then use that to really install the system.
>>
>
> Thanks for the reminder. I don't remember if V7 on the PDP-11 used the
> swap space (but I don't think so). That said, I fairly sure that by BSD 4.1
> the boot loader did, which I think is when that trick was first added to
> boot phase.
>
Just checked the archives. V7 had a stand alone program to restore a
filesystem image form the tape to the disk that you ran after running the
stand alone program to partition and newfs the disk... I think you are
right on your timeline. I installed a dozen Sun3 boxes from tape and hated
mistyping the file number and having to start over...
> Again, it was all about trying to get rid of the special /stand version of
> things. Funny, history would move on and we come back to that idea with
> busybox 🤔
>
Well, busybox is special in many ways, so there's that in common with
/stand, but it runs under a full otherwise standard kernel, not as some
special mini-exec that provides just enough of the unix APIs to keep the
standalone programs happy.
Warner
[-- Attachment #2: Type: text/html, Size: 2369 bytes --]
next prev parent reply other threads:[~2019-08-08 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 23:46 Grant Taylor via TUHS
2019-08-07 1:22 ` Andrew Warkentin
2019-08-07 13:04 ` Clem Cole
2019-08-07 16:40 ` Warner Losh
2019-08-08 13:31 ` Theodore Y. Ts'o
2019-08-09 1:52 ` Grant Taylor via TUHS
2019-08-10 0:23 ` Theodore Y. Ts'o
2019-08-10 2:28 ` Grant Taylor via TUHS
2019-08-10 4:21 ` Kevin Bowling
2019-08-10 4:50 ` Grant Taylor via TUHS
2019-08-10 4:52 ` Adam Thornton
2019-08-08 13:43 ` Clem Cole
2019-08-08 18:59 ` Warner Losh [this message]
2019-08-09 1:46 ` Grant Taylor via TUHS
2019-08-09 2:15 ` Warner Losh
2019-08-09 6:43 ` Kevin Bowling
2019-08-10 1:45 ` 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=CANCZdfqksWFQ-vMZtZjaQO0agCrdrDL0HeMEwjD1mLnBC9+CVA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=clemc@ccc.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).