I was getting dangerously close to running out of disk space since /usr was filling up fast. I thought it was simple to tar-copy /usr to a different drive/partiton using tar copy such as: (cd /usr; tar cpf - .) | (cd /newpartition; tar xpf -) I tar copied the contents of /usr into my new drive/partition and I changed the partition label to /usr, updated my /etc/fstab file, renamed my /usr to /usr-b, created an empty directory /usr, chmod it to 775, mounted /usr - and it all looked fine. I then unmounted /usr, and then rebooted. The reboot reported that there was a problem with the two library files: somelibfile.so.1 and somelibfile.so.2 and then gnome came up with user/password screen. I logged in as a normal user, and after that point, I a black screen came up with the gnome-X-cursor and then stopped. Nothing worked at this point. I then rebooted using rescue CD, and examined the messages log file and it appears that selinux reported all sorts of AVC denied over /usr and other non-system mounted filesystems. Clearly, it seems that selinux is having problems. I suppose I can reboot setting the selinux = 0 and then begin the task of somehow repairing selinux tags in all of my files? Does this make any sense? Anyone have a better solution? I could reverse the /usr process and get rename /usr-b and comment out the /usr from my fstab, but I wanted some input from member in this forum before attempting to do that - I would end up back to my original disk-space problem. Any advice? No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.15/1173 - Release Date: 12/5/2007 9:29 PM
