Discuss

discuss@lists.centos.org

34758 discussions

RE: Re: Re: [CentOS] CentOS Based Fierwall Document
by pctech＠mybellybutton.com 04 Aug '06

04 Aug '06

>On 8/4/06, pctech(a)mybellybutton.com <pctech(a)mybellybutton.com> wrote: >> He didn't ask for a link. He asked who I was and why should he care. > >No he didn't, he said: > >"and who are you ? >and what / where is your firewall doc ?" > >and this was after you said: > >"Then there's no reason for you to fricken reply, is there?" > >First angry words were yours. Please development some people skills, >or at least reflect before posting. Actually don't bother, this is >really entertaining and has made my Friday. > Wrong...His FIRST e-mail said, "Who are you and why should we care?" and THAT is when I responded the way I did. >Cian > > >> >_______________________________________________ >> >CentOS mailing list >> >CentOS(a)centos.org >> >http://lists.centos.org/mailman/listinfo/centos >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> http://lists.centos.org/mailman/listinfo/centos >> >_______________________________________________ >CentOS mailing list >CentOS(a)centos.org >http://lists.centos.org/mailman/listinfo/centos

3 2

RE: Re: [CentOS] CentOS Based Fierwall Document
by pctech＠mybellybutton.com 04 Aug '06

04 Aug '06

>On Fri, 2006-08-04 at 06:12 -0700, Frank Tanner III wrote: >> It's a well known "fact" amongst the general public that the Linux >> "evangelists" are a rude flaming bunch. There are hundreds of news >> articles stating such. An THIS is what the public in general bases >> their attitudes with regards to the community as a whole on. > >You have to keep in mind that support from lists like this one are >voluntary in nature. So, it only seems decent to try to get the >etiquette of the list, and (although it does not apply here) research a >problem before posting questions to the list. > Etiquette? What etiquette? The FIRST comment out of anyone's "mouth" was "piss off". Where's the etequitte in that? >IMHO calling Linux community members a "rude flaming bunch" is highly >inappropriate. The community built a free operating system, and provides >free support. If people need hand holding or extensive support they can >get a support contract from a prominent North-American Linux vendor, or >one of the other venues that provides Linux support. > Well then prove me wrong? Because that's all I've gotten at every turn was nothing but flames. I tried to be helpful and offer something to the community that I, obviously mistakenly, though muight be useful and got a hearty "f*ck you" for my efforts. Where's the "community spirit" in that? >-- Daniel > >_______________________________________________ >CentOS mailing list >CentOS(a)centos.org >http://lists.centos.org/mailman/listinfo/centos

2 1

Openvpn problem not able to access the other machines on remote subnet
by ankush grover 04 Aug '06

04 Aug '06

