Discuss January 2005

discuss@lists.centos.org

125 participants
150 discussions

CentOS-4.0 (Beta) for i386 Official Release
by Johnny Hughes 18 Jan '05

18 Jan '05

The CentOS team is happy to announce the availability of CentOS-4.0 (Beta) for i386. This product supports AMD Athlon, Athlon XP, Duron, and Intel Pentium, Pentium Pro, Pentium II, Pentium III, Pentium 4 and Pentium Xeon processors. A bittorent for individual CD binary iso files is available from: http://beta.centos.org/centos/4.0beta/isos/i386/CentOS-4.0-Beta-i386-discs1… The source RPMS are available via bittorrent from: http://beta.centos.org/centos/4.0beta/isos/i386/CentOS-4.0-Beta-i386-src6-9… If possible, please use bittorrent to download all files and please leave your download client running after the download is complete (with ports 6881-6889 open) as your client will become part of the peer to peer bittorrent network and reduce the load on our network mirrors. If you need some quick pointers for getting up to speed on bittorrent read: http://www.centos.org/modules/smartfaq/faq.php?faqid=24 If you can't use bittorrent (please try), ISOs are available here: Binary and Source CDs: http://beta.centos.org/centos/4.0beta/isos/i386/ --------------------- NOTE: This is a Beta distribution and may not be suitable for use in production environments. Please add any errors or bugs you encounter to bugzilla on http://www.centos.org/bugs --------------------- You must change your "/etc/sysconfig/rhn/sources" and your "/etc/yum.conf" files to point to the beta server. For examples of each of these files see: http://centos.HughesJR.com/build/ --------------------- To stay current with CentOS: Join the CentOS mailing list at: http://lists.caosity.org/mailman/listinfo/centos Join various team members on IRC at irc.freenode.net #centos Visit our new website at http://www.centos.org Enjoy, The CentOS Team

3 2

CentOS-4.0 (Beta) for x86_64 Official Release
by Johnny Hughes 18 Jan '05

18 Jan '05

The CentOS team is happy to announce the availability of CentOS-4.0 (Beta) for x86_64. This product supports AMD64 and Intel EM64T processors. A bittorent for individual CD binary iso files is available from: http://beta.centos.org/centos/4.0beta/isos/x86_64/CentOS-4.0-x86_64-beta-bi… A bittorrent for the DVD binary iso images is available from: http://beta.centos.org/centos/4.0beta/isos/x86_64/CentOS-4.0-x86_64-beta-bi… The source RPMS are the same as the i386 version of CentOS-4.0 (Beta), and are available via bittorrent from: http://beta.centos.org/centos/4.0beta/isos/i386/CentOS-4.0-Beta-i386-src6-9… If possible, please use bittorrent to download all files and please leave your download client running after the download is complete (with ports 6881-6889 open) as your client will become part of the peer to peer bittorrent network and reduce the load on our network mirrors. If you need some quick pointers for getting up to speed on bittorrent read: http://www.centos.org/modules/smartfaq/faq.php?faqid=24 If you can't use bittorrent (please try), ISOs are available here: Binary CDs: http://beta.centos.org/centos/4.0beta/isos/x86_64/ Source CDs: http://beta.centos.org/centos/4.0beta/isos/i386/ --------------------- NOTE: This is a Beta distribution and may not be suitable for use in production environments. Please add any errors or bugs you encounter to bugzilla on http://www.centos.org/bugs --------------------- You must change your "/etc/sysconfig/rhn/sources" and your "/etc/yum.conf" files to point to the beta server. For examples of each of these files see: http://centos.HughesJR.com/build/ There is also a known bug with openoffice.org, the library compat- libstdc++-33-3.2.3-46.1.i386.rpm was not included on the ISO. After doing the installation, and after changing your yum.conf (or up2date sources) file as detailed above, issue one of these commands to get the library: yum install compat-libstdc++-33.i386 or up2date compat-libstdc++-33.i386 --------------------- To stay current with CentOS: Join the CentOS mailing list at: http://lists.caosity.org/mailman/listinfo/centos Join various team members on IRC at irc.freenode.net #centos Visit our new website at http://www.centos.org Enjoy, The CentOS Team

1 0

RHEL 4 => CentOS 4
by Michiel van Es 17 Jan '05

17 Jan '05

Hi, I would like to try to switch from CentOS 3.4 => CentOS 4 beta. I hava a couple of questions: -is possible to upadte/upgrade my test box from 3.4 => 4 and what are the yum.conf settings/requirements? -is it easy to update your CentOS 4 beta => CentOS 4 when the stable version comes out? Thanks in advance! -- Kind Regards, Michiel van Es

7 15

