From owner-freebsd-stable Mon Feb 26 13: 0:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from be-well.ilk.org (lowellg.ne.mediaone.net [24.147.184.128]) by hub.freebsd.org (Postfix) with ESMTP id 5901737B4EC for ; Mon, 26 Feb 2001 13:00:44 -0800 (PST) (envelope-from lowell@be-well.ilk.org) Received: (from lowell@localhost) by be-well.ilk.org (8.11.2/8.11.2) id f1QL0fM76824; Mon, 26 Feb 2001 16:00:41 -0500 (EST) (envelope-from lowell) To: freebsd-stable@freebsd.org Cc: yanek@cigital.com Subject: Re: chflags: Operation not permitted as root? References: <97efpl$1iu6$1@FreeBSD.csie.NCTU.edu.tw> From: Lowell Gilbert Date: 26 Feb 2001 16:00:41 -0500 In-Reply-To: yanek@cigital.com's message of "27 Feb 2001 04:54:13 +0800" Message-ID: <4466hxf9c6.fsf@lowellg.ne.mediaone.net> Lines: 22 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yanek@cigital.com (Yanek Korff) writes: > And here's how I try to get rid of the immutable manually: > omega# chflags noschg ./libscrypt.so.2 > chflags: ./libscrypt.so.2: Operation not permitted > omega# > > And there's how it didn't work. > > > I've got a 4.2-STABLE system which I upgraded from 4.1.1-STABLE a month back > or so... and I didn't encounter this problem. Has anyone else seen > this/have a solution? > Seen it? Certainly. Mostly when running at a raised securelevel. It is one of the *intended* results of running at a raised securelevel. If you didn't know that, read the man page for init(8) so that you'll know *what* securelevels are supposed to do. If you really want to normally run at high securelevels, then you'll need to drop to single-user mode to perform this operation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message