From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 16:28:19 -0400 [thread overview]
Message-ID: <CADxT5N6Vxxw9GivitVF1LjzAHP6ac3dvHF4gCs83TNzup3OEUA@mail.gmail.com> (raw)
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
next reply other threads:[~2016-07-27 20:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 20:28 Mark Longridge [this message]
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57 ` Clem Cole
2016-07-27 21:01 ` Clem Cole
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=CADxT5N6Vxxw9GivitVF1LjzAHP6ac3dvHF4gCs83TNzup3OEUA@mail.gmail.com \
--to=cubexyz@gmail.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).