Re: Fedora14 is filling up my HDD without a reason

2011-05-08 Thread Joel Rees
Looking at all the confusing advice you've been given, I'm going to start over from scratch. On Thu, May 5, 2011 at 7:25 AM, Aradenatorix Veckhom Vacelaevus wrote: > Hi everybody: > > I didi about a month ago an instalation of Fedora14 inisde an old Dell > Optiplex Gx260 using an IDE HDD with onl

Re: Fedora14 is filling up my HDD without a reason

2011-05-08 Thread Joel Rees
erk. On Sun, May 8, 2011 at 7:18 PM, Joel Rees wrote: > [...] > Finally, someone mentioned du and dh. Unless you have partitioned that > 10G disk (I'm guessing not.) du won't do much for you, but it also has > the -h (human readable) option. I'm losing touch in my old age. Make that du and df,

Re: Fedora14 is filling up my HDD without a reason

2011-05-08 Thread Frank Murphy
On 06/05/11 04:04, Aradenatorix Veckhom Vacelaevus wrote: > Hi again: > > Thanks once more for all your helping. Well, I don't know if baobab can > help me or if its installed or how to search for it (is it a joke?, I > have not space and are you suggesting me to install more things? ¬¬), > I'm try

killing myself softly with selinux

2011-05-08 Thread Joel Rees
Anyone know a quick way to restore your SELinux policy rules after something gets them so completely messed up that avc can't even talk to itself? (After an upgrade, F13 to F14, and hand-merging the *.rpmsave and *.rpmnew stuff, sudenly no interne, then no login. Had to boot debian to muck in root

Re: killing myself softly with selinux

2011-05-08 Thread Bruno Wolff III
On Sun, May 08, 2011 at 20:19:15 +0900, Joel Rees wrote: > Anyone know a quick way to restore your SELinux policy rules after > something gets them so completely messed up that avc can't even talk > to itself? Boot with a enforcing=0 and autorelabel=1 kernel parameters to fix labelling and not

Re: Fedora14 is filling up my HDD without a reason

2011-05-08 Thread Tim
On Sun, 2011-05-08 at 19:18 +0900, Joel Rees wrote: > I do have something against web applets that gratuitously access your > file system. Recommend against that, as a matter of policy and > principle. It's the kind of security slippery-slope that Microsoft so > blithely rides their software down.