On Fri, Nov 7, 2008 at 9:49 AM, Daniel J Walsh <dwalsh@xxxxxxxxxx> wrote: > selinux-policy-targeted is a memory hog, but it should not have changed > that drastically in updates. > > Is this repeatable? 100% repeatable on the 3 attempts on the lower-mem machine. On the same machin The package selinux-policy-targeted 3.3.1 103.fc9 -- I am running a couple of additional installs to gather more information. On Fri, Nov 7, 2008 at 9:59 AM, Chris Lumens <clumens@xxxxxxxxxx> wrote: >> - Anaconda OOMs without a warning or useful message to the user > > I don't believe there's any way for anaconda to know this, and there's > certainly no way for us to do anything about it. Well, the behaviour is really weird. Perhaps there is no OOM killer in place during an anaconda install? If there was, it'd expect the rpm process or anaconda to be shot down -- but the machine is halting instead, it literally switches off. Whatever is bootstrapping anaconda (init script in the initrd?) should be able to at least see the odd exit status and echo a "something went wrong" msg...? Maybe that's the problem? cheers, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
