Date: Mon, 28 May 2012 13:05:45 -0600 From: Gary Aitken <freebsd@dreamchaser.org> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: removing /var/empty on a non-system disk Message-ID: <4FC3CC89.1000504@dreamchaser.org> In-Reply-To: <20120526000123.cf1a67f8.freebsd@edvax.de> References: <4FBBF32D.9070505@dreamchaser.org> <20120522234510.a406941d.goksin.akdeniz@gmail.com> <4FBD7BA0.7070502@dreamchaser.org> <4FBEE05A.6000909@dreamchaser.org> <20120525035108.a3af81c1.freebsd@edvax.de> <CA%2BtpaK2Rwvg_G8veqh9bwV_KZPx6Tz4pxWr0cVh8ZbPEBg5=pg@mail.gmail.com> <4FBFAB5B.6010405@dreamchaser.org> <4FBFCC61.2010504@dreamchaser.org> <4FBFE5E2.6070305@dreamchaser.org> <20120525222123.474401eb.freebsd@edvax.de> <4FBFF3F2.60501@dreamchaser.org> <20120526000123.cf1a67f8.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/25/2012 4:01 PM, Polytropon wrote: > On Fri, 25 May 2012 15:04:50 -0600, Gary Aitken wrote: >> On 05/25/12 14:21, Polytropon wrote: >>> On Fri, 25 May 2012 14:04:50 -0600, Gary Aitken wrote: >>>> something I'm not seeing >>>> >>>> I've got a disk previously used as a sys disk I'm trying to clean up. >>>> What's the key to removing /var/empty? >>>> >>>> 280 /hd1/var#sysctl kern.securelevel >>>> kern.securelevel: -1 >>>> 281 /hd1/var#ls -l >>>> total 4 >>>> dr-xr-xr-x 2 root wheel 512 Jan 3 00:55 empty >>>> 282 /hd1/var#chflags noschg empty >>>> 283 /hd1/var#chmod 777 empty >>>> chmod: empty: Operation not permitted >>>> 284 /hd1/var#rmdir empty >>>> rmdir: empty: Operation not permitted >>> >>> Interesting, I just tried this on my home system (FreeBSD 8.2-STABLE) >>> and it worked as intended. I did use the exact commands, >>> same securelevel. >>> >>> Use the -o option for ls (ls -lo) to check on the effect >>> of chflags and chmod. >> >> Just found it, something I forgot about a long time ago... >> I was running under su logged in as my normal user. >> Had to back all the way out and log in as root. > > I should have mentioned that I did the (successful) test > logging in as root (real console login). If you use "su -" > or "su root", the effect should be the same. You can always > check the success of your operation with the "ls -lo" command. Nope. That was the problem. I had logged in on the vty as normal user and done su root. Had to back all the way out and log in on the vty as root to make it work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FC3CC89.1000504>