Discuss December 2005

discuss@lists.centos.org

219 participants
328 discussions

Jigdo, etc...
by Maciej Żenczykowski 04 Jan '06

04 Jan '06

Hi folks, I've just finished rsyncing/downloading/jigdoizing the entire i386/x86_64 CentOS 4.2 distribution. If anyone is interested go to http://mirror.tcs.ii.uj.edu.pl/jigdo/ You'll need to edit the .jigdo file by hand to change the server section [Servers] CentOS42=file:/opt/mirrors/centos/4.2/ to point to a local mirror (file, http or ftp), ie. to use kernel.org: [Servers] CentOS42=http://mirrors.kernel.org/centos/4.2/ While doing this I have come upon a few questions: a) it seems the server cd's have a lot of stuff not present in the normal directory mirror, I guess this is an artifact of the build process? [the template files for the servercd's are ~120MB] b) what are the .newheaders and .repodata directories on i386 CD1? c) why do the mirror repodata/*.xml.gz files not match neither the CD nor DVD versions for i386? d) why does the i386 DVD not match ideally, but the x86_64 DVD matches for _all_ files. The x86_64 CD1 also matches _much_ better than the i386 CD1... e) why aren't identical files between the two trees hardlinked? $ ls -ali os/*/CentOS/RPMS/yum*noarch* 278532 -rw-rw-r-- 1 maze maze 395922 Sep 4 19:48 i386/CentOS/RPMS/yum-2.4.0-1.centos4.noarch.rpm 1165388 -rw-rw-r-- 1 maze maze 395922 Oct 10 22:20 x86_64/CentOS/RPMS/yum-2.4.0-1.centos4.noarch.rpm $ md5sum os/*/CentOS/RPMS/yum*noarch* 371d55a19f8e4ca13d22974128ab4671 i386/CentOS/RPMS/yum-2.4.0-1.centos4.noarch.rpm 371d55a19f8e4ca13d22974128ab4671 x86_64/CentOS/RPMS/yum-2.4.0-1.centos4.noarch.rpm Just an example of two identical files from my mirror, one of which is wasting space even though contents are identical. I expect we have this situation for almost _all_ i386 packages from the x86_64 distribution... $ pwd /opt/mirrors/centos/4.2/os/x86_64 $ find|grep "i386\.rpm"|while read i;do diff -qr "$i" "../i386/$i";done $ find|grep "i386\.rpm"|while read i;do cat "$i";done|wc -c 440745010 $ find|grep "noarch\.rpm"|while read i;do diff -qr "$i" "../i386/$i";done $ find|grep "noarch\.rpm"|while read i;do cat "$i";done|wc -c 426816227 $ pwd /opt/mirrors/centos/4.2/updates/x86_64 $ find|grep "i386\.rpm"|while read i;do diff -qr "$i" "../i386/$i";done $ find|grep "i386\.rpm"|while read i;do cat "$i";done|wc -c 12819616 $ find|grep "noarch\.rpm"|while read i;do diff -qr "$i" "../i386/$i";done diff: ../i386/./RPMS/createrepo-0.4.3-1.noarch.rpm: No such file or directory $ find|grep "noarch\.rpm"|while read i;do cat "$i";done|wc -c 2164495 $ ls RPMS/createrepo-0.4.3-1.noarch.rpm -al -rw-rw-r-- 2 maze maze 18284 Sep 5 13:59 RPMS/createrepo-0.4.3-1.noarch.rpm That seems to me to be a 880 MB mirror space savings to be made there... Considering the i386/x86_64 mirror takes up 7.7GB (without iso's) that's quite a bit... I also imagine the noarch files are shared with most of the other architectures... so I'd assume another 400MB per every next arch can be saved... f) Why aren't jigdo files available on the site? They'd really come in useful, especially in the situation I had where I already had a complete mirror of all the files, but I still had to bittorrent the CD/DVD's even though I had 99% of the required data on disk! Cheers, MaZe.

2 3

megaide support for 4.2
by Kris Buytaert 04 Jan '06

04 Jan '06

In 2.4 there used to be a megaide driver for certain ata raid controllers. In 2.6 I can't access more than my /dev/hda , I can see my other 4, I can create filesystems on them, but I can't mount them Anyone knows how to use these on a 2.6 kernel (Centos 4.2) greetings Kris 00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to ATA Host Controller (rev 02) Subsystem: Compaq Computer Corporation Integrated Ultra ATA-100 IDE RAID Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at 2010 [size=8] I/O ports at 2018 [size=4] I/O ports at 2020 [size=8] I/O ports at 2028 [size=4] I/O ports at 2030 [size=16] Capabilities: [60] Power Management version 2 -- Kris Buytaert <mlkb(a)x-tend.be>

7 15

slow GUI
by Robert Moskowitz 04 Jan '06

04 Jan '06

System: PIII 500Mhz 128MB memory 20GB drive Current CentOS 4.2 Gnome GUI The system runs 'idle' at around 70Mb memory used and 4% cpu usage. But whenever I go to start a task: Start Gedit, Services tool, a Terminal window, Firefox It takes a minute or so. CPU mayyyypeak at 100% briefly then come down. Memory has yet to exceed 100Mb usage. Any pointers of where to look to see why it is slow?

10 17

Crashing Nameservers
by John Hinton 03 Jan '06

03 Jan '06

