Odd problems after running PUP

Kronoz · #1 19th February 2006, 10:09 PM

After running pup to update all packages I was prompted to reboot but when fedora started again it got to "starting udev" and them showed error message that udev didn't how to create various devices, tty1, null, etc.
Then when the GUI took over a blue spinning cursor started and the screen froze.
I have reinstalled FC5 now but I would like to know/debate how to prevent this kind of problem from happening in the future.
Yes I do know that FC5 is testing software but I want to test so I am sticking with it.

Zigzagcom · #2 19th February 2006, 10:41 PM

I've experienced the same problem after I installed FC5T2 on VMware. The install became completely unusable, so I dumped the virtual partition and reloaded FC5. Next I used yum to install yumex and did a few updates from the fedora-extras-development repo.
Today I ran pup again, and it came up empty as far as updates were concerned. At the moment I have no faith in pup, there are no choices to be made. You'd have to trust it completely, and from my last experience, I think it is hardly ready.

**Finalzone** · #3 19th February 2006, 10:44 PM

FYI, pup is integrated with Pirut, the system-config-packages sucessor.

Zigzagcom · #4 19th February 2006, 10:48 PM

Ah, I remember distinctly, that on my first install I had SElinux enabled. On the second try, I disabled it, but then I didn't run pup again. That's FC5 testing for ya...

Did I miss something just now, FinalZone...seems like you edited your post....

**Finalzone** · #5 19th February 2006, 11:13 PM

I edited it. Trying to set SELinux policies to permissive might do the trick.

Zigzagcom · #6 19th February 2006, 11:16 PM

Thanks....
btw, is pup limited by what it can do at the moment, and can one manipulate it any other way?

Kronoz · #7 19th February 2006, 11:17 PM

Ok, so SELinux is causing problems in testing 2?
When I reinstalled I gave SELinux 'Enforce' option, how can I turn it off now? is it possible?

Zigzagcom · #8 19th February 2006, 11:22 PM

At the commandline interface type

Code:

setenforce 0

I can't remember off the top of my head if it persist through a reboot.

**Finalzone** · #9 19th February 2006, 11:23 PM

Change SELinux option to 'Permissive'. 'Enforce' option caused the sytem to not boot.
You can do that via System-->Administration-->Security or via terminal "system-config-securitylevel"

***bob*** · #10 19th February 2006, 11:35 PM

(moved FC5-Dev)