TUHS

tuhs@tuhs.org

17 participants
6470 discussions

Memoir Marks the 25th Anniversary of First Transgender Employment Policy

by Mary Ann Horton

This may be a bit off-topic, so please forgive me. Lucent is central to the book. I want to let you know I had a memoir published today, on the 25th anniversary of Lucent's historic policy. Here's the main part of the press release. > Before 1997, transgender workers were routinely fired when their > employers found out they were changing their sex. That changed on Oct. > 28, 1997, when Lucent Technologies became the first Fortune 500 > company to formally commit that it would not discriminate based on > "gender identity, characteristics, or expression". Dr. Mary Ann > Horton, who instigated the change, has written a memoir, Trailblazer: > Lighting the Path for Transgender Inclusion in Corporate America. > "When I led transgender-101 workshops, my personal story was people's > favorite part. They wanted more, and Trailblazer is the result," said > Horton. "It will be released on the 25th anniversary, Oct. 28." > > Horton was a software technology worker at Lucent in Columbus, Ohio, > when Lucent added the language. It allowed Mary Ann, then known as > Mark, to come out in the workplace without fear of reprisal. When she > didn't need to spend energy hiding part of herself, her productivity > soared, and she was promoted. Three years later, she persuaded Lucent > to cover gender-confirming medical care in their health insurance. She > blazed the trail for Apple, Avaya, Xerox, IBM, Chase, and other > companies to follow. Nokia blogged about it today. https://www.nokia.com/about-us/careers/life-at-nokia/employee-blogs/25th-an… You can find the book at https://www.amazon.com/Trailblazer-Lighting-Transgender-Equality-Corporate-… If you read it, please post a review to Amazon. -- Thanks, /Mary Ann Horton/ (she/her/ma'am) maryannhorton.com <https://maryannhorton.com> "This is a great book" - Monica Helms "Brave and Important" - Laura L. Engel Available on Amazon and bn.com! <https://www.amazon.com/Trailblazer-Lighting-Transgender-Equality-Corporate-…>

2 years, 5 months

SunOS4.1.3, etc., on GitHub

by Rich Salz

Sorry if this is a repost. No idea of the legality, and therefore no idea how long it will stay: https://twitter.com/nixcraft/status/1586276475614818305 is the tweet and https://github.com/Arquivotheca/SunOS-4.1.3 is the repository with this README, below. Many other OS's there too. README <https://github.com/Arquivotheca/SunOS-4.1.3#readme> This is the SunOS 4.1.3 SUNSRC CD-ROM. It contains the source in 3 forms. 1. plain text source, as a ufs tree, rooted at the top level of this filesystem. Symlinks to the SCCS hierarchy are in place. 2. SCCS hierarchy, rooted at SCCS_DIRECTORIES. 3. a tar image of the SCCS hierarchy, in a file named 4.1.3_SUNSRC.tar. This is rooted at ./SCCS_DIRECTORIES. Please see the SunOS 4.1.3 Source Installation Guide for further details.

2 years, 5 months

Version 3.1 of Installing and Using Research Unix Version 7 note is up the blog

by Will Senn

Following up on my v6 udpate a couple of weeks ago, I've updated my v7 note to use OpenSIMH and bring it up to date. In addition, I've switched the multi-session notes over to DZ-11 from DC-11 cuz it supports 9600 over telnet. Here's the link: http://decuser.blogspot.com/2022/10/installing-and-using-research-unix_29.h… Changes since revision 2.1 (2/3/2022) Revision 3.1 (10/29/2022) - minor revision: Changed over to DZ-11 vs DC-11 for serial connections which allows for 9600 baud connections. Revision 3.0 (10/28/2022) - major revision: Started using OpenSIMH Restored the learn notes which went missing between 2.0 and 2.1 Updated host notes for Macos Monterey Cleaned up a number of lingering issues This note covers building a working v7 instance from tape files that will run in the OpenSImH emulator. First, the reader is led through the restoration of a pristine v7 instance from tape to disk. Next, the reader is led through adding a regular user and making the system multi-user capable. Then, the reader is shown how to make the system multi-session cable to allow multiple simultaneous sessions. Finally, the system is put to use with hello world, DMR style, and the learn system is enabled. The note explains each step of the process in detail.

2 years, 5 months

who invented the link register

by ron minnich

