[comp.unix.questions] Undeliverable mail

root@apg-3.arpa (03/30/87)

Mail to host "[255.255.255.255]" could not be sent.
Destination host is unknown.

------- Unsent message is below -------

Date: Fri, 27 Mar 87 15:58:38 EST
From: The SuperUser <root@apg-3.ARPA>
Subject: Undeliverable mail
To: info-unix-request@BRL-SEM.arpa

Mail addressed to host apg-5.arpa could not be sent for the following reason:

554 Message has travelled too many hops
------- Unsent message is below -------

Received: from BRL-SEM.ARPA by APG-3 ; 27 Mar 87 15:54:07 EST
Received: from BRL-SEM.ARPA by SEM.BRL.ARPA id aa07644; 27 Mar 87 13:37 EST
Received: from [192.5.19.3] by SEM.BRL.ARPA id aa06897; 27 Mar 87 12:04 EST
Received: from ics.uci.edu by ICSC.UCI.EDU id a000915; 27 Mar 87 9:03 PST
Received: from bboards by ICS.UCI.EDU id a005629; 27 Mar 87 8:59 PST
Received: from brl-sem.arpa by ICS.UCI.EDU id a005611; 27 Mar 87 8:57 PST
Received: from BRL-SEM.ARPA by SEM.brl.ARPA id aa06199; 27 Mar 87 10:45 EST
Received: from [192.5.19.3] by SEM.BRL.ARPA id aa05643; 27 Mar 87 9:33 EST
Received: from ics.uci.edu by ICSC.UCI.EDU id a000530; 27 Mar 87 6:28 PST
Received: from bboards by ICS.UCI.EDU id a004004; 27 Mar 87 6:24 PST
Received: from brl-sem.arpa by ICS.UCI.EDU id a003970; 27 Mar 87 6:19 PST
Received: from BRL-SEM.ARPA by SEM.brl.ARPA id aa04804; 27 Mar 87 8:14 EST
Received: from [192.5.19.3] by SEM.BRL.ARPA id aa04786; 27 Mar 87 8:06 EST
Received: from ics.uci.edu by ICSC.UCI.EDU id a000427; 27 Mar 87 5:01 PST
Received: from bboards by ICS.UCI.EDU id a003428; 27 Mar 87 4:56 PST
Received: from brl-sem.arpa by ICS.UCI.EDU id a003400; 27 Mar 87 4:52 PST
Received: from BRL-SEM.ARPA by SEM.brl.ARPA id aa04382; 27 Mar 87 7:05 EST
Date:     Fri, 27 Mar 87 3:46:35 EST
From:     Mike Muuss (UNIX Wizards) <unix-wizards-request@BRL.ARPA>
To:       info-unix@BRL.ARPA
Subject:  Duplicate digests
Message-ID:  <8703270346.aa03771@SEM.BRL.ARPA>

      Good morning,

   I am not sure just how it happened, but the issue counter for the
digest got reset.  Sorry for the duplicate digests....

--for Mike Muuss,
				Later,
				    Bob
				    <reschly@BRL>

Postmaster%UMNACVX.BITNET@wiscvm.wisc.edu (PMDF Mail Server) (08/18/87)

The message could not be delivered to:

Addressee: DFSLAB4
Reason: %MAIL-E-SYNTAX, error parsing 'NELSEN@S1.MSI.UMN.EDU'

----------------------------------------

Received: from JNET-DAEMON by UMNACVX.BITNET; Mon, 17 Aug 87 23:19 CDT
Received: From WISCVM(SMTP) by UMNACVX with RSCS id 8237          for DFSLAB4@UM
   NACVX; Mon, 17 Aug 87 23:19 CDT
Received: from SEM.BRL.MIL by wiscvm.wisc.edu ; Mon, 17 Aug 87 23:13:40 CDT
Received: from SEM.BRL.MIL by SEM.brl.ARPA id aj14137; 14 Aug 87 19:02 EDT
Received: from sem.brl.mil by SEM.BRL.ARPA id aa05631; 13 Aug 87 2:46 EDT
Date: Thu, 13 Aug 87 02:45:52 EST
From: The Moderator (Mike Muuss) <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V3#226
To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Message-ID:  <8708130246.aa05631@SEM.BRL.ARPA>

INFO-UNIX Digest          Thu, 13 Aug 1987              V3#226

Today's Topics:
        Re: Re: How do you link the terminfo library on SysV.2?
                 Re: Why does vipw *require* /bin/csh ?
                         lp spool system query
                     Ultrix password ageing - How?
                        Re: writers' work bench
                  Re: (Probably dumb) SysVR3 questions
        Re: Re: How do you link the terminfo library on SysV.2?
                  Re: (Probably dumb) SysVR3 questions
                             Dot file diff?
                             Unix versions
                   Looking for a VT102 termcap entry.
                           Re: spell bug?????
                        Re: System V commands...
       Unix shell script to eliminate mail from sender available.
                          Re: Maxwell's deamon
                           Re: spell bug?????
                Re: Negative numbers as expr(1) argument
                   Re: Ultrix password ageing - How?
         Re: How to prevent low-grade uucp work during daytime?
     Re: Unix shell script to eliminate mail from sender available.
                 Re: red herrings (was spell bug?????)
                        Init not running gettys
                           Re: spell bug?????
                       Re: lp spool system query
-----------------------------------------------------------------

From: "Kim Chr. Madsen" <kimcm@ambush.uucp>
Subject: Re: Re: How do you link the terminfo library on SysV.2?
Date: 11 Aug 87 09:04:19 GMT
To:       info-unix@SEM.BRL.MIL

In article <1377@chinet.UUCP> randy@chinet.UUCP (Randy Suess) writes:
>In article <449@ambush.UUCP> kimcm@ambush.UUCP (Kim Chr. Madsen) writes:
>>But also
>>the disadvantage of not being able to add new attributes to the files.

>    Sure you can.  SysVr2 comes with the tic (terminfo compiler) that
>    allows you to replace any entry in the /usr/lib/terminfo/* that
>    you want.

Sure, that exactly the point you can replace any existing field but if I
want to include information about using graphic symbols on my teminal i.e.
to make frames around a window - neither the standard termcap or terminfo
supports this, but in termcap you could make new entries (provided you could
find a two-letter code not already in use) however it is impossible in
terminfo since it only allocates addresses (in the compiled entry) for known
fields - which is why the tic command has been altered between SYSVR2 and
SYSVR3 since more entries were added. Fast but clupsy - I'd rather had the
termcap entries split up into several files in /usr/lib/termcap/?/* thus
keeping compatibility between old termcap routines (as used in other UNIX'es)
and the improved speed in finding & readin the entry.

                        Kim Chr. Madsen.

-----------------------------

From: Simon Brown <xsimon@its63b.edinburgh.ac.uk>
Subject: Re: Why does vipw *require* /bin/csh ?
Date: 11 Aug 87 10:13:57 GMT
Keywords: vipw
To:       info-unix@brl-sem.arpa

In article <2647@lifia.UUCP> phs@lifia.UUCP (Philippe Schnoebelen) writes:
>When you call vipw in order to modify the passwd file under UNIX BSD4.3, it
>performs several so called "sanity checks", e.g.  that you have su'ed, that
>noone else  is currently modifying  it, ...  but more surprisingly  it also
>verifies that your shell  is bin/csh or /bin/sh, which  forbids  you to use
>another shell when su'ed.
>
>Is there any  way around this other than patching the source and recompiling?

Yeah - fire up an "adb -w", and change that "c" in csh to something more useful
- like a "k", perhaps?
--
 ----------------------------------
| Simon Brown                    | UUCP:  seismo!mcvax!ukc!its63b!simon
| Department of Computer Science | JANET: simon@uk.ac.ed.its63b
| University of Edinburgh,       | ARPA:  simon%its63b.ed.ac.uk@cs.ucl.ac.uk
| Scotland, UK.                  |
 ----------------------------------     "Life's like that, you know"

-----------------------------

From: Carlos Mendioroz <tron@mrecvax.uucp>
Subject: lp spool system query
Date: 11 Aug 87 20:47:30 GMT
Keywords: lpr spool lock
To:       info-unix@SEM.BRL.MIL

I 'm running ULTRIX 1.2 on a uVax and have a pair of printers connected
to the same port (a tty line) via an inteligent switch.
The problem is how to tell lpd that both printers share the same tty line
and so, he shouldn't try to write both at the same time.
I 've tried using the same spool directory but that didn't work.

Any suggestion ?
Thanks in advance.

Carlos G Mendioroz - Ministerio de Relaciones Exteriores y Culto
             Buenos Aires  ARGENTINA
UUCP : {seismo|uunet|pyramid!utai|decvax!utcsri}!atina!mrecvax!tron

"I've had nothing yet",Alice replied in an
offended tone, "so I can't take more."
"You mean you can't take less," said the Hatter:
"it's very easy to take more than nothing."

-----------------------------

From: 8753 <mechjgh@tness1.uucp>
Subject: Ultrix password ageing - How?
Date: 11 Aug 87 15:38:50 GMT
Keywords: password expiration dates
To:       info-unix@brl-sem.arpa

Is password ageing implemented in Ultrix-32 ?
The manuals didn't mention it.

-----------------------------

From: Guy Harris <guy%gorodish@Sun.COM>
Subject: Re: writers' work bench
Date: 12 Aug 87 06:15:23 GMT
Sender: news@sun.uucp
Keywords: wwb, writers work bench, grammer analysis, spelling, writing
To:       info-unix@SEM.BRL.MIL

> You can buy the Writer's Workbench in source form from AT&T.  In binary
> form you can buy copies from Elan (415) 322-2450, Textware (617) UNI-TEXT,
> and Image Network (415) 967-0542.  Note that other companies sell "enhanced"
> versions of DWB under various names (SQtroff from SoftQuad, Crystalwriter
> from I don't know who).  If you're interested in PostScript support, let
> me know as we sell an add-on package for ditroff->PostScript conversion.

I presume you meant *Documenter's* Workbench above?  WWB and DWB are rather
different beasts.
    Guy Harris
    {ihnp4, decvax, seismo, decwrl, ...}!sun!guy
    guy@sun.com

-----------------------------

From: Guy Harris <guy%gorodish@Sun.COM>
Subject: Re: (Probably dumb) SysVR3 questions
Date: 12 Aug 87 07:37:41 GMT
Sender: news@sun.uucp
To:       info-unix@brl-sem.arpa

> > The 14-character file-name limit is killing us; is it extendable
> > (redefine something, somewhere?) by remaking the kernel?
>
> No, you would also have to remake many of the standard commands.
> (ls, etc...)
>
> You would then run into problems with anything else that thinks
> there is a 14 character size (SGS, uucp, cpio, etc....)

"cpio" thinks there is a 14 character size?  Gee, that's news to me.  Sun has
supplied "cpio" with its systems for quite a while, and has had file systems
without a 14-character file size limit for at least as long.  The only changes
made to "cpio" (until a lot of real grot was cleaned up recently) had nothing
to do with the directory format; "cpio" doesn't even know what directories look
like!

As for "uucp", well, err, umm, there's this #define constant in the Honey
Danber source to S5R3 called "BSD4_2"; presumably it wasn't just stuck in there
for decoration.  It may not *use* more than 14 characters of the file name, but
it uses the directory library so it should be capable of surviving changes to
directory names.

COFF, unfortunately, thinks file names are limited to 14 characters (I presume
this is the source of SGS's problem), but that's just a botch.  You could stick
longer file names in the string table, and just have first 4 bytes of the
filename auxiliary entry be zero and the next 4 be a string table index.

You missed the *real* killer, though; if he just redefined DIRSIZE to something
other than 14, and recompiled the kernel, every single one of the file systems
on his disks would be totally unusable by that kernel!

DIRSIZE is in the "fundamental constants of the implementation-- cannot be
changed easily" section of <sys/param.h>, with good reason.  (Other items in
that section, such as CLKTICK ("microseconds in a clock tick") and CDLIMIT
("default max write address", i.e. default "ulimit"), don't belong there at
all, of course.  The latter should, of course, be changed to 0x7fffffff or some
other flavor of MAXLONG.)
    Guy Harris
    {ihnp4, decvax, seismo, decwrl, ...}!sun!guy
    guy@sun.com

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: Re: How do you link the terminfo library on SysV.2?
Date: 12 Aug 87 17:04:02 GMT
To:       info-unix@SEM.BRL.MIL

In article <454@ambush.UUCP> kimcm@ambush.UUCP (Kim Chr. Madsen) writes:
>Sure, that exactly the point you can replace any existing field but if I
>want to include information about using graphic symbols on my teminal i.e.
>to make frames around a window - neither the standard termcap or terminfo
>supports this, but in termcap you could make new entries (provided you could

Both termcap and terminfo support alternate line-drawing character sets,
with terminfo "acsc" (termcap "ac") defining the pairings with the normal
character set, if the VT100 defaults are not appropriate, and smacs (as)
to start alternate character set mode, rmacs (ae) to end alternate character
set mode, and enacs (eA) if something has to be done to enable the alternate
character set before using smacs (as).  These aren't described very well in
older documentation, including that supplied with 4.3BSD, but they're at
least mentioned in current versions, if I recall correctly.  (I may have left
"eA" out of the termcap manual.  I need to bring it up to SVR3 level anyway.)

>find a two-letter code not already in use) however it is impossible in
>terminfo since it only allocates addresses (in the compiled entry) for known
>fields - which is why the tic command has been altered between SYSVR2 and
>SYSVR3 since more entries were added. Fast but clupsy - I'd rather had the
>termcap entries split up into several files in /usr/lib/termcap/?/* thus
>keeping compatibility between old termcap routines (as used in other UNIX'es)
>and the improved speed in finding & readin the entry.

Terminfo has many advantages over termcap besides eliminating the linear
search through the database.  For example, its parameter mechanism is
more general.

    -- your semi-friendly 4.3BSD termcap manual entry editor

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: (Probably dumb) SysVR3 questions
Date: 12 Aug 87 17:08:07 GMT
To:       info-unix@brl-sem.arpa

In article <25420@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:
>COFF, unfortunately, thinks file names are limited to 14 characters (I presume
>this is the source of SGS's problem), but that's just a botch.  You could stick
>longer file names in the string table, and just have first 4 bytes of the
>filename auxiliary entry be zero and the next 4 be a string table index.

All "ar" utilities I know of, including 4.2BSD's, restrict member names
to something like 14 or 16 characters.  Thus the problem is not restricted
to COFF filename entries.

-----------------------------

From: Mike Kao <mkao@pnet01.CTS.COM>
Subject: Dot file diff?
Date: 12 Aug 87 03:57:46 GMT
Sender: news@crash.CTS.COM
To:       info-unix@SEM.BRL.MIL

Please explain to me the different purposes of the files .login and .profile.

To insure my reception of any replies, please respond via e-mail. Thanks!

                                                                  -- Mike Kao

UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!mkao
ARPA: crash!pnet01!mkao@nosc.mil
INET: mkao@pnet01.CTS.COM

-----------------------------

From: Mike Kao <mkao@pnet01.CTS.COM>
Subject: Unix versions
Date: 12 Aug 87 10:56:22 GMT
Sender: news@crash.CTS.COM
To:       info-unix@brl-sem.arpa

What is the difference between all these different versions of Unix anyways?
How is System V different from the standard (or is there one?)?

To insure my reception of any replies, please respond via e-mail. Thanks!

                                                                  -- Mike Kao

UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!mkao
ARPA: crash!pnet01!mkao@nosc.mil
INET: mkao@pnet01.CTS.COM

-----------------------------

From: Peter Lauterbach <pbach@itsgw.RPI.EDU>
Subject: Looking for a VT102 termcap entry.
Date: 12 Aug 87 15:26:36 GMT
To:       info-unix@brl-sem.arpa


    I'm looking for a VT102 termcap entry that takes advantage of the
line drawing characters. This is actually for the MS-Kermit 2.29x terminal
emulator, as I've only seen one real VT102, and never any documentation.
Thanks.

--
    aka          : Peter Lauterbach
    BITNet       : USEREZ8Y@rpitsmts.bitnet
    Internet     : pbach@itsgw.rpi.edu
    Internet     : lauterbach@rpitsmts.rpi.edu

-----------------------------

From: Neal Ziring <nz@hotlg.att.arpa>
Subject: Re: spell bug?????
Date: 12 Aug 87 12:49:30 GMT
Keywords: is this in every system?
To:       info-unix@SEM.BRL.MIL

In article <1024@hoqax.UUCP> bicker@hoqax.UUCP (The Resource, Poet of Quality)
 writes:
 > In article <541@augusta.UUCP>, bs@augusta.UUCP (Burch Seymour) writes:
 > > Three of the words which are passed through by spell are:
 > >  vfppvdu, plbpvhb, and nbclowd
 > > Is this a known problem? Do these words pass on all unix systems?
 > Not mine.

Not mine either.  I am on an AT&T System V 2.0v2 with Bell Labs enhancements
on a VAX 8650.  It is labelled (sp?) as revision 1.7, for whatever good that
does.
--
 ...nz  (Neal Ziring  @  ATT-BL Holmdel, x2354, 3H-437)
    "You can fit an infinite number of wires into this junction box,
    but we usually don't go that far in practice."
                    London Electric Co. Worker, 1880s

-----------------------------

From: "R. Brad Kummer" <rbk@akgua.ATT.COM>
Subject: Re: System V commands...
Date: 12 Aug 87 12:10:06 GMT
To:       info-unix@SEM.BRL.MIL

In article <5004@ihlpa.ATT.COM>, kai@ihlpa.ATT.COM (Irwin) writes:
> mailx does have a "r" respond, although no forward

A simple way to forward mail from mailx is to use the '|' command to
pipe the message to 'mail', e.g. at the ? prompt, type: | "mail joe!user"
Note that the quotes are required; the '|' command seems to want only
one argument.

    R. Brad Kummer    {ihnp4, akgua}!akguc!rbk
    AT&T Bell Laboratories    Atlanta, GA

-----------------------------

From: "Wilfredo V. Perez" <wvp@aplvax.uucp>
Subject: Unix shell script to eliminate mail from sender available.
Date: 12 Aug 87 14:17:38 GMT
To:       info-unix@brl-sem.arpa


Hello,

    Recently, I had a discussion with someone on the net that deteriorated
into insults from the other part (my guess is that he couldn't handle to have
his arguments refuted in a calm and civilized way).  Since it was a pointless
discussion I decided to write the enclosed Unix shell script to eliminate the
mail from this person.  It has its limitations but it was fun to write it.  Any
problems, ideas, or comments please feel free to send me e-mail. This is the
first time that I post sources, so, my apologies if it goes to the wrong
newsgroup.

    Hope you never need this,
    -- Willy
       arpa: wvp@aplvax
       uucp: ...!seismo!mimsy!aplcen!aplvax!wvp


[to Jim: now you know why i have not been answering your mail, if any]

 --------------------------------- cut here
 -------------------------------------
#! /bin/sh
#
#  Revision: 1.1
#
#  (C) Copywright 1987 by Wilfredo V. Perez
#  Address:  arpa -- wvp@aplvax
#            uucp -- ...!seismo!mimsy!aplcen!aplvax!wvp
#
#  This script was implemented as a quick/dirty way to eliminate mail from
#  the user's system mail box of mail from an "undiserable sender".
#  Called from the .login/.profile file it will eliminate the mail before
#  you even find out about it, eliminating the temptation of reading it and
#  been agravated by it.  The author will be modifying it in the near future
#  to overcome its limitations (e.g., only one sender, only the first message)
#  marked with and FM (future modification).  You can test it by sending
#  mail yourself.
#
#  Notes:      This software is in the public domain.  If you received it from
#              unreliable sources, contact the author for a good version
#              (avoid been fool by a TROJAN version!!!).
#
#  Disclaimer: You assume all the risks involved in using it.  My employer has
#              nothing to do with this.
#

#
# put the name of undiserable sender here (e.g., AssH=James.Doe),
# FM: make this a list for multiple undiserable sources.
#
AssH=James.Doe
FrAssH="From $AssH"
#
# put your system mailbox here
#
Spool=/usr/spool/mail/$USER
Mail=/usr/ucb/Mail
Tmp=$HOME/tmp/tmp$$

if (test ! -r $Spool)
then
    echo "You have no messages in your system mailbox."
    exit 1
fi

NumMsg=`grep -c "From " $Spool`
echo "You have $NumMsg message(s) in your system mailbox."
AssMsg=`grep -c "$FrAssH" $Spool`

#
# FM: make this a double loop to eliminate multiple messages from
#     multiple undiserable sources.
#
if (test $AssMsg != 0)
then
    grep "From " $Spool | sed -e 's/From \([^ ]*\) .*/\1 /' > $Tmp
    From=`grep -n "$AssH" $Tmp`
    From=`echo $From | sed -e 's/\(.*\):.*$/\1/'`
    echo "d $From
    echo "Now you have `grep -c \"From \" $Spool` in your mailbox."
    rm -f $Tmp
    exit 0
else
    exit 1O
fi

-----------------------------

From: Alexander Dupuy <dupuy@amsterdam.columbia.EDU>
Subject: Re: Maxwell's deamon
Date: 12 Aug 87 20:11:52 GMT
Sender: nobody@columbia.EDU
Followup-To: comp.unix.questions
To:       info-unix@SEM.BRL.MIL


There was a game (of sorts) for the DMD 5620 (aka Blit) bitmap terminals called
maxwell.  It created a box with two halves, with white and black balls bouncing
around inside.  There was a door between the two.  By clicking on the door you
could open it or shut it.  If you were bored you could play maxwell's daemon,
and get all the black balls on one side, and all the white on the other (unless
you got a court order to desegregate :-).  Another possibility was to get all
the balls on one or the other side.  Oh - the black and white balls moved at
different speeds, and when collisions occurred, balls could change from one
color to the other.  I don't think we have it any more though.

@alex
---
arpanet: dupuy@columbia.edu
uucp:    ...!seismo!columbia!dupuy

-----------------------------

From: Chris Purdom <purdom@rabbit1.uucp>
Subject: Re: spell bug?????
Date: 12 Aug 87 12:47:53 GMT
Keywords: is this in every system?
To:       info-unix@brl-sem.arpa


BSD 4.1 spell also misses the weird words posted earlier.

-----------------------------

From: Robert Claeson <robert@pvab.uucp>
Subject: Re: Negative numbers as expr(1) argument
Date: 12 Aug 87 08:52:10 GMT
To:       info-unix@brl-sem.arpa

In article <3628@ihlpg.ATT.COM> bamford@ihlpg.UUCP (Harold E. Bamford) writes:

>This seems to work for me:
>
>    expr -1 + 10
>
>It replies with "9"
>
>What exactly are you giving to expr?

When I do the same on my Sun, it says "non-numeric argument".
A machine running SVR2.2 says "expr: unknown operation\n-1".
I haven't had a chanse to run it on the 3b2 w/SVR3.1.

