From owner-freebsd-stable Sat Oct 7 12:54:01 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA17462 for stable-outgoing; Sat, 7 Oct 1995 12:54:01 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA17449 for ; Sat, 7 Oct 1995 12:53:57 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA08707; Sat, 7 Oct 1995 12:53:42 -0700 From: "Rodney W. Grimes" Message-Id: <199510071953.MAA08707@GndRsh.aac.dev.com> Subject: Re: Confusing errors from mtree when building -stable To: fenner@parc.xerox.com (Bill Fenner) Date: Sat, 7 Oct 1995 12:53:41 -0700 (PDT) Cc: stable@freebsd.org In-Reply-To: <95Oct7.112856pdt.177475@crevenia.parc.xerox.com> from "Bill Fenner" at Oct 7, 95 11:28:55 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1722 Sender: owner-stable@freebsd.org Precedence: bulk > > I just sup'd -stable and started a "make world"; I got some interesting > error messages from the mtree stage: > > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include > missing: ./machine (not created: File exists) > missing: ./net (not created: File exists) > missing: ./netccitt (not created: File exists) > missing: ./netinet (not created: File exists) > missing: ./netiso (not created: File exists) > missing: ./netns (not created: File exists) > missing: ./nfs (not created: File exists) > missing: ./sys (not created: File exists) > missing: ./ufs (not created: File exists) > missing: ./ufs/ffs (not created: File exists) > missing: ./ufs/lfs (not created: File exists) > missing: ./ufs/mfs (not created: File exists) > missing: ./ufs/ufs (not created: File exists) > missing: ./vm (not created: File exists) > > mtree thinks it's missing but doesn't create it because it exists? Pretty > cool. Mtree is currently confused by symbolic links and needs an -H option that says if the spec says this should be a directory and you find a link follow the link to see if it points to a directory, if it does then do the right things about setting permissions. Or something close to that.. carefull though needs to go into the implementation of a -H option for mtree as interesting things might happen if you had broken symbolic links are where not carefull with how you handled it (IMHO, that case should cause an error more like: missing: ./machine (not created: Broken symbolic link)) Anyone feel like tackling mtree and symbolic links.... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD