Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!turnkey!itcorp!geoff
From: geoff@ITcorp.com (Geoff Kuenning)
Newsgroups: comp.sys.next
Subject: Re: Various questions
Keywords: release 1.0a, NextAnswers, Techdoc, Stuart, kermit, screen
Message-ID: <1991Apr8.065844.26237@ITcorp.com>
Date: 8 Apr 91 06:58:44 GMT
References: <3210@beguine.UUCP>
Organization: Interrupt Technology Corporation, Manhattan Beach, CA
Lines: 13

In article <3210@beguine.UUCP> Gerben.Wierda@samba.acs.unc.edu (Gerben Wierda) writes:

> 3. I did the change "chown uucp Kermit; chmod u+s Kermit" instead of
> making /dev/cua writable readable for everybody. But now any file I get
> to the system is owned by uucp instead of me. Isn't chmod on /dev/cua a
> better solution after all? Or is there another fix?

I prefer to do "chgrp uucp Kermit; chmod u-s,g+s Kermit" and make things
writable by the uucp group.  This still means that files will be members of
the uucp group, so you probably should remember to do chgrps on them, but
at least they're owned by you.
-- 
	Geoff Kuenning   geoff@ITcorp.com   uunet!desint!geoff