I know branch and link was in the 360; was it earlier? And ... anybody know who invented it? This came up in a risc-v meeting just now :-) My claim is that if anybody knows, they will be in this group.

2 years, 6 months

Re: who invented the link register

by jnc＠mercury.lcs.mit.edu

> From: ron minnich > I know branch and link was in the 360; was it earlier? Well, as I understand it, branch and link (BAL and BALR) did a couple of different things (if I have this wrong, I hope someone will correct me). It was a subroutine call, but it also loaded a base register. (Those were used to deal with the /360's bizarro memory management, which was not 'base and bounds, with a user's virtual address space starting at zero', like a lot of contemporary machines. Rather, a process saw its actual physical memory location, so depending on where in memoty a process was loaded, it would be executing at different addresses visible to it; the base registers were used to deal with that. This made swapping complicated, since it had to be swapped back in to the same location.) Which function of BALR are you enquiring about? The subroutine call part? > From: Angelo Papenhoff > The Whirlwind used the A register for this purpose. ... > Might be earlier than this, I just happen to know the Whirlwind > somewhat well. It's late 40s machine, so you probably won't find > anything *much* older. The only machines older than Whirlwind I know of are the ACE (design; not implemented until later) and EDVAC. I have ACE stuff, but i) the documentation is really wierd, and hard to read, and ii) it's really bizarre (it didn't have opcodes; different registers did different things). There were subroutines written for it, but it's not clear how they were called. The EDVAC, the only thing I have on it is von Neumann's draft, and it's even harder to read than Turing's ACE Report! Noel

2 years, 6 months

Revised v6 Instructions Posted

by Will Senn

All, I have revised my Research Unix Version 6 instructions for 2022, in part to support the change to OpenSSH and also to bring it along into the modern era (I did it on my Monterey instance). I updated the links, cleaned up some lingering issues, and confirmed it working. Please take a look and let me know if you find any issues, misrepresentations, missing pieces, etc. I haven't touch v6 in a while, but it was fun to reminisce. http://decuser.blogspot.com/2022/10/installing-and-using-research-unix.html Regards, Will

2 years, 6 months

Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code

by jnc＠mercury.lcs.mit.edu

>> Looking at net_vdh.h, it seems to be a "VDH-11C" >> ... >> I wasn't able to find anything out about it at all. (I have some >> hardcopy manuals for other ACC IMP interface products, and I was going >> to look in them to see if any of them listed its manual in a 'see >> also', but I can't find them.) > From: Lars Brinkhoff > Noel Chiappa wrote: >> Did VDH PDP-11's have a special VDH interface > Sorry, no idea. That was a semi-rhetorical question; after I typed it, I did some looking, and came up with the answer above, the ACC VDH-11. I did eventually find the hardcopy manuals for other ACC IMP interface products, but none of them mention the VDH11. On a hunch, I looked to see if there was a VDH11 driver for ELF, and sure enough, there was: https://github.com/pdp11/elf-operating-system/blob/master/files/kdvdh.m11%5… (If anyone wants to look at it, ktbl.sml hold the register definitions.) With no manual for the device, and no museum catalog hits to show that someone has one which hasn't been scanned in yet, that's probably a dead end, although with the two drivers, one could probably mock up a rudimentary programmming manual. I'm not sure there's any point, though; using an LH/DH interface is going to work as well, and those device are already supported. > From: Paul Ruizendaal > impio.c: available here: Thanks for chasing those all down; I knew the BBN system was based on the NCP Unix (called in this discussion the 'NOSC' system), so I figured it would have the missing files, in some form. Looking at a diff between the damaged impio.c in the NOSC tree, and the impio.c in the BBN tree, there are some changes (in the section where we have both versions) between the NOSC one and the BBN one, but it will probably be possible to take the missing piece off the bank end of the BBN one and tack it on to the NOSC one. Somewhere in the document scans available online from DOD, there used to be a long thing from the UIUC people who did the original NCP Unix. I don't know if it included source; it might have. Noel

2 years, 6 months

Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code

by Paul Ruizendaal

