From: Larry McVoy <lm@mcvoy.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] building world using sh run in /usr/source in v6
Date: Mon, 31 Dec 2018 16:39:16 -0800 [thread overview]
Message-ID: <20190101003916.GB15969@mcvoy.com> (raw)
In-Reply-To: <5f8d3f32-3cd1-7dbe-6e59-25b8c577f9f9@gmail.com>
On Mon, Dec 31, 2018 at 06:29:11PM -0600, Will Senn wrote:
> 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
This smells like a file system that is corrupted (I used to hack UFS
a few decades back).
Can you do a
ls -l | od -c
because I want to see what those ?? are.
And cron is really 3246 bytes? And 2054 for init? Don't those seem
too small? Linux's cron is 44472 and that's with shared libs, I'm
assuming that v6 didn't have shared libs, it's all static.
next prev parent reply other threads:[~2019-01-01 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:29 Will Senn
2019-01-01 0:39 ` Larry McVoy [this message]
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=20190101003916.GB15969@mcvoy.com \
--to=lm@mcvoy.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@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).