-- robert
--
SNAIL:    Robert Claeson, PVAB, P.O. Box 4040, S-171 04 Solna, Sweden
UUCP:    {seismo,mcvax,munnari}!enea!pvab!robert
ARPA:    enea!pvab!robert@seismo.arpa

-----------------------------

From: Patrick Barron <pdb@sei.cmu.EDU>
Subject: Re: Ultrix password ageing - How?
Date: 12 Aug 87 12:46:28 GMT
Sender: netnews@sei.cmu.EDU
Keywords: password expiration dates
To:       info-unix@SEM.BRL.MIL

In article <219@tness1.UUCP> mechjgh@tness1.UUCP (8753) writes:
>Is password ageing implemented in Ultrix-32 ?
>The manuals didn't mention it.


Sorry, password aging doesn't exist in Ultrix (at least, in Ultrix 1.2 and
2.0).

If you're really desparate for it, you can maintain a separate database
of password aging information (system V keeps this info in /etc/passwd,
it probably isn't a good idea to try this with Ultrix), have /bin/passwd
update it every time a user changes their password, and have /bin/login
check it on each login (this of course assumes you have sources).  You'd
also need to write some utility programs to modify minimum/maximum password
ages, etc.

--Pat.

-----------------------------

From: "Carl S. Gutekunst" <csg@pyramid.pyramid.COM>
Subject: Re: How to prevent low-grade uucp work during daytime?
Date: 12 Aug 87 20:46:23 GMT
Keywords: uucico grade time-to-call restrictions
To:       info-unix@brl-sem.arpa

In article <3572@cit-vax.Caltech.Edu> mangler@cit-vax.Caltech.Edu (System
 Mangler) writes:
>How can I tell slave-mode uucico to defer low-grade work during
>those hours?

The intention of grading in 4.3BSD was to keep phone bills down, not to reduce
machine load. Hence, if a machine calls you and isn't picky about grade, then
everything goes.

But you can do what you want: run the slave uucico from a shell script with
the appropriate options. We do this for news all the time. Something like:

    nuucp:xyzzyxyzzyxyz:6:1:UUCP Login:/usr/lib/uucp:/usr/lib/uucp/uugraded

where the file /usr/lib/uucp/uugraded contains

    #!/bin/sh
    exec /usr/lib/uucp/uucico -gc

Of course, the script can be as ellaborate as you like, checking the time and
so on.

One DANGEROUS security hole: if you run a shell script like this, then make
sure that the home directory for the login is *NOT* uucppublic. Otherwise you
will have a world-writable directory from which the shell may look for a login
startup script. (Actually, I believe 4.3BSD /bin/sh will not run .profile if
it is invoked non-interactively as it is here. But /bin/csh definitely runs
its .login and .cshrc scripts. And why take unnecessary chances?)

<csg>

-----------------------------

From: Rick Adams <rick@seismo.CSS.GOV>
Subject: Re: Unix shell script to eliminate mail from sender available.
Date: 12 Aug 87 22:53:12 GMT
To:       info-unix@brl-sem.arpa


Or, if you are using ucbmail or mailx, you can put something like the
following in your .mailrc

d baduser

which will delete all mail form baduser before showing it to you.

---rick

-----------------------------

From: Brown <daveb@geac.uucp>
Subject: Re: red herrings (was spell bug?????)
Date: 12 Aug 87 14:40:21 GMT
To:       info-unix@SEM.BRL.MIL

>In article <944@bsu-cs.UUCP>, dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>> A good way of preserving a copyright on collections of items that
>> individually cannot be copyrighted is to include a few red herrings
>> that could not be there by chance.... Similarly, I've heard that
>> dictionaries include a few authentic-sounding nonsense words that were
>> created by the publisher.

This is also often used on maps, but the technique is subtler: a road
junction is malformed to look (subtely) different than on the
underlying topo maps.  This can, of course, be taken to extremes:  the
tourist map of PEI (Prince Edward Island) contains a number of blatant
lies...
--
 David Collier-Brown.                 |  Computer Science
 Geac Computers International Inc.,   |  loses its memory
 350 Steelcase Road,Markham, Ontario, |  (if not its mind)
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.

-----------------------------

From: Cathy Accettura <cathy@larry.uucp>
Subject: Init not running gettys
Date: 12 Aug 87 21:04:20 GMT
Keywords: login getty init
To:       info-unix@brl-sem.arpa

Here is a strange one for you.  We just finished reconfiguring
our systems in order to add a new disk drive.  We are running
Ultrix 1.2 on a uVax II.  The root partion was moved from one
disk to another so the answer to the problem might be very
obvious.

The problem is there are no gettys running on any of the terminals.
We can log onto the system with no problem over the ethernet.
We have checked the permissions on /dev and all the  terminals.
ps shows that init is running.

If you have any ideas (even silly and obvious ones) please
share them with me.   THANKS IN ADVANCE.
 --------
cathy@larry.sal.wisc.edu

-----------------------------

From: Randy Orrison <randy@umn-cs.uucp>
Subject: Re: spell bug?????
Date: 11 Aug 87 04:39:00 GMT
Keywords: is this in every system?
Posted: Mon Aug 10 23:39:00 1987
To:       info-unix@SEM.BRL.MIL

In article <541@augusta.UUCP>, bs@augusta.UUCP (Burch Seymour) writes:
> Three of the words which are passed through by spell are:
>  vfppvdu, plbpvhb, and nbclowd
> Is this a known problem? Do these words pass on all unix systems?

They all pass with flying colors on this Vax 11/780 running (i think) vanilla
4.3BSD.  Couldn't it just be a simple matter of a hash collision?
--
Randy Orrison, University of Minnesota School of Mathematics
UUCP:    {ihnp4, seismo!rutgers!umnd-cs, sun}!umn-cs!randy
ARPA:    randy@ux.acss.umn.edu         (Yes, these are three
BITNET:    randy@umnacvx             different machines)

-----------------------------

From: Jon Reeves <reeves@decvax.uucp>
Subject: Re: spell bug?????
Date: 13 Aug 87 00:22:32 GMT
Keywords: spell
Posted: Wed Aug 12 20:22:32 1987
To:       info-unix@SEM.BRL.MIL

In article <1262@sol.ARPA> ken@cs.rochester.edu (Ken Yap) writes:
>Nobody has mentioned the possibility that the words in question fell
>through spell's probabilistic detection algorithm.

This is, indeed, what happened.  Ken's description was mostly correct
(except the magic number is 11) for BSD systems.  Even with proper
tuning, the algorithm still has a 1-in-2048 chance of generating a false
match.  As an example, "nbclowd" collides with:

chloroplatinate, telephone/vulnerable, nonogenarian/polarography, crocus,
gummy, irremovable, kingpin, lucre/tangential, alma, whirligig, Curran.
(Where two words are separated by a slash, both collide with the same
hash value.)

On a BSD-derived system, the best way to check for nonsense strings is
to use match (or grep, or comm) against /usr/dict/words.  Spell is
designed for catching typos.

System V uses a completely different algorithm that can't generate this
kind of false matches.
--
Jon Reeves    decvax!reeves -or- reeves@decvax.dec.com
"[T]he use of the binary system in the machine is a passing phase ..."
 - Douglas Hartree, University of Cambridge, 1949.

-----------------------------

From: Bruce McLaughlin <bruce@chas2.uucp>
Subject: Re: lp spool system query
Date: 12 Aug 87 21:31:22 GMT
Keywords: lpr spool lock
To:       info-unix@SEM.BRL.MIL

In article <374@mrecvax.UUCP> tron@mrecvax.UUCP (Carlos Mendioroz) writes:
>I 'm running ULTRIX 1.2 on a uVax and have a pair of printers connected
>to the same port (a tty line) via an inteligent switch.
>The problem is how to tell lpd that both printers share the same tty line
>and so, he shouldn't try to write both at the same time.
>I 've tried using the same spool directory but that didn't work.

I'm having the same trouble with a set of Sun 3/50's nfs'd together and
sharing 4 printers (2 Epsons, 2 HP LJ+) off of two of the Sun serial ports.
We are trying to go through a set of "smart" boxes (The Logical Connection).

I found some filters in mod.sources Volume 3 for the laser printers, and am
now getting things other than garbage to print, but trying to get...

    Sun-A to spool things on Sun-B to printer-C while
    Sun-C spools to printer-D  while
    Sun-D spools to Sun-C for printer-A ..... etc.

Needless to say, the contention is not working out well.
Help, please????

     ... cit-vax!elroy!jplgodo!chas2!bruce

  --Bruce McLaughlin          Jet Propulsion Laboratory
                              4800 Oak Grove Drive, M/S 301/250D
                              Pasadena, California, 91109

     "Wisdom suffers only when Triumph meets Conviction"

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster%FINFUN.BITNET@WISCVM.WISC.EDU (PMDF Mail Server) (10/09/87)

The message could not be delivered to:

Addressee: pietilainen
Reason: %MAIL-E-NOSUCHUSR, no such user PIETILAINEN at node OPMVAX

----------------------------------------

Received: from FINFUN.BITNET by OPMVAX.KPO.FI; Fri, 9 Oct 87 12:14 N
Received: From WISCVM(SMTP) by FINFUN with RSCS id 7810          for
 PIETILAI@FINFUN; Fri,  9 Oct 87 12:14 O
Received: from SEM.BRL.MIL by WISCVM.WISC.EDU ; Fri, 09 Oct 87 03:27:05 CDT
Received: by SEM.BRL.ARPA id ab07669; 7 Oct 87 3:27 EDT
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab07553; 7 Oct 87 3:00 EDT
Received: from sem.brl.mil by SEM.BRL.ARPA id aa07515; 7 Oct 87 2:45 EDT
Date: Wed, 07 Oct 87 02:45:33 EST
From: The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#037
To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Message-ID:  <8710070245.aa07515@SEM.BRL.ARPA>

INFO-UNIX Digest          Wed, 07 Oct 1987              V4#037

Today's Topics:
        Re: Looking for a high-quality digital voice synthesiser
                            Re: VI questions
                       Re: question about signal
-----------------------------------------------------------------

From: apn@nonvon.uucp
Subject: Re: Looking for a high-quality digital voice synthesiser
Date: 3 Oct 87 16:35:42 GMT
To:       info-unix@SEM.BRL.MIL

 ------------

Whatson used to have an 800 number for demo purposes, and... I found thier
product acceptable, but not as good as something that Vynet has.
I'm not sure, though, if Vynet is currently offering it for sale as a stand-
alone card for PC's or Unix or whatever...

The Person to contact ( I don't know Vynets number, but this is the
                        individual who is responsible for most of the
                development of this product )

This product is currently in use in multiline IAS systems throughout the USA

Durand Interstellar
(408) 356 3886


Good Luck, Dr Phelps,

Alex P Novickis
(707) 575 9616

--
UUCP: {ihnp4,ames,qantel,sun,amdahl,lll-crg,pyramid}!ptsfa!nonvon!apn

{* Only those who attempt the absurd   ...   will achieve the impossible   *}
{* I think... I think it's in my basement... Let me go upstairs and check. *}
{*                                                      -escher            *}
--
UUCP: {ihnp4,ames,qantel,sun,amdahl,lll-crg,pyramid}!ptsfa!nonvon!apn

{* Only those who attempt the absurd   ...   will achieve the impossible   *}
{* I think... I think it's in my basement... Let me go upstairs and check. *}
{*                                                      -escher            *}

-----------------------------

From: Karel van Houten <karel@dutesta.uucp>
Subject: Re: VI questions
Date: 5 Oct 87 08:08:29 GMT
Keywords: VI, Bells
To:       info-unix@SEM.BRL.MIL

In article <3050@uwmcsd1.UUCP> zhao@csd4.milw.wisc.edu.UUCP (T.C. Zhao) writes:
>
>2. I remember a while back someone mentioned ' visual bells' in Vi,
>that is instead of a bell the screen flashes should an error occur.
>Can someone tell me how to do this ?

This has to be defined in the TERMCAP (file or environment variable).
Below is my entry for a CIT101 terminal. When you want to put
these commands in a file, don't forget you must use 'source file...',
otherwise the environment of the subshell will be set only.
Please note the 'vb' entry, This will reverse the screen, send some NULLs,
and reverse it again.

setenv TERM cit101n
setenv TERMCAP 'd1|cit101n:al=\E[L:\
    :am:bs:cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:co#80:\
    :cs=\E[%i%d;%dr:dc=\E[P:dl=\E[M:ei=:ic=\E[@:im=:kd=\E[B:\
    :kl=\E[D:kr=\E[C:ku=\E[A:li#24:nd=\E[C:pt:se=\E[m:so=\E[1m:\
    :ue=\E[m:up=\E[A:us=\E[4m:\
    :vb=\E[?5h\200\200\200\200\200\200\200\200\200\200\200\200\E[?5l:\
    :xn:xv:k0=\EOP:k1=\EOQ:k2=\EOR:k3=\EOS:k4=\EOw:k5=\EOx:k6=\EOy:\
    :k7=\EOm:k8=\EOt:k9=\EOu:l0=PF1:l1=PF2:l2=PF3:l3=PF4:sf=\ED:\
    :sr=\EM:vs=\E[5v\E\=:ve=\E[4v\E>'

--
Karel van Houten                       BITNET   : NO! NO! NO!
Delft University of Technology         INTERNET : karel@dutesta.UUCP
Faculty of Electrical Engineering      UUCP     : ..!mcvax!dutrun!dutesta!karel
Room 9.29H, Mekelweg 4                 SURFnet  : DUTRUN::KAREL
2628 CD  DELFT, The Netherlands        VOICE    : +31 15 783502

-----------------------------

From: "John Woods, Software" <john@frog.uucp>
Subject: Re: question about signal
Date: 5 Oct 87 22:56:00 GMT
To:       info-unix@SEM.BRL.MIL

In article <4248@udenva.UUCP>, rneitzel@udenva.UUCP (RICHARD NEITZEL ) writes:
> In article <720001@hpclmar.HP.COM> mar@hpclmar.HP.COM (Michelle Ruscetta)
 writes:
> > Question about signal():
> >  Should the return from a signal handling routine specified by a call
> >  to signal() go to the instruction which caused the signal, or to the
> >  instruction immediately following that which caused the signal?
> >  void (*p_my_handler)();
> >  main()
> >  {
> >     extern void my_handler();
> >     int y = 0;
> >     int x = 3;
> >     p_my_handler = my_handler:
> >     signal(SIGFPE, p_my_handler);
> >     x = x/y;              /* should my_handler return to here? */
> >     printf("return from signal\n");  /* or to here? */
> >  }
>
I would argue that the signal should return to the instruction causing the
problem, if it returns at all.  Presumably, your handler will either fix
up the problem to allow the instruction to complete correctly (e.g., it
would determine that one of the arguments is 0.0, print a message, stuff a
1.0 into the register or temporary, and return), it would bypass the
effects of the instruction and advance the program counter that will be
returned to (e.g., it prints a message, stores an IEEE infinity into the
result of the instruction (register, memory location, whatever), bumps the
PC, and returns), or it prints out an error message, maybe a stack backtrace,
and craps out again with a core dump.

Note that two of these aren't portable things.  Furthermore, they may become
impossible in processors with separate, asynchronous, floating point units
(e.g. the venerable PDP-11), or with lots of internal pipelining:  how does
one "properly" re-do

    divf    fr0,fr1
    inc    r0
    addf    fr1,fr2

if the divf gets an exception AFTER the 'inc r0' has executed?

In short, it is probably easiest to offer to repair damage from an exception
if the exception handler is told which instruction faulted and is allowed
to return to it, but in the *general* case the only useful thing a signal
handler can do in this case is:

my_FPE_handler() {
    fprintf(stderr,"Ah, geez, a floating point exception happened!\n");
    abort();
}

--
John Woods, Charles River Data Systems, Framingham MA, (617) 626-1101
 ...!decvax!frog!john, ...!mit-eddie!jfw, jfw@eddie.mit.edu

"Cutting the space budget really restores my faith in humanity.  It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation."
        -- Johnny Hart

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster%FINFUN.BITNET@WISCVM.WISC.EDU (PMDF Mail Server) (10/10/87)

The message could not be delivered to:

Addressee: pietilainen
Reason:
  %MAIL-E-NOSUCHUSR, no such user PIETILAINEN at node OPMVAX

----------------------------------------

Received: from FINFUN.BITNET by OPMVAX.KPO.FI; Sat, 10 Oct 87 03:10 O
Received: From WISCVM(SMTP) by FINFUN with RSCS id 4582 for PIETILAI@FINFUN;
 Sat, 10 Oct 87 03:10 O
Received: from SEM.BRL.MIL by WISCVM.WISC.EDU ; Fri, 09 Oct 87 10:39:57 CDT
Received: by SEM.BRL.ARPA id ab21070; 29 Sep 87 4:46 EDT
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab20790; 29 Sep 87 2:52 EDT
Received: from sem.brl.mil by SEM.BRL.ARPA id aa20763; 29 Sep 87 2:46 EDT
Date: Tue, 29 Sep 87 02:46:04 EST
From: The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#029
To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Message-ID:  <8709290246.aa20763@SEM.BRL.ARPA>

INFO-UNIX Digest          Tue, 29 Sep 1987              V4#029

Today's Topics:
                      mounting forms on lp ??????
                     Pascal to C translator wanted
                            Re: tty watcher
                  Re: SysV lp spooler a security hole
                   Re: Using subdirectories from make
                          CSI Tape for 3B2/400
                         question about signal
                 Re: Re: Re: History (origin of foobar)
                      Re: Invisible Ascii with VI
                       Re: question about signal
     Need getting Kermit or Xmodem going between SUNos and APPLE II
-----------------------------------------------------------------

From: "Donald D. Woelz" <don@grc.uucp>
Subject: mounting forms on lp ??????
Date: 24 Sep 87 20:46:23 GMT
To:       info-unix@brl-sem.arpa

I am using System V.2.2 on a NSC32032 based system.

I have a printer connected via serial rs232 port.  I want to be
able to mount different forms on the printer for various reports
(such as mailing labels, invoices, etc.).

What do I need to do to the interface shell script, or any other program
(I have only binaries for all but the interface program) to
accommodate changing forms without other reports in the print
queue printing on those forms, and vice-versa?

I am in desperate need of a quick solution.  Your collective
help would be much appreciated.

Thanks
*******************************************************
Don Woelz
GENROCO, Inc.
{seismo?, ames, rutgers, harvard}!uwvax!uwmcsd1!grc!don
*******************************************************

-----------------------------

From: Duke Robillard <rgr@m10ux.uucp>
Subject: Pascal to C translator wanted
Date: 24 Sep 87 21:21:01 GMT
To:       info-unix@SEM.BRL.MIL




We have some Pascal code (about 12,000 lines) that we wish were
C (so we could have the same source for Suns, VAX/UNIX, Amdahl/UTS,
and Cray machines).  I understand HCR Corp. has a Pascal compiler
that translates to C first and then compiles the C.  Has anyone used
this product to translate Pascal to maintainable C?  Has anyone used
anything else to translate Pascal to maintainable C?
--
  +-------------------------------------------------------------------+
  |          Duke Robillard                {ihnp4!}m10ux!rgr          |
  |              Disclaimer:  I claim to live in Dis.                 |
  +-------------------------------------------------------------------+

-----------------------------

From: Peter da Silva <peter@sugar.uucp>
Subject: Re: tty watcher
Date: 25 Sep 87 04:06:25 GMT
To:       info-unix@SEM.BRL.MIL

In article <1431@cognos.UUCP>, brianc@cognos.uucp (Brian Campbell) writes:
> ! <...an effective tty watcher or "spy" program,
> ! <Looks like MS-DOS wins this round.
> ! When did MS-DOS start supporting multiple users so that such a thing
> ! would make sense?
>    Well, although the posted message didn't specifically mention it, the
> original question related to watching what callers were doing on a BBS.
> I guess MS-DOS just might have won this round.

You can, of course, do the same thing on UNIX (watch what people are doing
on a BBS), exactly the same way (have the BBS program echo stuff). I've seen
two systems that do it (one of which not only traps the characters, but talks
to called processes via pipes so you can have other programs do mail, etc,
and have them echoed too).
--
-- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter
--                 'U`  Have you hugged your wolf today?
-- Disclaimer: These aren't mere opinions... these are *values*.

-----------------------------

From: "Michael C. De Masi" <demasi@paisano.uucp>
Subject: Re: SysV lp spooler a security hole
Date: 24 Sep 87 17:45:48 GMT
To:       info-unix@brl-sem.arpa

In article <484@riddle.UUCP>, domo@riddle.UUCP (Dominic Dunlop) writes:
  ...
>
> Incidentally, it occurs to me that the only reason that
>
>     lp < file
>
> gets around the problem is because of a security hole in the UNIX kernel.
> Were access rights checked on every read, rather than just when the file is
> opened, a setuid program would be unable to read a file with restricted
> permissions, even if it had been opened and attached to stdin by a shell
> which was able to read it.
  ...
> Dominic Dunlop
> domo@riddle.uucp  domo@sphinx.co.uk

How can this be considered a security hole?  When redirecting standard
input from a file into a program, setuig-gid or not, one still has to
have the proper permissions to read the file that's being redirected.
That is, if you can't read the file, you can't redirect it as input
to another program, anyway, so what's the problem?  If I'm reading
what you wrote correctly, every utility within UNIX would have to
have the same ownership (effectively) as every file on which it is
to work.  You can't mean that, can you?

By the same token, what you say is true, permissions are only
checked at the time a file is opened.  But all that amounts to is
that if you are reading from (or writing to) one of my files, and
within the course of your process I change the permissions on that
file in such a way as to make it inaccessable to you, it will have
no effect on your process (unless you close the file, for some rea-
son, then try to re-open it) but again, what's the big deal?  If
you wish to maintain a file with restricted access, create it that
way.

As I said, perhaps I misunderstand you, if so, please point
out my error (Nothing like a good argument, huh?)
--
Michael C. De Masi - AT&T Communications (For whom I work and not speak)
3702 Pender Drive, Fairfax, Virginia 22030   Phone: 703-246-9555
UUCP:   seismo!decuac!grebyn!paisano!demasi
     "There are monkey boys on the premises."  Unknown red Lectroid.

-----------------------------

From: Wallis <snafu@ihlpm.ATT.COM>
Subject: Re: Using subdirectories from make
Date: 25 Sep 87 13:31:05 GMT
To:       info-unix@brl-sem.arpa

In article <204@tut.cis.ohio-state.edu>, mdf@tut.cis.ohio-state.edu (Mark D.
 Freeman) writes:
> In <831@ektools.UUCP> jim@ektools.UUCP (James Hugh Moore) writes:
> >Basically, he has asked me if
> >there is a way of keeping source in one directory and objects in another and
> >using one makefile.
>
> >we would like to specify paths from a common directory, and have different
> >directories for source, objects, special testing software, etc.
>
> I am in need of similar advice.  I want:
>
> /foo = sources
> /foo/reg = objects
> /foo/special = objects created with certain #defines the regular ones
>         don't have.
>
> just doesn't hack it.   Yes, I'm doing some things under MSDOS...

On UNIX, the following should work. I'll base the example on the following
directory structure (which I think is a little more common than the one
above.

            proj
                        ||||
     ------------------- || --------------
     |            -------||------        |
     |            |             |        |
    bin        include         obj      src

Also, assume theat the makefile is in the 'src' directory.
----
# BASE == the root directory of the project
BASE = ..

SOURCE_DIR = $(BASE)/src
INC_DIR = $(BASE)/include
OBJ_DIR = $(BASE)/obj
BIN_DIR = $(BASE)/bin

PRODUCT = foobar

CFLAGS = -c -I$(INC_DIR)
LDFLAGS = -s
SPEC_DEFS = -DJUNK=boffo

OBJ_FILES = $(OBJ_DIR)/foo.o \
            $(OBJ_DIR)/bar.o

$(PRODUCT): $(OBJ_FILES)
        $(CC) $(LDFLAGS) -o $(PRODUCT) $(OBJ_FILES)

$(OBJ_DIR)/foo.o: $(SRC_DIR)/foo.c $(INC_DIR)/hdr.h
        $(CC) $(CFLAGS) $(SRC_DIR)/bar.c

$(OBJ_DIR)/bar.o: $(SRC_DIR)/bar.c $(INC_DIR)/hdr.h
        $(CC) $(CFLAGS) $(SPEC_DEFS) $(SRC_DIR)/bar.c
 -----
Whether or not these types of constructs work under MS-DOS depends
on whose 'make' command you are using. I have one version of make
that is almost totally compatible with unix make, and another that
would not handle this at all.

Note that the same techniques used above can be used with multiple
source or object directories. If you need to be able to build multiple
versions of a particular object with different #defines, try the following:

$(OBJ_DIR_A)/foo.o: $(SRC_DIR)/foo.c $(INC_DIR)/hdr.h
        $(CC) $(CFLAGS) $(SPEC_DEFS_1) $(SRC_DIR)/bar.c

$(OBJ_DIR_B)/foo.o: $(SRC_DIR)/foo.c $(INC_DIR)/hdr.h
        $(CC) $(CFLAGS) $(SPEC_DEFS_2) $(SRC_DIR)/bar.c

$(PRODUCT_1): $(OBJ_FILES_1)
        $(CC) $(LDFLAGS) -o $(PRODUCT_1) $(OBJ_FILES_1)

$(PRODUCT_2): $(OBJ_FILES_2)
        $(CC) $(LDFLAGS) -o $(PRODUCT_2) $(OBJ_FILES_2)

Hope this helps. Let me kow if I confused you more than ever!




                              Dave Wallis
                           ihnp4!ihlpm!snafu
                       AT&T Network Systems, Inc.
                            (312) 510-6238

-----------------------------

From: Yasuki Izaki <ysk@pbhyf.uucp>
Subject: CSI Tape for 3B2/400
Date: 25 Sep 87 18:20:26 GMT
Keywords: SCSI Tape
To:       info-unix@brl-sem.arpa

Does anyone out there know about SCSI Tape Drive board from Feith Systems?
They just announced this product a month ago(I think). We are considering
purchasing it. We'd like to know how it works in terms of the performance.
Any inputs will be appreciated. Thanks in advance.

Yasuki Izaki
Work     : (415) 867-5073
Work UUCP: {ihnp4|ptsfa}!pbhyf!ysk
--
Yasuki Izaki          {ihnp4,pyramid,qantel}!ptsfa!pbhye!ysk
(415) 867-5073

-----------------------------

From: Michelle Ruscetta <mar@hpclmar.HP.COM>
Subject: question about signal
Date: 25 Sep 87 02:54:19 GMT
To:       info-unix@brl-sem.arpa


 Question about signal():

  Should the return from a signal handling routine specified by a call
  to signal() go to the instruction which caused the signal, or to the
  instruction immediately following that which caused the signal?

  For example:

  void (*p_my_handler)();

  main()
  {
     extern void my_handler();
     int y = 0;
     int x = 3;
     p_my_handler = my_handler:
     signal(SIGFPE, p_my_handler);
     x = x/y;                   /* should my_handler return to here? */
     printf("return from signal\n");  /* or should my_handler return to here? */
  }

  void my_handler()
  {
     signal(SIGFPE, SIG_IGN);
     /* do something useful */
     signal(SIGFPE, p_my_handler);
  }


 ---------------------------

  I have run this example on two different machines, with different results;
  (both were running implementations of System V) one returned to the statement
  following that which cause the signal (the printf), and the other returned
  to the instruction which caused the signal -- hence throwing the program
  into an infinite loop continuously executing x/y and catching the floating
  point exception.

  I know it is not very good practice to return from signal-handlers
  but this question came up in a discussion and I would be interested to
  hear opinions as to which is the 'correct' way for signal to handle this.

-----------------------------

From: Dave Decot <decot@hpisod2.HP.COM>
Subject: Re: Re: Re: History (origin of foobar)
Date: 25 Sep 87 04:41:33 GMT
To:       info-unix@brl-sem.arpa

This is not related to UNIX.

See mod.announce.newusers, including you oldusers who should know better.

Dave

-----------------------------

From: "Paul Sutcliffe Jr." <paul@devon.uucp>
Subject: Re: Invisible Ascii with VI
Date: 28 Sep 87 04:03:36 GMT
Keywords: vi
To:       info-unix@SEM.BRL.MIL

In article <258@unx1.UUCP> andy@unx1.UUCP (Andy Clews) writes:
> Specifically: I sometimes get files from a net source that have an "extra"
> CR tacked on the end of the line, and VI shows them as ^M on the screen.
> For various reasons these are a pain. I'd like to be able to get rid of
> them with, say, a global substitute. I've tried 1,$s/^V^M$// but this
> does not seem to do what I want.
> I'd appreciate email replies if any.

I thought this reply might be of general interest, so I'm posting it.

Your "1,$s/^V^M$//" didn't work because the search pattern didn't match
anything in your text file.  You asked vi to find all lines where the
character just before the end of line ($) was a carriage-return.  This
pattern will not match because the lines in your text were terminated
by a CR/LF pair, so there was a line-feed between the "^M" and the "$".

A better way to do this would have been "1,$s/^V^M//".  This would replace
all occurrances of ^M with nothing.  You don't need an end-of-line indicator
as there are (should be) no other ^M's in the text.

- paul

--
Paul Sutcliffe, Jr.

UUCP (smart):  paul@devon.UUCP
UUCP (dumb):   ...{rutgers,ihnp4,cbosgd}!bpa!vu-vlsi!devon!paul

-----------------------------

From: Chris Torek <chris@mimsy.uucp>
Subject: Re: Invisible Ascii with VI
Date: 28 Sep 87 13:31:47 GMT
Keywords: vi
To:       info-unix@SEM.BRL.MIL

In article <469@devon.UUCP> paul@devon.UUCP (Paul Sutcliffe Jr.) writes:
>Your "1,$s/^V^M$//" didn't work because the search pattern didn't match
>anything in your text file.  You asked vi to find all lines where the
>character just before the end of line ($) was a carriage-return.  This
>pattern will not match because the lines in your text were terminated
>by a CR/LF pair, so there was a line-feed between the "^M" and the "$".

Nope.

A linefeed is a Unix newline; CR-LF pairs form a literal control-M
followed by a newline.  vi breaks a file apart at newlines (so as
to create a series of lines), and, internally, does not carry around
the newlines (linefeeds) at all.  There is no line-feed between the
^M and the $-end-of-line, and in fact, typing the characters

    : % s / ^V ^M $ / /

works fine for me.

Of course, this could be a bug in other versions of vi.  (At this
very moment, I am running `Version 3.7, 6/7/85'---so says `:ver'.)

(Going the *other* way---adding ^Ms---is another matter entirely.)
--
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:    chris@mimsy.umd.edu    Path:    uunet!mimsy!chris

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: question about signal
Date: 28 Sep 87 19:32:32 GMT
To:       info-unix@SEM.BRL.MIL

In article <720001@hpclmar.HP.COM> mar@hpclmar.HP.COM (Michelle Ruscetta)
 writes:
>  Should the return from a signal handling routine specified by a call
>  to signal() go to the instruction which caused the signal, or to the
>  instruction immediately following that which caused the signal?

If it's an asynchronous trap, it should complete the interrupted
instruction sequence.  If it's a synchronous trap (e.g. SIGFPE),
there is no "right" answer.  Presumably the synchronous exception
occurred because some machine operation had invalid operands;
unless you can be sure that the signal handler has fixed the
operands (which is almost never the case, due to code optimization
etc.), retrying the faulting instruction would just cause another
trap.

Portable, robust programs should not just return from a SIGFPE
handler.

-----------------------------

From: Peter Klosky <peter@citcom.uucp>
Subject: Need getting Kermit or Xmodem going between SUNos and APPLE II
Date: 25 Sep 87 20:17:02 GMT
Keywords: kermit modem xmodem Sun Apple smartterm emulator
To:       info-unix@brl-sem.arpa

We are trying to get an Apple II one of our people has at home to
send files over the phone to our Sun network running 3.2 Sunos.
We need to get kermit or xmodem going, we suppose.  It does not
look like the Sun comes with a communications protocol like
xmodem or kermit; does anyone know if it perhaps hidden in some
directory we've never seen or on some tape we have not read?
We don't think we can get uucp g protocol going on the Apple.
Has anyone heard of Smartterm, a Hayes product to run on the
Apple?  What protocols does it run?  What would you suggest we
do to get these two machines talking?   To retransmit our request,
let us say again we need retransmission in case of line noise.
--
Peter Klosky, Citcom Systems (materiel de telecommunications)
seismo!vrdxhq!baskin!citcom!peter (703) 689-2800 x 235

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster%FINFUN.BITNET@WISCVM.WISC.EDU (PMDF Mail Server) (10/10/87)

The message could not be delivered to:

Addressee: pietilainen
Reason:
  %MAIL-E-NOSUCHUSR, no such user PIETILAINEN at node OPMVAX

----------------------------------------

Received: from FINFUN.BITNET by OPMVAX.KPO.FI; Sat, 10 Oct 87 21:43 O
Received: From WISCVM(SMTP) by FINFUN with RSCS id 4666 for PIETILAI@FINFUN;
 Sat, 10 Oct 87 21:43 O
Received: from SEM.BRL.MIL by WISCVM.WISC.EDU ; Sat, 10 Oct 87 14:22:28 CDT
Received: by SEM.BRL.ARPA id ab04419; 30 Sep 87 6:54 EDT
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab03529; 30 Sep 87 3:02 EDT
Received: from sem.brl.mil by SEM.BRL.ARPA id aa03505; 30 Sep 87 2:45 EDT
Date: Wed, 30 Sep 87 02:45:40 EST
From: The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#030
To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Message-ID:  <8709300245.aa03505@SEM.BRL.ARPA>

INFO-UNIX Digest          Wed, 30 Sep 1987              V4#030

Today's Topics:
        Re: Looking for a high-quality digital voice synthesiser
                                Re: AWK
                    Re: Info about ratfor and/or efl
                                 Eyacc
                        Invisible Ascii with VI
                    Exclusive file creation and NFS.
           csh environment variables and special commands...
             variables set in sh while loop don't get set?
                     ps -s /dev/null kills system?
-----------------------------------------------------------------

From: Greg Hackney <jgh@killer.uucp>
Subject: Re: Looking for a high-quality digital voice synthesiser
Date: 25 Sep 87 18:01:19 GMT
To:       info-unix@brl-sem.arpa

In article <2138@pbhyf.UUCP>, tlh@pbhyf.UUCP (Lee Hounshell) writes:
    >I'm looking for a high-quality digital voice box that can be
    >used with any System V Unix machine..  through an RS-232 interface.
     >Lee Hounshell - ptsfa!pbhyf!tlh 2600 Camino Ramon, #4E700
     >415-823-2432   San Ramon, CA. 94583

You might look at Digital Equipment Corporations DecTalk Model DT-01
voice synthesizer. We have 3 of them that are used for calling in
to get voice mail on System 5 Unix machines.

There are several standard male and female voices, or you can
design your own. The input is RS232 plain old ascii text, or
you can input phonetically.

DecTalk has an internal speaker, and an external speaker jack. It also
has jacks to attach to a Touch-Tone phone line. It can answer the line,
prompt for touch tone responses, etc. It can also originate a call
and prompt for responses under computer control.

The manual gives examples of C programs necessary to drive
the interactive calls. Or, you can plug a dumb terminal into it
and just type sentences for fun.

Price...I think around $2,500.

I wrote some C programs that interface the standard unix mail
files so users can get their mail via the phone from home, but
I have always toyed with the idea of hooking one to a home alarm
system via a PC, you know, something like, "Greg! There is a car
coming up the driveway". I can hardly wait for the voice recognition
technology to be better developed.

--
Greg Hackney
Southwestern Bell Telephone Co.
ihnp4!killer!jgh

-----------------------------

From: Guy Harris <guy%gorodish@Sun.COM>
Subject: Re: AWK
Date: 26 Sep 87 04:32:11 GMT
Sender: news@sun.uucp
Keywords: awk, unix S5R3.1, 4.3BSD
To:       info-unix@brl-sem.arpa

> Does anyone know what the new features are in this "latest" version
> of awk ??  For example, are functions included ??
> It gets frustrating to keep encountering all of awk's new features
> in the CACM's "Programming Pearls" column, but not be able to get
> hold of the program !!

If you have the requisite 1) money and 2) source license, you need suffer no
more; the new "awk" is, indeed, the one used by Bentley and does have
functions, along with some new built-in functions and variables.  It also
supports 8-bit characters.

It is *not*, however, 100% compatible with the old "awk".  The S5R3.1 release
notes list these incompatibilites.  The new "awk" is "nawk" in S5R3.1; "awk" is
still the old one.  According to the release notes, in the next major S5
release the new "awk" will become "awk" and the old one will be renamed "oawk".

> Also, Guy Harris noted about a week ago that the version of awk
> supplied with S5R2 was "faster" than the 4.3 BSD version, so I went
> ahead and compiled the S5 version on our BSD VAX.

You may want to apply some of the bug fixes made in the 4.3BSD version to the
S5R2 version.  I'm reposting a list of bug fixes to the S5R2 version to
"comp.bugs.sys5"; they include those fixes, as well as some
null-pointer-dereference fixes.  I think the new "awk" has all those fixes.

> The S5 version turned out to be almost 3 times faster for a simple program
> (print $1) and 30% faster for a long (200 line) awk script.

Unfortunately, the new "awk" loses some of that speed advantage, at least in
the tests I ran.
    Guy Harris
    {ihnp4, decvax, seismo, decwrl, ...}!sun!guy
    guy@sun.com

-----------------------------

From: Patrick Pesch <pat@seradg.Dayton.NCR.COM>
Subject: Re: Info about ratfor and/or efl
Date: 26 Sep 87 01:34:57 GMT
Keywords: f77 preprocessors structure
To:       info-unix@SEM.BRL.MIL

In article <12@vanvleck.MATH.WISC.EDU> kailhofe@vanvleck.MATH.WISC.EDU
(kailhofe) writes:
>I'm looking for information about the two fortran preprocessors efl(1) and
>ratfor(1), preferring info about efl.  All I have are the man pages,
>which, as always, could use a bit of fleshing out.
>

Sorry, no efl info... BUT

    I think ratfor is used/discussed in the "Software Tools" by Kernighan
    and Plaugher(sp?).  If I remember correctly, a ratfor pre-processor
    implementation is given in the book.

            Pat Pesch
            NCR Corporation

-----------------------------

From: Stefan Olausson <olausson@chalmers.uucp>
Subject: Eyacc
Date: 24 Sep 87 13:04:32 GMT
To:       info-unix@brl-sem.arpa

Does anyone have documentation (or pointer to documentation) for "eyacc"?
Eyacc  is an enhanced version of yacc that comes with Berkeley's Pascal
distribution, which supports error recovery etc.

Please respond by e-mail.

  Stefan Olausson
=========================================================================
  UUCP: {seismo,philabs,decvax}!mcvax!enea!chalmers!olausson
  CSnet: olausson@chalmers.csnet
  Mail: Informations-behandling, Chalmers University,
        S-412 96 Goteborg, SWEDEN

-----------------------------

From: Andy Clews <andy@unx1.uucp>
Subject: Invisible Ascii with VI
Date: 23 Sep 87 13:30:37 GMT
To:       info-unix@SEM.BRL.MIL

Does anyone out there know if it's possible to insert/search/replace
non-printing ascii characters?
Specifically: I sometimes get files from a net source that have an "extra"
CR tacked on the end of the line, and VI shows them as ^M on the screen.
For various reasons these are a pain. I'd like to be able to get rid of
them with, say, a global substitute. I've tried 1,$s/^V^M$// but this
does not seem to do what I want.
I'd appreciate email replies if any.

Andy Clews
andy@uk.ac.sussex.unx1

-----------------------------

From: John Sperbeck <sperbeck@mipos3.intel.COM>
Subject: Exclusive file creation and NFS.
Date: 25 Sep 87 15:33:28 GMT
Keywords: NFS exclusive file creation
To:       info-unix@SEM.BRL.MIL



Does NFS support exclusive file creation?  That is, does the call:

    fd = open("t.tmp", O_CREAT | O_EXCL)

always fail if t.tmp already exists on an NFS file system?

I have heard from two people that it usually works, but there is
a race condition that can occur if two client processes try to
do the open on the same non-existent file.  When the server does
the work of creating the file, both client processes receive a
message that the file was created successfully.

Can this really happen?  I ask because we have /usr/spool/mail
mounted on many machines and I am under the impression that
the programs that read and deliver mail use the exclusive file
creation for locking.

By the way, the machines I am dealing with right now are Ultrix 2.0,
but I would be interested in whether or not other implementations
of NFS have the same problem.

--
John Sperbeck
 ...{hplabs|decwrl|amdcad|qantel|oliveb}!intelca!mipos3!sperbeck

-----------------------------

From: Rob DeMarco <robertd@ncoast.uucp>
Subject: csh environment variables and special commands...
Date: 26 Sep 87 15:14:28 GMT
To:       info-unix@brl-sem.arpa


    Hello, I am looking for some CSH
environmental variables and SPECIAL csh
commands. That is, i'm not interested
in "if" commands, but special commands
like "rehash" and environmental
variables like "ignoreof".

    Thanks,
        [> Rd
--
North Coast Computer Resources(ncoast) - 216-781-6201 (or 781-6202)

UUCP:decvax!mandrill!ncoast!robertd

Sysop: NEODG (login "sbbs")

-----------------------------

From: Thomas Mellman <mellman@ttrdd.uucp>
Subject: variables set in sh while loop don't get set?
Date: 24 Sep 87 15:22:46 GMT
Keywords: sh, ksh scripts, loops
To:       info-unix@SEM.BRL.MIL

When I set a variable in a while loop in a sh script, in some scripts
it doesn't seem to get set.  For example, a common thing is to do a

    pipeline | while read proc
    do

and then to test for some condition in a case statement.  Twice now, I
have written scripts where a variable set in the case loop (or anywhere
in the while loop, for that matter) won't have been changed from its
initial value after the while loop terminates.  Can anyone explain to me
why this is so.

For example, I have a little script that will log me off of my 630 terminal
by nohup-ing the login process - as long as only insignificant processes
are still running:

#
# This script will shutdown my account
#

PATH=$HOME/bin:/bin:/usr/bin:/usr/lbin
options="xd"
arglist=""
optlist=""

set -- `getopt $options $*`
if [ $? != 0 ]; then
    echo "Usage: $0 [$options]"
    exit -1
fi

for arg in $*; do
    case $arg in
    --)
        shift
        break
    ;;
    -d)
        execute=2
        export execute
        shift
    ;;
    -x)
        execute=1
        export execute
        shift
    ;;
    esac
done

ps -u$LOGNAME | awk '{print $4}' | while read proc
do
    execute=3
    case $proc in
        sysmon | awk | ksh | ps | layers | COMMAND)
        ;;
        "")
            echo '\007\007' defunct process?
            execute=0
            export execute
        ;;
        *)
            echo '\007\007' $proc still running
            execute=0
            export execute
        ;;
    esac
done

echo execute is $execute

if [ $? -eq 0 ]; then
    if [ ${execute:-0} -eq 1 ]; then
        kill -1 ${fatherpid:-"fatherpid not set"}
    else
        echo ${fatherpid:-"fatherpid not set"}
    fi
fi

But, at the echo, it can be seen that execute never got set during the
while loop.  It's driving me crazy.  Any help would be appreciated.

-----------------------------

From: Thomas Mellman <mellman@ttrdd.uucp>
Subject: ps -s /dev/null kills system?
Date: 24 Sep 87 15:54:19 GMT
Keywords: system V, examining core files
To:       info-unix@brl-sem.arpa

ps(1) says, about the -s option:

"Use the file *swapdev* in place of -/dev/swap-.  This is useful when
examining a *corefile*; a *swapdev* of -/dev/null- will cause the user
block to be zeroed out."

Is this for real?  What is the *user block*, anyway?  Presumably, if it's
a disk block, you have to be the super-user to have write access to disk,
but even then...

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster%FINFUN.BITNET@WISCVM.WISC.EDU (PMDF Mail Server) (10/13/87)

The message could not be delivered to:

Addressee: pietilainen
Reason:
  %MAIL-E-NOSUCHUSR, no such user PIETILAINEN at node OPMVAX

----------------------------------------

Received: from FINFUN.BITNET by OPMVAX.KPO.FI; Sat, 10 Oct 87 22:58 O
Received: From WISCVM(SMTP) by FINFUN with RSCS id 4912 for PIETILAI@FINFUN;
 Sat, 10 Oct 87 22:58 O
Received: from SEM.BRL.MIL by WISCVM.WISC.EDU ; Sat, 10 Oct 87 14:55:22 CDT
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab15695; 10 Oct 87 2:58 EDT
Received: from sem.brl.mil by SEM.BRL.ARPA id aa15682; 10 Oct 87 2:45 EDT
Date: Sat, 10 Oct 87 02:45:40 EST
From: The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#040
To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Message-ID:  <8710100245.aa15682@SEM.BRL.ARPA>

INFO-UNIX Digest          Sat, 10 Oct 1987              V4#040

Today's Topics:
           Re: variables set in sh while loop don't get set?
                        Re: windowing on a vt100
                        vi, eqn & troff in 1995?
                Re: [nt]roff proportional spacing and h
                     Re: Problem with rcp/rsh/rdump
   Re: System V manuals (was Re: What real non-UNIX 'C' compilers...)
                          Re: BSD for the 386?
                        How to set TZ for cron?
                            Re: VI questions
-----------------------------------------------------------------

From: Steve Losen <scl@virginia.acc.virginia.EDU>
Subject: Re: variables set in sh while loop don't get set?
Date: 28 Sep 87 15:26:36 GMT
Keywords: sh, ksh scripts, loops
To:       info-unix@SEM.BRL.MIL

In article <212@ttrdd.UUCP> mellman@ttrdd.UUCP (Thomas Mellman) writes:
>When I set a variable in a while loop in a sh script, in some scripts
>it doesn't seem to get set.  For example, a common thing is to do a
>
>    pipeline | while read proc
>    do

    done  # assumed

What is happening is that the while loop is being run as a separate
process.  The shell is very fond of doing this sort of thing,
especially in pipelines.  At the "done" the "while loop process" exits,
giving control back to the parent shell, whose variables haven't
changed.  I suggest that you do this:

pipeline | (
    while read proc
    do
        # set some variables
    done
    # now use the variables set in while loop
)

This forces everything between the parentheses to happen in the child
process, so you can get some use out of those variables.
--
Steve Losen
University of Virginia Academic Computing Center

-----------------------------

From: Guy Harris <guy%gorodish@Sun.COM>
Subject: Re: windowing on a vt100
Date: 8 Oct 87 18:02:10 GMT
Sender: news@sun.uucp
To:       info-unix@brl-sem.arpa

> Anyone  in "netland" know of a way to get multiple windows(24x80) up on a
>     vt100 terminal.  I've heard rumblings that it is possible using
>     the newest X11 version of X windows????

Anything's possible, I guess, but I would be VERY surprised if this were the
case.  X was specifically designed for bit-map displays, and I suspect
almost all X programs assume that you have a bit-mapped display handy.  There
is a huge gap between dumb character terminals and bit-map displays, and trying
to build a window system that supports the former would probably result in one
that inadequately supported the latter.

> Other alternatives would be helpful as well.
>
>     Note we are running on a VAX 8650 with Ultrix 1.2(incomplete SV curses)

There have been several windowing programs for dumb terminals posted to the net
at various times; check out the "comp.sources.unix" archives.  There is one
provided with 4.3BSD, called "window"; you may be able to get that to run, if
you have 4.3BSD source handy.
    Guy Harris
    {ihnp4, decvax, seismo, decwrl, ...}!sun!guy
    guy@sun.com

-----------------------------

From: ray sachs <sachs@tanner.berkeley.EDU>
Subject: vi, eqn & troff in 1995?
Date: 6 Oct 87 19:29:26 GMT
Sender: nobody@cartan.Berkeley.EDU
Keywords: busy, obsolete
To:       info-unix@SEM.BRL.MIL

I work on suns and Vaxes within the ucb system to do number
crunching and word processing.
I'm quite happy with vi, eqn and troff.  But some people
have suggested that I have to eventually switch to emacs
and tex, or something, or end up so out of date that I can't
get advice, decent hard copy, new graphics,...
I hate to spend time learning something new when the old seems
fine, but if I have to eventually switch, the sooner the better.
Expert advice solicited (by e-mail, whatever that is); I'll
summarize if interest warrants.

-----------------------------

From: brad@bradley.uucp
Subject: Re: [nt]roff proportional spacing and h
Date: 7 Oct 87 17:53:00 GMT
Nf-ID: #R:wpg.UUCP:167:bradley:10800008:000:349
Nf-From: bradley.UUCP!brad    Oct  7 12:53:00 1987
To:       info-unix@SEM.BRL.MIL


I would use ditroff (or newtroff) and write a device driver.
I wrote one for fixed width chars. (just so see if I could do it)
so if you know the char widths it shouldn't be hard.


Bradley Smith            UUCP: {cepu,ihnp4,noao,uiucdcs}!bradley!brad
Text Processing            ARPA: cepu!bradley!brad@CS.UCLA
Bradley University        PH: (309) 677-2337
Peoria, IL 61625

-----------------------------

From: Kyle Jones <kyle@xanth.uucp>
Subject: Re: Problem with rcp/rsh/rdump
Date: 9 Oct 87 08:33:52 GMT
Keywords: Where are you?
To:       info-unix@brl-sem.arpa

In <759@gargoyle.UChicago.EDU>, chris@gargoyle.UChicago.EDU writes:
> #
> # Check to see if this is an interactive shell...
> if ($?prompt) then
>  ...
> endif

An oft missed optimization of this is

if ($?prompt == 0) exit 0

which allows csh to skip parsing the rest of the file.

kyle jones  <kyle@odu.edu>  old dominion university, norfolk, va  usa

-----------------------------

From: Guy Harris <guy%gorodish@Sun.COM>
Subject: Re: System V manuals (was Re: What real non-UNIX 'C' compilers...)
Date: 9 Oct 87 02:29:04 GMT
Sender: news@sun.uucp
Followup-To: comp.unix.questions
To:       info-unix@SEM.BRL.MIL

> Haven't seen the book you cite anywhere. All the bookstores around here
> have the SVID-based one only.

Well, that's too bad, but the book *you* cite appears to be the only book that
claims to be a System V manual (as opposed to a System V interface definition)
and that has this layout.  In other words, the book you cite is an exception to
the rule, and complaints about its contents cannot validly be extended to
complaints about System V documentation in general.

> I wish it was. Unfortunately the book I cite is the only one I've seen,
> and it's also the one Microport is distributing as their UNIX manual.

It's not the one AT&T is distributing as *its* UNIX manual, nor is it, I
suspect, what most vendors distribute.

> I didn't say it was in section 2 or section 3. I said it was in BA_SYS...

I quote here from your original article:

> Except that the O/S *manuals* follow the SVID. And except that it confuses
> people. "Hey, peter, how come they have read and fread?" "Well, fread is
> a library routine." "Oh. How do you tell which ones are library routines?"
> "read the manual. Library routines are section 3" "section 3? I don't
> have a section 3" "What? Let me look at that... they must be kidding".

I see nothing about BA_SYS here.  I see only a claim that "the O/S manuals
follow the SVID", which is NOT true in general; it is only true for that one
anomalous manual you saw.  All the System V manuals we've gotten from AT&T have
the traditional division between sections 2 and 3.

> > Remember, we're NOT just talking about "traditional UNIX systems" here.
> > This "read" could be implemented atop a non-UNIX system, or a UNIX system
> > with more general facilities for sharing than "traditional" systems.
>
> Since the title of the message is "System V manuals", don't you think we
> should be talking about System V?

Well, first of all, if we're talking about System V, we should talk about it in
comp.unix.questions, so this discussion is moving there.

Second of all, in the claim you made said nothing about implementing "read"
under a vanilla System V system.  You just said

> I don't believe you could implement "read" as a library routine and retain
> the attribute of leaving the file descriptor at the point last read, unless
> you were to "implement" it by making a direct call to the existing read
> routine. Certainly buffering would be out.

with no such qualification.  You could definitely do this under some
non-vanilla implementations, e.g. Apollo's DOMAIN/IX.

For that matter, you could probably do it under vanilla System V, if the IPC
code, including shared memory, is configured into the kernel.  You may not
*want* to do it that way, but it's not impossible.

The fact that it *doesn't* happen to be implemented that way in most UNIX
systems is irrelevant; you didn't say it *wasn't* done that way, you said that
you didn't believe it *could* be done that way.
    Guy Harris
    {ihnp4, decvax, seismo, decwrl, ...}!sun!guy
    guy@sun.com

-----------------------------

From: "Michael S. Fischbein" <msf@amelia>
Subject: Re: BSD for the 386?
Date: 9 Oct 87 18:39:44 GMT
Sender: usenet@ames.arpa
To:       info-unix@brl-sem.arpa

In article <2742@tekgvs.TEK.COM> keithe@tekgvs.UUCP (Keith Ericson) writes:
>In article <843@cup.portal.com> Mark_David_McWiggins@cup.portal.com writes:
>>I've seen several references to Sys V for the 386, but none for
>>4.x BSD.  Why not?  Are there any such implementations in the works?
>
>At this point it appears to my limited-distance vision that it's a
>circular development: vendors are providing SysV so management-types
>are requiring SysV so vendors are providing SysV so...

The problem is finding a UNIX `standard.'  There are so many to choose
from....(:-)  However, the only one that seems to be really complete
(in that something that meets the standard, with no extensions, is an
actual useable system) is SVID.  X/Open?  No, but close.  POSIX?  Not
even close.  BSD?  BSD doesn't have any sort of formal or semiformal
standard; how can you define a `BSD' system?  Don't tell me you know it
when you see it; so do I, but I can't write a specification that way.

Management types, particularly those reviewing purchase request for
computer systems acquisitions, like having `accepted standards.'  For
that matter, as a programmer, I like them too.  Now, I like the extra
features BSD offers, but have problems stating why in terms that would
satisfy a legal department.  You could probably just about anything that
had any 4.x code a `BSD system,' even if it was socket calls on CICS!
You can't call something System V if it doesn't meet the SVID. Now, a
real UNIX based on UCB code vice AT&T code is just fine, but how do you
specify it, and if you make it, how does someone ask for it?

    mike

Michael Fischbein                 msf@prandtl.nas.nasa.gov
                                  ...!seismo!decuac!csmunix!icase!msf
These are my opinions and not necessarily official views of any
organization.

-----------------------------

From: "Markus N. Richardson" <markus@etn-rad.uucp>
Subject: How to set TZ for cron?
Date: 9 Oct 87 00:09:53 GMT
Keywords: cron TZ help
To:       info-unix@brl-sem.arpa


We are having problems *encouraging* cron to accept our (PST8PDT) timezone.
So far we have done the following to try to alleviate the problem:

Placed the line "TZ=PST8PDT; export TZ" at the beginning of /etc/rc
Placed the line "TZ=PST8PDT; export TZ" at the beginning of /etc/profile
Placed the line "setenv TZ PST8PDT" in /etc/cshprofile (our csh startup file)

None of these have solved the problem.  All cron jobs still execute based
on the default timezone (EST)!  Any good ideas?

FYI, we are running 5v2r2 UNIX.  Please e-mail any responses as this is
(hopefully :-) a simple problem that probably has been hashed out before.
Thanks in advance.
--

        Markus N. Richardson
        Research and Development
        Eaton Corporation IMSD
        Westlake Village, CA 91359

        { voder,ihnp4,trwrb,scgvaxd,jplgodo }!wlbr!etn-rad!markus
          markus@etn-rad.eaton.com

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: VI questions
Date: 10 Oct 87 04:44:24 GMT
Keywords: VI, Bells
To:       info-unix@SEM.BRL.MIL

In article <504@kuling.UUCP> irf@kuling.UUCP (Stellan Bergman) writes:
>In article <3050@uwmcsd1.UUCP> zhao@csd4.milw.wisc.edu.UUCP (T.C. Zhao) writes:
>>2. I remember a while back someone mentioned ' visual bells' in Vi,
>In your terminfo (or termcap) file you add a 'flash' entry (e.g. escape

The termcap name for this string capability is "vb"; the terminfo name
is "flash".  Warning: usually, such entries assume that your terminal
is operated in a particular B-on-W or W-on-B state; if you use reverse
video when that's the opposite of what the termcap/terminfo entry
assumes, the first visual bell will toggle your B/W mode.

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster@wharton.upenn.EDU (PMDF Mail Server) (12/27/87)

Your message could not be delivered to: 

    reilly@facman.wharton.upenn.edu

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows: 

Return-path: <info-unix-request@SEM.BRL.MIL>
Received: from SEM.BRL.MIL by wharton.upenn.edu via TCP; Wed Dec 23 04:39 EST
Received: by SEM.BRL.ARPA id aa14359; 23 Dec 87 4:22 EST
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab13998; 23 Dec 87 2:58 EST
Received: from sem.brl.mil by SEM.BRL.ARPA id aa13974; 23 Dec 87 2:45 EST
Date: Wed, 23 Dec 87 02:45:30 EST
From: The Moderator (Mike Muuss) <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#109
To: INFO-UNIX@BRL.ARPA
X-VMS-To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA

Postmaster@wharton.upenn.EDU (PMDF Mail Server) (12/28/87)

Your message could not be delivered to: 

    reilly@facman.wharton.upenn.edu

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows: 

Return-path: <info-unix-request@SEM.BRL.MIL>
Received: from SEM.BRL.MIL by wharton.upenn.edu via TCP; Thu Dec 24 04:38 EST
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab22303; 24 Dec 87 2:56 EST
Received: from sem.brl.mil by SEM.BRL.ARPA id aa22201; 24 Dec 87 2:45 EST
Date: Thu, 24 Dec 87 02:45:41 EST
From: The Moderator (Mike Muuss) <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#110
To: INFO-UNIX@BRL.ARPA
X-VMS-To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Resent-date: Thu, 24 Dec 87 04:39 EST

Postmaster@wharton.upenn.EDU (PMDF Mail Server) (12/29/87)

Your message could not be delivered to: 

    reilly@facman.wharton.upenn.edu

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows: 

Return-path: <info-unix-request@SEM.BRL.MIL>
Received: from SEM.BRL.MIL by wharton.upenn.edu via TCP; Fri Dec 25 04:52 EST
Received: from SEM.BRL.MIL by SEM.brl.ARPA id aa28835; 25 Dec 87 3:00 EST
Received: from sem.brl.mil by SEM.BRL.ARPA id aa28782; 25 Dec 87 2:45 EST
Date: Fri, 25 Dec 87 02:45:37 EST
From: The Moderator (Mike Muuss) <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#111
To: INFO-UNIX@BRL.ARPA
X-VMS-To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Resent-date: Fri, 25 Dec 87 04:52 EST

Postmaster@wharton.upenn.EDU (PMDF Mail Server) (12/30/87)

Your message could not be delivered to: 

    reilly@facman.wharton.upenn.edu

Your message has been enqueued and undeliverable for 6 days.
The mail system will continue to try to deliver your message
for an additional 6 days.

The beginning of your message follows: 

Return-path: <info-unix-request@SEM.BRL.MIL>
Received: from SEM.BRL.MIL by wharton.upenn.edu via TCP; Wed Dec 23 04:39 EST
Received: by SEM.BRL.ARPA id aa14359; 23 Dec 87 4:22 EST
Received: from SEM.BRL.MIL by SEM.brl.ARPA id ab13998; 23 Dec 87 2:58 EST
Received: from sem.brl.mil by SEM.BRL.ARPA id aa13974; 23 Dec 87 2:45 EST
Date: Wed, 23 Dec 87 02:45:30 EST
From: The Moderator (Mike Muuss) <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V4#109
To: INFO-UNIX@BRL.ARPA
X-VMS-To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Fri, 1 Jul 88 14:13 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 8819 for TRIN4@TRINCC;
 Fri,  1 Jul 88 14:12 EST
Received: by YALEVM (Mailer X1.24) id 8813; Fri, 01 Jul 88 13:41:12 EST
Date: Tue, 28 Jun 88 11:15:44 PDT
From: PGTLRAH%CALSTATE.BITNET@cunyvm.cuny.edu
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments:     Resent-From: PGTLRAH%CALSTATE.BITNET@cunyvm.cuny.edu
Comments: To: INFO-UNIX@BRL.ARPA
Comments: cc: PAAAAAR@cunyvm.cuny.edu

When "forced" to be "serious," I must agree that venerable COBOL is a good
language to work in.  The new '85 standard has made many improvements.  I
really should stop indulging my petty bias against it.

Thanks,
Rick H.

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Sat, 2 Jul 88 14:17 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 9424 for TRIN4@TRINCC;
 Sat,  2 Jul 88 14:16 EST
Received: by YALEVM (Mailer X1.24) id 9421; Sat, 02 Jul 88 14:17:26 EST
Date: Fri, 1 Jul 88 15:05:37 EDT
From: Root Boy Jim <rbj@cmr.icst.nbs.gov>
Subject: Subscription Cancellation
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: info-unix@BRL.ARPA

I'm forwarding this request. Please do not cancel *me*.

? Date: Mon, 27 Jun 88 13:19 5
? From: SANDRA%nuhub.acs.northeastern.edu@relay.cs.net
? X-Vms-To: IN%"info-unix%brl.arpa@RELAY.CS.net"

? Please cancel my subscription to info-unix.

? Thank you.

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Fri, 1 Jul 88 14:13 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 9719 for TRIN4@TRINCC;
 Fri,  1 Jul 88 14:12 EST
Received: by YALEVM (Mailer X1.24) id 9712; Fri, 01 Jul 88 13:56:58 EST
Date: Thu, 30 Jun 88 12:07:37 EST
From: TAI-CRAY Systems Administrator <BAYNESRT@v880np.newport>
Subject: Request for Info
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: info-unix@BRL.ARPA, unix-wizards@BRL.ARPA

    We have a user that wishes UNIX to look
    more like VMS (sorry, but that is the
    request)! Does anyone know of any shell
    script(s) that would provide a VMS
    look-alike interactive environment?

    Thanks,

    Bob Baynes
    baynesrt%v880np.decnet@nusc-npt.arpa

    TAI
    ASECC Building 112, Soth End
    NUSC
    Newport, RI 02840

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Sat, 2 Jul 88 17:31 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 1455 for TRIN4@TRINCC;
 Sat,  2 Jul 88 17:31 EST
Received: by YALEVM (Mailer X1.24) id 1451; Sat, 02 Jul 88 17:32:00 EST
Date: Fri, 1 Jul 88 16:22:27 EDT
From: Root Boy Jim <rbj@cmr.icst.nbs.gov>
Subject: "cd path" strangeness [summary]
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: barnett@vdsvax.steinmetz.ge.com
Comments: cc: info-unix@BRL.ARPA

? From: "Bruce G. Barnett" <barnett@vdsvax.steinmetz.ge.com>

? Try:
?     alias @         'set \!:1=$cwd'

No, *don't* try it. `@' has a defined meaning. Pick another alias.

?     Bruce G. Barnett     <barnett@ge-crd.ARPA> <barnett@steinmetz.UUCP>
?                 uunet!steinmetz!barnett

    (Root Boy) Jim Cottrell    <rbj@icst-cmr.arpa>
    National Bureau of Standards
    Flamer's Hotline: (301) 975-5688
    The opinions expressed are solely my own
    and do not reflect NBS policy or agreement
    Careful with that VAX Eugene!

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Sat, 2 Jul 88 19:21 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 2469 for TRIN4@TRINCC;
 Sat,  2 Jul 88 19:20 EST
Received: by YALEVM (Mailer X1.24) id 2465; Sat, 02 Jul 88 19:20:50 EST
Date: Fri, 1 Jul 88 17:35:28 PDT
From: Ev Batey-NSWSES-805/982-5881 <suned1!efb@BRL.ARPA>
Subject: Mot Sys 1100 / V68 Unix LIST
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: info-unix@BRL.ARPA
Comments: cc: sys-1131@elroy.jpl.nasa.gov


I've looked and looked for living members of the Motorola System 113x cult
who run Motorola / AT&T System V Unix / V68 R2/R3.x.  We have several and
are involved in development.  Unless someone knows of a prior existing list
I volunteer to start this one.  To address the list mail to sys-1131 ...
and for admin (ADD / DELETE) sys-1131-request via these paths:

hplabs!motsj1!unicon!suned1!sys-1131
sun!tsunami!suned1!sys-1131
suned1!sys-1131@elroy.JPL.Nasa.Gov

 Everett F. Batey II         }   {UUCP:  sun!tsunami!suned1!efb
                                         suned1!efb@elroy.JPL.Nasa.Gov
 USNSWSES - Code 4V33        }   {ARPA:  efbatey@NSWSES.ARPA
 Port Hueneme,CA  93043-5007 }   {DDD:   805/982-5881 983-1220(ans)

 SoCalif SUN Local User Group - Vta-SantaBarbara-SanLuisObispo DECUS

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Sat, 2 Jul 88 17:15 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 1309 for TRIN4@TRINCC;
 Sat,  2 Jul 88 17:15 EST
Received: by YALEVM (Mailer X1.24) id 1306; Sat, 02 Jul 88 17:16:02 EST
Date: Fri, 1 Jul 88 15:31:55 EDT
From: Root Boy Jim <rbj@cmr.icst.nbs.gov>
Subject: vi documentation
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: info-unix@BRL.ARPA

? tomf@boulder.Colorado.EDU (Tom Fredericks) writes:
? >
? >   I could also use some vi docs.  If anyone knows of a book or has
? >   some 'complete' docs in a file I would really appreciate it.
? >
? >    Tom...

You must be running TPC UNIX or you wouldn't have to ask. The definitive
reference manuals are "An Introduction to Display Editing with VI",
"EX Reference Manual", "EDIT: A Tutorial", "Tutorial Introduction to ED",
and "Advanced Editing on UNIX". They are distributed with every BSD based
system I know of and are numbered USD:{15,16,14,12,13} in 4.3 BSD.

? Here are two recommendations:

Forget it. Read the *real* manuals.

    (Root Boy) Jim Cottrell    <rbj@icst-cmr.arpa>
    National Bureau of Standards
    Flamer's Hotline: (301) 975-5688
    The opinions expressed are solely my own
    and do not reflect NBS policy or agreement
    Careful with that VAX Eugene!

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Sat, 2 Jul 88 16:42 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 0973 for TRIN4@TRINCC;
 Sat,  2 Jul 88 16:42 EST
Received: by YALEVM (Mailer X1.24) id 0968; Sat, 02 Jul 88 16:42:47 EST
Date: Fri, 1 Jul 88 16:15:33 EDT
From: Root Boy Jim <rbj@cmr.icst.nbs.gov>
Subject: utility to determine rlogin?
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: warwick!maujd@cmr.icst.nbs.gov
Comments: cc: info-unix@BRL.ARPA

? From: Geoff Rimmer <maujd@warwick.uucp>

? What's wrong with a simple shell script like this?

? #!/bin/csh -f

You don't need to use any csh features. While I am not opposed to
csh scripts in general (in fact any nontrivial script that I do not
care about portability *is* written in csh), you should use sh here.

[script deleted]

?     opal!maujd    ttyp7   Jun 21 13:20      (garnet)

? for a remote login (with the original machine shown in brackets).

Brackets? Brace {yourself} for this [parenthetical] expression :-)

    (Root Boy) Jim Cottrell    <rbj@icst-cmr.arpa>
    National Bureau of Standards
    Flamer's Hotline: (301) 975-5688
    The opinions expressed are solely my own
    and do not reflect NBS policy or agreement
    Careful with that VAX Eugene!

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Fri, 1 Jul 88 13:52 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 7349 for TRIN4@TRINCC;
 Fri,  1 Jul 88 13:52 EST
Received: by YALEVM (Mailer X1.24) id 7345; Fri, 01 Jul 88 01:41:13 EST
Date: Thu, 23 Jun 88 07:25:02 MST
From: Duke Mangum <dwm%asbf-cs.huachuca-em.arpa@huachuca-em.arpa>
Subject: labelit/volcopy.
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: info-unix@BRL.ARPA

Hope someone out there has an answer to this problem :

I'm the SA on a Unisys ( Sperry ) 5000/80. A week or so ago, I was getting
ready to do some file system volcopies. The target device for the volcopies
is a 1600 bpi Cypher tape drive.  The first file system I went to volcopy
required three reels, so I executed 'labelit' on these three reels
preparatory to using them. I used labelit as follows ( the reel/volume
names changed for each reel, of course ) :

    labelit /dev/rmt/c0d0h work 1462 -n

I next used labelit to verify the labels on the three tapes. So far, so
good !    I then did the volcopy - no problems. The next file system I
needed to volcopy required two reels. I used labelit ( -n ) as above to
label these tapes; however (comma) when I then used labelit to verify the
labels, I got a 'printout' of the labels followed by the nastygram :

    "illegal blocksize=512"

Subsequent attempts to get around this, using different variations of
everything I could think of, produced no change. Finally, I decided to go
ahead and try the volcopy. The file system I was volcopying has a partition
size of 50024 blocks. At the end of the volcopy execution, the blocks
copied figure was 100048 blocks. 'Restoring' from these tapes produces
the same block count, however a subsequent 'df -t' shows the partition
to be the expected size.

What is irritating is that, if memory serves me correctly, I had this same
problem on our Gould 6032 about two years ago, but I do NOT remember what
caused it and how I finally got around it; I just remember that I did.

I called this situation in on the Unisys 'hotline', but they seem to feel
( at the moment, anyway ) that this is not a problem !

If anyone out there has a solution to this problem, I would *really*
appreciate it. If I didn't have a memory fault in this sector, it wouldn't
BE a problem. Many (hopeful) thanks in advance.

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/07/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Sat, 2 Jul 88 18:21 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 1796 for TRIN4@TRINCC;
 Sat,  2 Jul 88 18:21 EST
Received: by YALEVM (Mailer X1.24) id 1792; Sat, 02 Jul 88 18:21:49 EST
Date: Fri, 1 Jul 88 15:49:35 EDT
From: Root Boy Jim <rbj@cmr.icst.nbs.gov>
Subject: RCS and SCCS
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: unccvax!wdg@cmr.icst.nbs.gov
Comments: cc: info-unix@BRL.ARPA

? From: Doug Gullett <wdg@unccvax.uucp>

? The standard MAKE program understands SCCS and not RCS.  This one limitation
? is solved by intelligent setup of the makefile dependencies.

Try

.DEFAULT:
    co $@

Of course, then you must explicitly list that every .o file depends on the
corresponding .c file.

Another gambit if you do not use a separate RCS directory and do not
keep sources checked out is:

.SUFFIXES: .c,v

.c,v.o:
    co $*.c
    $(CC) $(CFLAGS) -c $*.c
    rm $*.c

Apologys if I screwed up, I just typed this off the top of my head.

It is rumored that some people (ok, I give, U of Md. among others) have
hacked make to understand RCS, altho to what level , I don't know.
Maybe someone with initials ACT will clear this up. :-)

Finally, there is GNU make, which recognizes prefixes as well as suffixes,
in a totally new (gnu?) way. I have it but haven't used it yet.

?             Doug Gullett
?             University of NC at Charlotte

    (Root Boy) Jim Cottrell    <rbj@icst-cmr.arpa>
    National Bureau of Standards
    Flamer's Hotline: (301) 975-5688
    The opinions expressed are solely my own
    and do not reflect NBS policy or agreement
    Careful with that VAX Eugene!

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/08/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Mon, 4 Jul 88 03:27 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 3860 for TRIN4@TRINCC;
 Mon,  4 Jul 88 03:12 EST
Received: by YALEVM (Mailer X1.24) id 3854; Mon, 04 Jul 88 03:10:42 EST
Date: Mon, 27 Jun 88 02:45:36 EST
From: Mike Muuss The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V5#081
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: INFO-UNIX@BRL.ARPA

INFO-UNIX Digest          Mon, 27 Jun 1988              V5#081

Today's Topics:
                    has anybody put $VPATH into mk?
                   Re: "Deep Background" applications
            Re: "Deep Background" applications (correction)
       Re: "Deep Background" applications (One of those days...)
            Re: basename(1) (Was Re:argv[0] in shellscript?)
                    Re: utility to determine rlogin?
          Is a NEED for more COMMERCIAL usenet feed providers?
                  Re: has anybody put $VPATH into mk?
Re: csh :t modifier (Was Re: basename(1) (Was Re:argv[0] in shellscript?))
                            Re: RCS and SCCS
                    Re: Meaning of "rc" in cron/log
     Need utils: head,yes,& nroff (-man) for SysV2 (CCI 2.21or2.22)
                              plot, graph
   Re: Need utils: head,yes,& nroff (-man) for SysV2 (CCI 2.21or2.22)
-----------------------------------------------------------------

From: "Stephen J. Friedl" <friedl@vsi.uucp>
Subject: has anybody put $VPATH into mk?
Date: 26 Jun 88 04:08:06 GMT
To:       info-unix@SEM.BRL.MIL

Hi folks,

     We recently got mk from the Toolchest (Hi Andrew!) and
before I go hacking it up too much I want to check with others.
Has anybody added $VPATH to mk?  Make has this very helpful
undocumented feature and I want it here.

     For those unfamiliar with $VPATH, it is a make variable that
provides a colon-separated list of paths to search when looking
for dependencies.  With VPATH set to

        VPATH=/usr/project/include:$INFORMIXDIR/incl ; export VPATH

you can convert:

        foo.o   : foo.h ../include/defs.h ${INFORMIXDIR}/incl/dbtypes.h
into
        foo.o   : foo.h defs.h dbtypes.h

     We like to stick these assignments in the project's .profile;
it really helps keep Makefiles from getting too cluttered.  Has
anybody done this to mk yet?  Will you share it?

     Thanks in advance,
     Steve

--
Steve Friedl     V-Systems, Inc. (714) 545-6442     3B2-kind-of-guy
friedl@vsi.com     {backbones}!vsi.com!friedl    attmail!vsi!friedl

Nancy Reagan on the Free Software Foundation : "Just say GNU"

-----------------------------

From: Jon Sweedler <cjosta@taux01.uucp>
Subject: Re: "Deep Background" applications
Date: 26 Jun 88 10:10:02 GMT
To:       info-unix@SEM.BRL.MIL

In article <2772@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes:
>In article <11019@cgl.ucsf.EDU>, seibel@cgl.ucsf.edu (George Seibel) writes:
>#In article <29500025@urbsdc> aglew@urbsdc.Urbana.Gould.COM writes:
>#]For example, fixed priority
>#]scheduling - there have been many times that I wanted to have
>#]a "deep background" application, that would run only when the
>#]system is otherwise idle. No matter how much you nice, your
>#]process will still take some cycles away when the system isn't
>#]idle.

Not true (at least according to the "renice" man page...)

>#We'd really like a way to make
>#those jobs butt out when someone wants to run a short (10 min-1 hr)
>#job.   Does anyone know of an easy way to do something like this on
>#a bsd 4.[2-3] system?

Yes, just run a process with a priority of 20 (see below).

>
>Maybe a watch-dog program could be kludged up to use SIGSTOP to suspend
>the multi-day jobs when another job goes into background?  (If the new job
>takes too long, or when it finishes, the stopped jobs would be restarted with
>SIGCONT.)

This is much more complicated than necessary.  According to the "renice"
man page, running a process with a priority of 20 (PRIO_MAX really) will
accomplish this (I don't know why it doesn't say this in the "nice" man
page as well...):

RENICE(8)        UNIX Programmer's Manual        RENICE(8)

NAME
     renice - alter priority of running processes
 .
 .
 .
     Useful priorities are: 20 (the affected processes
     will run only when nothing else in the system wants to)

--
Jon Sweedler   =====   National Semiconductor (Israel)
UUCP:   {ames!amdahl,hplabs,sun,decwrl}!nsc!taux01!cjosta
Domain: cjosta@taux01.nsc.com
Paper:  6 Maskit st., P.O.B. 3007, Herzlia B 46104, Israel

-----------------------------

From: Jon Sweedler <cjosta@taux01.uucp>
Subject: Re: "Deep Background" applications (correction)
Date: 26 Jun 88 11:27:52 GMT
To:       info-unix@SEM.BRL.MIL

In article <779@taux01.UUCP> cjosta@taux01.UUCP (Jon Sweedler) writes:
>This is much more complicated than necessary.  According to the "renice"
>man page, running a process with a priority of 20 (PRIO_MAX really) will
                                                    ^^^^^^^^
Oops.  This should be PRIO_MIN.  And also, under BSD 4.2, PRIO_MIN is
set to 19.  Under BSD 4.3 it is 20.
--
Jon Sweedler   =====   National Semiconductor (Israel)
UUCP:   {ames!amdahl,hplabs,sun,decwrl}!nsc!taux01!cjosta
Domain: cjosta@taux01.nsc.com
Paper:  6 Maskit st., P.O.B. 3007, Herzlia B 46104, Israel

-----------------------------

From: Jon Sweedler <cjosta@taux01.uucp>
Subject: Re: "Deep Background" applications (One of those days...)
Date: 26 Jun 88 11:56:25 GMT
To:       info-unix@brl-sem.arpa

In article <780@taux01.UUCP> cjosta@taux01.UUCP (Jon Sweedler) writes:
>In article <779@taux01.UUCP> cjosta@taux01.UUCP (Jon Sweedler) writes:
>>man page, running a process with a priority of 20 (PRIO_MAX really) will
>                                                    ^^^^^^^^
>Oops.  This should be PRIO_MIN.  And also, under BSD 4.2, PRIO_MIN is
>set to 19.  Under BSD 4.3 it is 20.

Sorry for the multiple postings, but I think I have it right this time...
This is kind of bizarre, but what can you expect from Unix?

Under true BSD 4.3, PRIO_MAX is defined as 20 and PRIO_MIN is defined
as -20.  Regular users can "nice" their processes from 0 to 20.

Under two BSD 4.2 workalikes (DYNIX and Ultrix) that we have here,
PRIO_MAX is defined as -20 and PRIO_MIN is defined as 20 (i.e. backwards
from BSD 4.3 and thus the reason for my confusion).  Regular
users can "nice" their processes from 0 to 19 (despite the fact
that in the Ultrix man page for "nice" it says from 0 to 20).

"Standards are wonderful, there are so many to chose from..."
     -- someone

--
Jon Sweedler   =====   National Semiconductor (Israel)
UUCP:   {ames!amdahl,hplabs,sun,decwrl}!nsc!taux01!cjosta
Domain: cjosta@taux01.nsc.com
Paper:  6 Maskit st., P.O.B. 3007, Herzlia B 46104, Israel

-----------------------------

From: Jerry Peek <jerryp@cmx.npac.syr.edu>
Subject: Re: basename(1) (Was Re:argv[0] in shellscript?)
Date: 26 Jun 88 12:40:43 GMT
To:       info-unix@brl-sem.arpa

In article <3680037@eecs.nwu.edu> squires@eecs.nwu.edu (Matthew Squires) writes:
> / eecs.nwu.edu:comp.unix.questions /
>  davidsen@steinmetz.ge.com (William E. Davidsen Jr)
> /  1:15 pm  Jun  6, 1988 /
>
> > In article <1813@stpstn.UUCP> aad@stpstn.UUCP (Anthony A. Datri) writes:
> > |
> > | I want to write a script that will have multiple links to it, and be
> > | able to tell what name it was invoked with.  Ideas?
> >
> >   How about $0? That's the name of the called program.  Watch out if you
> > have a full pathname (ie.  $0 = foo/something). ...
>
> Then perhaps you could use basename(1)...

But using basename means that the shell has to start another process.
I saw another article where the person mentioned using shell wildcards
to get around the full-pathname problem.  That works great, and it doesn't
start a child process.

Here are two examples of a program with four links (names): ll, lf, lg, and
lr.  The left-hand column shows the sh version; the right-hand shows how to
do it in csh.  Since I put a * before each matching pattern, it always works:

#! /bin/sh                          #! /bin/csh -f
case "$0" in                        switch ($0)
*ll) ls -l $* ;;                    case *ll:
*lf) ls -F $* ;;                        ls -l $*; breaksw
*lg) ls -lg $* ;;                   case *lf:
*lr) ls -lR $* ;;                       ls -F $*; breaksw
*) echo "$0: Wrong name!" 1>&2      case *lg:
   exit 1                               ls -lg $*; breaksw
   ;;                               case *lr:
esac                                    ls -lR $*; breaksw
                                    default:
                                        echoerr "${0}: Wrong name\!"
                                        breaksw
                                    endsw

--Jerry Peek, Northeast Parallel Architectures Center, Syracuse, NY
  jerryp@cmx.npac.syr.edu
  +1 315 423-4120

-----------------------------

From: Jerry Peek <jerryp@cmx.npac.syr.edu>
Subject: Re: utility to determine rlogin?
Date: 26 Jun 88 13:11:48 GMT
To:       info-unix@brl-sem.arpa

A while back, I wrote about a utility called "ttykind" that looks up your
terminal type in /etc/ttys.

