TUHS

tuhs@tuhs.org

6532 discussions

by Larry McVoy

> From: Albert Cahalan <albert(a)users.sf.net> > Subject: Re: [TUHS] cvsweb for BSD > > One of the big problems is that they move files all over the place as BSD > > developed and CVS doen't work too elegantly with those kind of changes. > > Bitkeeper handles this well. I suspect that Larry McVoy would > at least be mildly interested in giving advice for such > a project. Bitkeeper is SCCS-based. Yes, I'd be interested. Other than the renames I think we can automate most of this. > Bitkeeper also has a superior web interface. You can't beat > standard unified diff format with a tiny bit of color added. Thanks. One day we'll get around to adding sub line highlighting - that would be an improvement. > From: "M. Warner Losh" <imp(a)bsdimp.com> > Subject: Re: [TUHS] cvsweb for BSD > > If you are going to use a proprietary system, you might as well use > perforce, which has better branching and file movement support than > bitkeeper. But I guess I'm a little biased because I like p4 better > than bk. Both biased and incorrect. There are over 10,000 branches of the linux kernel floating around in BitKeeper (we know, we counted them) and we handle file movement much more nicely than perforce does (we have our own concept of an inode, a pathname is a attribute of an inode just like contents are an attribute of the inode - so you can move A to B, I modify A, you pull from me and the changes apply to B in your tree.) You can be as biased as you want, I don't want to turn this into a SCM discussion, but try and be accurate. About the only thing that p4 does that we don't do is centralized locking; we don't need to do that in a distributed/replicated system but people sometimes want it. -- --- Larry McVoy lm at bitmover.com http://www.bitkeeper.com

21 years, 1 month

Grokline: Tracing the history of Unix IP

by Chris Palmer

Maybe everyone here already knows about this, but I haven't seen anything, so I'm posting it. http://www.groklaw.net/article.php?story=20040524130757328 "We hope with this Grokline project to be able to identify any conceivable legal issues that those wishing to block, slow, hobble or tax GNU/Linux may try to use in future legal assaults on the community. If there are litigation risks, even just from nuisance lawsuits, particularly with respect to patents, we want to find those risks, hopefully before they do, and mitigate or resolve them now. I am personally convinced, as you no doubt are too, that the next wave of attacks on GNU/Linux and the GPL will involve patents." -- http://chris.nodewarrior.org/

21 years, 1 month

m68k SVR2 on Perq (was: web site detailing Apple's mc68k UNIX, A/UX)

by Eric Riebling

> >Incidentally, the Unisoft m68k port of SVR2 at the core of A/UX was also >ported to the Perq-5 in 1986/1987, to create the Crosfield Studio 9500. > >Perq had just folded, but a core group of ex-Perq employees worked with a >team from the UK company Crosfield Electronics to take the machine (which at >that time existed only as a wire-wrap prototype) through to production. > >I was a member of that team and I have fond memories of sitting in a >basement office in Pittsburgh surrounded by kernel listings (with a very >puzzled look on my face). > >Just a small footnote in Unix history... > >-- >Roger That's strange, I have those very same memories. In fact I was looking for someone who would appreciate this: #ifdef PYTHON Cheers, Eric

21 years, 1 month

Quasijarus 0c now listed on SIMH Software Kits page

by Kenneth Stailey

http://simh.trailing-edge.com/software.html __________________________________ Do you Yahoo!? SBC Yahoo! - Internet access at a great low price. http://promo.yahoo.com/sbc/

21 years, 1 month

[pups] E11 and versions and I/O devices

by Gregg C Levine

Hello from Gregg C Levine I've got a bundle of questions regarding E11, and its range of I/O devices. Here goes: 1) Is anyone running the DOS/Windows version with the Display Register device attached to a LPT port? Where did they obtain the LED devices for it? 2) How did they configure its interpretation of the PDP-11 serial devices? 3) Or the network connections? Favorite Ethernet cards as well. And last but not least: 4)Which printer arrangement was used? Serial? Even a parallel solution? To be honest I haven't seen any action on both lists with in the past number of days, so I thought I'd post something new to the PUPS list, and give it something to chew on. ------------------- 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

21 years, 1 month

cvsweb for BSD

by Kenneth Stailey

Hi, I just thought of a neat idea. Put old versions of BSD source code into a CVS archive using "cvs import" and then run a CVSWEB site with that. Possibly converting SCCS to RCS to CVS. I don't know how far back my BSD SCCS goes. Maybe a smaller project to CVS 4.3BSD-tahoe to Quasijarus first. One of the big problems is that they move files all over the place as BSD developed and CVS doen't work too elegantly with those kind of changes. Maybe subversion not CVS but I've yet to do anything with subversion. Does anything like this already exist? Thanks, Ken __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

21 years, 1 month

Re: [TUHS] cvsweb for BSD

by msokolov＠ivan.Harhan.ORG

Kenneth Stailey <kstailey(a)yahoo.com> wrote: > One of the big problems is that they move files all over the place as BSD > developed and CVS doen't work too elegantly with those kind of changes. Yes, neither SCCS nor RCS nor CVS tracks file moves, and for this single reason an SCCS/RCS/CVS tree is not sufficient by itself to act as a complete BSD history tree. See this page for an idea of what I had to go through: http://ifctfvax.Harhan.ORG/Quasijarus/sccs.html MS

21 years, 1 month

SVR4-MP "ps -z" and "ps -Z"

by Albert Cahalan

I'm seeking info about the SVR4-MP ps options -z and -Z, as used for mandatory access control. This is so that they can be implemented for Linux. Alternately, are there more-common ways to handle this security data or more-common usage of the -z and -Z options? I could use some example output. All "trusted" high-security systems are of interest.

21 years, 1 month

Re: [TUHS] Lions book (was: Booting v6)

by Brian S Walden

I <tuhs(a)cuzuco.com> wrote: > I resurrected the Lions' source code for the commentary I made some > 15 years back -- line numbers at all. It had been lost for some time > and it took a bit, but I finally found it on some obsolete media. > In making it I didn't have v6 source so it was reverted from v7. > > See http://v6.cuzuco.com/ Sorry to bother again, but I just noticed that the PostScript versions I uploaded were the portrait mode ones, not landscape. I have put the right ones in now, so if you downloaded them before this message, you'll need to get them again. Both PDFs however were and are correct. -B

21 years, 2 months

Fw: [TUHS] Re: Lions' book

by Roger Willcocks

On Thursday, April 15, 2004 6:40 AM, Warren Toomey <wkt(a)tuhs.org> wrote: > >>I will give you all three guesses as to who Leo was. Hint: he lives > >>in Australia. > > On Thu, Apr 15, 2004 at 09:18:45AM +1000, Peter Jeremy wrote: > >That would rule out John since he no longer lives in Australia. > > True. The person is alive and well and living on the Gold Coast in > Queensland where he works for a small private university. He is > also semi-active in the arena of Unix history. He has a beard. He > regrets never admitting to the copying of the commentary to John > Lions personally, because John would probably have commended the > act. Hmmm, try Googling for /interests "unix history" australia latex/ :-) You wouldn't know, off-hand, whether 'Leo' actually rekeyed the content ? -- Roger

21 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