Maybe I’m dim, but I’ve lost track in this discussion of what is missing / corrupted. sys4.c: I think this is available in BBN V6: https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ken> In this file the only real network addition is Jack Haverty’s user timer variable, I think. What else is missing? imp11a.c: available in two versions here: https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/dmr <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/dmr> impio.c: available here: https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ncpkernel/impio.c <https://minnie.tuhs.org/cgi-bin/utree.pl?file=BBN-V6/ncpkernel/impio.c> Maybe the compiler has a different opinion, but they don’t look obviously corrupted [??] Also, the BBN-VAX files may be a solution. BBN sent four tapes with snap shots to CSRG in 1981. The TUHS website has the newest version, but there are 3 older ones (all 4 come from Kirk McKusick’s DVD set). They all have a slightly different set of files. These tapes also have IMP and ACC drivers in them, along with a token ring driver that was apparently based on Noel’s work back in the day. These files may also help filling in blank spots in PDP11 files. Paul

2 years, 6 months

John Lions: 3 sabbaticals at Bell Labs. 1978 and which other years? 1989?

by steve jenkin

Berkeley Tague says he invited John to work with the USG in 1978 [ AUUG, below. Also by Ronda Hauben in multiple places ] [ In two ‘recollections’ / history docs sourced from UNSW, ] [ the first visit was misremembered as 1976 or 1977. ] I was wondering when John's two other sabbaticals to Bells Labs were. The Peter Ivanov interview with John in “Unix Review”, 1985, notes two sabbaticals by then. After writing the celebrated Commentary on the UNIX Operating System in 1976, Lions was asked to spend two sabbaticals at the Labs. This comment in 2000 on “9fans” from Rob Pike says John also visited in 1989, but sadly his work by then had been affected. <https://marc.info/?l=9fans&m=144372955601968&w=2> Anyone know when the other visit was? Presumably 1983 or 1984 if John took a semester off every 5 years. ======== In AUUGN Oct 1995, V16 #5, there’s a collection of emails, an ‘interview’ with John PDF pages 17 & 24 <https://www.tuhs.org/Archive/Documentation/AUUGN/AUUGN-V16.5.pdf> Berkeley Tague says in 1978 he invited John to work with the USG. then He wanted to come to Murray Hill for his sabbatical so it was a win/win situation. He spent two or three summers at Bell Labs over the years and supplied us with many of his graduate students for sabbaticals and permanent employment. Later: AUUGN: What have been the professional highlights of your career? JL: For myself, three sabbaticals at Bell Laboratories have been highlights. For my students, opportunities arose for employment at the Laboratories. ======== -- Steve Jenkin, IT Systems and Design 0412 786 915 (+61 412 786 915) PO Box 38, Kippax ACT 2615, AUSTRALIA mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin

2 years, 6 months

Re: Attempting To Build NOSC and BBN UNIXs + ARPANET code

by jnc＠mercury.lcs.mit.edu

> From: Michael Casadevall > sys4.c is entirely corrupted, and part of impio.c is cut off The copy on MIT-CSR (the origin of the copy at TUHS) has the same issues. I doubt it's possible to recover them from that system; you'll have to find some other way to recover them (perhaps through a dump of the BBN system), or re-code them (as you did with sys4.c). > I do need to do a readthrough for the VDH driver ... I think that might > be for the radio links to Hawaii and the UK? No. Read BBN 1822. The LH and DH bit-serial physical interfaces only work up to about 1000 feet or so. (Less for LH; DH is logically idential to LH, but uses differential pairs - the LH is single-sided). VDH is, in the bottom layer, simply a synchronous serial link, allowing the host to be up to hunreds of miles from the IMP. > From: Lars Brinkhoff > Another it adding emulators for various IMP interfaces. I.e. you will > not get anywhere without adding one of IMP11A, ACC, or VDH to SIMH. Did VDH PDP-11's have a special VDH interface, or did they simply use an off-the-rack DEC synchronous serial interface like a DU11? (More of them here: http://gunkies.org/wiki/Category:DEC_Synchronous_Serial_Interfaces if anyone wants.) Looking at net_vdh.h, it seems to be a "VDH-11C" Looking online, the VDH-11 seems to be an ACC prodict, but I wasn't able to find anything out about it at all. (I have some hardcopy manuals for other ACC IMP interface products, and I was going to look in them to see if any of them listed its manual in a 'see also', but I can't find them.) I'm not sure why people did just use an off-the-rack DEC synchronous serial interface; maybe the VDH11 did a BBN specific CRC, or something (in addition to using DMA; mostr DEC sync interfaces didn't, IIRC)? Anyway, you don't want to use VDH. Noel

2 years, 6 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