On 04/25/2013 05:49 PM, Ed Greshko issued this missive:
On 04/26/13 08:39, Richard Vickery wrote:
Since I'm not up on F19, there is really no reason to write to the test list, is there? I believe I will give up with all this push-back.
rpm -qa | grep fc19 produced nothing. How am I supposed to write this to the test list when there is no context?
Violating my declaration....
Well, earlier you stated....
"The command called was: sudo fedup-cli --network 19 --debuglog fedupdebug.log"
But, very apparently, you've not upgraded to F19. So, best to just drop it all and move on. Nothing on this thread applies to your situation.
That is correct. A cat of his /etc/issue resulted in showing he's still on F18. The fedup probably failed in a similar manner (I don't think fedup is really fully baked yet).
Richard, if I read one of your last postings correctly, I believe your kernel issue has been resolved with a "yum update kernel*", in that you're now on a 3.8 kernel rather than 3.7. Is that correct? If not, check your /boot directory and verify you have 3.8 kernels in there. If so, then the problem is probably the grub configuration not booting the new kernel. Now that we've established that you actually on an F18 system, we can (probably) sort out the rest of your issues. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - If your broker is so damned smart...why is he still working? - ----------------------------------------------------------------------