From owner-freebsd-current Wed Apr 30 09:41:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA05283 for current-outgoing; Wed, 30 Apr 1997 09:41:31 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA05278 for ; Wed, 30 Apr 1997 09:41:29 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id JAA06991; Wed, 30 Apr 1997 09:41:16 -0700 (PDT) Message-Id: <199704301641.JAA06991@austin.polstra.com> To: imp@village.org Subject: Re: Bug in dump | restore Newsgroups: polstra.freebsd.current In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Wed, 30 Apr 1997 09:41:15 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is old stuff, but I didn't see any replies. In article , Warner Losh wrote: > > 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? No. It's a bug. Personally, I think the immutable flag is a joke and should be ignored at securelevel <= 0. It has never saved me from myself, but it's gotten in my way a few thousand times. But that's a different topic. > P.S. All the links should be created and then the mutable flags > should be set, imho. Or, for each link: clear flags, make the link, restore flags. That's probably easier than saving up all the links and doing them at the end. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth