From owner-freebsd-hackers Thu May 29 12:02:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA02451 for hackers-outgoing; Thu, 29 May 1997 12:02:04 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02443 for ; Thu, 29 May 1997 12:02:01 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/8.7.3) id MAA20045; Thu, 29 May 1997 12:01:52 -0700 (MST) From: Don Yuniskis Message-Id: <199705291901.MAA20045@seagull.rtd.com> Subject: Re: uucp uid's To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 29 May 1997 12:01:51 -0700 (MST) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19970529190015.FX15381@uriah.heep.sax.de> from "J Wunsch" at May 29, 97 07:00:15 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings! > > I have a couple of (older) SysV derivatives that had uucp own the > > files and nuucp be the working "public" login. > > Yep, but i've also seen systems where it's been just reversed. (I > think DG/UX came this way in version 4.3x, probably due to BSD > history, and maybe even swapped them in version 5.4x to increase the > degree of confusion.) Undoubtedly! :-( Seems like everyone wants to break it in a slightly different way! :> > > Having the administrative id the same as the working id I guess is just > > annoying since it doesn't allow you to 'su - uucp' before modifying > > any of the configuration files of creating new directories. > > `su -m uucp' should work though. With the exception of having to move into /etc/uucp manually instead of letting $HOME do it for you... I guess it's just a matter of what you're accustomed to! --don