HDTenEightyP/NetNews huggingface dataset:
From: dnb@meshugge.media.mit.edu (David N. Blank-Edelman)
Subject: Re: CAP aufs desktop problem
Organization: M.I.T. Media Laboratory
	<trimble.726431386@ph-meter.beckman.uiuc.edu>
Date: Fri, 8 Jan 1993 05:01:26 GMT

>  We've experienced this, also. The problem only exists in the "root"
>  directory of that shared volume. All of the subdirectories will
>  store the files' locations just fine. We have not figured out how
>  to solve this problem and have basically concluded that it's just a
>  bug.

Actually, you are probably experiencing something which is in the
spec.  When I asked about this quite a while ago David Hornsby noted:

> The AFP spec contains this little peculularity in that to make the finder
> info stick, you have to be the owner of the volume in question (so that
> the owner bit is set in the permissions block, Ref: Inside AppleTalk 2,
> page 13-88, lower right).
> 
> So, my guess is that if you mount the volume as the user who owns the
> directory, then things should work OK. In addition, CAP 6.0 has the ability
> to set this stupid bit by having the directory setuid bit set, ie:
> 
> 	chmod u+s volname
> 
> so others can save the finderinfo on a shared volume.
> 

This helped my problem, I hope it solves yours (and the original
poster's).
       Peace,
          dNb
--

 David N. Blank-Edelman              o/    \  /    \ /     /      \o   
 M.I.T. Media Laboratory            /#      ##o     #     o##      #\
 E15-473F, (617) 253-2169           / \    /  \    /o\    / |\    / \

Newsgroups: comp.protocols.appletalk
From: Paulo Antonio Costa Goncalves <pacg@inesc.pt>
Subject: Re: papif/lpd prob running cap60.126 w/ SUN NIT (HELP!)
X-Xxmessage-Id: <A7787B82210120B9@helium.inesc.pt>
X-Xxdate: Tue, 12 Jan 93 13: 43:30 GMT
Organization: INESC (Inst. de Eng. de Sistemas e Computadores)
X-Useragent: Nuntius v1.1.1d12
Date: Tue, 12 Jan 1993 12:44:54 GMT

In article <1993Jan11.155625.18505@riogrande.cs.tcu.edu> Craig Morgenstern,
morgenst@riogrande.cs.tcu.edu writes:
>We've just switched from IPtalk via a kbox to native ethertalk (phase 2) on
>a SUN3 (4.0.3) and a SPARCstation-2 (4.1.1), and now laserwriter access is 
>broken on both machines.  In lpd-errs, we get the following message
>
>	Jan 11 09:14:39 red lpd[3238]: restarting lw132
>	Jan 11 09:15:29 red last message repeated 59 times
>
>
>Here's the printcap entry, cap.printers entry, and the shell script to
>invoke papif (these worked when we were using IPtalk):
>
>	(printcap)
>	lw132:\
>         	:lp=/dev/lw132:\
>         	:sd=/var/spool/lw132:\
>         	:sf:\
>         	:lf=/var/adm/lw-log:\
>         	:if=/usr/local/lib/cap/lw132:\
>         	:of=/usr/local/lib/cap/papof:
>
>	(cap.printers)
>	lw132=132 PLW:LaserWriter@CoSc Labs
>
>	(lw132 shell script)
>	#!/bin/sh
>	BANNERLAST=0
>	BANNERFIRST=0
>	DOACCT=0
>	export BANNERLAST BANNERFIRST DOACCT
>	/usr/local/lib/cap/papif -P lw132 $*
>
>Aufs, atlook, etc all work fine, and we can print a postscript file to lw132
>using lwpr.  Under ethertalk, the machines are in a different zone than
>they were when running IPtalk.  etcdest and all other dests were all set to
>/usr/local/lib/cap.
>
>I've RTFM all weekend, and I'm completely stymied.  I haven't been following
>threads about printer probs, so I don't know if this is a common prob or not.
>Could someone in the know please enlighten me?  Any suggestions would be
>very much appreciated!
>
>Thanks in advance.
>
>Craig Morgenstern
>morgenst@riogrande.cs.tcu.edu

	What is the protection of /dev/nit in your SUNs?
	I had to "chmod 660 /dev/nit", "chgrp staff papif" and "chmod g+s papif" (set
gid bit
to staff). Then it all worked!
	Hope this helps!
	
	Paulo Goncalves.

****************************************************************************
***
 Paulo Antonio Costa Goncalves       E-mail:  pacg@inesc.pt
       INESC - CCAE                  Eunet:   mcsun!inesc!pacg
    Tel. 351-1-3100069                        mcsun!inesc!pacg@uunet.UU.NET
     Lisboa - PORTUGAL               PSI/VMS: PSI%(+0268)004010314::inesc::pacg
****************************************************************************
***

	    The Golden Rule is: Who has the Gold, Makes the Rule !!!

****************************************************************************
***
Newsgroups: comp.protocols.appletalk
From: wtierney@leland.Stanford.EDU (Bill Tierney)
Subject: CAP -papif not working
Organization: DSG, Stanford University, CA 94305, USA
Distribution: usa
Date: Tue, 12 Jan 93 18:21:44 GMT


I am running CAP (126) on RS6000 3.2.3 and am having a problem
with papif.  It says it is starting up and printing but
nothing comes out.

I am able to to use the sub-command lwpr and it works fine.

Any ideas?

Please send replies to wtierney@leland.stanford.edu.

Thank You
Newsgroups: comp.protocols.appletalk
From: pineapp@netcom.com (Daniel Curry)
Subject: Copy files from MAc to Suns
Organization: Netcom-Online Communication Services (408 241-9760 guest)
Date: Mon, 4 Jan 1993 22:10:58 GMT

   I am having problems on copy files from my mac to a Sun machine
using CAP. I am getting "no permissions" from my mac. 
  I am using CAP pl100 and MAC 7.0.1. I do not like the idea
that I have to create .resources on the sun side. Is this a known
bug?





-- 
Dan Curry                                   WB6STW
Pineapp@netcom.com                   K6ANN Rptr 444.500
From: sundvall@perrier.embnet.se (Mats Sundvall)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP and Solaris 2
Date: 11 Jan 1993 15:28:37 GMT
Organization: EMBNet Project Sweden
Distribution: world
Reply-To: sundvall@perrier.embnet.se
NNTP-Posting-Host: perrier.embnet.se


Yea,

me to. I can't even figure out if something similar to /dev/nit is present.

Regards,

Mats Sundvall
Dept of Medical Genetics
Uppsala, Sweden


Newsgroups: comp.protocols.appletalk,comp.unix.aux
From: brian@intercon.com (Brian Lichorowic)
Subject: Re: Compiling CAP on A/UX 3.0
Reply-To: brian@intercon.com (Brian Lichorowic)
Organization: GTE Contel Federal Systems
X-Newsreader: InterCon TCP/Connect II 1.1b23
Date: Mon, 4 Jan 1993 14:12:56 GMT

In article <93003.132835AUBXG@ASUACAD.BITNET>, Ben Goren 
<AUBXG@ASUACAD.BITNET> writes:
> OK, I know that this is supposed to work pretty much straight out of the 
> box, but it isn't for me. Could one of you who's got CAP60 patched to 
> 126 kindly give mNever mind....
From: ferch@ucs.ubc.ca (Les Ferch)
Newsgroups: comp.protocols.appletalk
Subject: Sharing a Printer on Ethernet between Macs and Unix machines
Date: 9 Jan 93 01:34:50 GMT
Organization: The University of British Columbia
NNTP-Posting-Host: swiss.ucs.ubc.ca

I'm looking into a way of sharing one laser printer among several
ethernet-connected Macs and Unix systems. I'm sure this is an FAQ, but I
will first relay some information that may be new to some of you. 

One product that promises to do this in a slick way is called "EtherWrite
LPR" from Compatible Systems. The product was announced in July but has
not shipped yet. I talked to the company this week and they think it will
be ready to ship sometime in February - we'll see. EtherWrite LPR is a box
that has two ports, one plugs into the LocalTalk port on a printer and the
other plugs into an ethernet network. It handles both EtherTalk from Macs
(i.e. printer shows up in Chooser) and TCP/IP (print from Unix systems
using lpr). It will have a SRP of about $1000.

What other methods for this amount of money or less are available for
acomplishing the same goal? Would the new version of AppleTalk Internet
Router work? 

I suppose a new printer that has an ethernet port that supports both
EtherTalk and TCP/IP (any available?) would be the best solution overall,
especially if the old printer can be used elsewhere. Or, the existing
LocalTalk printer could be used for the Macs only via LaserBridge from
Sonic Systems and a new TCP/IP compatible printer could be bought for the
Unix machines. 

One of the Sun machines has CAP installed already if that's any help.
From: loflin@emx.cc.utexas.edu (Don Loflin)
Newsgroups: comp.protocols.appletalk
Subject: Hardware info on PC-Localtalk board
Date: 5 Jan 93 01:01:33 GMT
Organization: The University of Texas at Austin


I'm looking for hardware details on the PC-Localtalk board (from
Apple nee Farallon).  Specifically, I'd like to find enough info
to be able to program to it at the hardware-level (i.e. write
a driver for it that does _not_ use PhonenetTalk/PC, as the localtlk
packet driver does). [Why, you ask?  I have 3-4 of these boards doing
nothing as Localtalk boards, but I have possible uses for an RS422 
interface].

