Sponsored Content
The Lounge What is on Your Mind? A terrific historical video about UNIX circa 1982 with well known names. Post 303033206 by bakunin on Monday 1st of April 2019 02:57:21 PM
Old 04-01-2019
OMG, Brian Kernighan in young!

Great find, wisecracker.

bakunin
This User Gave Thanks to bakunin For This Post:
 

9 More Discussions You Might Find Interesting

1. IP Networking

TCP-IP discussions from 1982 to 1991

Found this archive on the net: TCP-IP discussions from 1982 to 1991.... very interesting reading!! http://www-mice.cs.ucl.ac.uk/multimedia/misc/tcp_ip/ (0 Replies)
Discussion started by: Neo
0 Replies

2. UNIX for Dummies Questions & Answers

historical ps

Hi there I am trying to find out what processes were running on my sun solaris 5.8 server yesterday. There are no jobs running on the server which are monitoring/logging processes on the server. Is there a way to find this out - is there an operating system log for processes? Thanks in... (4 Replies)
Discussion started by: niamh
4 Replies

3. UNIX for Dummies Questions & Answers

Unix training Video's

Hello any body knows a website that can Purchase and download Video training for unix ?? (1 Reply)
Discussion started by: wickedsoul
1 Replies

4. AIX

Historical Disk bandwidth utilization

Early this morning our sar reports show that WIO on the system was over 50% for about an hour. We also had some users complain about response time problems during this time. Is there a way I can go back and check what disks were busy during this time (something like topas but for historical data)? (1 Reply)
Discussion started by: 2dumb
1 Replies

5. IP Networking

historical question - endianess

why Network Byte Order is Big-Endian, (not a Little-Endian, like most modern PCs use) ? (3 Replies)
Discussion started by: variety
3 Replies

6. Red Hat

historical port usage information

are there linux commands or applications that i can use to find out what application was using a certain port at a certain time? there's teamquest,but it doesnt have this kind of information. TIA. (2 Replies)
Discussion started by: bumblebee
2 Replies

7. Shell Programming and Scripting

Help File Copy Historical Files

Hello, I have a directory /files/storage in which I have files having file name in format as follows sabclin.yyyymmdd.0 e.g. sabclin.20110621.0 etc. I want to copy all files that have a date in their file name i.e. yyyymmdd from today till 300 days in the past to another directory, I need... (3 Replies)
Discussion started by: srattani
3 Replies

8. What is on Your Mind?

Video: What Do You Do for a Living? @UNIX.com

Video: What Do You Do for a Living? @UNIX.com https://youtu.be/eTddtFa_Z_g We asked our users at UNIX.com what they do for a living, and this was their top three replies in 1080 HD video. Shout-outs to quotes in the video from forum members Akshay Hegde, geeky404, ni2 and joeyg. Here... (0 Replies)
Discussion started by: Neo
0 Replies

9. What is on Your Mind?

A terrific quote:

Food for thought! """ Everybody in this country should learn to program a computer...because it teaches you how to think. """ Steve Jobs. So, SO, true! Merry XMAS all... (4 Replies)
Discussion started by: wisecracker
4 Replies
DITROFF(7)                                               Miscellaneous Information Manual                                               DITROFF(7)

NAME
ditroff - classical device independent roff DESCRIPTION
The name ditroff once marked a development level of the troff text processing system. In actual roff(7) systems, the name troff is used as a synonym for ditroff. The first roff system was written by Joe Ossanna around 1973. It supported only two output devices, the nroff program produced text ori- ented tty output, while the troff program generated graphical output for exactly one output device, the Wang Graphic Systems CAT typeset- ter. In 1979, Brian Kernighan rewrote troff to support more devices by creating an intermediate output format for troff that can be fed into postprocessor programs which actually do the printout on the device. Kernighan's version marks what is known as classical troff today. In order to distinguish it from Ossanna's original mono-device version, it was called ditroff (device independent troff) on some systems, though this naming isn't mentioned in the classical documentation. Today, any existing roff system is based on Kernighan's multi-device troff. The distinction between troff and ditroff isn't necessary any longer, for each modern troff provides already the complete functionality of ditroff. On most systems, the name troff is used to denote ditroff. The easiest way to use ditroff is the GNU roff system, groff. The groff(1) program is a wrapper around (di)troff that automatically han- dles postprocessing. SEE ALSO
[CSTR #54] The 1992 revision of the Nroff/Troff User's Manual by J. F. Ossanna and Brian Kernighan, see Bell Labs CSTR #54 <http://cm.bell- labs.com/cm/cs/cstr/54.ps.gz>. [CSTR #97] A Typesetter-independent TROFF by Brian Kernighan is the original documentation of the first multi-device troff (ditroff), see Bell Labs CSTR #97 <http://cm.bell-labs.com/cm/cs/cstr/97.ps.gz>. roff(7) This document gives details on the history and concepts of roff. troff(1) The actual implementation of ditroff. groff(1) The GNU roff program and pointers to all documentation around groff. groff_out(5) The groff version of the intermediate output language, the basis for multi-devicing. AUTHORS
Copyright (C) 2001, 2002, 2004, 2007, 2008, 2009 Free Software Foundation, Inc. This document is distributed under the terms of the FDL (GNU Free Documentation License) version 1.3 or later. You should have received a copy of the FDL on your system, it is also available on-line at the GNU copyleft site <http://www.gnu.org/copyleft/fdl.html>. This document is part of groff, the GNU roff distribution. It was written by Bernd Warken <bwarken@mayn.de> and is maintained by Werner Lemberg <wl@gnu.org>. Groff Version 1.21 25 June 2012 DITROFF(7)
All times are GMT -4. The time now is 07:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy