HDTenEightyP/NetNews huggingface dataset:
From: henrym@sacusr.mp.usbr.gov
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: FTP problems
Date: 19 Aug 92 19:22:43 GMT
Reply-To: HENRYM@SACUSR.MP.USBR.GOV
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Vms-Original-To: INET%"AL@mom.spie.org"


Al,
	If I'm reading your description correctly, the type of error
message is probably a little misleading, but the action, or rather
lack of action should be correct:  as a matter or security, you cannot
write files TO an ANONYMOUS account, you can only get files from there.

-HWM
----------
Henry W. Miller
Assistant Systems and Network Manager
U.S. Bureau of Reclamation
Mid Pacific Region
2800 Cottage Way MP1100
Sacramento, CA 95825
(916) 978-5108 / FTS - Same as commercial
Inet:	"henrym@sacwms.mp.usbr.gov"
BITNET:	"hmiller@scu"

"I've fallen, and I can't get up!"
From: ccla@marlin.jcu.edu.au (Lee Askew)
Subject: CMU-Tek Thanks lpr of OZ
Organization: James Cook University
Date: Tue, 18 Aug 92 05:06:52 GMT


I would like to thank all of you who helped in the solving of a problem
that i had with cmu lpr6.5, with a new version running and comparing my
config files with samples that others sent, I very much appreciate the
help given.

Special thanks to clement@rice.edu, henrym@sacusr, woodbury@oak.bme, to
mention but a few here.

Thank you all for your help, i really appreciate it.

Thanks Again

Lee.
(Oz - Down Under).
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Telnet 3270.
From: "ricardo E. Barahona - Univ. Sagrado Corazon"
Date: Wed, 12 Aug 92 14:21 AST
Reply-To: "Ricardo E. Barahona - Univ. Sagrado Corazon"
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Envelope-To: cmu-tek-tcp@cmutek.cc.cmu.edu
X-Vms-To: INTERNET"cmu-tek-tcp@cmutek.cc.cmu.edu"

Hi!

Has anybody tried to use CMU/Tek telnet to access IBM mainframes emulating
3270 terminals or compatible?

Thanks for your answers.

Ricardo.
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: Telnet server not recommended?
From: "Jonathan E. Hardis" <hardis@vax844.phy.nist.gov>
Date: Mon, 17 Aug 1992 17:42:36 EDT
Reply-To: "Jonathan E. Hardis" <hardis@vax844.phy.nist.gov>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: cmu-tek-tcp@cmutek.cc.cmu.edu, hardis@vax844.phy.nist.gov
X-Envelope-To: cmu-tek-tcp@cmutek.cc.cmu.edu

> According to the CMU-TEK manual the TELNET server is not recommended.
> I have just installed the program, and the server (which is the most
> important function for us) seems to work fine. Can anyone tell me what
> kind of problems I can expect?

I think I know where the confusion lies.

There are two ways of getting Telnet server functionality.  One is for the
IPNCP to pass packets to image TELNET_SERVER.EXE.  As it says on page 2-13,
this isn't recommended.  But that's because IPNCP can provide the server
functionality without the need for another image!

In INTERNET.CONFIG, make sure that:
  Variable:TELNET_SERVICE:1
is set so that IPNCP will provide Telnet service, and:
  ;;WKS:23:TELSRV:TCP$TELSRV:NETWRK,NOACNT:NETMBX,TMPMBX,PHY_IO:::::5:5
is commented out so that TCP$TELSRV (TELNET_SERVER.EXE) won't be used.
Then, everything will be fine.

  - Jonathan
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re:  help with setting up LPR
From: brian.t.carcich@cuspif.tn.cornell.edu
Date: 18 Aug 1992 15:35:48 EST
Reply-To: Brian.T.Carcich@CUSPIF.TN.CORNELL.EDU
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Vms-Original-To: INET%"rrb@nch.norasia.COM",CMUTEK


a typical printcap.txt on vax VMS:: to print on sparc.domain should look
like this:

ps "sparc.domain" "sparc.domain" "VMS::" default start

then on the vax,  you do

$ @sys$manager:lpr_startup

then on sparc.domain, create a queue called ps (unless one already exists)
and set up lpd.hosts or whatever to allow printing from vms.domain.

there may be a problem if your vax is not set up to cluster,
the error will look something like NOSUCHNOD on the vax side.
in that case edit lpr_startup.com on the vax by putting "-!" in front of
the line after "$ INITIALIZE" so that the /QUEUE/ON='scs_node' becomes

