4 Aug
2023
4 Aug
'23
3:05 a.m.
Both V6 and V7 used split I/D on the 45 and 70 where it as available.
You had to specify that you wanted it in your build, the choices were
the 407 flagged. a.out, which had a single text/data/bss space
(unspilt). 410 which still ran in one address space, but put the text
in read only segments so they could be shared. 411 ran the executable
in split I and D space.
The original use of the “sticky” bit in the inode mode indicated that a
410 or 411 program text would be held in swap.
-Ron
------ Original Message ------
From "Will Senn" <will.senn(a)gmail.com>
To tuhs(a)tuhs.org
Date 8/3/23, 4:35:09 PM
Subject [TUHS] Split addressing (I/D) space (inspired by the death of
the python... thread)
Does unix (v7) know about the PDP-11 45's split
I/D space through configuration or is it convention and programmer's responsibility
to know and manage what's actually available?
Will
On 8/3/23 12:00, Rich Salz wrote:
What, we all need something to kick now that
we've beaten sendmail? How about something unix, ideally a decade old?