On Mon, 2005-05-30 at 09:26 -0400, Matthew Miller wrote: > On Sat, May 28, 2005 at 09:30:58AM +0300, Panu Matilainen wrote: > > > It's probably good to list this stuff explicitly, but actually, I think > > > all you need to protect is the yum package itself, because an attempt to > > > remove glibc, rpm, or python eventually tries to remove yum too. > > Like said, this was just a trivial/mock-up version of the thing. There's a > > whole lot more to protect than just those to keep a system in bootable > > state, which I think would be a reasonable target for such a plugin. > > I agree. (Hmmm -- maybe anything in the 'core' group?) Is there an updated > version of something like <http://adrian.gimp.org/rpm-graph/> anywhere > around? I kind of suspect that *anything* which would make the system not > boot would also cause (eventually) yum itself to get pulled into the > set to be removed. I think a reasonable alarm set is > 100 pkgs being removed or glibc, rpm and python. the system (esp chroots) do not need kernels to run. -sv
