From owner-freebsd-hackers Sun Feb 9 10:23:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA27787 for hackers-outgoing; Sun, 9 Feb 1997 10:23:54 -0800 (PST) Received: from po7.andrew.cmu.edu (PO7.ANDREW.CMU.EDU [128.2.10.107]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27782 for ; Sun, 9 Feb 1997 10:23:48 -0800 (PST) Received: (from postman@localhost) by po7.andrew.cmu.edu (8.8.2/8.8.2) id NAA03931 for freebsd-hackers@freefall.FreeBSD.org; Sun, 9 Feb 1997 13:23:32 -0500 Received: via switchmail; Sun, 9 Feb 1997 13:23:25 -0500 (EST) Received: from apriori.cc.cmu.edu via qmail ID ; Sun, 9 Feb 1997 13:22:45 -0500 (EST) Received: from apriori.cc.cmu.edu via qmail ID ; Sun, 9 Feb 1997 13:22:44 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.05.56.sun4.41.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.apriori.cc.cmu.edu.sun4m.412 via MS.5.6.apriori.cc.cmu.edu.sun4_41; Sun, 9 Feb 1997 13:22:43 -0500 (EST) Message-ID: Date: Sun, 9 Feb 1997 13:22:43 -0500 (EST) From: Robert N Watson To: freebsd-hackers@freefall.FreeBSD.org Subject: Ownership -- ports, packages + cdrom under 2.1.5 (+6) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This may be correct under 2.2, 3.0-SNAP (I couldn't find any instances in the 3.0 packages I installed.) Under 2.1.5, when I installed packages, I would find them owned by arbitrary (but common) uid's other than ones that exist on my system. Often they would be user id's like 2035 or 278, and often with seemingly arbitrary group id's (like 137.) On the CD-ROM's, many files are owned by 2035 (Jordan? :). Would it be possible to ship out CD's + ports owned by standard users? It was an uncomfortable experience when I created a user and found they owned the whole xemacs tree (installed as a package), etc. With the dore port, etc, I've had the same problem with installed binaries. Also, under 2.1.5, I've suffered from running sysinstall/package management programs and using a umask other than 0 -- the packages tend to get installed readable ownly by owner. Again, this may be corrected, but it would be nice if sysinstall set the umask to 0 for the course of its installation, or warned the user about the problem. I don't think I've had this experience under 3.0, so I assume that's fixed. I realize I've been a source of complaints for the last day or so, but having discovered that freebsd-hackers is an accessible list despite undergoing n-hundred posts a day, I'm suffering a bout of report-stuff syndrome. :) Once I get my 3.0-SNAP system running with a bigger drive, I'll get the source going and do something more constructive, assuming that's desirable. :) Thanks, Robert Watson