From owner-freebsd-questions Sat Nov 25 17:37:24 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sunny.pacific.net.sg (sunny.pacific.net.sg [203.120.90.127]) by hub.freebsd.org (Postfix) with ESMTP id 6505637B4C5 for ; Sat, 25 Nov 2000 17:37:21 -0800 (PST) Received: from pop2.pacific.net.sg (pop2.pacific.net.sg [203.120.90.86]) by sunny.pacific.net.sg with ESMTP id eAQ1bGo18561; Sun, 26 Nov 2000 09:37:16 +0800 (SGT) Received: from pacificnet (spoff107.pacific.net.sg [203.120.95.107]) by pop2.pacific.net.sg with SMTP id JAA07163; Sun, 26 Nov 2000 09:37:14 +0800 (SGT) Message-ID: <000a01c05749$71ffea00$6b5f78cb@pacificnet> From: "James Lim" To: , References: <20001126013052.3261.qmail@hyperreal.org> Subject: Re: can't chflags/mv current kernel Date: Sun, 26 Nov 2000 09:37:31 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, /sbin/sysctl -a | grep kern.securelevel , wat is your output? itmight be likely that ur kern.securelevel is already 1 or 2 which made it impossible for you to chflags your /kernel. you could set ur kern.secureleve to -1 temporarily. sysctl -w kern.securelevel=-1 hope this helps, Regards, James Lim ----- Original Message ----- From: To: Sent: Sunday, November 26, 2000 9:30 AM Subject: can't chflags/mv current kernel > I rolled the dice and it looks like I can use 2 NICs in the old doorstop > after all, so I'll still be working on trying to configure NAT. > > I compiled a new kernel to support the second NIC, and now I'm having a > more fundamental problem: I cannot touch the old/current kernel. > > # make install > chflags noschg /kernel > chflags: /kernel: Operation not permitted > *** Error code 1 (ignored) > mv /kernel /kernel.old > mv: rename /kernel to /kernel.old: Operation not permitted > *** Error code 1 > > What is this a symptom of? > > It's not covered in the Handbook and I have never had it happen before. > The default kernel was removed just fine. Doesn't matter if I'm in > single-user mode or not; the kernel is untouchable. > > -Mike > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message