From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] building world using sh run in /usr/source in v6
Date: Mon, 31 Dec 2018 18:29:11 -0600 [thread overview]
Message-ID: <5f8d3f32-3cd1-7dbe-6e59-25b8c577f9f9@gmail.com> (raw)
The setting up document hints at how to build world so to speak in v6.
However, when I log in as bin (most files are owned by bin) and:
chdir /usr/source
sh run
I get a number of failed items along these lines:
cp a.out /etc/cron
Can't create new file.
cp a.out /etc/init
Can't create new file.
A little digging around points to the problem - some files are owned by
daemon, others by root:
-rwsrwsr-- 1 daemon 3246 Oct 10 12:54 cron
-rwxrwxr-- 1 root 2054 May 13 23:50 init
My question is this, is the system recompiled en-masse using the run
script in /usr/source or not? It certainly appears to be the method, as
it contains a bunch of chdir somedir; time sh run lines including the
/usr/sys/run file... If it's not, what was the method?
I gather I can force it by logging in as root and running those sections
of the run script pertaining to files owned by root, and the same for
daemon, but that seems inefficient and begs the question why didn't they
have run scripts for root and daemon that were separate from the ones
for bin.
Thanks,
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
next reply other threads:[~2019-01-01 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:29 Will Senn [this message]
2019-01-01 0:39 ` Larry McVoy
2019-01-01 0:48 ` Will Senn
2019-01-01 4:11 Noel Chiappa
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=5f8d3f32-3cd1-7dbe-6e59-25b8c577f9f9@gmail.com \
--to=will.senn@gmail.com \
--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).