Where might I find specs and/or source code examples for programming 
this board?

Alternatively, I also have a Novell NA1000 (or whatever it's called)
Localtalk board.  Info for this board would be equally welcomed.

I've found info on programming SCC interfaces (from KA9Q-NOS), but 
it seems to me the Localtalk board is a bit more complex. (It's
got a 6502 on board) (The na1000 has a z80)


Thanks,
  Don Loflin
From: braun@isctssl.NoSubdomain.NoDomain (Curtis Braun)
Newsgroups: comp.protocols.appletalk
Subject: Re: Mac Plus/MacTCP 1.1.1
Date: 6 Jan 93 21:04:22 GMT

While we're on this subject. How do I go about upgrading
my plus on MacTCP 1.1? Is there a place to ftp the 
patch from? Thanks, this explains some of my precieved 
problems.

-- 
Curtis Braun (curtis@computronics.com) (n2hkd)
Computronics, POBOX 1002 Fairport,NY 14450 
Guest@Digital Telstar,Network Operations Center Kodak
From: mclagan@sfu.ca
Newsgroups: comp.protocols.appletalk
Subject: Strange NetWare-System 7 behavior
Date: 7 Jan 93 18:44:42 GMT
Distribution: world
Organization: The Internet

NetWare 2.15c with AppleTalk VAPs 2.15

Strange problem #1:
Locked files are being interpreted as aliases by System 7 machines.
When one of these files is opened we get the message:
     The alias "XXX" could not be 
     opened, because this item is really not
     an alias (oops!). The problem has
     now been corrected. Please try again.

The finder then "corrects" the problem, which results
with an unlocked file. Everthing is normal under System 6.

Strange problem #2:
When copying a folder with some files inside it from a
local disk to a server disk we get the message:
     The file "XXX" couldn't be
     written, because it cannot be found. Do
     you want to continue copying?

Again, everything behaves normally under System 6.

I have rebuilt the desktop under Sys 6 but I don't
know of a way to force Sys 7 to do it.

Much gratitude to all who can help.
 
Scott McLagan
mclagan@fraser.sfu.ca

Newsgroups: comp.protocols.appletalk
From: tt@thor.acc.Virginia.EDU (Tang Tang)
Subject: Re: Sharing a Printer on Ethernet between Macs and Unix machines
Reply-To: tt@virginia.edu
Organization: Academic Computing Center, University of Va.
Date: Sat, 9 Jan 1993 16:38:30 GMT

In article <ferch.726543290@swiss.ucs.ubc.ca>, ferch@ucs.ubc.ca (Les Ferch) writes:
|> I'm looking into a way of sharing one laser printer among several
|> ethernet-connected Macs and Unix systems. I'm sure this is an FAQ, but I
|> will first relay some information that may be new to some of you. 
|> 
|> One product that promises to do this in a slick way is called "EtherWrite
|> LPR" from Compatible Systems. The product was announced in July but has
|> not shipped yet. I talked to the company this week and they think it will
|> be ready to ship sometime in February - we'll see. EtherWrite LPR is a box
|> that has two ports, one plugs into the LocalTalk port on a printer and the
|> other plugs into an ethernet network. It handles both EtherTalk from Macs
|> (i.e. printer shows up in Chooser) and TCP/IP (print from Unix systems
|> using lpr). It will have a SRP of about $1000.
|> 
|> What other methods for this amount of money or less are available for
|> acomplishing the same goal? Would the new version of AppleTalk Internet
|> Router work? 
|> 
|> I suppose a new printer that has an ethernet port that supports both
|> EtherTalk and TCP/IP (any available?) would be the best solution overall,
|> especially if the old printer can be used elsewhere. Or, the existing
|> LocalTalk printer could be used for the Macs only via LaserBridge from
|> Sonic Systems and a new TCP/IP compatible printer could be bought for the
|> Unix machines. 
|> 
|> One of the Sun machines has CAP installed already if that's any help. 

  We use etherprint box from Dayna ($350) and CAP's papif with 
good success.  The new laserwriter IIg is even better, you don't
even need to have the Dayna box.  Many thanks to the people that
work on CAP.

Sincerely,
Tang Tang
University of Virginia
ITC/Academic Computing Center           Internet: tt@virginia.edu
Gilmer Hall                             Bitnet:   tt@virginia
Charlottesville, Va.  22903             Phone:    (804) 924-0632
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP aufs desktop problem
From: maariano@skyler.arc.ab.ca (Marco Ariano)
Date: 12 Jan 93 23:38:05 GMT
Organization: Alberta Research Council, Calgary Alberta, Canada
In-reply-to: dplatt@ntg.com's message of 10 Jan 93 06:40:39 GMTLines: 56

I am having a similar problem with respect to view information not
being kept.  If this is a FAQ, please point me in the right direction.

I'm not the sysadmin but I'm allowed to write to a publically
available volume.  (CAP AUFS was installed by the previous sysadmin
and the current one knows little about it.  I'm hoping to find out
here the answer to my problem so that I can pass it on to the new
sysadmin.  It's easier to get things fixed if you can tell someone how
to do it...)

In order for several people to be able to write to the PublicVolume, a
unix group (say apple) was created.  All the files in the PublicVolume
(in the unix world) are given rwX permissions for the owner and group.
All people that should be able to write to PublicVolume are included
in the apple group (including me).  Is this a reasonable idea in the
first place?

I can now write files and folders to the PublicVolume, including into
folders that I don't own.  If I set the view for these folders (those
owned by someone else) to "by Small Icon" or "by Icon", things look
fine until I reopen the folder.  (Other views seem to work fine.)
Subfolders of which I'm owner all appear on top of each other in the
upper-left corner of the folder.  (This behavior seems worse when
viewing "by Icon".)  I believe I've made sure that all necessary files
exist and have the correct permissions.

