TUHS

tuhs@tuhs.org

29 participants
6496 discussions

RE: [TUHS] SCO reveals major UNIXT IP violations

by norman＠nose.cs.utoronto.ca

Gregg C Levine: Kenneth, doesn't that mean, that their case can be closed, because they themselves are the guilty party? Caldera was bought by SCO. I thought it was the other way around: Caldera bought the UNIX-OS part of SCO, then (around the time the current fracas started) renamed themselves The SCO Group. Norman Wilson Toronto ON

21 years, 5 months

SCO reveals major UNIX IP violations

by Kenneth Stailey

an excerpt: << SCO this week said it was "examining" the AT&T settlement to see who might have leaked the ancient AT&T-derived UNIX� code and put it into a BSD distribution. Allowing such hallowed innovations to be used under an open source license, would, we agreed thoroughly devalue SCO's IP assets. So we set about looking for who could perpetrate such a foul violation. And deep on a warez site of dubious origins, we unearthed a highly incriminating statement. There we found a script kiddie shameless boasting of his crime. The poster claimed that he'd released - "... the ancient UNIX releases (V1-7 and 32V) under a "BSD-style" license. I've attached a PDF of the license letter hereto. Feel free to propogate it as you see fit" Propagate? We shivered. The subject line of the email confirmed our worst fears. [...] So after a little digging, we traced this serious UNIX� violation to a hacker outfit called "Caldera Inc." The email was datelined 23 Jan 2002. Perhaps using an assumed identity, the hacker signed himself as "Dion L. Johnson II - Product Manager and one of many open source enthusiasts in Caldera Intl." We shall be doing some more digging soon, to see where these hackers can be traced. And as dutiful citizens, we shall inform The SCO Group of these violations as our enquiries continue. As soon as we find out who these Caldera hackers are. Can you help? >> complete article: http://www.theregister.co.uk/content/4/34102.html __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

21 years, 5 months

Why Caldera Released Unix: A Brief History

by Kenneth Stailey

http://linux.oreillynet.com/pub/a/linux/2002/02/28/caldera.html __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

21 years, 5 months

SCO's additional law suits

by Brantley Coile

Wonder where they are getting the money to do this? Who has the most to gain by shutting down BSD and LINUX? Brantley Coile

21 years, 5 months

SCO To Expand Its Lawsuit Beyond Linux

by Pat Villani

I wonder how much trouble 32I will be: <http://www.atnewyork.com/news/article.php/3110981> Pat -- Technology is a way of organizing the universe so that man doesn't have to experience it. -- Max Frisch

21 years, 5 months

[pups] DEC PRO or P/OS

by Gregg C Levine

Hello from Gregg C Levine Can any of you point me in the directions of a website that completely discusses this operating system, PRO or P/OS? As I recall the DEC Professional system was basically a shrunken PDP-11. Finding one of course, would be a good thing. ------------------- Gregg C Levine hansolofalcon(a)worldnet.att.net ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )

21 years, 5 months

32I status as of 17 Nov 2003

by patv＠monmouth.com

1. Converted unpublished locore to AT&T syntax. Work still underway on new locore.S file. 2. Will use coff executable format. May comply with Sys V ABI. The latter is TBD. 3. Gcc is tool chain unless someone wants to take on 32V compiler. May take advantage of inline and asm in machine dependent files. I wouldn't recommend using the 32V compiler, mainly because there are so many syntax changes, as well as newer compiler technology, missing from it as to make it a very challenging project. 4. Gcc cross compile to be used for building. I'll make this available later next month, after I shake out the bugs. 5. May go to Bitkeeper for source control. More to follow. 6. License for all new files to be the "revised BSD license." This is compatible with the Caldera license, an "original BSD license" with the advertising clause specific to Caldera. I want to keep it open source, and this is the best compromise I see for project license. 7. May change spln() to more understandable nomenclature, e.g., spl4() becomes spltty(), similar to BSD practice. 8. 32I is the interim name. I would have preferred Unix version 7, but can't for obvious trademark reasons. Project name still up for grabs. I was thinking of UNX, named after the old DEC name for the facility I work in. Sort of a tribute to days gone by, as is porting 32V. Probably get into trouble for that one as well. --------------------------------------------- This message was sent using Monmouth Internet MI-Webmail. http://www.monmouth.com/

21 years, 5 months

RE: [pups] DEC PRO or P/OS

by Fred N. van Kempen

