Re: [TUHS] building world using sh run in /usr/source in v6

Re: [TUHS] building world using sh run in /usr/source in v6

[Noel Chiappa]

    > From: Larry McVoy

    > 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

No, 3246 is the same as mine, and my init (which has a few changes from stock) is
2064.

I'm not surprised the later one is 44KB - that's in part due to the denseness
of PDP-11 binary (and the word-size is only 16 bits), but more broadly, I
expect that it goes to my complaint about later Unixes - they've lost, IMO,
the single most important thing about the PDP-11 Unixes, which is their
bang/buck ratio.

	  Noel

Re: [TUHS] building world using sh run in /usr/source in v6

[Will Senn]

On 12/31/18 6:39 PM, Larry McVoy wrote:
> 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.

Hi Larry,

I'm not sure where the ? came from, but I think that's just the email, 
here is init:

ls -l /etc/init|od -c
0000000  -  r  w  x  r  w  x  r  -  -        1     r  o
0000020  o  t                 2  0  5  4     M  a  y
0000040  1  3     2  3  :  5  0     /  e  t  c  /  i  n
0000060  i  t \n \0
0000063

ls -l /etc/init|od
0000000 071055 074167 073562 071170 026455 020040 020061 067562
0000020 072157 020040 020040 031040 032460 020064 060515 020171
0000040 031461 031040 035063 030065 027440 072145 027543 067151
0000060 072151 000012
0000063

As for how big they are, that's just the beauty of v6, everything is 
super small. Linux is blubbery in comparison.

Will



-- 
GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF

Re: [TUHS] building world using sh run in /usr/source in v6

[Larry McVoy]

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.

[TUHS] building world using sh run in /usr/source in v6

[Will Senn]

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