Had two nameservers crash in the last few hours... This 'never' happens! On the console was sent an invalid ICMP type 3, code 3 error to a broadcast: 255.255.255.255 on eth0 sent an invalid ICMP type 3, code 3 error to a broadcast: 255.255.254.255 on eth0 with the IP address of the offender? in front of that line. Any ideas? Best, John Hinton

7 8

DNS wizard
by Sam Drinkard 03 Jan '06

03 Jan '06

Do we have anyone here who is a bind/dns wizard? I've been under the impression my dns setup which I've used for so many years on a bsd machine is now considered lame. If there is someone who would not mind taking a look at my configuration to see where I'm missing something, or where the difference lies between bind 9 and previous bind 8 configs? I'd prefer to do this off list via direct e-mail. The zone is very small, and the files are small too.. Sam

9 38

RE: [CentOS] Version download problem?
by Young, Darren 03 Jan '06

03 Jan '06

> Yep. They're obsolete, and we're trying to save > space/bandwidth on the mirrors, since the space is donated. > 3.6 is 3.1 with all the > updates+errata. If you REALLY need 3.1 for some hellish reason, you'll > need to get it from the vault. ( vault.centos.org ) Hellish, maybe -> Tivoli Storage Manager. Actually, what I need is kernel 2.4.21-4.0.1 according to IBM. I thought that since that version was in an older version of the "other enterprise linux" it would be in an older CentOS as well. Am I correct in this assumption or fighting a losing battle? Not sure how *hard* that requirement is, might just be kernel 2.4.whatever, but I have to find out. Was that version in 3.0 or 3.1 of CentOS? Also have a requirement for kernel 2.4 from the Tivoli Integrated Solution Console as well. Not sure on this requirement as well, I do know that with CentOS 4 the installer blew up with "unsupported kernel version xxx". Tried tricking the installer by replacing the uname binary with a script that returned what the other linux gives from `uname -a` but it didn't work.

5 5

RE: [CentOS] centos 4.2 update - help!
by Terry Tai 02 Jan '06

02 Jan '06

Hello I have installed centos 4.2 in dell poweredge 850. but I found that when I launch up2date to do a update action, it always get time out problem. just like error while retrieving package gtk 2-2.14.13-18 the message is time out any one can give some help Thanks and Regards Terry ************************************ E-mail Disclaimer ************************************ This e-mail message (together with any attachments) is confidential to the addressee and may also be privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. Please also notify the sender immediately by return e-mail and delete it from your system. Internet communications cannot be guaranteed to be secure or error-free. The sender and the entity through which this message is sent therefore do not accept liability for errors or omissions as contained in the message and any spreading of viruses as a result of Internet transmission. Any opinions contained in this message are those of the sender personally and would not bind any entity unless otherwise clearly stated and with the authority of the sender duly verified. *******************************************************************************************

3 2

noprobe boot option with askmethod and NFS install
by Jerry Geis 31 Dec '05

31 Dec '05

>insmod <module> should do it On 31/12/05, Jerry Geis <geisj at pagestation.com <http://lists.centos.org/mailman/listinfo/centos>> wrote: >/ />/ If you specify noprobe at boot can you then manually />/ specify to load the 8139too network module? If so how? />/ />/ Thanks, />/ />/ jerry I am trying to to boot with askmethod to do an nfs install I did the noprobe insmod 8139too and it did not load the network driver. Did I miss something? my command is "linux askmethod noprobe insmod 8139too" Thanks, Jerry /

1 0

noprobe boot option
by Jerry Geis 31 Dec '05

31 Dec '05

If you specify noprobe at boot can you then manually specify to load the 8139too network module? If so how? Thanks, jerry

2 1

RE: Intel Corporation 82573V Gigabit Ethernet Controller
by Gerald Waugh 31 Dec '05

31 Dec '05

> > Attempting to install CentOS on a new MSI MB (MS 9618), which > uses the subject controllers. > There are two controllers on the board, seems as though only > one can be used. > I have to manually init, using ifconfig eth0, to use it. > > I understand that the Ethernet controller drivers are not available. > Is there any news on this or a possible date when drivers > will be incorporated into the install. > > lspci reads; > 03:00.0 Ethernet controller: Intel Corporation 82573V Gigabit > Ethernet Controller (Copper) (rev 03) > 04:00.0 Ethernet controller: Intel Corporation 82573V Gigabit > Ethernet Controller (Copper) > > I find that on bootup the Intel boot loader indicates that > The Ethernet port is corrupted or not initalized, now I assume that > the boot loader is in the ROM, as it comes up early in the > boot process. > > Dmesg says; > ======================================================= > Intel(R) PRO/1000 Network Driver - version 6.0.54-k2-NAPI > Copyright (c) 1999-2004 Intel Corporation. > ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 10 (level, low) -> IRQ 10 > PCI: Setting latency timer of device 0000:03:00.0 to 64 > divert: allocating divert_blk for eth0 > e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection > ACPI: PCI interrupt 0000:04:00.0[A] -> GSI 11 (level, low) -> IRQ 11 > PCI: Setting latency timer of device 0000:04:00.0 to 64 > e1000: 0000:04:00.0: e1000_probe: The EEPROM Checksum Is Not Valid > e1000: probe of 0000:04:00.0 failed with error -5

4 4

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 December 2005