Well, those programs emulate both the CPU (which *is* the same as those found in the PRO systems), but *also* the surrounding stuff like disk controllers, serial controllers and so on. It would not be (that) hard to add "PRO" emulation to SimH, if some sort of hardware specs are still available. cheers, Fred > -----Original Message----- > From: Gregg C Levine [mailto:hansolofalcon@worldnet.att.net] > Sent: Tuesday, November 18, 2003 2:56 AM > To: 'David Evans' > Cc: pups(a)minnie.tuhs.org > Subject: RE: [pups] DEC PRO or P/OS > > > Hello (again) from Gregg C Levine > I take it this means that the software written for those things, won't > run on an emulator normally running as a member of the regular PDP > family of machines? Such as the SIMH PDP-11 emulator, or the E11 ones. > Mr. Wilson, (John), mentions the operating system for the PRO, on the > PDF file that describes the E11, both versions as being copyrighted, > and mentions the company name. > ------------------- > Gregg C Levine hansolofalcon(a)worldnet.att.net > ------------------------------------------------------------ > "The Force will be with you...Always." Obi-Wan Kenobi > "Use the Force, Luke." Obi-Wan Kenobi > (This company dedicates this E-Mail to General Obi-Wan Kenobi ) > (This company dedicates this E-Mail to Master Yoda ) > > > > > -----Original Message----- > > From: pups-bounces(a)minnie.tuhs.org > [mailto:pups-bounces@minnie.tuhs.org] On > > Behalf Of Wilko Bulte > > Sent: Monday, November 17, 2003 5:19 PM > > To: David Evans > > Cc: pups(a)minnie.tuhs.org; Gregg C Levine > > Subject: Re: [pups] DEC PRO or P/OS > > > > On Mon, Nov 17, 2003 at 04:50:21PM -0500, David Evans wrote: > > > On Mon, Nov 17, 2003 at 10:05:33PM +0100, Wilko Bulte wrote: > > > > > > > > A Pro350 was an F11, a Pro380 a T11 (I hope I remember this > correctly) > > > > CPU. I think you could also run RT-11 on them. Some big VAX > models > > > > had Pro's as console processors/systems. RD5x disk drives on the > Pro's. > > > > And special I/O cards which only fit in Pros. > > > > > > > > > > Yeah, that's my memory as well. Rick Macklem did a port of > 2.9BSD to them. > > > I used one for a time; it took something like thirty seconds to > load vi! > > > > The 380 was pretty much OK in my recollection. 350 was downright > slow. > > RD5x drives did not help here.. > > > > -- > > | / o / /_ _ wkb(a)freebie.xs4all.nl > > |/|/ / / /( (_) Bulte > > _______________________________________________ > > PUPS mailing list > > PUPS(a)minnie.tuhs.org > > http://minnie.tuhs.org/mailman/listinfo/pups > > _______________________________________________ > PUPS mailing list > PUPS(a)minnie.tuhs.org > http://minnie.tuhs.org/mailman/listinfo/pups >

21 years, 5 months

Re: [TUHS] 32I status as of 17 Nov 2003

by macbiesz＠optonline.net

Perhaps v7upgrade would make a nice combination with the 32I kernel. http://www.southern-storm.com.au/v7upgrade.html Maciek > > > > 3. Gcc is tool chain unless someone wants to take on 32V > compiler. May > > take advantage of inline and asm in machine dependent files. > > > > I wouldn't recommend using the 32V compiler, mainly because there > > are so many syntax changes, as well as newer compiler technology, > > missing from it as to make it a very challenging project. > > There are a couple of options here. One is to use one of the > compilersfrom MIT that will match the code in 32V very closely. > You can google for > these if they aren't already on Warren's site. The other option > is to use LCC. I wouldn't use GCC if I were doing it. (Of course > I'm not > so these are just suggestions.)>

21 years, 5 months

RE: [pups] DEC PRO or P/OS

by Fred N. van Kempen

> A Pro350 was an F11, a Pro380 a T11 (I hope I remember this correctly) > CPU. The 380 had a J11, the 350 had an F11. I *believe* the 280 was somewhere between an 11/73 and an 11/53, and the 350 was somewhat like an 11/23. > I think you could also run RT-11 on them. Some big VAX models > had Pro's as console processors/systems. RD5x disk drives on > the Pro's. Correct. If memory serves me right, you had P/OS (a menu-driven branch of the RT11 system), and Venix, a somewhat Unix-like system. Given some work, one should be able to get standard RT working on it. --f

21 years, 5 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