On Thu, 2007-03-15 at 10:56 -0500, Reuven wrote: > [test2@localhost ~]$ su Shoulda done "su -" not just "su", that's why fdisk wasn't found later on. Not sure if that'd be the cause of any yum problems, though. > [root@localhost test2]# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sda2 9.5G 8.4G 621M 94% / > tmpfs 500M 0 500M 0% /dev/shm > /dev/sda5 6.9G 2.0G 5.0G 29% /usr/D > /dev/sda6 9.8G 776M 9.0G 8% /usr/E Yes, that's rather full. I presume you have a D and E for Windows? I've had systems with less free space than that, but they were just serving files. I wasn't installing things to them, or using applications that needed lots of swap or temporary file space. If I did something that wanted that, it would foul up. > [root@localhost test2]# fdisk -l > bash: fdisk: command not found > > [root@localhost test2]# yum clean packages > Loading "installonlyn" plugin > Killed > [root@localhost test2]# > Message from syslogd@localhost at Thu Mar 15 10:46:20 2007 ... > localhost kernel: Oops: 0000 [1] SMP Hmm, serious problems, but I doubt any of us could tell why from here (low or bad memory, lack of disc space, software errors, etc.). You can try manually doing the same as "yum clean packages" by removing all .rpm files in the subdirectories inside /var/cache/yum/. You won't cause any problems by doing that. -- (This box runs FC5, my others run FC4 & FC6, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
