The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 17:01:36 -0400	[thread overview]
Message-ID: <CAC20D2MAjpiW3Cg4e0syi+EO9fkDuAjc7oBK1L_rne-PTkD6kg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NymVJ=fxcwBUk3ObU_iwc+FieOXLpnt-d=PJwJuzdAeg@mail.gmail.com>

BTW: Mark if you are running on a simulator, just create an extra drive in
the RK05 driver, put 4280 blocks on it and mount it on /tmp in /etc/rc when
you go multi-user.     You should be all set, and you will be running like
many/most V6 and V7 systems in years gone by.

On Wed, Jul 27, 2016 at 4:57 PM, Clem Cole <clemc at ccc.com> wrote:

> That is exactly how its was done.   In fact, DEC made a Solid State Disk
> (out of RAM) just for UNIX that people used to use for /tmp.
>
>
> Also to be fair, Dennis did symlinks before 4.2.   They were part of the
> V8 I believe.  I remember talking to him and Steve Bourne about them and
> ideas in the FS.  Dennis's basic thesis was that while UNIX had a typed
> file system, he & Ken intentionally kept the number of types very very
> small.    The problem he was afraid of what that too many systems had ended
> up so many different ways to handle things.    Just keep everything as a
> ASCII text file and let the user space deal with it.   Symlinks, or "late
> name binding" for the FS was a mixed bag.    Just as Dennis predicted,
> Solaris was an example of an implementation that went symlink happy.
>
> I created Conditionally Dependant Symlinks (CDSL) which I think only
> showed up in Masscomp's RTU, Stellix and Tru64.   The were not only late
> binding, but added the concept of a user settable context.   Very handy
> when trying to create a "single system image" from multiple system.   I
> miss them today from Linux clusters and even put them back into one of my
> systems.   B
>
>
> Also, around the same time that Dennis added symlinks, Apollo's Aegis (aka
> Domain) guys came up with a cool idea where you can run application code
> from a link - extensible types.    I remember talking to Dennis and Ken
> about them at a SOSP IIRC, and toyed with putting them into one of the
> Locus UNIX Kernels.   We proposed it for HP-UX and Tru64, but never got
> funded to try it, although I think / believe others did some where else.
>
>
>
> On Wed, Jul 27, 2016 at 4:31 PM, William Pechter <pechter at gmail.com>
> wrote:
>
>> Mark Longridge wrote:
>> > Hi folks,
>> >
>> > My root partition for Unix v6 is almost full and /dev/rk0 only has 83
>> blocks.
>> >
>> > The trouble is I wanted to compile bc.y and I think it needs around
>> > 300 blocks of temporary space. I was wondering if there was a way to
>> > set up Unix v6 so that it could use one of the other drives for tmp
>> > space. I tried to set up a link using ln but it seems I can't link
>> > across filesystems.
>> >
>> > The exact error is "26: Intermediate file error".
>> >
>> > I managed to rearrange things so that /dev/rk0 had over 300 blocks of
>> > free space and it fixed the problem, but I'm curious if there was
>> > another solution.
>> >
>> > Mark
>> Ah the good old days before BSD's symlinks.
>> Only thing I can think of is add another drive or partition and mount it
>> as /tmp.
>>
>>
>> Bill
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160727/7acc6cf3/attachment-0001.html>


  reply	other threads:[~2016-07-27 21:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 20:28 Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57   ` Clem Cole
2016-07-27 21:01     ` Clem Cole [this message]
2016-07-27 21:10     ` William Pechter
2016-07-28  0:49       ` Clem cole
2016-07-28  1:03         ` William Pechter
2016-07-28 11:23           ` [TUHS] History repeating itself (was: Unix v6 problem with /tmp) Michael Kjörling
2016-07-28 12:18             ` Tony Finch
2016-07-28 13:57             ` John Cowan
2016-07-30  7:56               ` Greg 'groggy' Lehey
2016-07-30 11:41                 ` William Cheswick
2016-07-30 23:28                   ` Greg 'groggy' Lehey
2016-07-30 23:50                     ` scj
2016-08-01 11:36                   ` Tony Finch
2016-07-30 14:15                 ` John Cowan
2016-07-30 15:30                   ` [TUHS] History repeating itself Michael Kjörling
2016-07-28  1:03       ` [TUHS] Unix v6 problem with /tmp Clem cole
2016-07-28 23:16     ` [TUHS] environments/universes (was: Unix v6 problem with /tmp) Sven Mascheck
2016-07-29  3:05       ` arnold
2016-07-29 14:14         ` Clem Cole
2016-07-29 13:55       ` Clem Cole
2016-07-27 20:41 [TUHS] Unix v6 problem with /tmp Norman Wilson
2016-07-27 21:18 Norman Wilson
2016-07-28  0:47 ` Clem cole

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=CAC20D2MAjpiW3Cg4e0syi+EO9fkDuAjc7oBK1L_rne-PTkD6kg@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).