For example, assume that the file
   .../Mac/PublicVolume
is mounted as a public volume and that the unix world looks something
like (I haven't included all the files):

   File:                                   Owner:    Group: Perms:

   .../Mac/.finderinfo                     ftpadmin  apple  drwxrwxr-x
           PublicVolume/                   ftpadmin  apple  drwxrwxr-x
                        .finderinfo        ftpadmin  apple  drwxrwxr-x
                        .resource          ftpadmin  apple  drwxrwxr-x
		        foo/               ftpadmin  apple  drwxrwxr-x
                            .finderinfo    ftpadmin  apple  drwxrwxr-x
                            .resource      ftpadmin  apple  drwxrwxr-x
                            Original       ftpadmin  apple  drwxr-xr-x
                            Mine           maariano  apple  drwxrwxr-x
                                /*         maariano  apple  

Changing the view of foo works once at most.  After that, the folder
Mine (and any other similar folders) appears on top of the folder
Original.  The foo/.finderinfo file is even modified.  Views within
Mine are 'remembered'.

Is this a bug or just a feature due to trying to to use CAP AUFS
inappropriately?  Any help would be appreciated.
--
Marco Ariano                      Alberta Research Council                
maariano@skyler.arc.ab.ca	  Advanced Computing and Engineering Dept.
ph:  (403) 297-2672		  Calgary, Alberta                        
fax: (403) 297-2339		  Canada  T2E 7H7
From: caywood@teb.larc.nasa.gov (John Caywood)
Newsgroups: comp.protocols.appletalk
Subject: Re: Dumping Mac disks to unix hosted tape
Date: 5 Jan 1993 21:35:12 GMT
Organization: NASA Langley Research Center, Hampton, VA  USA
Distribution: world
NNTP-Posting-Host: teb.larc.nasa.gov
Keywords: dump backup

In article <1hnmj6INNb8l@rave.larc.nasa.gov>, caywood@teb.larc.nasa.gov (John Caywood) writes:
|> I'm looking for a Macintosh network backup solution....

In the previous summary I neglected to post this alternative solution
sent by Charles Lindahl.  Please accept my sincerest apologies.

>From lindahl@ee.uta.edu Sat Jan  2 01:18:57 1993

I have one solution, which I plan to implement here: 

1) Establish a CAP-based mountable disk. 
2) Use FRONTIER (a Mac scripting system) to do scheduled mounts
   of this filespace (at night) and incrementally copy files to this
   "partition". 
3) Use a UNIX CRON job to copy this filespace to tape. 

It is easiest to use FRONTIER (system 7) to do the "scheduling"; however,
it should be possible to write equivalent C code to do the same thing. 

--
The opinions expressed herein are my own.-------------------------------------
  !John Caywood, System Administrator               !J.S.Caywood@LaRC.NASA.GOV
  !UNISYS Corp., under contract to Tech. Ed. Branch,!caywood@wyvern.twuug.com
  !NASA Langley Research Center, Hampton, VA        !(804)864-2496 voice
  +-------------------------------------------------!(804)864-8311 fax
From: apple.com (Ben Beasley)
Newsgroups: comp.protocols.appletalk
Subject: Re: SNMP Support in AppleTalk v 58
Date: 7 Jan 93 00:44:07 GMT
Distribution: usa
Organization: Apple

At this point you can get the following RFCs to discribe some of the MIB stuff
RFC 1243 and RFC 1213.  Also this might just be symantics but the SNMP doesn't
spew anything on the network until it is requested from a remote management 
console. I hope this helps some.
B


In article <robrick-060193115828@big-geek.erenj.com>, robrick@erenj.com (Bob Brickman) writes:
> 
>    The documentation for the Network Software Installer v 1.3 mentions that
> the version 58.0 of Appletalk provides some form of SNMP support but gives
> no details. Can anyone provide any more detailed info about what
> information the agent is reporting out over my network?
> 
> Thanks,
> Bob Brickman       <robrick@erenj.com>
>   -- disclaimer: the preceding represent my personal opinions and do not
> reflect the opinions, policies, or practices of my employer
From: phil@compnews.co.uk (Phil Male)
Newsgroups: comp.protocols.appletalk
Subject: Remote site connectivity via IP
Date: 6 Jan 93 18:19:03 GMT
Reply-To: phil@compnews.co.uk
Organization: Computer Newspaper Services, Howden, UK.
NNTP-Posting-Host: sage.compnews.co.uk
X-Newsreader: Tin 1.1 PL4

We run all of our Macs on LocalTalk networks connected to our IP networks
using FastPath 5 boxes. CAP servers are running on Unix hosts scattered all
over the place and the world is a wonderful place.

However, what I need to do now is hook up an external site running EtherTalk
phase I and II networks. We have an existing IP connection to this site
(using cisco routers), but our normal 'throw a FastPath at it' solution is
not going to work, we need to encapsulate packets from the EtherTalk thin-net
onto the IP thin-net.

Is there a box that does this for me? a FastPath with two thin-net
interfaces is really what I'm after (I guess).

--

phil 
   ___/   /
   /_/)  /             Phil Male, Director, Information Systems
  / /_ '/  Computer Newspaper Services, The Bishops Manor, Howden, DN14 7BL
 / / ///    +44 43043 Tel: 1100 Fax: 1108/2022  email: phil@compnews.co.uk
From: billm@phantom.gatech.edu (Bill McLure)
Newsgroups: comp.protocols.appletalk
Subject: Re: recent CAP STAT_CACHE patches
Date: 4 Jan 1993 11:49:31 -0500
Organization: Georgia Institute of Technology
NNTP-Posting-Host: oit.gatech.edu

  Oops..can't put a .sig on the message if I don't have one.

Bill McLure, Systems Support Specialist, Information Technology
Georgia Institute of Technology, Atlanta, Georgia, 30332-0715
uucp: ...!{the known world}!gatech!prism!billm
INTERNET: billm@prism.gatech.edu OR bill.mclure@oit.gatech.edu
Newsgroups: comp.protocols.appletalk
From: rob@leland.Stanford.EDU (Rob Tanner)
Subject: Problem with FileMaker Pro version 2.0v2 on a CAP volume
Keywords: CAP FileMaker
Reply-To: "Rob Tanner" <rob@sherlock.stanford.edu>
Organization: Stanford University, California
Distribution: na
Date: Fri, 8 Jan 93 22:54:58 GMT


I have an on-going (meaning I haven't been able to fix it yet) with
FileMaker Pro version 2.0 (both 2.0v1 and 2.0v2) files becoming
damaged (and sometimes NOT recoverable) when residing on a CAP volume.
I have not had the same problem with files residing on the Mac.

Is there some parameter, et cetera, I need to be aware of in building
CAP (I'm using 6.0pl100 and about to upgrade to 60pl126)?  Has anybody
seen a similar problem.  It is intermittent.  The user may go for
several days with no problem and then try to open the file and get the
message: 

           This file was not closed properly. Filemaker
           is now performing a consistency check

Followed immediately by:
 
           Sorry, this file is badly damaged. Please use
           the recover command.

I'd appreciate any help I can get with this problem.

Thanks,

Rob Tanner
Stanford University


-- 
Rob Tanner                              Internet: rob@sherlock.stanford.edu
System Administrator
Stanford University, California
From: dplatt@ntg.com (Dave Platt)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP aufs desktop problem
Date: 10 Jan 93 06:40:39 GMT
Organization: New Technologies Group, Inc.  Palo Alto CA

>If the user would like another layout on his/hers CAP-folders than the
>standard ones, the changes are not stored by aufs. Even if the
>ADeskTop and .IDeskTop files are deleted and rebuilt it does not have
>any effect on the layour. 
>
>Does anyone have the solution to this problem?

This ought to be in the FAQ list, if it isn't already.

The folder layout information is not stored in the .ADesktop/.IDesktop
files - these hold icon information and application-location bindings,
but not visual-display info.  Instead, it is stored in the .finderinfo
directory.

Your problem is probably this:  the Finder layout information for the
top-level directory (the "disk window" layout) is being lost, because
CAP cannot find a place to store it.  The information is _not_ stored in
the directory that you are "publishing" on the network - instead, it's
stored in the .finderinfo directory which is located "in parallel" to
this top-level directory.  You probably have not created this
.finderinfo directory or have not set the permissions properly.

By way of example:  if you wish to publish /foo/bar/baz as a Macintosh
network disk, you must create _four_ Unix directories:

	/foo/bar/baz
	/foo/bar/baz/.resource
	/foo/bar/baz/.finderinfo
	/foo/bar/.finderinfo

The last of these is probably the one that you are missing.  You should
create it, and set its ownership and write-permissions to be identical
to those of the other three.  Then, dismount the network volume, mount
it again via the Chooser, and set the "View by" arrangement to whatever
you wish - this time it will "stick" properly.
-- 
Dave Platt                                                VOICE: (415) 813-8917
              Domain: dplatt@ntg.com      UUCP: ...netcomsv!ntg!dplatt
 USNAIL: New Technologies Group Inc. 2470 Embarcardero Way, Palo Alto CA 94303