UNIX Circuit Design System Post: 302963490

Sponsored Content

Special Forums UNIX and Linux Applications UNIX Circuit Design System Post 302963490 by mghis on Thursday 31st of December 2015 11:32:59 AM

12-31-2015

Registered User

UNIX Circuit Design System

Hi all.

In some articles I have read about a "UNIX Circuit Design System", which was written originally in some version of
Research UNIX by Sandy Fraser.

Here is a quote from the article "A Research UNIX Reader: Annotated Excerpts from the Programmer's Manual", by Douglas McIlroy:

Quote:

CDL (v7 pages 60-63)
Although most users do not encounter the UNIX Circuit Design System, it has long stood as an important application in the lab. Originated by Sandy Fraser and extended by Steve Bourne, Joe Condon, and Andrew Hume, UCDS handles circuits expressed in a common design language, cdl. It includes programs to create descriptions using interactive graphics, to lay out boards automatically, to check circuits for consistency, to guide wire-wrap machines, to specify combinational circuits and optimize them for programmed logic arrays (Chesson and Thompson). Without UCDS, significant inventions like Datakit, the 5620 Blit terminal, or the Belle chess machine would never have been built. UCDS appeared in only one manual, v7.

Even this page of a book recorded by "Google Books" describes in some extent its use.

However I could not find the source code nor the manual, even though 7th Edition UNIX nowadays is freely available. (I have searched through TUHS Archives)

Does anyone know why is is not included in V7 sources and how can I get it?

Thank you in advance.

mghis

View Public Profile for mghis

Find all posts by mghis

6 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Latest Design of New Unix Header (Flash)

As everyone might know by now, we have a new 'draft' banner with matrix theme, falling unix commands, blinking numbers, and more. This will be the new default theme for the forums. We are in the process of sending final comments to our designer, please feel free to post your suggestions here....

2. UNIX for Dummies Questions & Answers

Urgent help with web design problems - mac, safari and unix computer

Hi (Help, Help, Help) I am on a computer course and have designed a web site as one of my assignments. just before Xmas my college tutor "very kindly" viewed my site with a mac, safari browser and unix operating system computer. This is what she Emailed back to me, and I am trying to sort...

3. UNIX for Advanced & Expert Users

How to design a simple multi tasking shell in unix using C language

can any one help me in designing a shell in unix like bash shell using c language plzzzzzzzzzzzzzzzzzzzz help

4. Programming

c++, design patterns and Unix

I know this is C Unix section, still I address a C++ question. How often did you see/use/apply or consider is welcome to write C++ code on Unix, based on 'design patters'? Since I'm at the very beginning with Unix programming, I have this doubt, ... about DP techniques and languages where to apply...

5. UNIX for Advanced & Expert Users

how to design compiler for unix os

i have to design a compiler for unix os can anybody help me out to solve this problem

6. Shell Programming and Scripting

Short circuit if

Hello everyone, just wondering if this type of if condition will execute properly. Suppose I have a script with two functions in it called abc and def: is this code valid, or is there a better way to short circuit the if statement? #! /bin/ksh93 abc(){ statement 1 using $1 statement 2...

LEARN ABOUT DEBIAN

history

HISTORY(5)							File Formats Manual							HISTORY(5)

NAME

       history - record of current and recently expired Usenet articles

DESCRIPTION

       The file /var/lib/news/history keeps a record of all articles currently stored in the news system, as well as those that have been received
       but since expired.  In a typical production environment, this file will be many megabytes.

       The file consists of text lines.  Each line corresponds to one article.	The file is normally kept sorted in the order  in  which  articles
       are  received,  although  this  is not a requirement.  Innd(8) appends a new line each time it files an article, and expire(8) builds a new
       version of the file by removing old articles and purging old entries.

       Each line consists of two or three fields separated by a tab, shown below as 	:
	      <Message-ID>   	   date
	      <Message-ID>   	   date	 	   files

       The Message-ID field is the value of the article's Message-ID header, including the angle brackets.

       The date field consists of three sub-fields separated by a tilde.  All sub-fields are the text representation  of  the  number  of  seconds
       since  the  epoch -- i.e., a time_t; see gettimeofday(2).  The first sub-field is the article's arrival date.  If copies of the article are
       still present then the second sub-field is either the value of the article's Expires header, or a hyphen if no expiration date  was  speci-
       fied.   If  an article has been expired then the second sub-field will be a hyphen.  The third sub-field is the value of the article's Date
       header, recording when the article was posted.

       The files field is a set of entries separated by one or more spaces.  Each entry consists of the name of the newsgroup, a  slash,  and  the
       article number.	This field is empty if the article has been expired.

       For  example, an article cross-posted to comp.sources.unix and comp.sources.d that was posted on February 10, 1991 (and received three min-
       utes later), with an expiration date of May 5, 1991, could have a history line (broken into two lines for display) like the following:
	      <312@litchi.foo.com>  		666162000~673329600~666162180  	
		  comp.sources.unix/1104 comp.sources.d/7056

       In addition to the text file, there is a dbz(3z) database associated with the file that uses the Message-ID field as a key to determine the
       offset  in  the	text  file  where the associated line begins.  For historical reasons, the key includes the trailing  byte (which is not
       stored in the text file).

HISTORY

       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  This is revision 1.12, dated 1996/09/06.

SEE ALSO

       dbz(3z), expire(8), innd(8), news-recovery(8).

																	HISTORY(5)