Date: Sat, 25 Nov 2000 23:26:17 -0800 (PST) From: Roop Nanuwa <roop@gw.carpoolbc.com> To: mike@hyperreal.org Cc: freebsd-questions@FreeBSD.ORG Subject: Re: can't chflags/mv current kernel Message-ID: <Pine.BSF.4.21.0011252325550.4843-100000@gw.carpoolbc.com> In-Reply-To: <20001126013052.3261.qmail@hyperreal.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Are you sure you're logged in (or su'd) as root? RSN On Sat, 25 Nov 2000 mike@hyperreal.org wrote: > 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?Pine.BSF.4.21.0011252325550.4843-100000>