From owner-freebsd-current  Thu Apr 17 22:03:03 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA03056
          for current-outgoing; Thu, 17 Apr 1997 22:03:03 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA03049
          for <current@freebsd.org>; Thu, 17 Apr 1997 22:02:58 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wI5p1-0004eB-00; Thu, 17 Apr 1997 23:02:55 -0600
To: current@freebsd.org
Subject: Bug in dump | restore
Date: Thu, 17 Apr 1997 23:02:55 -0600
From: Warner Losh <imp@village.org>
Message-Id: <E0wI5p1-0004eB-00@rover.village.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Consider:

# newfs /some/place/interesting
# mount /some/place/interesting
# cd /some/place/interesting
# dump 0f - /usr | restore -rf -
...
warning: cannot create hard link ./bin/ypchsh->./bin/chpass: Operation not permitted
warning: cannot create hard link ./bin/ypchfn->./bin/chpass: Operation not permitted
warning: cannot create hard link ./bin/ypchpass->./bin/chpass: Operation not permitted
warning: cannot create hard link ./bin/chsh->./bin/chpass: Operation not permitted
warning: cannot create hard link ./bin/chfn->./bin/chpass: Operation not permitted
warning: cannot create hard link ./bin/yppasswd->./bin/passwd: Operation not permitted

chpass and passwd are imutable, so the hardlink fails.  I claim this
is a bug.  Can anybody think of a good reason to think of this as a
desirable feature?

Warner

P.S.  All the links should be created and then the mutable flags
should be set, imho.