In article <16281@brl-adm.ARPA> rbj@cmr.icst.nbs.gov (Root Boy Jim) writes:
> ? From: Rick Lindsley <richl@penguin.uss.tek.com>
>
> ? In article <16109@brl-adm.ARPA> rbj@icst-cmr.arpa (Root Boy Jim) writes:
> ?     Why not just do `switch ($term)'? You don't need ttykind, except for
> ?     finding out *other* peoples terminal types.
>
> ? Because rlogin will pass the terminal type across for you. $term may not
> ? provide the information you want.
>
> Well, I see your point, but still disagree. If I rlogin from a sun console
> to a VAX, why would I want anything other than a Sun termcap?

It's not just to get the termcap.  Someone posted a note about terminal
concentrators; that's what Rick was talking about, too, I think.  They can
hide the real terminal characteristics.

For instance, I used to use 1200-baud dialup lines a lot (yecch!).  Some
programs check the data rate and adjust to slow lines.  For instance, "vi"
sets a smaller window size at slow speeds.  But our Sytek hid the dialup
lines' speeds; all Sytek port connections to our VAX were at 9600 baud.
We had the same problem on network connections; the real terminal speed was
lost.  So, I put a test in .login for the output of "ttykind" -- if the port
was sytek or network, I'd be prompted for the *real* data rate, which was
stored in an envariable named REAL_BAUD -- that was used to set aliases,
EXINIT and RNINIT envariables, etc., that made baudrate-sensitive programs
work right on sytek and network connections.

--Jerry Peek, Northeast Parallel Architectures Center, Syracuse, NY
  jerryp@cmx.npac.syr.edu
  +1 315 423-4120

-----------------------------

From: Greg Corson <milo@ndmath.uucp>
Subject: Is a NEED for more COMMERCIAL usenet feed providers?
Date: 26 Jun 88 16:27:01 GMT
To:       info-unix@SEM.BRL.MIL

A fairly simple question...I've been noticing that usenet mail/news feeds
are getting harder and harder to get lately because of the mounting number
of machines that want onto the net.

Do you think there is a NEED for another system which can provide usenet
feeds and mail feeds for a FEE to people who couldn't get them otherwise?
I am in a position where I could probably organize such a system if anyone
would be interested in using it.  If it was setup the system would probably
be accessable through Telenet, Tymnet (or something like it) by a local
call in most cities.  This might turn out to be a cheaper way of getting
a feed than calling some other network site long distance.

The fees would probably be somewhere around $5 per hour for however much time
it takes to feed your computer all the newsgroups you want. (subject to change,
I haven't looked into the costs too much yet).  Services provided would
be limited to UUCP-mail and USENET feeds.  Note that this would NOT be
login-and-read/send-mail/news...it would be UUCP access to feed mail/news
to YOUR computer...nothing more.

Please let me know if you think this sort of service is something you (or
someone you know) could use, if there is enough demand I'l see if I can
organize something.  Please don't flame me about advertising on the net,
remember that for MANY people who get feeds by long distance this could
be a REAL money saver...and I don't expect to make much money off it in any
case.

Please reply by usenet mail, US mail or phone as I don't get on the net
often enough to avoid missing things posted to news.

Greg Corson
19141 Summers Drive
South Bend, IN 46637
(219) 277-5306 (weekdays till 6 PM eastern)
{pur-ee,rutgers,uunet}!iuvax!ndmath!milo


-----------------------------

From: Rick Richardson <rick@pcrat.uucp>
Subject: Re: has anybody put $VPATH into mk?
Date: 26 Jun 88 14:30:40 GMT
To:       info-unix@SEM.BRL.MIL

In article <732@vsi.UUCP> friedl@vsi.UUCP (Stephen J. Friedl) writes:
>     We recently got mk from the Toolchest (Hi Andrew!) and
>before I go hacking it up too much I want to check with others.
>Has anybody added $VPATH to mk?  Make has this very helpful
>undocumented feature and I want it here.

I think that if you want VPATH, you should've gotten Fourth
Generation Make (newmake?) from AT&T.




--
        Rick Richardson, PC Research, Inc.

(201) 542-3734 (voice, nights)   OR     (201) 389-8963 (voice, days)
uunet!pcrat!rick (UUCP)            rick%pcrat.uucp@uunet.uu.net (INTERNET)

-----------------------------

From: Leo de Wit <leo@philmds.uucp>
Subject: Re: csh :t modifier (Was Re: basename(1) (Was Re:argv[0] in
 shellscript?))
Date: 25 Jun 88 18:16:11 GMT
To:       info-unix@brl-sem.arpa

In article <709@ubu.warwick.UUCP> maujd@warwick.UUCP (Geoff Rimmer) writes:
> [other stuff deleted]...
>cat /etc/passwd | sed "s/:[^:]*:[^:]*:[^:]*:/    /" | sed "s/[,:].*//" | sort
>                       ^^TAB^^
>---------------------------------------------------------------------
>    (BTW, anyone got any improvements on this 'sed' line?)
>---------------------------------------------------------------------

You COULD of course use awk (using IFS) ...
but, assuming you're as devoted a sed worshipper as I am, yes, I've got
an improvement:
Don't use the cat; sed can open the file or even the shell can open it for
sed (saves a process).
Don't use sed twice; one is just as good (even faster).

So the result is:

sed -e "s/:[^:]*:[^:]*:[^:]*:/    /" -e "s/[,:].*//" /etc/passwd | sort

Now maybe even the sed could be improved upon ...?

      Leo.

-----------------------------

From: "John F. Haugh II" <jfh@rpp386.uucp>
Subject: Re: RCS and SCCS
Date: 26 Jun 88 15:41:46 GMT
To:       info-unix@SEM.BRL.MIL

In article <8158@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
 writes:
>In article <661@pyuxe.UUCP> mayerar@pyuxe.UUCP (80132-A Mayer) writes:
>>One good point of RCS is that it stores the most recent version and
>>uses deltas to get back to the previous versions.  SCCS stores the
>>original version and uses deltas to get to the most recent version.
>
>No, it doesn't.  I don't know who started this myth, but it's false.
>SCCS makes one sequential pass to do a "get".

just because get(1) only makes one pass over a file does not mean
the SCCS file is stored in most-recent-version order.  since it is
possible to know which versions the desired version depends on,
get(1) can follow the insert/delete commands in the s-file to create
the desired version.

if i start off with a file which reads

Now is the time for all good men.

and put it in an SCCS file, the results, sans extra cruft is

^AI 1
Now is the time for all good men.
^AE 1

and then you create a delta to make the file

Now is the time for all good men.
To come to the aid of their party.

you end up with

^AI 1
Now is the time for all good men.
^AI 2
To come to the aid of their party.
^AE 2
^AE 1

since the body for version 1 (as bracketed by the ^AI 1/^AE 1 pair) contains
the text for version 2, i would say that SCCS does indeed store the original
version and newer deltas.  the other way would look like

^AI 2
Now is the time for all good men.
^AD 1
To come to the aid of their party.
^AE 1
^AE 2

- john.
--
John F. Haugh II                 +--------- Cute Chocolate Quote ---------
HASA, Division "S"               | "USENET should not be confused with
UUCP:   killer!rpp386!jfh        |  something that matters, like CHOCOLATE"
DOMAIN: jfh@rpp386.uucp          |             -- with my apologizes

-----------------------------

From: Richard Harter <g-rh@cca.cca.com>
Subject: Re: RCS and SCCS
Date: 27 Jun 88 00:18:54 GMT
To:       info-unix@SEM.BRL.MIL

In article <3255@rpp386.UUCP> jfh@rpp386.UUCP (The Beach Bum) writes:
>In article <8158@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
 writes:
>>In article <661@pyuxe.UUCP> mayerar@pyuxe.UUCP (80132-A Mayer) writes:
>>>One good point of RCS is that it stores the most recent version and
>>>uses deltas to get back to the previous versions.  SCCS stores the
>>>original version and uses deltas to get to the most recent version.

>>No, it doesn't.  I don't know who started this myth, but it's false.
>>SCCS makes one sequential pass to do a "get".

It is my understanding that the original implementation of SCCS was in
the form of the original version plus subsequent deltas and that it was
changed to the present form (interleaved deltas) circa 1980.  If anyone
has precise knowledge on this point, could they please post it or send me
e-mail.

>just because get(1) only makes one pass over a file does not mean
>the SCCS file is stored in most-recent-version order.  since it is
>possible to know which versions the desired version depends on,
>get(1) can follow the insert/delete commands in the s-file to create

    ... specific example deleted ...

The answer is, of course, that SCCS uses neither most-recent-version
order nor oldest-version-order.  It does not apply deltas in the sense
of starting with a base version and applying a sequence of updates which
produce a sequence of intermediate versions.  It does apply deltas in the
sense of checking, for each line ever present, the effect of the deltas
on the line.  The difference in performance between the two senses is
enormous; the difference is due to the fact that, in schemes based on
the first sense, each line must be processed once for each delta, whereas
in the second sense each line is only processed once.

It is true, however, that there is, in principle, a signifigant performance
advantage for the RCS scheme versus the SCCS scheme.  SCCS must process
all lines including those not currently active; RCS need only process those
that are currently active.  Furthermore RCS does not need to do any processing
on the line other than copying it out; SCCS has to check the control data
for the line.  On the other hand, RCS pays a penalty if the version being
extracted is not the latest.
--

In the fields of Hell where the grass grows high
Are the graves of dreams allowed to die.
    Richard Harter, SMDS  Inc.

-----------------------------

From: Karl Kleinpaste <lvc@tut.cis.ohio-state.edu>
Subject: Re: Meaning of "rc" in cron/log
Date: 26 Jun 88 21:34:26 GMT
To:       info-unix@brl-sem.arpa

In article <717@mccc.UUCP> pjh@mccc.UUCP (Pete Holsberg) writes:
>
>Would some kind soul please point out where in the SysV R3 docs I could
>go to find out what "rc=xxx" in my /usr/lib/cron/log means?
>

rc=xxx means the exit value (Return Code) of the program executed by cron
is xxx.
--
Larry Cipriani, AT&T Network Systems and Ohio State University
Domain: lvc@tut.cis.ohio-state.edu
Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (strange but true)

-----------------------------

From: Jay Hiser <jay@hqda-ai.arpa>
Subject: Need utils: head,yes,& nroff (-man) for SysV2 (CCI 2.21or2.22)
Date: 26 Jun 88 21:36:16 GMT
Keywords: dwb, tail, Power 6, BSD
To:       info-unix@SEM.BRL.MIL

I'm responsible for 3 CCI 6/32s that run SysV (CCI's rel. 2.22).  I'm
looking for replacements for some of the utils that I'm used to with
BSD.

head: the opposite of 'tail'.   Shouldn't be hard to implement this in
c, but I don't want to reinvent the wheel.  Thought this was part of
'std' unix, but its not in my sys's docs.

yes: pipe the output to some other program that expects 'y' or 'n'.
I've got a file full of 'y\n' that essentially duplicates yes's
function, but it doesn't seem as neat as yes.

nroff: I realize that this has been unbundled (dwb?) from SysV. I
still need to format man pages.  Our OA sys can handle virtually all
my formatting needs, except for nroff -man.  Maybe this could be a GNU
application some day?

Anybody have an alternate source for this useful stuff?  Thanks,

-----------------------------

From: Mitchell Wyle <wyle@solaris.uucp>
Subject: plot, graph
Date: 25 Jun 88 12:31:11 GMT
To:       info-unix@SEM.BRL.MIL


My wife needs grids with numbered tic marks for her lab report graphs.
Has anyone hacked graph(1) to add numbers to the tic marks?  According
to the manual (yes, I RTFM (read the fine manual)):

>     -g gridstyle
>         Gridstyle is the grid style: 0 no grid,  1  frame  with
>         ticks, 2 full grid (default).

and graph(1) always puts a key at the bottom left of how he scaled the
graph.  The home-grown packages here are too applications specific.
I'm looking for a robust scatter-plot package.

We have NO arpa FTP here.  Please reply via e-mail.  As always I'll
post a summary if there are more than 2 me-too's.

I don't have and therefore haven't looked at: gnuplot, graph+,
crc_plot, vplot, quickplot, or lplot.  If anyone (preferably in Europe)
uses any of these PD packages, and knows it's what I want, I would
appreciate his sending it my way.

Cheers, and thanks!   -Mitch
--
-Mitchell F. Wyle            wyle@ethz.uucp
Institut fuer Informatik     wyle%ifi.ethz.ch@relay.cs.net
ETH Zentrum
8092 Zuerich, Switzerland    +41 1 256-5237

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: Need utils: head,yes,& nroff (-man) for SysV2 (CCI 2.21or2.22)
Date: 27 Jun 88 03:55:28 GMT
Keywords: dwb, tail, Power 6, BSD
To:       info-unix@SEM.BRL.MIL

In article <6007@hqda-ai.ARPA> jay@hqda-ai.ARPA (Jay Hiser) writes:
>head: the opposite of 'tail'.

if [ $# -eq 0 ]
then    n=10
else    case $1 in
    [0-9]*)    n=$1;    shift;;
    *)    n=10;;
    esac
fi
exec sed -e ${n}q $*

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/09/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Mon, 4 Jul 88 03:17 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 3884 for TRIN4@TRINCC;
 Mon,  4 Jul 88 03:14 EST
Received: by YALEVM (Mailer X1.24) id 3880; Mon, 04 Jul 88 03:12:36 EST
Date: Fri, 1 Jul 88 02:46:03 EST
From: Mike Muuss The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V5#085
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: INFO-UNIX@BRL.ARPA

INFO-UNIX Digest          Fri, 01 Jul 1988              V5#085

Today's Topics:
                      wanted: L.Wall's MetaConfig
                            Re: RCS and SCCS
                  Re: has anybody put $VPATH into mk?
                          Re: UUCP Over TCP/IP
                     Re: Questions without answers
                Re: Real-time UNIX - what is it & who h
   Re: Need utils: head,yes,& nroff (-man) for SysV2 (CCI 2.21or2.22)
                Re: vi vs emacs in a student environment
                          Re: Historical Fact
   Re: Question: Driver access to memory mapped devices on 386 SysV.3
                       Re: plot, graph (summary)
                           OSF v. ATT/Sun :-)
                          Re: UUCP Over TCP/IP
                          Rn on a V.3 machine
                           NFS/YP alternative
            MKS Toolkit/UNIX [r] System, SEA ARC/PKARC, ...
                       Re: how can I "." in csh?
   Re: Question: Driver access to memory mapped devices on 386 SysV.3
-----------------------------------------------------------------

From: Dave Hammond <daveh@marob.masa.com>
Subject: wanted: L.Wall's MetaConfig
Date: 29 Jun 88 15:00:58 GMT
Posted: Wed Jun 29 11:00:58 1988
To:       info-unix@brl-sem.arpa



I've been looking for a copy of Larry Wall's _MetaConfig_ for a few weeks
with no success. Searches of the mod.sources and comp.sources listings
have thus far proved fruitless.

Can anyone offer any clues where I might acquire a copy of the program ?

Please E-mail responses, don't post; Thanks in advance for any help.

Dave Hammond
UUCP:   ...!marob!daveh
 --------------------------------

-----------------------------

From: Joel Clark <joel@intelisc.uucp>
Subject: Re: RCS and SCCS
Date: 29 Jun 88 15:37:58 GMT
Posted: Wed Jun 29 11:37:58 1988
To:       info-unix@brl-sem.arpa

In article <10406@ulysses.homer.nj.att.com> ekrell@hector (Eduardo Krell)
 writes:
>In article <290@intelisc.UUCP> joel@intelisc.UUCP (Joel Clark) writes:
>
>>Can anyone explain to me how a program could store `the most recent version`
>>such that each line in the file does not need to be examined to determine
>>if it is in the most recent version?
>
>You store the most recent version at the beginning of the file in clear
>text followed by the reverse delta to get the previous version
>(followed by the reverse delta to get the version before that, etc.).
>
>Time to get the latest version is thus proportional only to the size of
>that version. Time to get version N is proportional to the size of
>the last version plus the size of all deltas necessary to get from there
>down to version N.
>
>    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ
>
>    UUCP: {ihnp4,ucbvax}!ulysses!ekrell        ARPA: ekrell@ulysses.att.com

How well does this work if (as we are) you are working from 3 branches at once.
We keep major branches for Development engineers, Sustaining engineers and
Evaluation all in the same source file.  This allows us to proceed with project
that may not go into production for 12-18 months based on the same sources
that we ship, folding in the changes to the production code as they become
solid.

-----------------------------

From: Eric Krohn <krohn@u1100a.uucp>
Subject: Re: has anybody put $VPATH into mk?
Date: 29 Jun 88 21:12:36 GMT
To:       info-unix@SEM.BRL.MIL

In article <732@vsi.UUCP> friedl@vsi.UUCP writes:
] ... about wanting mk (from the AT&T Toolchest) to recognize $VPATH (like
] BSD make) for easier handling of files in multiple directories....

I was looking for this same capability last week and was disappointed
by its absence.  Multiple metarules like
    %.o:    %.c
        $CC -c -O $prereq
    %.o:    ../group/%.c
        $CC -c -O $prereq
only produce errors about ambiguous metarules for making foo.o when foo.c
lives in both . and ../group (say I want to modify my own copy of one or two
files from the vi source and then build a new copy from scratch).
Regular expression metarules look promising but I have yet to get the desired
results:
    '\(.*\)\.o':R:    '\(\.|\.\./group\)/\1\.c'
        cc -c -O $stem2/$stem1.c
Mk just says: don't know how to make 'foo.o'.  Even if it would work given
sufficient backslashes and parentheses, it would be much too cryptic.
It would be nice if mk supported a $MKPATH or $VPATH directly and if the
"ambiguous metarules" checking were relaxed (maybe using the first applicable
metarule).
I'm almost desperate enough :-) to try GNU make which claims to support both
the %.o: %.c style metarules and $VPATH.

BTW, I have used nmake (also from the AT&T Toolchest) and it does support
multiple source directories through the .SOURCE target and it merely warns
about resulting ambiguities.  However, I find that nmake knows too much about
how I "ought" to build my targets when I try to do something unconventional.
I am also a bit repulsed by the extra baggage nmake carries around
(its own cpp, a file of compiled default rules whose source is nearly
incomprehensible (look at the definition of the :: operator!), a compiled
makefile, and a state file).  Don't get me wrong:  nmake is nice about using
short makefiles when you do typical things and about automatically checking
dependencies on include files.
--
--
Eric J. Krohn
krohn@ctt.ctt.bellcore.com  or  {bcr,bellcore}!u1100a!krohn
Bell Communications Research,    444 Hoes Ln,    Piscataway, NJ 08854

-----------------------------

From: Jeff Roth <ntm1569@dsacg3.uucp>
Subject: Re: UUCP Over TCP/IP
Date: 30 Jun 88 12:56:05 GMT
To:       info-unix@SEM.BRL.MIL

From article <10036@marduk.uucp>, by gww@marduk.uucp (Gary Winiger):
[responding to mparker@chip.UUCP's question on the TCP/IP UUCP service]

> Page 2 of L.sys(5) in the 4.3BSD documentation documents a ``caller''
> field value of TCP.  That will cause the sender's 4.3BSD UUCP system to
> open a TCP connetion to the receiver's uucpd.  The receiver, of course,
> needs to have configured access to uucpd.  I don't happen to have a 4.3
> system on hand configured that way to tell you what the inetd.conf line
> has to look like, but I recall it all being in the source directories
> for uucp.  (If it isn't already configured.)

from our /etc/inetd.conf:
uucpd  stream  tcp  nowait  uucp  /etc/uucpd  uucpd

from our /etc/services:
uucp    540/tcp    uucpd    # uucp daemon

from our /usr/lib/uucp/L.sys:
dsacg1 Any TCP uucp dsacg1 ogin:--ogin:--ogin: Udsacg3 ssword: PASSWORD
--
Jeff Roth (osu-cis!dsacg1!jroth) 614-238-9421 (Autovon 850-9421)
From the Internet: jroth%dsacg1.uucp@daitc.arpa
US Defense Logistics Agency Systems Automation       I speak for myself
Center, DSAC-TMP, Box 1605, Columbus, OH 43216

-----------------------------

From: Paul Houtz <gph@hpsemc.hp.com>
Subject: Re: Questions without answers
Date: 29 Jun 88 17:38:17 GMT
To:       info-unix@SEM.BRL.MIL

Michael L. Siemon writes:

-->More to the point (I think Brad is being diplomatic), when somebody asks
-->a moderately hard question (that LOOKS easy) we get 20 wrong responses
-->posted to the net, sowing great confusion.  Summaries are the way to go!
-->(Admittedly, the phrasing "email me, BECAUSE I don't have time to read
-->this group" is rather stupid.)

       Amen, Michael!   This has already happened to me, and I asked
       a fairly simple question.

-----------------------------

From: Rick Schneider <rick@vsi1.uucp>
Subject: Re: Real-time UNIX - what is it & who h
Date: 30 Jun 88 15:11:54 GMT
To:       info-unix@SEM.BRL.MIL

From article <8188@brl-smoke.ARPA>, by gwyn@brl-smoke.ARPA (Doug Gwyn ):
> In article <745@vsi1.UUCP> rick@vsi1.UUCP (Rick Schneider) writes:
>>The only problem with GOULD's RT-UNIX is that it is only intended to
>>run on GOULD machines.
>
> Does this somehow surprise you?  What IS your point?

The point is that if you want GOULD's RT-UNIX, you'll have to buy a GOULD
Powernode or NP series machine to run it on.

GOULD has in the past sold source licenses for all of its flavors of UNIX, so
I guess that the source for it RT-UNIX will also be available.  If you have a
large budget and like hacking the kernal, buy a low-end Powernode with a
UTX/32-RT source license, and port it wherever you would like.

I worked for GOULD-CSD for several years and from my experience, their
implementations have been excellent, support is above average, and pricing
is in line with the rest of the industry.

--
                  Rick Schneider       ...pyramid!vsi1!rick
VICOM SYSTEMS, INC.; 2520 Junction Avenue, San Jose, Ca, 95134, (408) 432-8660

  The  opinions  expressed  are  not  those  of  my  employer  or  are  they?

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: Need utils: head,yes,& nroff (-man) for SysV2 (CCI 2.21or2.22)
Date: 30 Jun 88 19:38:42 GMT
To:       info-unix@SEM.BRL.MIL

In article <366@theceg.UUCP> lkb@theceg.UUCP (Lawrence Keith Blische) writes:
>    head [-count] [file ...]

But that's a violation of the command syntax standard (if count > 9).
Thus my version omits the -.  It does make it hard to deal with files
whose names start with a digit, and is imperfect in other ways.

Actually I always type the direct "sed" command myself:
    program | sed 23q

-----------------------------

From: Fred Fish <fnf@fishpond.uucp>
Subject: Re: vi vs emacs in a student environment
Date: 30 Jun 88 15:19:59 GMT
To:       info-unix@brl-sem.arpa

In article <6056@megaron.arizona.edu> lm@megaron.arizona.edu (Larry McVoy)
 writes:
>As a consultant I'll volunteer the following advice:  don't get people used to
>emacs.  Please.  Why?  Because emacs is available on "some" unix machines.
>Vi is available on almost all unix machines.  Old habits die hard, so I think
>it's better to start people out with something they can stay with...

Until recently you could use almost exactly the same argument for NOT teaching
vi, since vi was ONLY available on Unix systems, while some EMACS or workalike
was available on almost any OS.  Now there are reasonable vi clones for many
of the more commonly used systems, so I don't think the "people portability"
factor is quite as onesided towards EMACS as it once was.  There are also
enough EMACS's available in source form (GNU, microemacs, jove, scame, mg,
etc) that any EMACS addict that has to work for any length of time on a given
Unix system will find some way to get one installed and thus avoid having
to use vi.

-Fred


--
# Fred Fish, 1346 West 10th Place, Tempe, AZ 85281,  USA
# noao!nud!fishpond!fnf                   (602) 921-1113

-----------------------------

From: Doug Gwyn  <gwyn@brl-smoke.arpa>
Subject: Re: vi vs emacs in a student environment
Date: 30 Jun 88 19:46:20 GMT
To:       info-unix@SEM.BRL.MIL

In article <6056@megaron.arizona.edu> lm@megaron.arizona.edu (Larry McVoy)
 writes:
>As a consultant I'll volunteer the following advice:  don't get people used to
>emacs.  Please.  Why?  Because emacs is available on "some" unix machines.
>Vi is available on almost all unix machines.  Old habits die hard, so I think
>it's better to start people out with something they can stay with...

If "vi" weren't such a crappy editor this might be good advice.
However, many users spend much of their time text-editing, so they
should use the best editor available rather than suffer with inferior
tools just because they are more universal.  (If they really have to
deal with a wide variety of UNIX systems, then it makes more sense to
emphasize universality.  It would also make sense in that case to
provide better tools on all those systems.)

I actually do use "vi" on my Sun, until I get "sam" running.  (The
SunTools text editor is a joke.)  Given a choice between "vi" or an
EMACS variant I'll choose EMACS, but those aren't the only choices.

-----------------------------

From: Ron Natalie <ron@topaz.rutgers.edu>
Subject: Re: Historical Fact
Date: 30 Jun 88 17:27:50 GMT
To:       info-unix@SEM.BRL.MIL

I would suspect the later.  There was a program to print
planet and sattelite orbits, but I believe it was called azel.
I left my V6 manual at home.

-Ron

-----------------------------

From: Ron Natalie <ron@topaz.rutgers.edu>
Subject: Re: Question: Driver access to memory mapped devices on 386 SysV.3
Date: 30 Jun 88 17:31:39 GMT
Keywords: drivers
To:       info-unix@brl-sem.arpa

Then I suppose you shouldn't teach them vi either.  I don't know vi,
I have never used it.  I've been doing UNIX since 1977.  I went straight
from /bin/ed to EMACS.  If I can't find EMACS on a machine, I use ed.
It means that I am a true master of regular expressions.  By the way,
EMACS is available on machines other than UNIX ones, which makes it
more advantageous than vi.  Remember EMACS started on DEC-10's.

-Ron

-----------------------------

From: Mitchell Wyle <wyle@solaris.uucp>
Subject: Re: plot, graph (summary)
Date: 29 Jun 88 10:37:55 GMT
To:       info-unix@SEM.BRL.MIL


Last week, I asked for plot(1) enhancements:
 ...
>and graph(1) always puts a key at the bottom left of how he scaled the
>graph.  The home-grown packages here are too applications specific.
>I'm looking for a robust scatter-plot package.
>
>I don't have and therefore haven't looked at: gnuplot, graph+,
>crc_plot, vplot, quickplot, or lplot.  If anyone (preferably in Europe)
>uses any of these PD packages, and knows it's what I want, I would
>appreciate his sending it my way.

I received the obligatory me-too's and am therefore posting a summary.

---Bill Jones <mcvax!calgary!vaxb!jonesb@cernvax.uucp> said:
You might want to check out "S", a language for data analysis available
from Bell Labs.  It's an interactive system which allows you to define
datasets, perform analysis on them, then produce graphical output using
many different styles.  My memory says (and you should verify this
before posting) that the price for source code is around $10000 for
commercial users, $100 for educational institutions.

---Marc Majka <mcvax!ubc-cs!majka@cernvax.uucp> said:
Hello.  I have recently written a scatterplot program which runs on
top of a superset of the UNIX plot(5) format, known as Superplot.  I
think that you may have Superplot there already.  Contact Gladys Wong
<wong@ethz.uucp> or phone her: 256 52 33 and see if she has Superplot.
If you would like the scatterplot program, I can mail it to you.  It
needs the Superplot layer to draw labels.  If you want the whole package
(It comes with Gnuplot and other goodies), send me a tape, self-addressed
mailer, and CAN$10 for postage.  I can put it on a small reel of tape
(600 foot) at 800, 1600, or 6250 BPI, or on a SUN cartridge tape.

I queried the csnet sources server and got crc_plot which satisfies the
need here.  The Makefiles and .h files are weak, but the package
compiles with no .c code changes on Sun OS EXPORT.  The language
interfaces look strong, and I have tested "qplot" with success.  The
plot3d program looks exciting as well. Thank you Rich Kulawiec!  For
those unfamiliar with Rich's crc plot package, here are excerpts from
the README:

---Rich Kulawiec, rsk@j.cc.purdue.edu writes:
The CRC plotting package is a device independent graphics system.
It includes subroutines for generating graphics which may be called
from Fortran or C, a two-dimensional plotting utility, and a
three-dimensional plotting utility.

The CRC package was originally developed at the Purdue University School
of Electrical Engineering by Carl Crawford; additional work has been
contributed by Mani Azimi and Malcolm Slaney, notably "plot3d".  This
software has been in use locally for several years, and so most of the
obvious bugs have hopefully been caught and fixed.  Although nobody's
willing to promise to fix future bugs immediately, it is not unreasonable
to assume that this package will continue to be supported, so please
do report bugs.  (If you like, send them to me, and I'll forward them
to the folks at EE.)  HOWEVER, no guarantees, folks.

This software has been developed on Vaxen running 4.XBSD; it's likely that
it will work on most machines running some variant of 4.XBSD.  The two
user programs contained herein (qplot and plot3d) are probably of some use
to folks who need quick plots with reasonable resolution and labels
and annotation and so on without a lot of bother.  Nice features of qplot
and plot3d include the ability to overlay multiple plots, tolerance of
a lot of different data formats, automatic or explicit scaling, logarithmic
plotting, ability to plot "bar graphs", and adjustable surface tilt (plot3d).

Thank you all for the replies, advice, etc.  Long live usenet!
-Mitch (wyle%ifi.ethz.ch@relay.cs.net)

--
-Mitchell F. Wyle            wyle@ethz.uucp
Institut fuer Informatik     wyle%ifi.ethz.ch@relay.cs.net
ETH Zentrum
8092 Zuerich, Switzerland    +41 1 256-5237

-----------------------------

From: Steve Schlesinger <steves@ncr-sd.sandiego.ncr.com>
Subject: OSF v. ATT/Sun :-)
Date: 30 Jun 88 19:32:19 GMT
To:       info-unix@brl-sem.arpa

Going from ATT/Sun control of Unix to OSF is like going
from the Shah to the Ayatolluh.

    (attributed to an anonymous Unisys employee).

-----------------------------

From: Greg Hackney <hack@bellboy.uucp>
Subject: Re: UUCP Over TCP/IP
Date: 30 Jun 88 17:57:39 GMT
Keywords: uucp, uucpd, bsd4.3
To:       info-unix@SEM.BRL.MIL

In article <175@chip.UUCP> mparker@chip.UUCP (M. D. Parker) writes:
>In bits of the BSD documentation, there is a mention of the TCP/IP UUCP server
>deamon (i.e. /etc/uucpd).  My question is if you are the sending party, how
>do you tell the system to use the UUCP protocol?   I find nothing in this
>in connection with the L.sys file, in fact, I have really found nothing at
>all.
>Can anybody enlighten me on /etc/uucpd and its operation, invokation, etc.?

On my Pyramid, it is set up like this in the L.sys file:

sitename Any TCP uucp sitename in:--in: nuucp password: hispassword

The site I send to is a Unisys system that doesn't have the /etc/uucpd
daemon, but does have telnet, so I use:

sitename Any TCP telnet sitename in:--in: nuucp password: hispassword

--
Greg

-----------------------------

From: "J. Steven Harrison" <jsh0@isg300.uucp>
Subject: Rn on a V.3 machine
Date: 30 Jun 88 15:30:53 GMT
To:       info-unix@brl-sem.arpa

I thought I would ask the net before diving into the code of rn about this
first.

Standard distribution tapes on AT&T V.3 machines with more than 1 drive
sets up the user file system on the second drive with root, swap, etc on
the first drive.

It seems that in the file util.c getwd only works for root on the root
partition (drive 1) without getting the error "getwd:  read error in ..".
If run as root from the second drive as root you get the same error and
if run as any user on the system (that doesn't have uid=0) the same error
also results.

Has anyone already solved this problem??  We are running on AT&T 3B2 600's,
700's and a 4000.

Thanks in advance for any help.


Steven Harrison
VP Programming/Support
Information Systems Group Inc.,  San Diego, CA
(619) 234-3405
{nitro!isg100, ucsdhub}!jack!steve

-----------------------------

From: "Larry W. Virden" <lwv@n8emr.uucp>
Subject: NFS/YP alternative
Date: 30 Jun 88 17:28:08 GMT
To:       info-unix@brl-sem.arpa


I have two questions.  First, can anyone explain why Yellow Pages requires
the files served to be in a DBM format?  Secondly, does anyone know of a similar
service that could be used for non-dbm files?  For instance, if for
 administrative
reasons I did NOT want to NFS mount the /usr/man and /usr/local/man pages but
instead distribute them in a manner similar to Yellow Pages, what could I do to
achieve this?

Thanks!

--
Larry W. Virden     75046,606 (CIS)
674 Falls Place, Reynoldsburg, OH 43068 (614) 864-8817
osu-cis!n8emr!lwv (UUCP)    osu-cis!n8emr!lwv@TUT.CIS.OHIO-STATE.EDU (INTERNET)
We haven't inherited the world from our parents, but borrowed it from our
 children.

-----------------------------

From: "The Resource, Poet of Quality" <bicker@hoqax.uucp>
Subject: MKS Toolkit/UNIX [r] System, SEA ARC/PKARC, ...
Date: 30 Jun 88 12:34:29 GMT
Keywords: AT&T, lawsuit, CSS, PC/Tools, PC/VI
To:       info-unix@brl-sem.arpa

> In article <166@skep2.ATT.COM>, wcs@skep2.ATT.COM (Bill.Stewart.<ho95c>)
 writes:
> > b) MKS has ported some UNIX tools and reimplemented others and is presumably
> >     following the rules for the products they use,

This raises a question in my mind in light of all the talk about
SEA suing PK Ware over the "look" of the archive tools.  If SEA has
a case doesn't AT&T?

--
/kohn/brian.c      AT&T Bell Laboratories Semantic Engineering Center
The Resource, Poet of Quality   ...ihnp4!hoqam!bicker  (201) 949-5850
"It is useless for sheep to pass resolutions in favor of vegetarianism
while wolves remain of a different opinion." - Wm. Ralph Inge, D.D.

-----------------------------

From: These terminals don't do umlauts!? <greywolf@unisoft.uucp>
Subject: Re: how can I "." in csh?
Date: 30 Jun 88 19:17:24 GMT
To:       info-unix@brl-sem.arpa

In article <3513@ncrcae.Columbia.NCR.COM> rogerc@ncrcae.Columbia.NCR.COM (Roger
 Collins) writes:
: In csh, is there an easy way to duplicate the function of Bourne's "."
: command?  I want to input commands from a file and have them
: change the current layer's environment.

How about:

    alias . source

Of course, source doesn't look along a path, so we have to hack this a bit.

    alias . 'source `ffo \!*`'

----
#! /bin/csh -f
# (well, why not csh if you're going to be using '.' like bourne shell, but
# using csh instead?)
# ffo:  find first occurrence of a file along the path

foreach i ( $argv )
    foreach i ( $path )
        if ( -e $path/$argv ) then
            echo $path/$argv
            exit
        endif
    end
end


: --
: Roger Collins
: NCR - E&M Columbia
: rogerc@ncrcae.Columbia.NCR.COM


--
 ** All views expressed herein are my own and not those of UniSoft Corp. **
# Re: removing -c from diff and adopting NIH attitude:  See Figure 1.     #
# Roan (RO-an) Anderson, UniSoft Corporation, (415) 420-6400 x 165.      #
# ...sun!unisoft!greywolf # /harley/davidson: Mount device busy.###########

-----------------------------

From: Eric Varsanyi <ewv@zippy.berkeley.edu>
Subject: Re: Question: Driver access to memory mapped devices on 386 SysV.3
Date: 1 Jul 88 02:29:06 GMT
Sender: usenet@agate.berkeley.edu
Keywords: drivers
To:       info-unix@brl-sem.arpa

In article <1196@award.UUCP> brian@apt.UUCP (Brian Litzinger) writes:
>I am running Microport Unix System V.3 on a discrete 386. I have
>successfully written drivers to control various I/O space mapped
>hardware devices.  However, I cannot access the memory space of
>a memory mapped device that I have.
>
>My documentation doesn't cover sptalloc, spbyte & fpbyte which were used
>in the Hercules driver. An explanation of these might solve my problem.

There is actually 1 lone man page in the software development set that
sort of explains these. In writing a driver for a board that uses
exclusively memory mapped IO, I used sptalloc for a couple of things:

#include <sys/types.h>
#include <sys/immu.h>
#include <sys/param.h>

extern char *sptalloc();

[ during init routine... ]

    /* Allocate and build the free list */

    npages = (dxnbuf*sizeof(struct dqe))/4096+1; /* Pages to get    */
    DBGMISC(printf("dxinit: Allocating %d pages via sptalloc\n",npages));
    if ((cdqe = (struct dqe *) sptalloc(npages,PG_P,NULL,NOSLEEP))==NULL) {
        printf("dxinit: Buffer allocate failed, will not initialize\n");
        return;
    }

[ This first part grabs memory from the system memory map for IO buffer,
  I didn't want to use buffers from the buffer pool since these buffers
  sometimes have to hang out for a long time.

  The PG_P gives the type of memory we want (always use PG_P), the NULL means
  we want memory from the system memory map (not a particular address), and
  the NOSLEEP means don't wait if its not available (its always available)

  The driver goes on to build a free list with its freshly allocated memory,
  then... ]

    /* Map boards in and initialize them */
    for (cnt=0; cnt<dxnbrd; cnt++) {
        if ( (
        dxbrd[cnt].base=(struct srcp *)sptalloc(2,PG_P,dxbase[cnt], 0)
             ) == NULL) {
            printf("Error mapping physical/virtual memory\n");
        } else {            /* Initialize board */
            dxbinit(&dxbrd[cnt]);
        }
    }

[ This loops through the all the boards (there can be more than 1 in a
  system) and maps their physical (dxbase[cnt]) memory into kernel
  virtual memory. The base is the physical PAGE number we want to map:
  0xD0 would point to D000:0000 (or D0000 for you linear folks)
  The 2 is the number of pages I want to map, and the NOSLEEP parameter
  has no meaning here, so I set it to 0
  When this loop finishes, I can get to the board memory via:
    dxbrd[cnt].base->xyzzy    (Where xyzzy is some register I want
                   to talk to)
]

>I particularly like the idea of obtaining a pointer to the memory mapped
>space of my device and using val=*(base+offset) and *(base+offset)=val
>for reading and writing.  However, I have had only PANICs so far.

No problem, instead of using a structure, get the kv address to a character
pointer, then have fun with *xx+yy=c all you like.

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster%TRINCC.BITNET@mitvma.mit.edu (PMDF Mail Server) (07/09/88)

The message could not be delivered to:

Addressee: TRIN4
Reason:
  %MAIL-E-SYNTAX, error parsing 'DJA1::[TRIN4.BOX1024]'

----------------------------------------

Received: from JNET-DAEMON by TRINCC.BITNET; Mon, 4 Jul 88 04:06 EST
Received: From YALEVM(MAILER) by TRINCC with Jnet id 4462 for TRIN4@TRINCC;
 Mon,  4 Jul 88 04:04 EST
Received: by YALEVM (Mailer X1.24) id 4459; Mon, 04 Jul 88 04:01:18 EST
Date: Wed, 29 Jun 88 02:45:52 EST
From: Mike Muuss The Moderator <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V5#083
Sender: Info-Unix distribution list <I-UNIX@TCSVM.BITNET>
To: Robert Cummings <TRIN4@TRINCC.BITNET>
Reply-to: INFO-UNIX@BRL.ARPA
Comments: To: INFO-UNIX@BRL.ARPA

INFO-UNIX Digest          Wed, 29 Jun 1988              V5#083

Today's Topics:
                       Re: Bliss Compiler wanted
                     Re: bbs for unix based systems
             Re: Real-time UNIX - what is it & who has it?
         Recommendations wanted for workstations and CASE tools
                       Re: "cd path" strangeness
                            Re: RCS and SCCS
            Re: HOW DO I MAKE VI'S AUTOINDENT NOT USE TABS?
      Shouting the return code. (Re: Meaning of "rc" in cron/log)
                       Re: how can I "." in csh?
    Re: Shouting the return code. (Re: Meaning of "rc" in cron/log)
        Re: Is a NEED for more COMMERCIAL usenet feed providers?
                      Re: AT&T vs. CSS (PC/Tools)
                               Tabs in VI
                      SLIP protocol specification
                       Termcap/Terminfo question
                            UUCP Over TCP/IP
                       Re: RCS and SCCS (and CMS)
                 Getting vi to automagically use macros
-----------------------------------------------------------------

From: Steve Simmons <simmons@applga.uucp>
Subject: Re: Bliss Compiler wanted
Date: 24 Jun 88 14:36:01 GMT
To:       info-unix@brl-sem.arpa

In article <315@gt-eedsp.UUCP> jensen@gt-eedsp.UUCP (P. Allen Jensen) writes:
>
>Is the CMU Bliss the same as the BLISS used by DEC ?

In '83 I was supporting some BLISS-10 utilities at ADP Network Services.
We ran into bugs in the DEC BLISS-10 compiler which DEC wouldn't fix.  We
had source, which was full of CMU names.  I went to CM to see if theirs
was PD, and if so, could we get it.  On doing some comparison, we found
that the DEC BLISS-10 compiler was absolutely identical to the CMU except
for a few bug fixes CMU had done since DEC picked it up.

About this time DEC came out with the BLISS-16, BLISS-32, and BLISS-36
compilers to be their "standard systems development language".  They
wanted a ludicrous amount of money for BLISS-36.  We ordered an evaluation
copy, and found it was absolutely identical to BLISS-10.  Same checksum.
And same support categore.  I forget the name, but it meant "We will
accept bug reports.  But we will take no action."

That's the way it was in '83.

Needless to say, we didn't buy BLISS-36.  If you can get BLISS from CMU
and you have a PDP-10 machine, do it.
--
+- Steve Simmons            UNIX Systems Mgr.         Schlumberger CAD/CAM -+
+  simmons@applga.uucp                              ...umix!applga!simmons  +
+- "Opinions expressed are all my own, etc, etc, etc, etc, etc, etc, etc." -+

-----------------------------

From: Karl Meiser <koala@ddsw1.uucp>
Subject: Re: bbs for unix based systems
Date: 24 Jun 88 19:41:55 GMT
To:       info-unix@brl-sem.arpa


I myself should be suggesting my own work,  premature as it is.  Currently
i am working on a message system (run from the shell) but it is no where
near complete.

I will however suggest AKCS.  Infact,  the system i am currently at is
the home of AKCS.  This software has linking prgs, etc, so that you can
connect systems together by sending new items back and forth.  This
system currently connects 4 systems,  and the more the better.  For more
information,  contact Karl Denniger at (312)566-8909 voice,  (312)566-8911
or (312)566-8912 for the system.  You can also send mail to ..!ddsw1!karl


--

Karl Meiser    ..!att!spl1!ddsw1!koala

I said that??  I musta been sleeping!

-----------------------------

From: Ian Kluft <kluft@hpcupt1.hp.com>
Subject: Re: Real-time UNIX - what is it & who has it?
Date: 24 Jun 88 20:34:30 GMT
To:       info-unix@SEM.BRL.MIL

/ adamm@necis.UUCP (Adam Moskowitz) / writes:
> A friend of mine has asked to help him locate a "real-time UN*X or UN*X-like
> operating system".
 [ ... ]
>     Assuming that you are doing something like data acquisition or
>     process control, what is required to make an O/S "real-time"?
>
> The answer he and I came up with was this: the ability to have absolute
> control over the scheduling of processes.

Two issues to note when looking for a real-time OS are
   kernel pre-emption
   context switching time

Kernel pre-emption is an important one to consider on Unix because most
Unix systems do not allow system calls to be interrupted.  Of course,
context-switching time is somewhat obvious because it affects the time
between arrival of an interrupt and (re)starting a user process to handle
the event.

That's really what it comes down to.  If a guarantee can be made of the
amount of time it takes between an event and entering the code to handle
it, an OS is considered real-time.  Of course, if that time is too long,
it isn't worth mentioning.

[End of unbiased material]

While everyone was mentioning the real-time Unix's they knew of, I thought
I'd mention the one I work with.  Hewlett-Packard's HP-UX is a full System
V with extentions for BSD 4.2 and real-time.  While I don't have the exact
numbers for measured real-time response, I remember that they are measured
in milliseconds, as would be expected.

 ------------------------------------------------------------
    Ian Kluft            RAS Lab
    hplabs!hprasor!kluft    HP Network Systems Group
    kluft@hpda.hp.com        Cupertino, CA
 ------------------------------------------------------------

-----------------------------

From: John Coughlin <jc@sce.uucp>
Subject: Recommendations wanted for workstations and CASE tools
Date: 25 Jun 88 16:20:27 GMT
To:       info-unix@SEM.BRL.MIL


    Our company will soon be purchasing a number of workstations
for use in software development with CASE tools. We are currently
considering Apollo or Sun machines and I would appreciate any
recommendations.


 ----------------------------------------------------------------------
Paul Burry                      UUCP:   sce!jc
Dy4 Systems Inc.                PHONE:  (613)-596-9911
21 Credit Union Way,
Nepean, Ontario
Canada  K2H 9G1
 ----------------------------------------------------------------------

-----------------------------

From: Geoff Rimmer <maujd@warwick.uucp>
Subject: Re: "cd path" strangeness
Date: 26 Jun 88 22:31:54 GMT
Sender: news@warwick.uucp
Keywords: csh cd xenix sysv
To:       info-unix@brl-sem.arpa

In article <922@.UUCP> jbush@ficc.UUCP (james bush) writes:
>In article <337@vector.UUCP>, chip@vector.UUCP (Chip Rosenthal) writes:
>> Here is a wierd one.  In csh, move to some directory which doesn't have
>> a "path" subdirectory.  Then type either "cd path" or "chdir path".
>>
>> The expected response would be "path: No such file or directory."  Instead,
>> no message is issued, and either you stay where you were or you move to
>> $path[1]...
>
>This is even more wierd. I tried it on our Intel Xenix system, and it worked
>as you said when I did it under my login.  However, when I tried to show it
>to my friend under his id, it came up with the "expected" error message! I
>am not sure what the difference is.

Perhaps he uses Bourne shell?

extravagent_prompt % sh
$ cd path
path: bad directory
$

No flames please - term finishes in under a week - so I won't be here
to read them 8-)

Geoff.

>James Bush, Ferranti, Houston                         Praise the Lord
>Internal address: jbush  extension 5230, mail stop A/3204, room A/3602
>External address: ..!uunet!nuchat!sugar!ficc!jbush

    -----------------------------------------------------------------
    Geoff Rimmer, Computer Science, Warwick University, UK.
            maujd@uk.ac.warwick.opal

    "I do SMILE humour - people aren't SUPPOSED to laugh."
    "Yeah, but they aren't supposed to throw heavy objects
     and shout 'Get off you boring bastard, we've heard better
                jokes on the speaking clock!'"

        - Filthy Rich and Catflap (BBC TV)
    (Get your local TV station to buy this excellent comedy series!!)
    -----------------------------------------------------------------

-----------------------------

From: Joel Clark <joel@intelisc.uucp>
Subject: Re: RCS and SCCS
Date: 27 Jun 88 17:28:47 GMT
To:       info-unix@brl-sem.arpa

In article <661@pyuxe.UUCP> mayerar@pyuxe.UUCP (80132-A Mayer) writes:
>In article <710@ubu.warwick.UUCP> maujd@warwick.UUCP (Geoff Rimmer) writes:
>>Which out of RCS and SCCS do people prefer?
>>
>>Geoff.
>
>One good point of RCS is that it stores the most recent version and
>uses deltas to get back to the previous versions.  SCCS stores the
>original version and uses deltas to get to the most recent version.
>
>        Andrew J. Mayer
>        BELLCORE
>
>{ariel,burl,clyde,floyd,gamma,harpo,ihnp4,mhuxl,rutgers}!pyuxe!mayerar

Even though I have written software with similar functionality as SCCS,
I have never understood this argument about storing the most recent
version as opposed to storing the original version.  For example given
the following actual SCCS file:


I 1
/*
 * module control port settings
 */
D 2
#define NPGM_DONE    0x01
E 2
I 2
#define RRCV        0x02
E 2
#define RLSRCV        0x02
#define    NPROGRAM    0x80
E 1

We see the original and the most recent stored in the same manor, line
by line.  Any program trying to a extract version still has to look at
every line to decide if that line is in the desired version or not.

Can anyone explain to me how a program could store `the most recent version`
such that each line in the file does not need to be examined to determine
if it is in the most recent version?

Joel Clark
Intel Scientific Computers            joel@intelisc.uucp.com
Beaverton, OR                {tektronix}!ogcvax!intelisc!joel
(503) 629 7732

-----------------------------

From: "David I. Berg" <dberg@cod.nosc.mil>
Subject: Re: RCS and SCCS
Date: 28 Jun 88 16:14:24 GMT
To:       info-unix@brl-sem.arpa

In article <710@ubu.warwick.UUCP>, maujd@warwick.UUCP (Geoff Rimmer) writes:
> Which out of RCS and SCCS do people prefer?  ..........
> .....  What are the good and bad points of each system?
>
I have used both systems, depending on which was available on the particular
computer I was using.  I find RCS particularly easier to use than SCCS.
In fact, in one case, I converted all my SCCS files to RCS using the
sccstorcs utility.  Another feature of RCS is that it stores the current
version of your file and the changes backward to the original, whereas
SCCS stores the original version of your file and the changes forward
to the current.  Therefore, it will take SCCS a trifle longer to produce
the current version than RCS.

-----------------------------

From: Eduardo Krell <ekrell@hector.uucp>
Subject: Re: RCS and SCCS
Date: 28 Jun 88 19:22:01 GMT
Sender: netnews@ulysses.homer.nj.att.com
To:       info-unix@SEM.BRL.MIL

In article <290@intelisc.UUCP> joel@intelisc.UUCP (Joel Clark) writes:

>Can anyone explain to me how a program could store `the most recent version`
>such that each line in the file does not need to be examined to determine
>if it is in the most recent version?

You store the most recent version at the beginning of the file in clear
text followed by the reverse delta to get the previous version
(followed by the reverse delta to get the version before that, etc.).

Time to get the latest version is thus proportional only to the size of
that version. Time to get version N is proportional to the size of
the last version plus the size of all deltas necessary to get from there
down to version N.

    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

    UUCP: {ihnp4,ucbvax}!ulysses!ekrell        ARPA: ekrell@ulysses.att.com

-----------------------------

From: Richard Harter <g-rh@cca.cca.com>
Subject: Re: RCS and SCCS
Date: 28 Jun 88 20:08:42 GMT
To:       info-unix@SEM.BRL.MIL

In article <290@intelisc.UUCP> joel@intelisc.UUCP (Joel Clark) writes:

>Can anyone explain to me how a program could store `the most recent version`
>such that each line in the file does not need to be examined to determine
>if it is in the most recent version?

There are two different ways that I know of to do this.  One is the way RCS
does it.  When the file is updated the delta is calculated in terms of carrying
the latest version to the previous version.  The delta is appended to the stored
deltas, and the previous version is replaced by the updated version.  I can't
give you the details on the other way (it is proprietary to ADC) but the
essence of the matter is the information about the lines do not have to be
stored with the lines.

--

In the fields of Hell where the grass grows high
Are the graves of dreams allowed to die.
    Richard Harter, SMDS  Inc.

-----------------------------

From: Joe Bob Willie <haugj@pigs.uucp>
Subject: Re: RCS and SCCS
Date: 28 Jun 88 21:46:14 GMT
To:       info-unix@brl-sem.arpa

In article <29975@cca.CCA.COM>, g-rh@cca.CCA.COM (Richard Harter) writes:
> It is true, however, that there is, in principle, a signifigant performance
> advantage for the RCS scheme versus the SCCS scheme.  SCCS must process
> all lines including those not currently active; RCS need only process those
> that are currently active.  Furthermore RCS does not need to do any processing
> on the line other than copying it out; SCCS has to check the control data
> for the line.  On the other hand, RCS pays a penalty if the version being
> extracted is not the latest.
> --
>     Richard Harter, SMDS  Inc.

[ In the Oil Fields of HELL,
    Where the drought grows long and HOT ]

OK - I'll bite, and I'm sure others will also.  What exactly does an
RCS file look like.  I'm a die-hard SCCS junkie.  How about a few
specific examples for those of us without RCS or RCS documentation.

- John.
--
 The Beach Bum                                 Big "D" Home for Wayward Hackers
 UUCP: ...!killer!rpp386!jfh                          jfh@rpp386.uucp :SMAILERS

 "You are in a twisty little maze of UUCP connections, all alike" -- fortune

-----------------------------

From: Clark Morgan <clarkm@tekig4.tek.com>
Subject: Re: HOW DO I MAKE VI'S AUTOINDENT NOT USE TABS?
Date: 28 Jun 88 07:53:13 GMT
To:       info-unix@SEM.BRL.MIL

?In article <1219@bakerst.UUCP> kathy@bakerst.UUCP (Kathy Vincent) writes:
>In article <2965@tekig4.TEK.COM> clarkm@tekig4.UUCP I whine:
>
>    ....about Vi putting tabs in my files....
>
?I'm coming in late to this discussion, so if I missed something,
?well, sorry.
?
?But there *is* an option that says not to auto-tab.
?
?I use vi all the time - using SVR2 and SVR3 on 3B20s, and using
?3.5 UNIX on my on my UNIX PC.  I never get any tabs I don't explicitly
?ask for.
?
?I did a
?
?    :se all
?
?to check the settings I have when I'm working, and included in the
?list is one
?
?    noautoindent
?
?That must be the default on all the systems I work on because I don't
?ever set up anything.
          ....
?
?Kathy Vincent ------>  {ihnp4|att|codas|pacbell}!bakerst!kathy
?              ------>  { favourite AT&T gateway }!wruxh!unix

====================================================================
Um Kathy, I want autoindent + NO TABS (for C programs and the like).
====================================================================

--
Clark Morgan, Tektronix Lab Instruments Engineering  (503) 627-3545
clarkm@tekig4.LEN.TEK.COM  |  {...,decvax,uw-beaver}!tektronix!tekig4!clarkm
US Mail: Tektronix, P.O. Box 500, DS 39-087, Beaverton, OR  97077

-----------------------------

From: Felix Lee <flee@gondor.cs.psu.edu>
Subject: Shouting the return code. (Re: Meaning of "rc" in cron/log)
Date: 28 Jun 88 11:08:37 GMT
Sender: news@psuvax1.cs.psu.edu
To:       info-unix@SEM.BRL.MIL

Does ksh let you put the return code in the prompt? Something like
PS1='($?) '?  Showing only non-zero return codes would be better.

Return codes are interesting.  Really.  IBM's VM/CMS will tell you about
non-zero return codes.  (The prompt is either 'R;' or 'R(nnn);')

Unix hides return codes well.  Ever try unconfusing someone about why
"true" is "exit 0", but "false" is "exit 1"?

Maybe if the shell shouted the return code, more programs would return
interesting codes.  (lament) Where are the return codes for fsck
documented?  Why does "strings" return -40?  Why does "od" return 10?
--
Felix Lee    flee@gondor.cs.psu.edu    *!psuvax1!gondor!flee

-----------------------------

From: "Wolf N. Paul" <wnp@dcs.uucp>
Subject: Re: how can I "." in csh?
Date: 28 Jun 88 12:32:45 GMT
To:       info-unix@brl-sem.arpa

In article <3513@ncrcae.Columbia.NCR.COM> rogerc@ncrcae.Columbia.NCR.COM (Roger
 Collins) writes:
 >In csh, is there an easy way to duplicate the function of Bourne's "."
 >command?  I want to input commands from a file and have them
 >change the current layer's environment.

The csh command you want is called "source". Thus, "source .login" is
roughly equivalent to the Bourne/Korn shell command ". .profile".
--
Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101
UUCP:     killer!dcs!wnp                 ESL: 62832882
DOMAIN:   wnp@dcs.UUCP                   TLX: 910-380-0585 EES PLANO UD

-----------------------------

From: Bob Mende Pie <mende@porthos.rutgers.edu>
Subject: Re: how can I "." in csh?
Date: 28 Jun 88 14:03:12 GMT
To:       info-unix@SEM.BRL.MIL

In article <3513@ncrcae.Columbia.NCR.COM> rogerc@ncrcae.Columbia.NCR.COM (Roger
 Collins) writes:
> In csh, is there an easy way to duplicate the function of Bourne's "."
> command?  I want to input commands from a file and have them
> change the current layer's environment.

  The command you want is source.


                    /Bob...
--
{...}!rutgers!mende      mende@aramis.rutgers.edu       mende@zodiac.bitnet

YOU can't talk, your SHIRT is BROKEN.

-----------------------------

From: Lloyd Zusman <ljz@fxgrp.uucp>
Subject: Re: how can I "." in csh?
Date: 28 Jun 88 20:05:42 GMT
To:       info-unix@brl-sem.arpa

In article <129@dcs.UUCP> wnp@dcs.UUCP (Wolf N. Paul) writes:
  In article <3513@ncrcae.Columbia.NCR.COM> rogerc@ncrcae.Columbia.NCR.COM
(Roger Collins) writes:
   >In csh, is there an easy way to duplicate the function of Bourne's "."
   >command?  ...

  The csh command you want is called "source". Thus, "source .login" is
  roughly equivalent to the Bourne/Korn shell command ". .profile".

 ... and you can even get a bona fide "." command in csh by means of
an alias:

    alias . source

 ... would do the trick.  You'd probably want to put this in your .cshrc
file.

--
  Lloyd Zusman                          UUCP:   ...!ames!fxgrp!ljz
  Master Byte Software              Internet:   ljz%fx.com@ames.arc.nasa.gov
  Los Gatos, California               or try:   fxgrp!ljz@ames.arc.nasa.gov
  "We take things well in hand."

-----------------------------

From: "Lawrence V. Cipriani" <lvc@tut.cis.ohio-state.edu>
Subject: Re: Shouting the return code. (Re: Meaning of "rc" in cron/log)
Date: 28 Jun 88 14:46:42 GMT
To:       info-unix@SEM.BRL.MIL

In article <3671@psuvax1.cs.psu.edu>, flee@gondor.cs.psu.edu (Felix Lee) writes:
> Does ksh let you put the return code in the prompt? Something like
> PS1='($?) '?
Yes, this PS1 displays the exit value of the "previous command".  $? will
change value on an interrupt however.

>  Showing only non-zero return codes would be better.
Why?  Knowing a command completed successfully might be useful if
stdout/stderr for the command were redirected.

> Return codes are interesting.  Really.  IBM's VM/CMS will tell you about
> non-zero return codes.  (The prompt is either 'R;' or 'R(nnn);')
Return codes are boring.  Really.

> Unix hides return codes well.
If you need them you can get them, if you don't want to see them you
don't have to.  I bet you don't have this flexibility in IBM's VM/CMS.

My feeling is the shorter my PS1 prompt the better.  There was a time
when my PS1 included my login id, the machine name I was logged in on,
the time of day (you can do this in ksh), and even some graphics
sequences.  After a few weeks I changed it all back to just the machine
name (since I will simultaneously be logged in several systems).

>Ever try unconfusing someone about why
> "true" is "exit 0", but "false" is "exit 1"?
Yeah, and read the man page for true/false to them, it always gets
funny looks, and usually some laughs after you explain it to them.
    ...
> Felix Lee    flee@gondor.cs.psu.edu    *!psuvax1!gondor!flee
--
Larry Cipriani, AT&T Network Systems and Ohio State University
Domain: lvc@tut.cis.ohio-state.edu
Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (strange but true)

-----------------------------

From: "William E. Davidsen Jr" <davidsen@steinmetz.ge.com>
Subject: Re: Is a NEED for more COMMERCIAL usenet feed providers?
Date: 28 Jun 88 16:44:39 GMT
To:       info-unix@SEM.BRL.MIL

In article <317@ditka.UUCP> kls@ditka.UUCP (Karl Swartz) writes:

| Greg, I know this isn't exactly what you had in mind, but what about
| a west coast uunet?  While helping a (non-local) friend look into
| news feed options, I realized that uunet costs a *lot* more for west
| coast folks than those who are closer.  This is based on a TrailBlazer

  For low budget sites, uunet can be reached by PC Pursuit and Dial
America service. This keeps the cost way down. If you need to send stuff
during the day, of course, you will still be faced with a stiff bill. If
you are looking for a local feed, rather than the gateway features uunet
provides, you should be able to find one almost anywhere. I think portal
will feed anyone on the west coast for a price, but I have no idea what
that price is.
--
    bill davidsen        (wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me

-----------------------------

From: Keith Ericson <keithe@tekgvs.tek.com>
Subject: Re: AT&T vs. CSS (PC/Tools)
Date: 28 Jun 88 18:46:18 GMT
Keywords: AT&T, lawsuit, CSS, PC/Tools, PC/VI
To:       info-unix@SEM.BRL.MIL

In article <142@wash08.UUCP> txr98@wash08.UUCP (Timothy Reed) writes:
>A friend at ATT told me last year that ATT owned more than afew copies
>of the MKS toolkit on DOS PCs at most of their sites in Jersey.  If MKS
>didn't license unix from ATT, would that be considered tacit approval?
>

Never assume that any one part of a large organization even knows,
much less approves, of what another department, section, group or
whatever is doing.

keith

-----------------------------

From: The Silent Killer <patkar@cb.ecn.purdue.edu>
Subject: Tabs in VI
Date: 28 Jun 88 19:01:17 GMT
To:       info-unix@brl-sem.arpa


> ====================================================================
> Um Kathy, I want autoindent + NO TABS (for C programs and the like).
> ====================================================================

The way I do it is by using the unix utility 'expand' from within
'VI'.  I know this does not prevent insertion of tabs, but it at least
removes them once you have used the command

!<movement command>expand

The <movement command> may be (, {, 1G etc.  In writing LISP functions,
for example, I find the command '!%expand' very useful.


Anant Patkar.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         o
__________________  ____________________________
/ ) |    |   ___|    |   | |    _|    __|_    /     | patkar@ecn.purdue.edu
 ---| o--|  (   |    `___| |   '     '__| ) o/      | patkar@purche.BITNET
\_) |    |   \  |        | |   `--      |     \

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-----------------------------

From: Lyndon Nerenberg <lyndon@ncc.nexus.ca>
Subject: SLIP protocol specification
Date: 28 Jun 88 20:11:23 GMT
To:       info-unix@SEM.BRL.MIL

Lately there have been a number of requests for a description of
the SLIP encapsulation scheme for sending IP packets over serial
links. SRI has (finally :-) issued an RFC describing how this is
currently implemented. It's only six pages long, so I've attached
a copy. Apologies if you've already seen this.

(cut the .signature at the end)

--lyndon  VE6BBM

 -----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
Network Working Group                                          J. Romkey
Request for Comments: 1055                                     June l988

 A NONSTANDARD FOR TRANSMISSION OF IP DATAGRAMS OVER SERIAL LINES: SLIP

INTRODUCTION

   The TCP/IP protocol family runs over a variety of network media:
   IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines,
   satellite links, and serial lines.  There are standard encapsulations
   for IP packets defined for many of these networks, but there is no
   standard for serial lines.  SLIP, Serial Line IP, is a currently a de
   facto standard, commonly used for point-to-point serial connections
   running TCP/IP.  It is not an Internet standard.  Distribution of
   this memo is unlimited.

HISTORY

   SLIP has its origins in the 3COM UNET TCP/IP implementation from the
   early 1980's.  It is merely a packet framing protocol: SLIP defines a
   sequence of characters that frame IP packets on a serial line, and
   nothing more. It provides no addressing, packet type identification,
   error detection/correction or compression mechanisms.  Because the
   protocol does so little, though, it is usually very easy to
   implement.

   Around 1984, Rick Adams implemented SLIP for 4.2 Berkeley Unix and
   Sun Microsystems workstations and released it to the world.  It
   quickly caught on as an easy reliable way to connect TCP/IP hosts and
   routers with serial lines.

   SLIP is commonly used on dedicated serial links and sometimes for
   dialup purposes, and is usually used with line speeds between 1200bps
   and 19.2Kbps.  It is useful for allowing mixes of hosts and routers
   to communicate with one another (host-host, host-router and router-
   router are all common SLIP network configurations).

AVAILABILITY

   SLIP is available for most Berkeley UNIX-based systems.  It is
   included in the standard 4.3BSD release from Berkeley.  SLIP is
   available for Ultrix, Sun UNIX and most other Berkeley-derived UNIX
   systems.  Some terminal concentrators and IBM PC implementations also
   support it.

   SLIP for Berkeley UNIX is available via anonymous FTP from
   uunet.uu.net in pub/sl.shar.Z.  Be sure to transfer the file in
   binary mode and then run it through the UNIX uncompress program. Take



Romkey                                                          [Page 1]

RFC 1055                     Serial Line IP                    June 1988


   the resulting file and use it as a shell script for the UNIX /bin/sh
   (for instance, /bin/sh sl.shar).

PROTOCOL

   The SLIP protocol defines two special characters: END and ESC. END is
   octal 300 (decimal 192) and ESC is octal 333 (decimal 219) not to be
   confused with the ASCII ESCape character; for the purposes of this
   discussion, ESC will indicate the SLIP ESC character.  To send a
   packet, a SLIP host simply starts sending the data in the packet.  If
   a data byte is the same code as END character, a two byte sequence of
   ESC and octal 334 (decimal 220) is sent instead.  If it the same as
   an ESC character, an two byte sequence of ESC and octal 335 (decimal
   221) is sent instead.  When the last byte in the packet has been
   sent, an END character is then transmitted.

   Phil Karn suggests a simple change to the algorithm, which is to
   begin as well as end packets with an END character.  This will flush
   any erroneous bytes which have been caused by line noise.  In the
   normal case, the receiver will simply see two back-to-back END
   characters, which will generate a bad IP packet.  If the SLIP
   implementation does not throw away the zero-length IP packet, the IP
   implementation certainly will.  If there was line noise, the data
   received due to it will be discarded without affecting the following
   packet.

   Because there is no 'standard' SLIP specification, there is no real
   defined maximum packet size for SLIP.  It is probably best to accept
   the maximum packet size used by the Berkeley UNIX SLIP drivers: 1006
   bytes including the IP and transport protocol headers (not including
   the framing characters).  Therefore any new SLIP implementations
   should be prepared to accept 1006 byte datagrams and should not send
   more than 1006 bytes in a datagram.

DEFICIENCIES

   There are several features that many users would like SLIP to provide
   which it doesn't.  In all fairness, SLIP is just a very simple
   protocol designed quite a long time ago when these problems were not
   really important issues.  The following are commonly perceived
   shortcomings in the existing SLIP protocol:

      - addressing:

         both computers in a SLIP link need to know each other's IP
         addresses for routing purposes.  Also, when using SLIP for
         hosts to dial-up a router, the addressing scheme may be quite
         dynamic and the router may need to inform the dialing host of



Romkey                                                          [Page 2]

RFC 1055                     Serial Line IP                    June 1988


         the host's IP address.  SLIP currently provides no mechanism
         for hosts to communicate addressing information over a SLIP
         connection.

      - type identification:

         SLIP has no type field.  Thus, only one protocol can be run
         over a SLIP connection, so in a configuration of two DEC
         computers running both TCP/IP and DECnet, there is no hope of
         having TCP/IP and DECnet share one serial line between them
         while using SLIP.  While SLIP is "Serial Line IP", if a serial
         line connects two multi-protocol computers, those computers
         should be able to use more than one protocol over the line.

      - error detection/correction:

         noisy phone lines will corrupt packets in transit. Because the
         line speed is probably quite low (likely 2400 baud),
         retransmitting a packet is very expensive.  Error detection is
         not absolutely necessary at the SLIP level because any IP
         application should detect damaged packets (IP header and UDP
         and TCP checksums should suffice), although some common
         applications like NFS usually ignore the checksum and depend on
         the network media to detect damaged packets.  Because it takes
         so long to retransmit a packet which was corrupted by line
         noise, it would be efficient if SLIP could provide some sort of
         simple error correction mechanism of its own.

      - compression:

         because dial-in lines are so slow (usually 2400bps), packet
         compression would cause large improvements in packet
         throughput. Usually, streams of packets in a single TCP
         connection have few changed fields in the IP and TCP headers,
         so a simple compression algorithms might just send the changed
         parts of the headers instead of the complete headers.

   Some work is being done by various groups to design and implement a
   successor to SLIP which will address some or all of these problems.












Romkey                                                          [Page 3]

RFC 1055                     Serial Line IP                    June 1988


SLIP DRIVERS

   The following C language functions send and receive SLIP packets.
   They depend on two functions, send_char() and recv_char(), which send
   and receive a single character over the serial line.

   /* SLIP special character codes
    */
   #define END             0300    /* indicates end of packet */
   #define ESC             0333    /* indicates byte stuffing */
   #define ESC_END         0334    /* ESC ESC_END means END data byte */
   #define ESC_ESC         0335    /* ESC ESC_ESC means ESC data byte */

   /* SEND_PACKET: sends a packet of length "len", starting at
    * location "p".
    */
   void send_packet(p, len)
           char *p;
           int len; {

     /* send an initial END character to flush out any data that may
      * have accumulated in the receiver due to line noise
      */
        send_char(END);

     /* for each byte in the packet, send the appropriate character
      * sequence
      */
           while(len--) {
                   switch(*p) {
                   /* if it's the same code as an END character, we send a
                    * special two character code so as not to make the
                    * receiver think we sent an END
                    */
                   case END:
                           send_char(ESC);
                           send_char(ESC_END);
                           break;

                   /* if it's the same code as an ESC character,
                    * we send a special two character code so as not
                    * to make the receiver think we sent an ESC
                    */
                   case ESC:
                           send_char(ESC);
                           send_char(ESC_ESC);
                           break;




Romkey                                                          [Page 4]

RFC 1055                     Serial Line IP                    June 1988


                   /* otherwise, we just send the character
                    */
                   default:
                           send_char(*p);
                           }

                   p++;
                   }

           /* tell the receiver that we're done sending the packet
            */
           send_char(END);
           }

   /* RECV_PACKET: receives a packet into the buffer located at "p".
    *      If more than len bytes are received, the packet will
    *      be truncated.
    *      Returns the number of bytes stored in the buffer.
    */
   int recv_packet(p, len)
           char *p;
           int len; {
           char c;
           int received = 0;

           /* sit in a loop reading bytes until we put together
            * a whole packet.
            * Make sure not to copy them into the packet if we
            * run out of room.
            */
           while(1) {
                   /* get a character to process
                    */
                   c = recv_char();

                   /* handle bytestuffing if necessary
                    */
                   switch(c) {

                   /* if it's an END character then we're done with
                    * the packet
                    */
                   case END:
                           /* a minor optimization: if there is no
                            * data in the packet, ignore it. This is
                            * meant to avoid bothering IP with all
                            * the empty packets generated by the
                            * duplicate END characters which are in



Romkey                                                          [Page 5]

RFC 1055                     Serial Line IP                    June 1988


                            * turn sent to try to detect line noise.
                            */
                           if(received)
                                   return received;
                           else
                                   break;

                   /* if it's the same code as an ESC character, wait
                    * and get another character and then figure out
                    * what to store in the packet based on that.
                    */
                   case ESC:
                           c = recv_char();

                           /* if "c" is not one of these two, then we
                            * have a protocol violation.  The best bet
                            * seems to be to leave the byte alone and
                            * just stuff it into the packet
                            */
                           switch(c) {
                           case ESC_END:
                                   c = END;
                                   break;
                           case ESC_ESC:
                                   c = ESC;
                                   break;
                                   }

                   /* here we fall into the default handler and let
                    * it store the character for us
                    */
                   default:
                           if(received < len)
                                   p[received++] = c;
                           }
                   }
           }














Romkey                                                          [Page 6]

--
{alberta,pyramid,uunet}!ncc!lyndon  lyndon@Nexus.CA

-----------------------------

From: ok@quintus
Subject: Termcap/Terminfo question
Date: 28 Jun 88 20:48:27 GMT
Sender: news@quintus.uucp
To:       info-unix@brl-sem.arpa

When should a program use the 'is' (initialisation string) or 'if'
(initialisation file) capabilities?  I have a program which sends this
string when it starts, but a number of VT100 emulators adapt to window
size by adding appropriate co#COLS and li#ROWS information, but leave
is: setting the scrolling region to 24 lines, which seems unhelpful.

There seem to be three sets of strings a program might send at start
and finish:
    is/rs    initialisation string / reset string
        [is1..is3/rs1..rs3 in terminfo; also if/rf]

    vs/ve    "visual" start / "visual" end

    ti/te    said to be meant for things that use cm (cursor motion)

Exactly when should these things be used?

Is there a book which explains in clear and simple language what each of
the capabilities means, how to decide what to set it to, and when to use it?
[I have the 5R3 manuals.  I need an idiot's guide.]

-----------------------------

From: "M. D. Parker" <mparker@chip.uucp>
Subject: UUCP Over TCP/IP
Date: 28 Jun 88 20:52:12 GMT
Keywords: uucp, uucpd, bsd4.3
To:       info-unix@brl-sem.arpa

In bits of the BSD documentation, there is a mention of the TCP/IP UUCP server
deamon (i.e. /etc/uucpd).  My question is if you are the sending party, how
do you tell the system to use the UUCP protocol?   I find nothing in this
in connection with the L.sys file, in fact, I have really found nothing at
all.

Can anybody enlighten me on /etc/uucpd and its operation, invokation, etc.?

Thanks....

-----------------------------

From: Doug Landauer <landauer@morocco.sun.com>
Subject: Re: RCS and SCCS (and CMS)
Date: 28 Jun 88 21:25:47 GMT
Sender: news@sun.uucp
Keywords: CMS RCS SCCS
To:       info-unix@brl-sem.arpa

In article <1134@cod.NOSC.MIL>, dberg@cod.NOSC.MIL (David I. Berg) wrote:
> Another feature of RCS is that it stores the current
> version of your file and the changes backward to the original, whereas
> SCCS stores the original version of your file and the changes forward
> to the current.

This is a common misconception (oversimplification) -- it implies that
it could take significantly longer using SCCS to get the current
version of the file than for it to get the original version.  In fact,
SCCS does not store separate deltas; it stores all of the deltas
together, in the appropriate places within "the original file", in the
file in such a way that it takes about the same amount of time to get
any version.

There are several barely relevant performance implications of the
differences between this scheme and what RCS does:

    + for RCS:  For retrieving the latest version (RCS is betting that
    this is the most common case), RCS is likely to be faster;

    ~ :  For retrieving any other versions, RCS slows down relative
    to its own performance on the latest version (and at some point
    depending on how many deltas as well as how many lines changed
    per delta, it may be slower than SCCS);

    + for SCCS:  Doing RCS check-ins (storing new versions) should be
    distinctly slower than doing SCCS deltas;

> I find RCS particularly easier to use than SCCS.

I personally agree with this statement (disclaimer:  Sun doesn't
officially agree).  The BSD "sccs" front-end command helps some.

Finally, the performance differences mentioned above probably add up
(over the course of my entire SCCS career) to less time than I spent
composing this message (as David I. Berg put it, "it will take SCCS a
trifle longer"), so the ease-of-use factor should become the overriding
factor if you're starting a new project in a new company or on your
own.  In practice, the "what-they-use-here" factor is the real
overriding factor.

This is one of the few areas where VMS (gasp!) really does do better
than Unix (IMHO) -- DEC's CMS (though it has brain damage in some ways)
really does have some features that would make it, on the whole, better
than either SCCS or RCS, if you could use it on Unix instead of VMS.
--
    Doug Landauer                Sun Microsystems, Inc.
    ARPA Internet:    landauer@sun.com    Software Products Division
    UUCP:  ...!sun!landauer
--
Acronym glossary:   (Some of these are trademarks -- you know who you are.)
    BSD -- Berkeley Software Distribution
    CMS -- Code Management System (I think)
    DEC -- Digital Equipment Corporation
    IMHO -- In My Humble Opinion
    RCS -- Revision Control System
    SCCS -- Source Code Control System
    UUCP -- Unix-to-Unix CoPy
    VMS -- Virtual Memory System (an operating system for some DEC computers)
--

-----------------------------

From: Adam Moskowitz <adamm@necis.uucp>
Subject: Getting vi to automagically use macros
Date: 28 Jun 88 23:01:19 GMT
Keywords: vi, macros
To:       info-unix@SEM.BRL.MIL

This has probably been asked before, but since limited disk space prevents me
from saving everything I might ever need . . .

Is there a way to set up some vi macros via my .exrc file or the EXINIT
environment variable? I know that I can fake it my mapping the two-char
sequence "@x" to the string I want, but is there a way to automatically
have a "real" macro set up every time I start-up vi?

E-MAIL me your replies and I'll summarize to the net if I get anything.

Thanx in advance.
--
Adam S. Moskowitz                ...!(backbone)!{necntc,encore}!necis!adamm

        "The morning blues, they make me feel so bad;
         it's the worst damn feeling I ever had."

-----------------------------


End of INFO-UNIX Digest
***********************

Postmaster@wharton.upenn.edu (PMDF Mail Server) (07/21/88)

Your message could not be delivered to: 

    reilly@facman.wharton.upenn.edu

Your message has been enqueued and undeliverable for 3 days.
The mail system will continue to try to deliver your message
for an additional 9 days.

The beginning of your message follows: 

Return-path: <info-unix-request@sem.brl.mil>
Received: from SEM.BRL.MIL by wharton.upenn.edu via TCP; Sat Jul 16 12:53 EST
Received: from SEM.BRL.MIL by SEM.BRL.ARPA id ab04672; 16 Jul 88 3:02 EDT
Received: from sem.brl.mil by SEM.BRL.ARPA id aa04584; 16 Jul 88 2:46 EDT
Date: Sat, 16 Jul 88 02:45:56 EST
From: The Moderator (Mike Muuss) <Info-Unix-Request@BRL.ARPA>
Subject: INFO-UNIX Digest  V5#099
To: INFO-UNIX@BRL.ARPA
X-VMS-To: INFO-UNIX@BRL.ARPA
Reply-to: INFO-UNIX@BRL.ARPA
Resent-date: Sat, 16 Jul 88 12:56 EST