hey friends, I have installed OpenVPN 2.0.7 (i386-redhat-linux-gnu [SSL] [LZO] [EPOLL] built on Apr 29 2006) on Centos4.0 through rpm (diag repository). The network scenario of my office is below Remote Client ----> Internet <-------> Cisco Pix Firewall (Gateway) <----> VPN Server & LAN Clients (192.168.5.0/24) Cisco Pix Firewall: Having a static public ip address and a LAN Address of 192.168.5.5 and it is also acting as gateway for the LAN VPN Server: 192.168.5.20 and this is also a server on LAN running few more services for the clients in LAN. LAN Clients: 192.168.5.0/24 VPN Server port that is 1194 is open on Firewall. This is a test scenario and I was able to connect to the VPN Server from my home machine but I was not able to browse the clients or servers in the network range of 192.168.5.0/24. Routing table on the client machine. The client machine is having static ipaddress of 172.19.112.154( dsl connection) 10.1.1.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 192.168.5.0 10.1.1.5 255.255.255.0 UG 0 0 0 tun0 10.1.1.0 10.1.1.5 255.255.255.0 UG 0 0 0 tun0 172.19.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 172.19.0.1 0.0.0.0 UG 0 0 0 eth0 Tue Aug 1 23:10:55 2006 SIGUSR1[soft,tls-error] received, process restarting Tue Aug 1 23:10:55 2006 Restart pause, 2 second(s) Tue Aug 1 23:10:57 2006 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. Tue Aug 1 23:10:57 2006 Re-using SSL/TLS context Tue Aug 1 23:10:57 2006 LZO compression initialized Tue Aug 1 23:10:57 2006 Control Channel MTU parms [ L:1542 D:166 EF:66 EB:0 ET:0 EL:0 ] Tue Aug 1 23:10:57 2006 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ] Tue Aug 1 23:10:57 2006 Local Options hash (VER=V4): '504e774e' Tue Aug 1 23:10:57 2006 Expected Remote Options hash (VER=V4): '14168603' Tue Aug 1 23:10:57 2006 UDPv4 link local: [undef] Tue Aug 1 23:10:57 2006 UDPv4 link remote: xx.xx.xx.xx:1194 --->> public ip address on pix firewall Tue Aug 1 23:11:21 2006 TLS: Initial packet from xx.xx.xx.xx:1194, ---->> public ip address on pix firewall sid=7c6f6585 62ec6b5f Tue Aug 1 23:11:21 2006 VERIFY OK: depth=1, /C=IN/ST=DE/L=ND/O=OpenVPN-TEST/OU=VPN_Server/CN= server1.test.net/emailAddress=postmater@localhost.localdomain Tue Aug 1 23:11:21 2006 VERIFY OK: nsCertType=SERVER Tue Aug 1 23:11:21 2006 VERIFY OK: depth=0, /C=IN/ST=DE/O=OpenVPN-TEST/OU=VPN_Server/CN=server1.test.net/emailAddress=postmater(a)localhost.localdomain Tue Aug 1 23:11:23 2006 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key Tue Aug 1 23:11:23 2006 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Aug 1 23:11:23 2006 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key Tue Aug 1 23:11:23 2006 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Aug 1 23:11:23 2006 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA Tue Aug 1 23:11:23 2006 [server1.test.net] Peer Connection Initiated with xx.xx.xx.xx:1194 Tue Aug 1 23:11:25 2006 SENT CONTROL [server1.test.net ]: 'PUSH_REQUEST' (status=1) Tue Aug 1 23:11:25 2006 PUSH: Received control message: 'PUSH_REPLY,route 192.168.5.0 255.255.255.0,dhcp-option DNS 192.168.5.10,route 10.1.1.0 255.255.255.0,ping 10,ping-restart 120,ifconfig 10.1.1.6 10.1.1.5' Tue Aug 1 23:11:25 2006 OPTIONS IMPORT: timers and/or timeouts modified Tue Aug 1 23:11:25 2006 OPTIONS IMPORT: --ifconfig/up options modified Tue Aug 1 23:11:25 2006 OPTIONS IMPORT: route options modified Tue Aug 1 23:11:25 2006 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Tue Aug 1 23:11:25 2006 TUN/TAP device tun0 opened Tue Aug 1 23:11:25 2006 /sbin/ip link set dev tun0 up mtu 1500 Tue Aug 1 23:11:25 2006 /sbin/ip addr add dev tun0 local 10.1.1.6 peer 10.1.1.5 Tue Aug 1 23:11:25 2006 /sbin/ip route add 192.168.5.0/24 via 10.1.1.5 Tue Aug 1 23:11:25 2006 /sbin/ip route add 10.1.1.0/24 via 10.1.1.5 Tue Aug 1 23:11:25 2006 Initialization Sequence Completed ifconfig on server tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.1.1.1 P-t-P:10.1.1.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:173 errors:0 dropped:0 overruns:0 frame:0 TX packets:145 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:14052 (13.7 KiB) TX bytes:12192 ( 11.9 KiB) ifconfig on client tun0 Link encap:Point-to-Point Protocol inet addr:10.1.1.6 P-t-P:10.1.1.5 Mask: 255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:143 errors:0 dropped:0 overruns:0 frame:0 TX packets:174 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:12024 (11.7 Kb) TX bytes:14112 (13.7 Kb) Tue Aug 1 23:01:10 2006 202.149.50.30:1030 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key Tue Aug 1 23:01:10 2006 202.149.50.30:1030 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Aug 1 23:01:10 2006 202.149.50.30:1030 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA Tue Aug 1 23:01:10 2006 202.149.50.30:1030 [clien1.test.net ] Peer Connection Initiated with 202.149.50.30:1030 Tue Aug 1 23:01:10 2006 clien1.test.net/202.149.50.30:1030 MULTI: Learn: 10.1.1.6 -> clien1.test.net/202.149.50.30:1030 Tue Aug 1 23:01:10 2006 clien1.test.net/202.149.50.30:1030 MULTI: primary virtual IP for clien1.test.net/202.149.50.30:1030: 10.1.1.6 Tue Aug 1 23:01:11 2006 clien1.test.net/202.149.50.30:1030 PUSH: Received control message: 'PUSH_REQUEST' Tue Aug 1 23:01:11 2006 clien1.test.net/202.149.50.30:1030 SENT CONTROL [ clien1.test.net] 'PUSH_REPLY,route 192.168.5.0 255.255.255.0,dhcp-option DNS 192.168.5.10,route 10.1.1.0 255.255.255.0,ping 10,ping-restart 120,ifconfig 10.1.1.6 10.1.1.5' (status=1) Tue Aug 1 23:34:41 2006 clien1.test.net/202.149.50.30:1030 [clien1.test.net] Inactivity timeout (--ping-restart), restarting Tue Aug 1 23:34:41 2006 clien1.test.net/202.149.50.30:1030 SIGUSR1[soft,ping-restart] received, client-instance restarting iptables -L on VPN Server Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 10.1.1.0/24 192.168.5.0/24 One setting is missing in client.conf that is "route 192.168.5.0 255.255.255.0" These entries are also added to iptables on VPN Server # Allow TUN interface connections to OpenVPN server iptables -A INPUT -i tun+ -j ACCEPT # Allow TUN interface connections to be forwarded through other interfaces iptables -A FORWARD -i tun+ -j ACCEPT # Allow TAP interface connections to OpenVPN server iptables -A INPUT -i tap+ -j ACCEPT # Allow TAP interface connections to be forwarded through other interfaces iptables -A FORWARD -i tap+ -j ACCEPT IP Forwarding is enable on the VPN Server. But still I am not able to access the machines/clients in subnet 192.168.5.0/24. I am attaching the server.conf(openvpnserver.conf) file with this emai. What more iptables entries needs to be added ? Please let me know if you need any further inputs. Thanks & Regards Ankush Grover