/QUEUE-!/ON='scsnode'

-brian carcich
From: rick%qucdnee.bitnet@bitnet.cc.cmu.edu (Rick Pim)
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: LPR... I got it working :)
Date: 12 Aug 92 21:58:00 GMT
Reply-To: Rick Pim <RICK%QUCDNEE.BITNET@BITNET.CC.CMU.EDU>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: CMU-TEK-TCP%CMUTEK.CC.CMU.EDU@CMU.EDU
X-Vms-To: IN%"chris%CSVAX1.UCC.IE@CARNEGIE.BITNET"
X-Vms-Cc: IN%"CMU-TEK-TCP%CMUTEK.CC.CMU.EDU@CARNEGIE.BITNET"
Content-Transfer-Encoding: 7BIT

> are  "J.C. Higgins, Sys Mgr CsVax1, UCC , Eire"

>PS: Anyone any ideas why I can print text files without problems, but the
>(only) postscript file I tried got truncated ??? Anyone had the problem and
>solved it ??? Anyone still reading this ??? Well if you can help then I'd
>appreciate it. Thanks.

we print PostScript from our Vaxen to remote printers (laserwriters, an
ln03r, a sparcprinter) on Suns & other Vaxen all the time. usually, it
works. the most important consideration is where the PostScript came
from: if it came from a "nice" application (like, for example, dvips
from the decus tex collection or pgplot), it prints w/o any problem.
if it's from a "not nice" application (like any number of PC packages)
we have problems.

in general, if a ps file is editable using something like edt without
any trouble, then it seems to print. if it's not (enormously long
records, for example) then all bets are off. (sometimes analyze/rms/fdl
followed by convert can be helpful.) in any case, it CAN work without
any fiddling if you have a nice application.

rp
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rick Pim                                            bitnet:rick@qucdnee
Department of Electrical Engineering         rick@qucdnee.ee.queensu.ca
Queen's University, Kingston                     (bitnet:rick@qucdnast)
(613) 545-6772                               (rick@bill.phy.queensu.ca)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Baldrick, you wouldn't see a subtle plan if it painted itself purple
and danced naked on top of a harpsichord singing 'Subtle Plans Are
Here Again'."
                    -- BlackAdder
From: meyers@sndsn1.sinet.slb.com
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: SIGNOFF CMU-TEK-TCP
Date: 14 Aug 92 15:21:15 GMT
Reply-To: <meyers@sndsn1.SINet.SLB.COM>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: MEYERS@sndsn1.SINet.SLB.COM
X-Vms-From: SNDSN1::MEYERS       "George Meyers - SINET::MEYERS 1 303 470 2530"
X-Vms-To: INTERNET::"cmu-tek-tcp@CMUTEK.CC.CMU.EDU"
X-Vms-Cc: MEYERS

SIGNOFF CMU-TEK-TCP
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: an obscure lpr difficulty inspired by the PostScript/LPR thread
From: "Michael L. Hitch" <osymh@trex.oscs.montana.edu>
Date: Thu, 13 Aug 1992 14:43:34 MDT
Reply-To: osymh@msu.oscs.montana.edu
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>

=> From: Rick Pim <RICK%QUCDNEE.BITNET@QUCDN.QueensU.CA>
=>
=> the recent thread about problems printing PostScript made me dig up some
=> difficulties i was having many months ago with printing via CMU lpr to a
=> remote unix system. the printer in question is an LN03, the application
=> that generates my .LN3 files is DVItoLN03, by brian hamilton kelly.
...
=> note the change in carriage control.
=>
=> this difference in file format caused some problems with this printer
=> configuration. some (not all) dvi files that will convert and print
=> correctly with 3.1-4 will not print correctly under 4.0. (my standard
=> example of this behaviour is a page in LaTeX picture format. it has all
=> the expected output, but instead of being on one page is split between two.)
...
=> now i know it's possible. :-) does anyone have any idea how one might be
=> able to coax the cmu lpr daemon into printing this kind of file (ln03
=> format, no carriage control) "correctly"?
=>

