[comp.sys.next] can't "talk" to anyone...

hemstree@jobs.mso.colostate.edu (Charles H. Hemstreet IV) (11/24/90)

Hey Folks, I have an old cube.  My talk daemon is giving me a 

	"talk:jobs: Can't figure out network address."

message when I try and talk to anyone, including myself.
BTW: I don't normally talk to myself, but I'm getting close to finals,
and getting a little crazy.  If someone could have mercy on me and
help me out, I would greatly appreciate it.  I am getting tired of
"write"ing to people I want to get a quick message to. (and talking to
myself :-)  Email replys are desired.  If
hemstree@jobs.mso.colostate.edu doesn't work, try
hemstree@handel.cs.colostate.edu


Thanks, 
Charles


--
!===========================================================================!
! Charles H. Hemstreet IV       !internet: hemstree@jobs.mso.Colostate.Edu  !
! Colorado State University     ! Microcomputer Services Organization (MSO) !
!===========================================================================!

cnh5730@calvin.tamu.edu (Chuck Herrick) (11/28/90)

In article <HEMSTREE.90Nov24003451@jobs.jobs.mso.colostate.edu) hemstree@jobs.mso.colostate.edu (Charles H. Hemstreet IV) writes:
)
)Hey Folks, I have an old cube.  My talk daemon is giving me a 
)
)	"talk:jobs: Can't figure out network address."
)
)message when I try and talk to anyone, including myself.

You think this is bad, my cube gives me

	"you don't exist. go away"

how about that for interpersonal computing!

scott@mcs-server.gac.edu (Scott Hess) (11/28/90)

In article <10423@helios.TAMU.EDU> cnh5730@calvin.tamu.edu (Chuck Herrick) writes:

WRT talk(1) not working:

   You think this is bad, my cube gives me

	   "you don't exist. go away"

   how about that for interpersonal computing!

That means that whatever you are using for an emulator is not correctly
setting up /etc/utmp and /dev/tty[pq]?.  Stuart and Terminal both do this
correctly, but since those files are in restricted areas of the system,
they must be setuid root to do their work.  To set this up (in the case
of Stuart):

su
chown root.tty Stuart
chmod 6755 Stuart

Of course, there are reasons _not_ to do this.  Here, we run Stuart setuid,
and it hasn't caused a problem.  In fact, I've not heard of anyone having
a problem with it, though I also haven't heard how many people are actually
running setuid, either.
--
scott hess
scott@gac.edu
Independent NeXT Developer	(Stuart)
GAC Undergrad			(Horrid.  Simply Horrid.  I mean the work!)
<I still speak for nobody>