Mod_Throttle for Apache 2?
by Matt Shields 17 Jan '05

17 Jan '05

We have some custom software that is put out on our 6 clustered(balanced) webservers. Every 5 minutes that software checks into our server for a new version, if there is a new version it downloads it (20MB file). This happens about 2-3 times per month. Currently there are over 10000 clients that need to download the update. Up until this past week we were able to handle the load and this is putting a serious strain on our webservers. We were hoping to throttle the amount of traffic that each of the webservers would take and the bandwidth that each client consumes. Previously I've used Mod_Throttle for Apache 1.3 on other projects, but on our new servers they are running Apache 2. So are there any similar solutions for Apache 2? -- Matt Shields http://masnetworks.biz http://shieldsmedia.com (currently under construction) http://shieldsproductions.com (currently under construction)

3 4

bind and 3.4
by Francois Caen 17 Jan '05

17 Jan '05

Hello, I encountered a problem when upgrading from 3.3 to 3.4 on i386. The machine is a production name server running bind. Looks like the new rpm moved my named.conf to .rpmsave and chkconfig'ed bind to off. That's really bad. A more gentle behavior would have been to save the new named.conf to .rpmnew and not mess with initscripts. Anyone else notice that? Francois Caen

12 29

Postfix 2.1 RPM?
by Support Ev.-Theol. Fak. Uni Bonn 16 Jan '05

16 Jan '05

hi all, i`m looking for an postfix 2.1 rpm for CentOS 3 with TSL support. i tried the rpm form: http://ftp.wl0.org/official/2.1/RPMS-rhel3-i386/postfix-2.1.5-4.rhel3.i386.… but it doesn`t support tsl.

3 2

Guide to stripping Centos 3
by R P Herrold 16 Jan '05

16 Jan '05

I responded to a post in the Dell poweredge mailing list earlier today. My answer was off the top of my head, with a bit of experimentation. The content may be useful in the Cenyos context as well to admin's looking to strip the size of an install to the bare bones. Comment welcomed. Can anyone see any packages which I have missed? -- Russ Herrold ---------- Forwarded message ---------- Date: Sat, 15 Jan 2005 12:29:12 -0500 (EST) From: R P Herrold <herrold(a)owlriver.com> To: linux-poweredge(a)dell.com Subject: Re: dell-lnx-pe] Re: Stripping RHEL 3.0? > At 07:58 PM 1/14/2005 -0500, David Hubbard wrote: >> Does anyone know of a good guide for stripping >> down RHEL 3.0? <snip> >> Due to all the dependencies >> I can't find a way to actually strip RHEL in a way >> that leaves everything happy. Great timing and a good question -- I was just building such a host. I'll test for a bit to minimize size. Kickstart and anaconda are your friends. Here is a quick guide: During each install, a file called 'ks.cfg' is left by anaconda in /root/ At the end of this post, I include the ks.cfg file which will build a stripped host. I have done a couple test installs, and gone through the resulting packagelist using; rpm -qa --qf '%{size} %{name} \n' | sort -n | less to see what I could add with the '-' prefix at the bottom of the file. (I have left in there a couple 'conveneince packages' and I usually add one extravagance -- I prefer 'konsole' to pop back as a remote terminal and so pay its space penalty, but comment it out here) As I said, I 'went hunting' and trimmed it down to 465 M ; more savings are possible. The worst remaining mandatory 'size offenders' in the install are: glibc-common 42M perl 27M kernel 22M Not much more we can do there. But ... Once the install is done, turn off auditting: chkconfig audit off service audit stop and reclaim the LARGE (100M) amout of room these files eat up cd /var/log/audit.d/ rm -f * Unfortunately the package is not deletable as there are dependency issues. As I say. I then end up at: 465M Using a network install from a local mirror and a ks.cf file permits 'gameing' to see what changed in the ks.cfg result in a given size profile. See my notes at: http://www.owlriver.com/tips/pxe-install/ for more information on setting up and debugging such an environment. It permits experimentation with fast test installs (under ten minutes per test shot, even on a low RAM host (64M)) to 'tune' for a desired result. -- Russ Herrold [root@ftp kickstart]# cat ks.cfg-Centos_34 # # Centos 34 server - built to be tiny as possible # install lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us mouse genericwheelps/2 --device psaux url --url ftp://10.16.33.105/pub/install/ftpinstall # xconfig --card "RIVA128" --videoram 4096 --hsync 31.5-35.1 --vsync 50-61 --resolution 1280x800 --depth 24 skipx network --device eth0 --bootproto dhcp # rootpw --iscrypted <elided> firewall --disabled # not yet in RHEL 3 # selinux --disabled authconfig --enableshadow --enablemd5 timezone America/New_York bootloader --location=mbr # --append hdb=ide-scsi # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --size=1024 --grow --ondisk=hda part /var/spool --fstype ext3 --size=1024 --grow --ondisk=hda part /var/cache --fstype ext3 --size=1024 --grow --ondisk=hda part /var/log --fstype ext3 --size=1024 --grow --ondisk=hda part swap --size=128 --grow --maxsize=256 --ondisk=hda # basically a unconfigured server - the new 2005 Centurion %packages kernel elinks grub joe lftp lynx rdate rpm-build rsync yum # kdebase -apmd -autofs -centos-yumcache -comps -cups -cups-libs -eal3-certification -eal3-certification-doc -finger -freetype -ipsec-tools -iptables -iptables-ipv6 -irda-utils -iscsi-initiator-utils -isdn4k-utils -krb5-libs -krb5-workstation -krbafs-utils -kernel-pcmcia-cs -libwvstreams -mdadm -mgetty -mtr -nano -nfs-utils -pam_krb5 -pam_smb -parted -portmap -raidtools -redhat-config-network-tui -redhat-config-securitylevel-tui -redhat-logos -redhat-menues -redhat-lsb -rpmdb-redhat -stunnel -sysreport -talk -tftp -specspo -vconfig -wireless-tools -wvdial -xinetd -ypbind -yp-tools # If you use yum, you do not need: -up2date -up2date-update %post [root@ftp kickstart]#