This looks like the same problem I ran into about three years ago.  I was
having problems with LPR printing some PostScript files.  At that time, LPR was
stupid about handling VMS files (i.e. it completely ignored the record format
and record attributes - it just copied the RMS file record and appended a '\n'
to the end.  If the file was created by a FORTRAN program, the Fortran carriage
control byte was left in the record being printed.  Since the printer on our
Ultrix system was looking for "%!" in column 1 to identify a PostScript file,
the file was actually printed out as ascii.

What I did was to patch LPR to check the record attributes and change the way
the record was handled:  if the record format was FTN (Fortran), I skipped the
first byte and appended the '\n'.  If the record attribute was CR or PRN,
then the record was copied as is and a '\n' appended.  Otherwise, the record
data was sent without appending the '\n' (this assumes that any format control
is done by control characters embedded in the record data).

I haven't looked at the 6.5 version of LPR, but I suspect it has the same
problem.
---
Michael L. Hitch                        osymh@msu.oscs.montana.edu
Computer Consultant                     OSYMH@MTSUNIX1.BITNET
Office of Systems and Computing Services
Montana State University
Bozeman, MT     USA
From: andre@hern.stonemarche.org
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: NFS on cmu tek 6.6-5, Does it work?
Date: 13 Aug 92 22:39:42 EDT
Organization: Hern the Hunter, Stonemarche (NH)

Well,
	I got the thing to work.  It seems that the problem was not only
that there was the `$' issue in the NFS.CONFIG file, but there was a problem
with what account I used for the `anonymous_user'.  Seems that the path to the
exported mount is checked for accessability regarding vms file protections.
I solved this by using the SYSTEM account in the short term.  I could do this
as I am working on a isoated network, (no outside connections).  I will need
to fine tune this, and expect to have this bite me again.

I have 2 solutions to the `$' problem, in summary don't use them.
  - Export `/'.
  - Define Logical names that have no `$' in them.  Use them insted.

I hope this helps.
					Andre'
-- 
andre@stonemarche.org				Andre' Wood
andre@hern.stonemarche.org			POBox 305,
...!dartvax!hern!andre				Greenfield, NH, 03047
Per chevron sable and vert, a stag's attire Or and in chief a mullet argent.
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: NFS on cmu tek 6.6-5, Does it work?
From: "tom Allebrandi - Inland Steel Research Labs"
Date: Fri, 14 Aug 92 13:20:01 CST
Reply-To: "Tom Allebrandi - Inland Steel Research Labs"
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Vms-Mail-To: UUCP%"cmu-tek-tcp@cmutek.cc.cmu.edu"
X-Vms-Mail-Cc: ALLEBRANDI

> I have 2 solutions to the `$' problem, in summary don't use them.
>   - Export `/'.
>   - Define Logical names that have no `$' in them.  Use them insted.

There is another place where "$" will get you in trouble - VMS
filenames that must have "$" in them. CMU/Tek NFS uses "$" as an escape
character to indicate Unix nonprintables and case switches. This means
that VMS filenames that naturally have "$" in them can be
misinterpreted from the client side.

I knew about this but ran hard into it attempting to use NFS to supply
the fonts for my X terminals. I need to have my X terminals using the
DECwindows fonts so that DECwrite, SoftPC and other things work
properly. The problem is that the DECwindows fonts are in:

	VMSDISK:[VMS$COMMON.SYSFONT.DECW.something]somethingelse.DECW$FONT
	            ^                                                ^

I trying to think of a way of dealing with this. If anyone has any
ideas I would love to here them.


Temporarily, I have modified NFS to allow the "$" to be escaped from
the client side. I'm not real happy with this idea, and it's not a
perfect solution to the problem. (It's also ugly in that you have to
present the escaped "$" to the server. This makes a mount command look
like
	mount -t nfs "Host:/drive/vms\\\$common/sysfont/decw" /fontpath

yuck!)


It also didn't fix my problem with the X terminals because the filename
for the font (including the .DECW$FONT) gets stored in a place that it
out of my reach. (My X terminals also run DECnet so it's not a real issue...)


I am thinking about adding a flag on the EXPORT statement that will
disable filename translation. This would allow you to use VMS filenames
exactly as they are. This is also not a perfect solution because it
would cause "abc" and "ABC" to become the same file. I'm thinking that
flag this would be used in cases like the above where you must use VMS
filenames unmangled and are willing to accept the limitiations.


Anybody else have any ideas? This fall I'm planning to start really
looking into CMU/Tek NFS and try to resolve these issues, the speed
problems and a few other things.


And, hopefully next week, I'll at least get NFS working again :-)


--- Tom
Tom Allebrandi             | Mail guru   - DECUS UUCP Development Team
Inland Steel Research Labs | NFS grunt   - CMU/Tek-IP
East Chicago, IN           | Chairperson - VMSnet Working Group, DECUS VAX SIG
219 399 6306               | Internet:  allebrandi@inland.com
DECUServe: allebrandi      | UUCP:      ...!uunet!inland!allebrandi
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Please remove me from the CMU-TEK distribution list
From: <meyers@sndsn1.sinet.slb.com>
Date: Wed, 12 Aug 92 14:39:15 GMT
Reply-To: <meyers@sndsn1.SINet.SLB.COM>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: MEYERS@sndsn1.SINet.SLB.COM
X-Vms-From: SNDSN1::MEYERS       "George Meyers - SINET::MEYERS 1 303 470 2530"
X-Vms-To: INTERNET::"cmu-tek-tcp@cmutek.cc.cmu.edu"
X-Vms-Cc: MEYERS

Please remove meyers@sinet.slb.com from the CMU-TEK distribution list

Thanks,
George Meyers
Schlumberger
From: burns@eisner.decus.org (Scott Burns)
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: SUBSCRIBE
Date: 22 Aug 92 23:16:13 GMT
Reply-To: Scott Burns <BURNS@Eisner.DECUS.Org>
Organization: Digital Equipment Computer Users Society
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Vms-To: IN%"cmu-tek-tcp@cmutek.cc.cmu.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

SUBSCRIBE
LIST
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Re: Performance Problems
From: "tom Allebrandi - Inland Steel Research Labs"
Date: Fri, 14 Aug 92 12:52:12 CST
Reply-To: "Tom Allebrandi - Inland Steel Research Labs"
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
X-Vms-Mail-To: uucp%"cmu-tek-tcp@cmutek.cc.cmu.edu"
X-Vms-Mail-Cc: ALLEBRANDI

> I have installed CMUTEK on a VAX with 32 MB Memory.

What model?

> When i mount a top-level directory on a VAX Drive (RA91) from a SUN 4/40 i
> measure the following performance:
> ...
> with a filesize of something like 1.5 MB i calculated a throughput of 22
> KByte/Second which is floppy performance.
> ...

CMU/TEK NFS is not a speed demon. I've got some ideas about how to speed
it up that I hope to work on this fall.

Tom Allebrandi             | Mail guru   - DECUS UUCP Development Team
Inland Steel Research Labs | NFS grunt   - CMU/Tek-IP
East Chicago, IN           | Chairperson - VMSnet Working Group, DECUS VAX SIG
219 399 6306               | Internet:  allebrandi@inland.com
DECUServe: allebrandi      | UUCP:      ...!uunet!inland!allebrandi
From: dragon@nscvax.princeton.edu (Mighty Firebreather)
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: RE: FTP problems
Date: 19 Aug 92 18:58:54 GMT
Reply-To: Mighty Firebreather <dragon@nscvax.princeton.edu>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: cmu-tek-tcp@cmutek.cc.cmu.edu


	Al Gill	<AL@mom.spie.org> writes:
>
>I'm a new CMU/Tek user; running version 6.6 on VMS version 5.5.
>
>My problem is with FTP;  I have defined the anonymous account and created
>a directory tree with World:Read,Write,Execute,Delete privileges owned by
>anonymous; yet all attempts to 'put' or 'send' an ascii file from another
>location (my tests also use a system running CMU/Tek 6.6 and VMS 5.5)
>result in:
>
>550 Requested action not taken.  No access.
>%FTP-E-NO_ACTION, Requested action not taken.  File unavailable.
>

	The anonymous account cannot be used by remote systems to store
files!  It's a "feature".  You can get files from any other system, they
can't send them to you.   That's the long and the short of it.

*************************************************************************
*                                                                       *
*                        Here, there be dragons!                        *
*                      dragon@nscvax.princeton.edu                      *
*                                                                       *
*                                                Richard B. Gilbert     *
*************************************************************************
From: mats@efd.lth.se
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Using the CMU DECwindows transport
Date: 20 Aug 92 16:33:31 GMT
Reply-To: <mats@efd.lth.se>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
CC: cmu-tek-tcp@CMUTEK.CC.CMU.EDU

> I've been unable to get the DECW$TRANSPORT_CMU.EXE of 28-JAN-1992 14:58 to work
> between our VMS 5.4-3, DECwindows Motif client and server (same machine).
> The error I recieve is:
>
> XIO:  unable to open connection _WSA7:
> after 0 requests (0 known processed) with 0 events remaining.
> %XLIB-F-IOERROR, xlib io error
> -SYSTEM-F-ABORT, abort
>
> Everything seems to be set up as recommended in the CMU transport installation
> text.  I'd really appreciate help getting this part of the distribution working.

Well there are booth good and bad News.

The bad news is That you have to relink the DECW$TRANSPORT_CMU.EXE to
use the Motif library. And even if you do it wont work with
Vms 5.4-3 (or Vms 5.5).

The Good news is that it work's very well with VMS 5.5-1......

I started to rewrite the code when i was with Vms 5.5 but then I
installed 5.5-1 and since I didn't have the time to finish the
rewrite I just gave up and start using the old DECW$TRANSPORT_CMU.EXE
(Relinked with Motif...)

--
  Mats Akerberg, System Manager (mats@efd.lth.se),(MATS@SELDC52) on Earn/Bitnet
  Lund Institute of Technology ,School of Electrical Engineering and
  Computer Sciences. Snail: Box 118  S-221 00 Lund Sweden
  Phone: + 46 46-109847 FAX: + 46 46-129948
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
From: johnston@amtsg0.ime.nrc.ca (Daniel F. Johnston)
Subject: NFS exporting - Summary? Next Step.
Organization: National Research Council of Canada
Date: Fri, 14 Aug 92 14:32:12 GMT

SInce I started this thread about NFS working for CMU Tek 6.6-5
I will try to offer a quick summary of the stuff running over
the net.

First: Do not use "$" (dollersigns) in your nfs.config file.
If your device name uses a $, like any cluster disk, then
define a system-wide logical name without a $ and use that 
instead.

Be careful with your choice of ANONYMOUS user.  If the username
you select does not have world read access to the files, then
the mount will not work.

That is the summary so far...  Now if I can only kick the users
off my microVAX-3100 I would restart the CMU software and 
try it again.  Maby this weekend.

Thanks to everyone who contributed to the discussion!

-- 
Daniel (Dan) F. Johnston                JOHNSTON@NRCAMT.IME.NRC.CA
National Research Council of Canada     Tel: (613) 993-6627
Montreal Road Campus, Bldg. M-3         Fax: (613) 998-2771
Ottawa, Ont. CANADA K1A 0R6
(((((( ... but the opinions expressed are my own!!  )))))))
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: SIGNOFF
From: Katsutoshi Ike <katsu@tsc.kddlabs.co.jp>
Date: Fri, 14 Aug 92 11:04:09 JST
Reply-To: Katsutoshi Ike <katsu@tsc.kddlabs.co.jp>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>
Return-Path: <katsu@tsc.kddlabs.co.jp>

SIGNOFF
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
Subject: Again about 6.6-5 patch
From: <tnuug@alyssa.rsinet.tn>
Date: Tue, 18 Aug 92 13:46:53 +0100
Reply-To: <tnuug@alyssa.rsinet.tn>
Organization: The Internet
Return-Path: <SYNFUL@CMUTEK.CC.CMU.EDU>
Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU
X-Listname: CMU-TEK TCP/IP Mailing list <CMU-TEK-TCP@CMUTEK.CC.CMU.EDU>


Hello,
 I just wanted to know if  any new patch for the cmu-tek package is out
 yet.
 Thank you in advance.
--regards
Newsgroups: vmsnet.networks.tcp-ip.cmu-tek
From: rrb@nch.norasia.COM (R.R.Buonanno)
Subject: help with setting up LPR
Followup-To: vmsnet.networks.tcp-ip.cmu-tek
Reply-To: rrb@nch.norasia.COM
Organization: Norasia Shipping Services SA
Date: Tue, 18 Aug 1992 13:22:21 GMT

Greetings from a newbie,

Here's my problem. Our VMS Sysman is off in Zimbabwe for a month getting
married and I'm here trying to set up the CMU/Tek-IP stuff without him.
It's been installed and telnet and ftp seem to be ok, so now I want to
set up a queue on our Vax that will spool to a PostScript printer on one
of our SPARCstations. Problem is -- I'm new to CMU/Tek and I'm a Unix
Sysman, NOT a VMS hacker. The doc seemed a bit skimpy even for someone
who knows what they're doing, so I'm completely lost. Fixing up the
PRINTCAP.TXT seemed simple enough, add an entry like
sparc "luke.norasia.com" "nchvax.norasia.com" NCH:: default ???
But I'm not sure what to use for the ???. Then do I create a queue called
SPARC on the Vax or what.

Any help would be appreciated... even RTFMs (if you tell me where in TFM).

Thanks all.

-- 
Richard R. Buonanno					rrb@nch.norasia.COM
Chief Hack and Window Washer				mcsun!chsun!nch!rrb
Norasia Shipping Services SA   PO Box 560   1700 Fribourg Switzerland