2 4

CentOS-announce Digest, Vol 18, Issue 4
by centos-announce-request＠centos.org 04 Aug '06

04 Aug '06

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2006:0298 Low CentOS 3 i386 openssh - security update (Tru Huynh) 2. CESA-2006:0298 Low CentOS 3 x86_64 openssh - security update (Tru Huynh) 3. CESA-2006:0368 Low CentOS 3 i386 elfutils - security update (Tru Huynh) 4. CESA-2006:0368 Low CentOS 3 x86_64 elfutils - security update (Tru Huynh) 5. CESA-2006:0437 Important CentOS 3 i386 kernel - security update (Tru Huynh) 6. CESA-2006:0437 Important CentOS 3 x86_64 kernel - security update (Tru Huynh) 7. CESA-2006:0576 Moderate CentOS 3 i386 kdebase - security fix (Tru Huynh) 8. CESA-2006:0576 Moderate CentOS 3 x86_64 kdebase - security fix (Tru Huynh) 9. CESA-2006:0591 Important CentOS 3 i386 samba - security update (Tru Huynh) 10. CESA-2006:0591 Important CentOS 3 x86_64 samba - security update (Tru Huynh) 11. CESA-2006:0604 Moderate CentOS 3 i386 ruby - security update (Tru Huynh) 12. CESA-2006:0604 Moderate CentOS 3 x86_64 ruby - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Thu, 3 Aug 2006 15:58:21 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2006:0298 Low CentOS 3 i386 openssh - security update To: centos-announce(a)centos.org Message-ID: <20060803135821.GA17314(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2006:0298 openssh security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2006-0298.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/openssh-3.6.1p2-33.30.9.i386.rpm updates/i386/RPMS/openssh-askpass-3.6.1p2-33.30.9.i386.rpm updates/i386/RPMS/openssh-askpass-gnome-3.6.1p2-33.30.9.i386.rpm updates/i386/RPMS/openssh-clients-3.6.1p2-33.30.9.i386.rpm updates/i386/RPMS/openssh-server-3.6.1p2-33.30.9.i386.rpm source: updates/SRPMS/openssh-3.6.1p2-33.30.9.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update openssh\* Tru -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Directory tree disk usage utility
by Robert Moskowitz 04 Aug '06

04 Aug '06

Is there some nice program that will display how much disk space is being used by each directory? e.g. 3.9G / 1.6G /etc 3.4K /etc/yum.repo and so forth?

2 2

Bind DNS service
by Nikos Zaharioudakis 04 Aug '06

04 Aug '06

Hi everybody, I have a request from a client that is an planning on a small ISP business. I am looking into a DNS {bind based} solution. Are there any hints or tips concerning hardware requirements? Is there any kind of tool to perform the sizing? Should I have different machines for caching ? Should i compile bind myself for xtra performance. There are going to be some 400K dsl customers and some 50-70K virtual hostings I know that most dns trafic is generated by MX lookups. Any hints are greatly appreciated. -- ########################################3 Zaharioudakis Nikos mob: +30 6947204063 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

1 0

Can't get rid of SYN_RECV
by Paul 04 Aug '06

04 Aug '06

OK, Something wacky. I'm getting many, many of these, it just keeps building: --snip-- netstat -vat: tcp 0 0 192.168.103.99:http statusurl.e-gold.com:57015 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:26377 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:64279 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:27807 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:29095 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:47009 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:41369 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:45120 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:63145 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:4027 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:11361 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:53867 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:64779 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:20063 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:43209 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:44629 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:49010 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:3974 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:6822 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:54650 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:43689 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:35714 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:3381 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:48516 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:52141 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:11431 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:50562 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:17152 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:10535 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:18219 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:7582 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:60773 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:46995 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:60185 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:34357 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:41346 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:1135 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:64816 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:16062 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:7499 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:60087 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:33579 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:6757 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:8912 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:50510 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:44317 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:2149 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:294 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:60112 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:52569 SYN_RECV tcp 0 0 192.168.103.99:http statusurl.e-gold.com:26452 SYN_RECV --snip-- So, seeing this is weird activity, I wanna see if I can put a stop to it. So I added to iptables: -A INPUT -s 209.200.128.0/255.255.192.0 -j DROP -A OUTPUT -o eth0 -p tcp -m tcp -d 209.200.128.0/255.255.192.0 -j DROP I restarted httpd and still get the same thing. WTF??? -- ^^^^^^^^^^^^| || \ | Budvar ######|| ||'|"\,__. | _..._...______ ===|=||_|__|...] "(@)'(@)""""**|(@)(@)*****(@)I -- ^^^^^^^^^^^^| || \ | Budvar ######|| ||'|"\,__. | _..._...______ ===|=||_|__|...] "(@)'(@)""""**|(@)(@)*****(@)I

2 2

RE: [CentOS] RHEL4 to CentOS 4
by tagarsi, arun 04 Aug '06

04 Aug '06

Thanks...that works great.... Arun -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org]On Behalf Of Will McDonald Sent: Thursday, August 03, 2006 3:16 PM To: CentOS mailing list Subject: Re: [CentOS] RHEL4 to CentOS 4 On 03/08/06, tagarsi, arun <atagarsi(a)cgg.com> wrote: > Hi , > For reasons I will not go in to does anyone know if you can convert a > RedHat RHEL4 box to CentOS 4 ? I am hoping this possible with our re > installing . If it if what do I need to do to get the system to run yum > instead of the RedHat updates. It should be relatively simple but test on non-critical, non-production systems first, obviously. The old instructions (we Kickstart CentOS on all new systems now) I have for switching from Whitebox to CentOS, which should be near as damnit what's needed to switch from RHEL too, were as follows... rpm --import http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-4 rpm -Uvh http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… \ http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… rpm -Uvh http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… rpm -e yum rpm -Uvh http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… rpm -Uvh http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… \ http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… \ http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… \ http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… \ http://www.sunsite.org.uk/sites/msync.centos.org/CentOS/4/os/i386/CentOS/RP… Add this to /etc/yum.repos.d/CentOS-Base.repo [base] name=CentOS-$releasever - Base baseurl=ftp://archive/centos/$releasever/os/$basearch gpgcheck=1 [update] name=CentOS-$releasever - Updates baseurl=ftp://archive/centos/$releasever/updates/$basearch/ gpgcheck=1 [extras] name=CentOS-$releasever - Extras baseurl=http://archive/centos/$releasever/extras/$basearch/ gpgcheck=1 enabled=0 Add this to /etc/yum.repos.d/Dag.repo [archive-rhel4-dag] name=RHEL4 Linux $releasever - $basearch - DAG baseurl=ftp://archive/dag/el4/ Quick Yum update... yum -y update Where we have "archive" you'd need to replace that with the path to a local mirror. And obviously the URLs for the RPM commands could be changed to somewhere closer with more recent RPMs. But that's an outline of what you'd need. There are additional artwork RPMs etc. if you're bothered about boot time splash screens and the like. Will. _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

3 2

OT: Measure 2U Server Amp Usage
by Karl R. Balsmeier 03 Aug '06

03 Aug '06

Hi, Running a bunch of CentOS servers on 2U supermicro equipment, usually with 8 drives on Adaptec SmartRAID V or LSI Megaraid. In designing a rack in a data center, the question arises as to how to measure the amperage the server uses, prior to investing in power drops that actually do that for you, even remotely, for about $260.00-300USD per unit. This number is the important one these days in determining rack/datacenter design. So the geek question is, "what do you use, from radio shack, or elsewhere, to accomplish this one time measurement *before* you implement a design"? Even deeper, is there an open-source equivalent to some of the software-based solutions that purport to be able to give a reading on amp usage. Just curious if you have a similar server-type, (supermicro=very popular), what your measurements have been. -karlski

4 3

RHEL4 to CentOS 4
by tagarsi, arun 03 Aug '06

03 Aug '06

Hi , For reasons I will not go in to does anyone know if you can convert a RedHat RHEL4 box to CentOS 4 ? I am hoping this possible with our re installing . If it if what do I need to do to get the system to run yum instead of the RedHat updates. Thanks Arun

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss