SCIENTIFIC-LINUX-DEVEL Archives

March 2007

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephen John Smoogen <[log in to unmask]>
Reply To:
Stephen John Smoogen <[log in to unmask]>
Date:
Tue, 13 Mar 2007 14:58:53 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (69 lines)
On 3/13/07, Troy Dawson <[log in to unmask]> wrote:
> Karanbir Singh wrote:
> > Troy Dawson wrote:

> > Do you intend to leave the rhn specific code in the distro ? apart from
> > that, I dont think there should be a major issue. But we need to watch
> > for that.
> >
>
> I still don't know.
> We pulled all the rhn stuff out of the comps file, and it looks like
> nothing depends on it.  So it looks like it would be safe to actually
> pull it out of the release.
> But in the back of my mind I just know that if we pull all the rhn stuff
> out of the release, someone is going to find a use for it.
> But on the other hand, if we don't pull it out, somebody is going to
> install it and then complain because it doesn't work, even though they
> would need a RHN subscription to get it to work.
>

Ok this is going to sound very silly.. but I know of certain locations
that 'need' to be able to have RHN working on their SciLin and Centos
systems. The reason was that they needed it to meet agency
interpretations of FISMA guidelines.


> We always have yum-conf be separate from yum.  So that if a site want's
> to have their own yum configuration, they don't have to worry about
> messing with the main yum file, they can just change the yum-conf.  We
> also add the kernel-module, and hopefully I can get the final minor bugs
> out of the merger of kernel-module and kmdl.
> But beyond that, the other plugins and utils will be their own rpm's.
> Actually, now that I think of it, Connie had mentioned putting
> protectbase into the main one, and Jarek had talked about getting
> fastestmirror in as well.
> Connie isn't here, so I can't ask her her opinion right now, so we'll
> have to get back to you on that.
> I know, the only problem I have with fastestmirror is getting the
> initial list of mirrors in a file.
> Does anyone else have any opinions about which plugin's should be in the
> base yum?
>

Looking at the Centos 4.92 extras

yum-allowdowngrade.noarch                1.0.3-1.el5.centos     extras
yum-changelog.noarch                     1.0.3-1.el5.centos     extras
yum-downloadonly.noarch                  1.0.3-1.el5.centos     extras
yum-fastestmirror.noarch                 1.0.3-1.el5.centos     extras
yum-fedorakmod.noarch                    1.0.3-1.el5.centos     extras
yum-kernel-module.noarch                 1.0.3-1.el5.centos     extras
yum-priorities.noarch                    1.0.3-1.el5.centos     extras
yum-protectbase.noarch                   1.0.3-1.el5.centos     extras
yum-skip-broken.noarch                   1.0.3-1.el5.centos     extras
yum-tsflags.noarch                       1.0.3-1.el5.centos     extras
yum-updateonboot.noarch                  1.0.3-1.el5.centos     extras
yum-utils.noarch                         1.0.3-1.el5.centos     extras
yum-versionlock.noarch                   1.0.3-1.el5.centos     extras
yumex.noarch                             1.2.2-1.0.el5.centos   extras

plus there is the yum-cron that seth says is a better plan for some
machines than yum-updatesd


-- 
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"

ATOM RSS1 RSS2