I wonder if anyone can shed any light on the timing and rationale for
the introduction of “word erase” functionality to the kernel terminal
driver. My surface skim earlier leads me to believe it came to Unix
with 4BSD, but it was not reincorporated into 8th Edition or later,
nor did it make it to Plan 9 (which did incorporate ^U for the "line
kill" command). TOPS-20 supports it via the familiar ^W, but I'm not
sure about other PDP-10 OSes (Lars?). Multics does not support it.
VMS does not support it.
What was the proximal inspiration? The early terminal drivers seem to
use the Multics command editing suite (`#` for erase/backspace, `@`
for line kill), though at some point that changed, one presumes as
TTYs fell out of favor and display terminals came to the fore.
- Dan C.
I've been doing some research on Lisp machines and came across an
interesting tidbit: there was Chaosnet support in Unix v8, e.g.
https://www.tuhs.org/cgi-bin/utree.pl?file=V8/usr/sys/chunix/chaos.c
Does anyone remember why that went in? My first guess would be for
interoperability with the Symbolics users at Bell Labs (see Bromley's
"Lisp Lore", 1986), but that's just speculation.
john
Wikipedia has a brief page on cscope, which has a link to
https://cscope.sourceforge.net/history.html
written by Harold Bamford, in which he talks about the
early days of cscope at Bell Labs and its inventor Joe Steffan.
I wondered if anyone can add any interesting information about using
cscope on their projects or anything about its development.
-Marcus.
> You can always read Josh Fisher's book on the "Bulldog" compiler, I
> believe he did this work at Yale.
Are you thinking of John Ellis’s thesis:
Bulldog: A Compiler for VLIW Architectures
John R. Ellis
February 1985
http://www.cs.yale.edu/publications/techreports/tr364.pdf
Fisher was Ellis’s advisor. The thesis was also published in ACM’s Doctoral Dissertation Award:
https://mitpress.mit.edu/9780262050340/bulldog/
I believe Ellis still has a tape with his thesis software on it, but I don’t know if he’s been able to read it.
Hello Everyone
One of polish academic institutions was getting rid of old IT-related stuff
and they were kind enough to give me all Solaris related stuff, including
lots (and i mean lots) of installation CD-ROMS, documentations, manuals,
and some solaris software, mostly compilers and scientific stuff.
If anyone would be interested feel free to contact me and i'd be happy to
share - almost everything is in more than a few copies and I have no
intention of keeping everything for myself.
Currently all of the stuff is located in Warsaw, Poland.
Best regards,
mjb
--
Maciej Jan Broniarz
> [Tex's] oversetting of lines caused by the periodic failure of the
> paragraph-justification algorithms drove me nuts.
Amen. If Tex can't do what it thinks is a good job, it throws a fit
and violates the margin, hoping to force a rewrite. Fortunately,
one can shut off the line-break algorithm and simply fill greedily.
The command to do so is \sloppy--an ironic descriptor of text
that looks better, albeit not up to Tex's discriminating standard.
Further irony: when obliged to write in Tex, I have resorted to
turning \sloppy mode on globally.
Apologies for airing an off-topic pet peeve,
Doug
I happened upon
https://old.gustavobarbieri.com.br/trabalhos-universidade/mc722/lowney92mul…
and I am curious as to whether any of the original Multiflow compilers
survive. I had never heard of them before now, but the fact that they were
licensed to so many influential companies makes me think that there might
be folks on this list who know of its history.
-Henry
ACPI has 4-byte identifiers (guess why!), but I just wondered, writing some
assembly:
is it globl, not global, or glbl, because globl would be a one-word
constant on the PDP-10 (5 7-bit bytes)?
Not entirely off track, netbsd at some point (still does?) ran on the
PDP-10.
> "BI" fonts can, it seems, largely be traced to the impact
> of PostScript
There was no room for BI on the C/A/T. It appeared in
troff upon the taming of the Linotron 202, just after v7
and five years before PostScript.
> Seventh Edition Unix shipped a tc(1) command to help
> you preview your troff output with that device before you
> spent precious departmental money sending it to the
> actual typesetter.
Slight exaggeration. It wasn't money, It was time and messing
with film cartridges, chemicals, and wet prints. You could buy a
lot of typesetter film and developer for the price of a 4014.
Doug
yeah that was the one that id' first mentioned.
Although I was more so interested in when/where the 386 PCC came from
Seems at best all those sources are locked away.
____
| From: Angus Robinson
| To: Jason Stevens
| Cc: TUHS main list
| Sent: March 25, 2024 09:17 AM
| Subject: Re: [TUHS] 386 PCC
|
|
| Is this it ?
|
| https://web.archive.org/web/20071017025542/http://pcc.l
| udd.ltu.se/
|
| Kind Regards,
| Angus Robinson
|
|
| On Sun, Mar 24, 2024 at 2:13?AM Jason Stevens <
| jsteve(a)superglobalmegacorp.com> wrote:
|
|
| I'd been on this whole rabbithole exploration thing of
| those MIT PCC 8086
| uploads that have been on the site & on bitsavers, it
| had me wondering is
| there any version of PCC that targeted the 386?
|
| While rebuilding all the 8086 port stuff, and MIT
| PC/IP was fun, it'd be
| kind of interesting to see if anything that ancient
| could be forced to work
| with a DOS Extender..
|
| I know there was the Anders Magnusson one in 2007,
| although the site is now
| offline. But surely there must have been another one
| between 1988/2007?
|
| Thanks!
|
|
|
|
