From owner-cvs-usrsbin  Thu May 15 01:51:21 1997
Return-Path: <owner-cvs-usrsbin>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA08154
          for cvs-usrsbin-outgoing; Thu, 15 May 1997 01:51:21 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA08050;
          Thu, 15 May 1997 01:48:07 -0700 (PDT)
From: "Andrey A. Chernov" <ache@FreeBSD.ORG>
Received: (from ache@localhost)
	by freefall.freebsd.org (8.8.5/8.8.5) id BAA17654;
	Thu, 15 May 1997 01:46:58 -0700 (PDT)
Date: Thu, 15 May 1997 01:46:58 -0700 (PDT)
Message-Id: <199705150846.BAA17654@freefall.freebsd.org>
To: CVS-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-usrsbin@FreeBSD.ORG
Subject: cvs commit:  src/usr.sbin/mtree mtree.c
Sender: owner-cvs-usrsbin@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

ache        97/05/15 01:46:58

  Modified:    usr.sbin/mtree  mtree.c
  Log:
  Change FTS_PHYSICAL (not follow symlinks but return them)
  to FTS_LOGICAL (follow symlinks and return their targets)
  
  Because
  1) In the real system there is a lot of symlinks nowdays over
  /var, /spool, etc. Mtree can't do anything for them, i.e. change
  permissions/owner. I.e. if you have /var/mail -> /somewhere
  it will never be changed to group "mail" 775 like -current does now,
  symlink totally confuses mtree.
  
  2) Mtree can't deal with symlinks properly in any case (they are created
  separately in other places now), so we lost no functionality by making
  them invisible for mtree.
  
  Revision  Changes    Path
  1.5       +1 -1      src/usr.sbin/mtree/mtree.c