Date: Sun, 26 Nov 2000 09:37:31 +0800 From: "James Lim" <jameslpin@pacific.net.sg> To: <mike@hyperreal.org>, <freebsd-questions@FreeBSD.ORG> Subject: Re: can't chflags/mv current kernel Message-ID: <000a01c05749$71ffea00$6b5f78cb@pacificnet> References: <20001126013052.3261.qmail@hyperreal.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <mike@hyperreal.org>
To: <freebsd-questions@FreeBSD.ORG>
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000a01c05749$71ffea00$6b5f78cb>