2 1

Re: UPDATED: resolved caching-nameserver network install failure
by donavan nelson 15 Jan '05

15 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 |>>Since people have both updates and os in their yum.conf files, how are |>>they _NOT_ going to get the update. |> |>I didn't think 7.3 was accessible unless you enabled the testing |>repository. I'll verify and hit lance if that's NOT the case as it |>would invalidate what I've just said. |> This was intended to imply via a yum command. |> |>>It seems to me they will still get the newer version via yum and |>>dependency resolution regardless of where in the directory structure it |>>is. |> |>If 7.3 is infact in updates, they are getting it. |> | | No ... if it is in centos/3.4/os/i386/RedHat/RPMS/ they are getting | it ... this is such a mess....but for everyone who may have this question. caching-nameserver-7.2 and caching-name-server-7.3 both exist in the centos/3.4/os/i386/RedHat/RPMS (new installs and network installs will get 7.3 due to the package list). System doing upgrades will only see 7.2 because 7.2 is the only package populated in centos/3.4/os/i386/headers/ . | yum.conf has an entry like this: | | [base] | name=CentOS-$releasever - Base | baseurl=mirror.../centos/$releasever/os/$basearch/ | | SO ... any RPM in centos/3.4/os/i386/RedHat/RPMS/ is going to also be in | package resolution...since 7.3 is in centos/3.4/os/i386/RedHat/RPMS/ and | since 7.2 is in updates, 7.3 will be installed. | See about regarding the location of both packages. Also yum only uses the headers it finds (as a result of using yum-arch). It doesn't NOT examine the actual files in the directory. .dn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB6Y4wCRFXD+VcGBkRAp6VAJ9YGUZF39lZtXESwF3Dps7IgKFlqACfYJZl hI4hZSUangOBEkNZ1Yr+BB0= =MTdH -----END PGP SIGNATURE-----

1 0

Loosing keyboard
by dan1 15 Jan '05

15 Jan '05

Hello. I am experiencing a problem with CentOS 3, it's that when I start Xwindow, my keyboard is lost and I can't do anything anymore. The Num Lock doesn't react nor the Caps lock. It's like if it would just be disabled. If I quit Xwindow, then my keyboard comes back again, working perfectly. Did anybody also have this problem ? I had a look elsewhere but didn't see anything helpful. My XF86Config file has a normal input section and I tried to change it without success. The current one: Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Of course I also changed the physical keyboard. Thanks for any pointers, Daniel No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 12.01.2005

3 3

rpmbuild --rebuild --define 'buildklips 1' openswan-2.3.0-1rhel.src.rpm quirk
by Ted Kaczmarek 15 Jan '05

15 Jan '05

rpmbuild --rebuild --define 'buildklips 1' openswan-2.3.0-1rhel.src.rpm The present kernel configuration has modules disabled. Type 'make config' and enable loadable module support. Then build a kernel with module support enabled. make[1]: *** [modules] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.21-27.0.1.EL' make: *** [module26] Error 2 make: Leaving directory `/usr/src/redhat/BUILD/openswan-2.3.0' error: Bad exit status from /var/tmp/rpm-tmp.43563 (%build) # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y I am tad perplexed here, any ideas? Regards, Ted

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2005