What TSS actually did was to divide each module into position independent >read-only CSECTs and relocatable read-write PSECTs, and extend the calling >sequence so each routine had a pair of addresses, the code address in its >CSECT and the base of its data PSECT. So all of the CSECT pages were
shared, and the PSECT pages had a separate copy in each process.
See my book for more details.
John Levine <johnl@taugh.com> spake the secret code ><1184vv2$pfs$2@gal.iecc.com> thusly:
What TSS actually did was to divide each module into position independent >>read-only CSECTs and relocatable read-write PSECTs, and extend the calling >>sequence so each routine had a pair of addresses, the code address in its >>CSECT and the base of its data PSECT. So all of the CSECT pages were >>shared, and the PSECT pages had a separate copy in each process.
See my book for more details.
Which book is that?
Hint: program loader
legalize+jeeves@mail.xmission.com (Richard) writes:
John Levine <johnl@taugh.com> spake the secret code >><1184vv2$pfs$2@gal.iecc.com> thusly:
What TSS actually did was to divide each module into position independent >>>read-only CSECTs and relocatable read-write PSECTs, and extend the calling >>>sequence so each routine had a pair of addresses, the code address in its >>>CSECT and the base of its data PSECT. So all of the CSECT pages were >>>shared, and the PSECT pages had a separate copy in each process.
See my book for more details.
Which book is that?
Why not ask google?
Takes about 5 seconds to get the answer.
slp53@pacbell.net spake the secret code
<6RVqS.32437$Sh34.6744@fx03.iad> thusly:
legalize+jeeves@mail.xmission.com (Richard) writes:
John Levine <johnl@taugh.com> spake the secret code >>><1184vv2$pfs$2@gal.iecc.com> thusly:
What TSS actually did was to divide each module into position independent >>>>read-only CSECTs and relocatable read-write PSECTs, and extend the calling >>>>sequence so each routine had a pair of addresses, the code address in its >>>>CSECT and the base of its data PSECT. So all of the CSECT pages were >>>>shared, and the PSECT pages had a separate copy in each process.
See my book for more details.
Which book is that?
Why not ask google?
Because I'm having a conversation with a human being?
Takes about 5 seconds to get the answer.
It took you longer to scold me than it would've taken you to share the
answer to my question.
+1, and also I think you're putting too much faith in Google Web
Search being able to provide relevant results. I can't see how well
does it fare myself because Google really really wants search users
to run Javascript.
On Fri, 18 Sep 2026 19:29:38 +0100
Nuno Silva <nunojsilva@invalid.invalid> wrote:
+1, and also I think you're putting too much faith in Google Web
Search being able to provide relevant results. I can't see how well
does it fare myself because Google really really wants search users
to run Javascript.
+1 to *this.* Google has been getting steadily worse for years now, and
when they started refusing to function at all without JS that was the
last straw for me.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:16:00 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |