Beau,
Most everything you could need to know is in the man pages for yum. If you have specific questions not answered by the man pages, please feel free to ask me for my experiences, Seth (who wrote the thing so should be able to answer *anything* about it), or the list.
I'm actually a Debian developer myself, but we're using CentOS at work, and I find yum quite comfortable (and a good deal less complex than apt for setting up and maintaining local repositories).
I've recently implemented the use of the yumgroups.xml file to define groups of packages for installation on different classes of machines. It works very well (provided you make sure that all the important files are actually readable!).
Claire
I love apt too, I've used yum in fedora 1, but my experiences were very unsatisfactory. I'm sure yum grew up since, I have to give it a spin one of these days.
Currently on Centos I'm using dag's apt http://dag.wieers.com/packages/apt/
and Repo-janitor http://www.bioxray.dk/~mok/repo-janitor.php to manage my local repository. The cool part about repo-janitor that the repository is both yum and apt so I can still use up2date for it.
This is my repo-janitor.xml file:
<repo-janitor id="Tracbox Apt/Yum repository" topdir="/var/repo-janitor/" >
<distribution id="centos-3">
<release id="3.3" arch="i386"> <description>Centos 3.3 release for i386 architecture.</description>
<component id="os"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/os/i386/RedHat/RPMS/</mirror> <mirror type="srpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/os/SRPMS/</mirror> <description>Main Centos Linux packages</description> </component>
<component id="updates"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/updates/i386/RPMS/</mirror> <mirror type="srpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/updates/i386/SRPMS/</mirror> <description>Updated and fixed versions of Centos Linux packages</description> </component>
<component id="addons"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/addons/i386/RPMS/</mirror> <mirror type="srpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/addons/i386/SRPMS/</mirror> <description>Addons for Centos Linux packages</description> </component>
<component id="contrib"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/contrib/i386/RPMS/</mirror> <mirror type="srpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/contrib/i386/SRPMS/</mirror> <description>Contrib for Centos Linux packages</description> </component>
<component id="extras"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/extras/i386/RPMS/</mirror> <mirror type="srpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/extras/i386/SRPMS/</mirror> <description>Extras for Centos Linux packages</description> </component>
<component id="testing"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/testing/i386/RPMS/</mirror> <mirror type="srpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/testing/i386/SRPMS/</mirror> <description>Testing for Centos Linux packages</description> </component>
<component id="docs"> <mirror type="rpm">rsync://mirror.physics.ncsu.edu/caoslinux/centos-3/3.3/docs/RPMS/</mirror> <description>Docs for Centos Linux packages</description> </component>
<component id="misc"> <description>Misc Local packages</description> </component>
</release> </distribution>
</repo-janitor>
On Tue, 07 Dec 2004 11:55:59 -0800, C.M. Connelly cmc@math.hmc.edu wrote:
Beau,
Most everything you could need to know is in the man pages for yum. If you have specific questions not answered by the man pages, please feel free to ask me for my experiences, Seth (who wrote the thing so should be able to answer *anything* about it), or the list.
I'm actually a Debian developer myself, but we're using CentOS at work, and I find yum quite comfortable (and a good deal less complex than apt for setting up and maintaining local repositories).
I've recently implemented the use of the yumgroups.xml file to define groups of packages for installation on different classes of machines. It works very well (provided you make sure that all the important files are actually readable!).
Claire
-- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc@math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Here are a few starters commands, these are the most common.
yum check-update (check to see if any packages need updating)
yum update (updates any/all packages that need it) yum update packagename1 packagename2 (only update packagename1 & 2)
yum install packagename1 (installs packagename) yum install packagename (same as above but does not prompt you for confirmation)
yum list available | grep -i packagename (checks to see if packagename is available at yum server)
yum search packagename (useful if you're not sure the name of the package, ie. httpd vs apache, RedHat names the Apache package httpd)
yum info packagename (similar to rpm -qi, give you info on packagename)
yum upgrade (I've only used this once, upgrading a test system running RHEL 3ES to CentOS, seems like if you point your Yum conf to a different distro's yum repo it will upgrade to that version, probably also useful for upgrade from CentOS2 to CentOS3)
For install, update, and upgrade, you can pass it the -y variable and it won't prompt you to confirm your actions. You can also customize your yum.conf to exclude certain packages from update/upgrade like the kernel. You can also specify that some packages(again kernel) only get installed and not upgraded.
This is more a samba question however I want to know the userlimit if anyone has deployed a large samba PDC with more than 50 users and if so any problems? Thanks in advance
I have about 150 different users in a standard samba user base (no LDAP) about 100 or so log on at a time and no problems here. We love it.
Dom
support@dynacomp.net wrote:
This is more a samba question however I want to know the userlimit if anyone has deployed a large samba PDC with more than 50 users and if so any problems? Thanks in advance
CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
Hey all,
Since we are on the yum topic...I have a little shell script that I put in /etc/cron.daily/, that checks for updates and emails root if updates are available. Otherwise, if no updates are available, it is silent. Here it is:
######################## #!/bin/sh
PATH=/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin
yum check-update >>/dev/null STATUS=$?
if [ "$STATUS" -eq 100 ]; then echo "CentOS RPM updates are available" | mail -s "Updates Available" root fi #########################
If you want it to actually email your personal email address, either change "root" to your email address, or better yet -- set up /etc/aliases to forward root's email to your personall address. If you do that be sure to run newaliases when you are done editing that file.
-Ryan
Matt Shields wrote:
Here are a few starters commands, these are the most common.
yum check-update (check to see if any packages need updating)
yum update (updates any/all packages that need it) yum update packagename1 packagename2 (only update packagename1 & 2)
yum install packagename1 (installs packagename) yum install packagename (same as above but does not prompt you for confirmation)
yum list available | grep -i packagename (checks to see if packagename is available at yum server)
yum search packagename (useful if you're not sure the name of the package, ie. httpd vs apache, RedHat names the Apache package httpd)
yum info packagename (similar to rpm -qi, give you info on packagename)
yum upgrade (I've only used this once, upgrading a test system running RHEL 3ES to CentOS, seems like if you point your Yum conf to a different distro's yum repo it will upgrade to that version, probably also useful for upgrade from CentOS2 to CentOS3)
For install, update, and upgrade, you can pass it the -y variable and it won't prompt you to confirm your actions. You can also customize your yum.conf to exclude certain packages from update/upgrade like the kernel. You can also specify that some packages(again kernel) only get installed and not upgraded.
Excellent!!! May I make one suggestion? Add $HOSTNAME in a couple places, so if you have multiple computers you know which one needs to be updated.
######################## #!/bin/sh
PATH=/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin
yum check-update >>/dev/null STATUS=$?
if [ "$STATUS" -eq 100 ]; then echo "CentOS RPM updates are available for $HOSTNAME" | mail -s "Updates Available for $HOSTNAME" root fi #########################
Matt Shields wrote:
Excellent!!! May I make one suggestion? Add $HOSTNAME in a couple places, so if you have multiple computers you know which one needs to be updated.
That's a great idea! That's why it's so useful to have many eyes looking at these things. =]
-Ryan
-
Andy Masiar -
C.M. Connelly -
Dominic Iadicicco -
Matt Shields -
Ryan Lane -
support＠dynacomp.net