TUHS

tuhs@tuhs.org

46 participants
6502 discussions

by Rudi Blom

>Date: Wed, 15 Mar 2023 16:56:45 -0700 >From: >Subject: [TUHS] Re: OSF/1.0 Sources >To: "Tautological Eunuch Horticultural Scythians" <tuhs(a)tuhs.org >Message-ID: <b3aa03ba-6c51-4f81-9ff4-21f72a9fe94d(a)app.fastmail.com> >Content-Type: text/plain;charset=utf-8 > >On Wed, Mar 15, 2023, at 14:03, Warren Toomey via TUHS wrote: >> I'm still worried about my legal butt :-( > >Speaking of, there’s also the OSF/1.0 source from the same uploader: > https://archive.org/details/SapphireDensetsu_gmail_OSF1 >-- >~j Being somewhat of a collector I also have a Osf1-2.0-Src Tar.zip :-) take care, uncle rubl -- The more I learn the better I understand I know nothing.

2 years, 2 months

virtual consoles / Alt-Fx

by Paul Ruizendaal

Thinking a bit more about terminal multiplexing was a major use case for early X, I recalled using Linux virtual consoles in the late 90’s for this purpose. According to Wikipedia, virtual consoles originated with Xenix and before that with concurrent CP/M. Perusing the documentation of those on Bitsavers, I can see that virtual consoles have a prominent mention in the manual for concurrent CP/M (1983), but not those of its forerunners MP/M II and MP/M (1979). I cannot find a mention of virtual consoles in Xenix documentation as late as 1988. No such thing as a virtual (as distinct from pseudo) tty on 16-bit Unix or early 32-bit, as far as I know; one could argue it does not make much sense with physical terminals. Wikipedia says no such thing existed on SunOS either. I think virtual consoles where present in Linux from a very early point. So, as far as I can tell virtual consoles were invented for concurrent CP/M around 1983, made their way to Xenix in the late 80’s and became part of Linux in the early 90’s. Have I missed other prior art?

2 years, 2 months

Re: [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary)

by jnc＠mercury.lcs.mit.edu

> From: Bakul Shah > In hindsight Algol68 may have been the last committee designed language > that was good. I do not grant your basic assertion. Hoare had it right: "ALGOL 60 [was] a language so far ahead of its time that it was not only an improvement on its predecessors but also on nearly all its successors." That would definitely include Algol68, which was a classic committee-designed nightmare. Noel

2 years, 2 months

GOTO etc

by Steve

Dennis added setjmp() and longjmp() so the shell could handle errors in a reasonable way. There are two places where setjmp was used in the original shell (7th edition) code as I recall. Both at the top level in main.c. The idea came from Algol68 but I do not know where it was originally invented. longjmp() was used in the "exitsh" function that got called on the exit command, default trap routine and a fault with no trap set. It was also used when executing a subshell to avoid a fork and exec. In this case the setjmp() was at top level in the initial sh setup. Hope this makes sense. But these were two different uses. One for error recovery and one to reset the execution environment back to initial state. Steve

2 years, 2 months

Re: UNIX System V Release 2.2 gdts Vax-780

by jnc＠mercury.lcs.mit.edu

> From: Larry McVoy > If there are no commercial users of that source base, you have a chance When was the last VAX sold? Maybe the VAX version people would be willing to let go of. Noel

2 years, 2 months

Re: UNIX System V Release 2.2 gdts Vax-780

by jnc＠mercury.lcs.mit.edu

> From: Ken Unix > I have mknod but need the (c,b) major/minor numbers for /dev/lp It looks like SysV still has conf.c; you're looking for 'cdevsw'. Noel

2 years, 2 months

Re: [TUHS]: C dialects

by Douglas McIlroy

> In hindsight Algol68 may have been the last committee designed > language that was good. The committee itself fractured over the design. Dissenters who thought it was far too complex upped stakes and formed WG2.3, which pointedly concentrated on program design, not language. Doug

2 years, 2 months

UNIX System V Release 2.2 gdts Vax-780

by KenUnix

Hi. I am trying to figure out how to create a device /dev for lp. I have mknod but need the (c,b) major/minor numbers for /dev/lp /etc/mknod name c | b major minor I do have the required software to run lp. I have read through the docs I have but no luck. Thanks Ken -- WWL 📚

2 years, 2 months

Re: I can't drive 55: "GOTO considered harmful" 55th anniversary

by jnc＠mercury.lcs.mit.edu

> From: Warner Losh > In C I use it all the time to do goto err for common error recovery > because C doesn't have anything better. That's because C doesn't have 'conditions'. (Apparently, from the following posts, most people here are unfamiliar with them. Too bad, they are a great idea. OK summary here: http://gunkies.org/wiki/Condition_handler for those who are unfamiliar with the idea.) I was at one point writing a compiler using a recursive descent parser, and decided the code would be a lot simpler/cleaner if I had them. (If, for example, one discovers discovers an un-expected 'end of file', there can be an extremely large number of procedure invocations in between where that is discovered, and where it is desirable to handle it. So every possible intervening procedure would have to have an 'unexpected EOF' return value, one would have to write code in every possible intervening procedure to _handle_ an 'unexpected EOF' return value, etc.)' (Yes, I could have used setjmp/longjmp; those are effectively a limited version of condition handlers.) Since C has a stack, it was relatively easy to implement, without any compiler support: on() became a macro for 'if _on("condition_name")'; _on() was a partially-assembler procedure which i) stacked the handler (I forget where I put it; I may have created a special 'condition stack', to avoid too many changes to the main C stack), and ii) patched the calling procedure's return point to jump to some code that unstacked the handler, and iii) returned 'false'. If the condition occurred, a return from _on() was simulated, returning 'true', etc. So the code had things like: on ("unexpected EOF") { code to deal with it } With no compiler support, it added a tiny bit of overhead (stacking/unstacking conditions), but not too bad. John Wroclawski and someone implemented a very similar thing entirely in C; IIRC it was built on top of setjmp/longjmp. I don't recall how it dealt with un-stacking handlers on exit (which mine did silently). Noel

2 years, 2 months

I can't drive 55: "GOTO considered harmful" 55th anniversary

by Steffen Nurpmeso

I wonder if Pink Floyd's Summer68 maybe refers to this. Other than that i am addicted and could not live without it. The other (terrible) song is from 1984 (east southern US). --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)

2 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

TUHS