TUHS

tuhs@tuhs.org

16 participants
6485 discussions

Re: [TUHS] So now that the source is finally out...

by norman＠nose.cs.utoronto.ca

Ken Wellsch: I'm fairly sure things like "=+" and so on were replaced with "+=" in the move from V6 to V7. I think structure assignments were added here too, and the much more obscure, being able to declare passed arguments in the function preamble as "register." I believe K&R reflects the C language as seen with V7... The V7 C compiler accepted =+, but it still accepted += as well; there was a lot of code written the old way, and nobody wanted to be forced to convert everything all at once. Similarly, the V7 compiler complained about implicit conversions between pointers of different types, or between ints and pointers, but they were treated as warnings, not fatal errors; you could still compile old code and just ignore the compiler's fussing. I recall that when I arrived at Bell Labs in 1984, it was apparently not long after the research group's C compiler had been changed to treat all the obsolete stuff as errors; certainly there was still code in /usr/src that hadn't been updated, and all of it had been recompiled recently to run on the VAX. A modern C compiler would choke even on some of the stuff that was legal in those days. Recently I recompiled tbl with lcc, and had a grand time cleaning out all the ideas we all thought were clever in the late 1970s but most of us would never think of doing now. For those with the virgin source handy, take a look at subroutine `point' and the way it is used and abused. Norman Wilson

23 years, 3 months

Re: [TUHS] So now that the source is finally out...

by Carl Lowenstein

> From: "P.A.Osborne" <P.A.Osborne(a)ukc.ac.uk> > To: "M. Warner Losh" <imp(a)village.org> > Cc: tuhs(a)minnie.tuhs.org > Subject: Re: [TUHS] So now that the source is finally out... > Date: Fri, 25 Jan 2002 11:16:37 +0000 > > On Fri, Jan 25, 2002 at 03:27:25AM -0700, M. Warner Losh wrote: > > Real as in 286 or as in 8088 :-). > > > > gcc can compile K&R, but the language has evolved some since the v7 > > days. =*, =+, etc became *=, +=, etc. There are some other subtle > > things too that I don't recall off the top of my head, but which vexed > > the comp.lang.c news groups in the early 1980's. > > That makes things a challenge. Still the source of the kernel is > around 10K lines IIRC and going through it in stages doesnt make life > too painfull. Doesn't one of the C beautifiers do that for you (rewrite =+ etc.) Either GNU indent or Berkeley? cb. carl -- carl lowenstein marine physical lab u.c. san diego clowenstein(a)ucsd.edu

23 years, 3 months

[pups] Unix Archive now available anonymously

by Warren Toomey

All, With the new Caldera license, the Unix Archive is now available to you anonymously. You can throw away those passwords now. The list of Archive mirrors is at: http://www.tuhs.org/archive_sites.html and if you can become a mirror, please read http://www.tuhs.org/mirroring.html and send me some e-mail when you are ready to be added to the list. I can tell you that up to now, 2,830 people obtained a SCO Ancient UNIX license, of which 250 had to pay the US$100 to get it. I'll turn off the CGI script which allows you to obtain a SCO license now .... You know this means that Net/2, 4.xBSD and 2.11BSD are all freely available now :) Cheers, Warren

23 years, 3 months

4.4BSD and the MicroVax 3400

by Rob Becker

Anyone here know if 4.4BSD supports the MicroVax 3400 series of machines? One was given to me by my school (clearing out old equipment) and I would like to get some pure BSD goodness on it again. Also, anyone know if it's possible to make tapes under VMS? Thanks in advance, Rob Becker

23 years, 3 months

Re: [TUHS] 4.4BSD and the MicroVax 3400

by msokolov＠ivan.Harhan.ORG

Rob Becker <becker(a)ab.edu> wrote: > Anyone here know if 4.4BSD supports the MicroVax 3400 series of machines? > > [...] > > get some pure BSD goodness on it again. For VAXen you don't want 4.4BSD, you want 4.3BSD-Quasijarus, especially if you want pure. Unfortunately, I haven't got the KA640 (3300/3400) support in there, just KA650 (3500/3600) and KA655 (3800/3900). It would be trivial to add, though, it just needs to be taught to look at the SIE in addition to the SID, recognise the KA640, and don't try to touch the non-existent B-cache. This wouldn't give you support for the on-board DSSI and Ethernet, but it'll run with your Q-bus devices. MS

23 years, 3 months

[pups] Re: Caldera license

by Warren Toomey

In article by Milo Velimirovic: > Warren, > The license didn't survive the digestification process on the list -- > Would you be kind enough to send me a copy of the ancient-source.pdf > directly or a URL to it? > > Thanks, > Milo Here it is, Warren http://www.tuhs.org/Archive/Caldera-license.pdf

23 years, 3 months

[pups] Ancient UNIX now under a BSD license

by Warren Toomey

All, Amazing news. I have been negotiating with Caldera to release the Ancient UNIX under a BSD-style license. Well, they got it done faster than I expected. See attached license. I'll start removing the username/password stuff on the Unix Archive soon. Warren

23 years, 3 months

Re: [pups] 2.11BSD disklabel-programm

by pete＠dunnington.u-net.com

On Jan 20, 18:45, Jochen Kunz wrote: > > Ahhhhh! My PDP 11 has this M8192 board with FPU but without ROMs... > I thought that this is the "original" 11/73 CPU. But on this PDP is > nothing "original". The BA23 was a MV II, the CPU was EPayed, the RAM > board was given to me by a friend. (Many PC/XTs had to donate there RAM > chips to fill it.) About the best use I can think of for a PC/XT :-) > I found the console SLU at the scrap yard, the Dilog > ESDI controller was EPayd (in England BTW ;-) ) ... and I am still > looking for a ROM card... If you can find an MRV11-D (to put MXV11-B ROMs into) or an MVX11-B, that would be the best option (and the only ones DEC supported). However, it should be possible to put the code from MXV11-B ROMs into several 24-pin 2Kx8 EPROMs (2716 or equivalent), and put the EPROMs into a BDV11. However, you'd want to modify the BDV11 for 22-bit operation (that's ECO 005). > > The BA23 was only rated for one hard disk and either a TK50 or an > RX50, > I know. I once saw a MV II with a second RD54 in an external case. There > was a real mess of wiring to get it and the internal RD54 work together > on one RQDX3. Puting the TK50 out of the BA23 and mounting the second > RD54 in the BA23 would have been much simpler. But not the DEC way of > live. ;-) Because old hard drives take a lot of current. The PSU and wiring loom won't take a full backplane and two hard drives. I did one of mine a different way. I have a BA11-N with the backplane modified to be 22-bit. In it is an RQDX2 (or an RQDX3, depending on what's been shuffled around this month), with a 50-way ribbon cable going to a DEC box (used to be a TKZ50) which has a PSU, a hard drive, and an RX50. In the box is also a small PCB I made to do the job of the distribution board found in a BA123. Also in the BA11-N backplane is a modified BDV11, with a pair of 28-pin EPROM sockets which normally hold microPDP-11/23 boot ROMs. -- Pete Peter Turnbull Network Manager University of York

23 years, 3 months

Re: [pups] 2.11BSD disklabel-programm

by pete＠dunnington.u-net.com

On Jan 19, 22:35, jkunz(a)unixag-kl.fh-kl.de wrote: > Only the first 3 slots are Q/CD. The other 5 slots are Q/Q in serpentine > bus grant wiring. Tony said that the memory should be in the first > slot. Lothar later said this is an H9276-A. That's a straight backplane, all Q22/CD. It seems he has a BA11-S not a BA23 :-) BTW, DEC normally recommended all comms and network cards go after the memory, tapes next, then disks. > AFAIK some 11/73 labeld boxen where sold with a 11/83 CPU in the first > slot and the memory in the second. It's the order of the boards (and the boot ROMs) that make it 11/73 or 11/83, not the circuit board. Though original 11/73s are 15MHz and original 11/83s are 18MHz. > AFAIK a 11/83 CPU can use QBus and (or?) PMI memory. If it is > configured with QBus memory it is calld a "11/73". But keep in mind > that there is a "real" 11/73 CPU (M8192 = KDJ11-A). That's a dual-height board, CPU only, with no boot ROMs, LTC, or SLUs. It was only sold as an OEM product or as an upgrade to 11/03 or 11/23 (not 11/23+ or microPDP-11/23) systems. Whilst it is a "real 11/73", it's no more "real" than any other :-) > Hmm. Are there Q/CD only BA23 backplanes? No. There are straight Q/CD and serpentine Q/Q backplanes of the same size but they're only used in other boxes (like BA11-N and BA11-S) or sold as OEM units. > I never saw a front panel like that, but your assumption sounds right. > All my front panels have only one disk write protect / online switch. The BA23 was only rated for one hard disk and either a TK50 or an RX50, but the BA123 (which uses the same panels) was rated for up to 4 MSCP devices. That's why the WP and ONLINE switches and LEDs are on a subassembly, so you can add another one. -- Pete Peter Turnbull Network Manager University of York

23 years, 3 months

Re: [pups] lcc (was: GCC)

by norman＠nose.cs.utoronto.ca

lcc is not public-domain nor GPL, but it is freely available for `personal research and instructional use,' and in general there is no restriction as long as you don't redistribute it for profit or resell it. Here's the official scoop, as inscribed in ./CPYRIGHT in the lcc 3.6 distribution. It is possible that the terms have changed for newer versions; I haven't been keeping track. ---- The authors of this software are Christopher W. Fraser and David R. Hanson. Copyright (c) 1991,1992,1993,1994,1995 by AT&T, Christopher W. Fraser, and David R. Hanson. All Rights Reserved. Permission to use, copy, modify, and distribute this software for any purpose, subject to the provisions described below, without fee is hereby granted, provided that this entire notice is included in all copies of any software that is or includes a copy or modification of this software and in all copies of the supporting documentation for such software. THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T MAKE ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. lcc is not public-domain software, shareware, and it is not protected by a `copyleft' agreement, like the code from the Free Software Foundation. lcc is available free for your personal research and instructional use under the `fair use' provisions of the copyright law. You may, however, redistribute lcc in whole or in part provided you acknowledge its source and include this CPYRIGHT file. You may, for example, include the distribution in a CDROM of free software, provided you charge only for the media, or mirror the distribution files at your site. You may not sell lcc or any product derived from it in which it is a significant part of the value of the product. Using the lcc front end to build a C syntax checker is an example of this kind of product. You may use parts of lcc in products as long as you charge for only those components that are entirely your own and you acknowledge the use of lcc clearly in all product documentation and distribution media. You must state clearly that your product uses or is based on parts of lcc and that lcc is available free of charge. You must also request that bug reports on your product be reported to you. Using the lcc front end to build a C compiler for the Motorola 88000 chip and charging for and distributing only the 88000 code generator is an example of this kind of product. Using parts of lcc in other products is more problematic. For example, using parts of lcc in a C++ compiler could save substantial time and effort and therefore contribute significantly to the profitability of the product. This kind of use, or any use where others stand to make a profit from what is primarily our work, requires a license agreement with Addison-Wesley. Per-copy and unlimited use licenses are available; for more information, contact J. Carter Shanklin Addison Wesley Longman, Inc. 2725 Sand Hill Rd. Menlo Park, CA 94025 415/854-0300 x2478 FAX: 415/614-2930 jcs(a)aw.com ----- Chris Fraser / cwfraser(a)microsoft.com David Hanson / drh(a)cs.princeton.edu $Revision: 1.3 $ $Date: 1996/09/30 13:55:00 $

23 years, 3 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