On Sun, Feb 27, 2011 at 7:43 PM, JB jb.1234abcd@gmail.com wrote:
So it would be: selinux=0 enforcing=0 1
Try it and report back.
Worked like a charm. The combination of first booting to runlevel 1, erasing some stuff to bring disk usage down from 100% to 98% and then disabling SELinux did the trick.
Thanks to everyone!. Btw. this box had Fedora 10... not 12... :) I now realize FC
On 2/27/11 4:01 PM, Fernando Cassia wrote:
On Sun, Feb 27, 2011 at 7:43 PM, JBjb.1234abcd@gmail.com wrote:
So it would be: selinux=0 enforcing=0 1
Try it and report back.
Worked like a charm. The combination of first booting to runlevel 1, erasing some stuff to bring disk usage down from 100% to 98% and then disabling SELinux did the trick.
Thanks to everyone!. Btw. this box had Fedora 10... not 12... :) I now realize
Time for an upgrade to the lastest version of Fedora?
Definitely time to clean up the drive and rid it of all unnecessary baggage.
James McKenzie
On Sun, Feb 27, 2011 at 9:37 PM, James McKenzie jjmckenzie51@gmail.com wrote:
Thanks to everyone!. Btw. this box had Fedora 10... not 12... :) I now realize
Time for an upgrade to the lastest version of Fedora?
Definitely time to clean up the drive and rid it of all unnecessary baggage.
James McKenzie
Surely, I´ve already got F14 running on another drive -actually, the same box-.
This particular hard drive containing F10 used to be in that same PC, but when it started acting up I decided to remove the HD "for later examination and fixing" which ended up being two years later.... as I eventually put the HD in a drawer and forgot about it. :-/
There should be bugfixes for brains with short attention spans like mine. ;)
FC
On 2/27/11 5:54 PM, Fernando Cassia wrote:
On Sun, Feb 27, 2011 at 9:37 PM, James McKenziejjmckenzie51@gmail.com wrote:
Thanks to everyone!. Btw. this box had Fedora 10... not 12... :) I now realize
Time for an upgrade to the lastest version of Fedora?
Definitely time to clean up the drive and rid it of all unnecessary baggage.
James McKenzie
Surely, I´ve already got F14 running on another drive -actually, the same box-.
This particular hard drive containing F10 used to be in that same PC, but when it started acting up I decided to remove the HD "for later examination and fixing" which ended up being two years later.... as I eventually put the HD in a drawer and forgot about it. :-/
There should be bugfixes for brains with short attention spans like mine. ;)
I agree. Good to see that the drive was not actually in use and that you solved the problem.
James McKenzie
FC