Date: Fri, 05 May 2006 20:09:58 -0700 From: John Pettitt <jpp@cloudview.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: rm: Operation not permitted Message-ID: <445C1386.5090900@cloudview.com> In-Reply-To: <20060506030038.GA14966@xor.obsecurity.org> References: <445C0FCF.20106@cloudview.com> <20060506030038.GA14966@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Fri, May 05, 2006 at 07:54:07PM -0700, John Pettitt wrote: > >> I'm having trouble erasing some files - this on a 6.1RC system (built >> from -STABLE) - I created a system image using his script: >> >> #!/bin/sh >> make buildworld KERNCONF=CLOCK >> make buildkernel KERNCONF=CLOCK >> mkdir -p /raid/diskless/clock >> make installworld DESTDIR=/raid/diskless/clock >> cd /usr/src/etc; make distribution DESTDIR=/raid/diskless/clock >> cd /usr/src >> make installkernel KERNCONF=CLOCK DESTDIR=/raid/diskless/clock >> >> and now when I try to delete it this happens ... >> >> # rm -rf clock >> rm: clock/bin/rcp: Operation not permitted >> rm: clock/bin: Directory not empty >> rm: clock/lib/libcrypt.so.3: Operation not permitted >> rm: clock/lib/libc.so.6: Operation not permitted >> rm: clock/lib: Directory not empty >> rm: clock/libexec/ld-elf.so.1: Operation not permitted >> rm: clock/libexec: Directory not empty >> rm: clock/sbin/init: Operation not permitted >> rm: clock/sbin: Directory not empty >> >> and so on. >> >> The system is running at securelevel -1 and the rm fails even in single >> user mode - what am I missing? >> > > chflags -R noschg > > Kris > Thanks that did it. Not enough caffeine today. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?445C1386.5090900>