Discuss May 2007

discuss@lists.centos.org

345 participants
442 discussions

"core" package groups
by Niki Kovacs 22 May '07

22 May '07

Hi, One nice thing I have with Debian is the possibility to have a really stripped-down install of things. Let's take an example. I want a cholesterol-free install of GNOME, I 'apt-get install gnome-core' which gives me the bare working minimum of GNOME as a starting point, and then I install what I really need. The same thing applies for KDE, with 'apt-get install kde-core'. Having such a thing would be great on CentOS. Currently, 'yum groupinstall <group>' tends to install many things. What do you think? Niki Kovacs -- Dyslexics have more fnu.

2 1

Installing to other than "/" label
by Kenneth Porter 22 May '07

22 May '07

I have a system with Fedora installed on the partition with label "/". Can I install CentOS on a new empty partition (/dev/cciss/c0d3p1), or do I need to remove the "/" label on the Fedora partition and change Fedora's fstab to mount by physical partition? I'd like to keep Fedora as a fall-back OS until I have CentOS completely up and working. My Fedora fstab: LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/cciss/c0d0p2 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0

3 3

CentOS-announce Digest, Vol 27, Issue 13
by centos-announce-request＠centos.org 22 May '07

22 May '07

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-2007:0343 Moderate CentOS 3 i386 gimp - security update (Tru Huynh) 2. CESA-2007:0343 Moderate CentOS 3 x86_64 gimp - security update (Tru Huynh) 3. CESA-2007:0343 Moderate CentOS-5 i386 gimp Update (Karanbir Singh) 4. CESA-2007:0343 Moderate CentOS-5 x86_64 gimp Update (Karanbir Singh) 5. CESA-2007:0343 Moderate CentOS 3 ia64 gimp - security update (Pasi Pirhonen) 6. CESA-2007:0343 Moderate CentOS 4 ia64 gimp - security update (Pasi Pirhonen) 7. CESA-2007:0343 Moderate CentOS 3 s390(x) gimp - security update (Pasi Pirhonen) 8. CESA-2007:0343 Moderate CentOS 4 s390(x) gimp - security update (Pasi Pirhonen) 9. CESA-2007:0343 Moderate CentOS 4 x86_64 gimp - security update (Johnny Hughes) 10. CESA-2007:0343 Moderate CentOS 4 i386 gimp - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 21 May 2007 17:08:47 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2007:0343 Moderate CentOS 3 i386 gimp - security update To: centos-announce(a)centos.org Message-ID: <20070521150847.GA19209(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2007:0343 gimp security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2007-0343.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/gimp-1.2.3-20.3.el3.i386.rpm updates/i386/RPMS/gimp-devel-1.2.3-20.3.el3.i386.rpm updates/i386/RPMS/gimp-perl-1.2.3-20.3.el3.i386.rpm source: updates/SRPMS/gimp-1.2.3-20.3.el3.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update gimp\* Tru -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

64 Bit?
by drew einhorn 22 May '07

22 May '07

Hi, I have access to remote VMware ESX server. Don't really know what the underlying hardware is. Looked at a few dmesg results. As always there is a bunch of stuff I understand and a bunch more that I don't understand. I'd really like to know if it's a 64 Bit CPU, before I create my next VM. But, I can't tell from the dmesgs I've looked at. -- Drew Einhorn

6 8

pygrub cannot find kernel
by Fong Vang 22 May '07

22 May '07

I just installed a CentOs 5 domU system on a CentOS 5 dom0 system following the instructions detailed here: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU. The installation went through successfully. After installation, however, pygrub can't find a kernel. This is the xen cfg file I'm using: bootloader="/usr/bin/pygrub" name = "testsrv" memory = "2048" disk = [ 'tap:aio:/root/testsrv.img,xvda,w', ] vif = [ 'bridge=xenbr0', ] vcpus=2 on_reboot = 'destroy' on_crash = 'destroy' this is the error: Traceback (most recent call last): File "/usr/bin/pygrub", line 499, in ? curses.wrapper(run_main) File "/usr/lib/python2.4/curses/wrapper.py", line 44, in wrapper return func(stdscr, *args, **kwds) File "/usr/bin/pygrub", line 455, in run_main sel = g.run() File "/usr/bin/pygrub", line 358, in run self.run_main(timeout) File "/usr/bin/pygrub", line 381, in run_main draw() File "/usr/bin/pygrub", line 366, in draw self.draw_main_windows() File "/usr/bin/pygrub", line 159, in draw_main_windows curses.use_default_colors() _curses.error: use_default_colors() returned ERR No handlers could be found for logger "xend" Error: Boot loader didn't return any data! Usage: xm create <ConfigFile> [options] [vars] Create a domain based on <ConfigFile>. Options: Anything I'm missing? Thanks for any help.

2 3

Printers?
by Ashley M. Kirchner 22 May '07

22 May '07

Where can I find a list of supported USB printers for Centos5? We're looking to add a printer to our system that can print out a full 8.5x11 sheet that has a peel off label on it. So I need something supported, and I need to figure out what to use to spit this stuff out. The data is coming in as a PDF file... -- W | It's not a bug - it's an undocumented feature. +-------------------------------------------------------------------- Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.

2 1

powerfolder on CentOS
by Dave 22 May '07

22 May '07

Hello, Has anyone got the Powerfolder server working on Centos? I've given up on iFolder and am looking for alternatives. Thanks. Dave.

1 0

Strange behaviour from http install
by MrKiwi 22 May '07

22 May '07

The Symptoms; ============= While watching a CentOS5 install hammer my webserver ( i used "askmethod' to point the machine to the webserver) i noticed a bunch of 404s; 10.1.1.119 - - [22/May/2007:15:01:53 +1200] "GET /cd/1/CentOS/termcap-5.5-1.20060701.1.noarch.rpm HTTP/1.1" 404 319 "-" "urlgrabber/3.1.0" and the installation failed to get started (the same file re-requested over and over) The Cause: ========== I had set my webserver up to serve the iso for centos 5 on /cd/0 and the sme_server7 iso on /cd/1 and the centos 4 iso on /cd/2 (/cd/3 is there, but not mounted to anything) Even though i used server : 10.1.1.8 path : cd/0 the centos 5 installation (anakonda?) seems to have gone up a folder, seen the 1,2,3 dirs and asked for .discinfo on the following paths; /cd/0 /cd/1 /cd/2 /cd/3 Upon finding .discinfo in folders /2 and /3 it has then got all confused (not enough to crash as both sme server and centos 4 are familiar file structures i guess?) and then asked the server for wrong versions of files (again and again in an endless loop) Removing the confusion ( umount /var/www/html/cd/1 ;umount /var/www/html/cd/2 ) solved the problem and everything went smooth after that Just thought i would let people know :) Out of curiousity, does anyone know the cause of this? I imagine it is some kind of fuzzy logic to do its best to recover from paths that are one folder too short/long, or maybe to make sure it is installing the highest version numbered folder? MrKiwi

1 0

Re: [CentOS] recompiling kernel results in error: .../linux-2.6.18.i686/arch//Makefile: No such file or directory
by dcw 22 May '07

22 May '07

The compile finished with no apparent errors. When I ran 'make xconfig' I selected 'm' for ne2000 support so that it would create a module. I used the find command to search in /home/cs/redhat for ne.ko and it was not found. I greped the .config file for the relevant lines: The command I used and the output are as follows: grep ISA /home/cs/redhat/SOURCES/kernel-2.6.18-`uname -m`.config | grep -v HISAX | grep -yv disable CONFIG_GENERIC_ISA_DMA=y # Bus options (PCI, PCMCIA, EISA, MCA, ISA) CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_EISA is not set # CONFIG_ISAPNP is not set CONFIG_NET_ISA=y # Wireless 802.11b ISA/PCI cards support # CONFIG_ISDN_DRV_AVMB1_B1ISA is not set # CONFIG_ISDN_DRV_AVMB1_T1ISA is not set # ISA-based Watchdog Cards CONFIG_I2C_ISA=m # CONFIG_I2C_PCA_ISA is not set # ISA devices I also greped for NE2000 in the same file: CONFIG_NE2000=m I am 99% sure that I entered 'y' for ISAPNP and ISA support and 'm' for ne2000. The above shows that ISAPNP is not set. In my research I read that it should be selected. Does it need to be? I am more than willing to recompile again and double check the settings after I have run 'make xconfig'. But before doing that, is there a way to limit which kernels in the i686 group are compiled? If it can be limited to one (ie. exclude xen, PAE etc.), then the compile will not take nearly as long. Thanks, David On Monday 21 May 2007 1:42 pm, Akemi Yagi wrote: > On 5/21/07, Akemi Yagi <amyagi(a)gmail.com> wrote: > > On 5/21/07, dcw <dwoody1(a)charter.net> wrote: > > > When I use the i386 the compile continues. > > > However, I had to edit the SOURCE config file after running make > > > xconfig. That command altered the first line of the config file. > > > > Yes, I was about to say the same thing. In fact, the arch name (i386) > > gets deleted twice. First, when rpmbuild -bp is run. But this is not > > a problem by itself, because in the next step .config is copied from > > SOURCE which has the correct first line. Then the second time is when > > make menuconfig (or xconfig) is run as you noted. This is the > > problem. At this point, arch needs to be added back manually to > > .config as just you did. > > > > I really want to why menuconfig does not do it right. > > I have done a bit of a search regarding this issue. Turns out the > same problem was reported as early as Feb 2005 on a Fedora list. So > this is not something new, nor CentOS specific. Bad news is that I > have yet to find an answer for this. The only thing I saw in the > search was the same manual editing of .config as we already did as a > temporary solution. > > http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-05/0405.html > > I am still trying to figure out why rpmbuild -bp messes up the first > line of .config. And of course this problem never surfaces if you run > rpmbuild -ba in the beginning because the incorrect version of .config > is created but *not* used in this operation. > > Akemi > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos --

2 1

Re: [CentOS] CentOS 5 ssloooowww when network unavailable
by Mark Nejedlo 22 May '07

22 May '07

I've been having a similar problem and wanted to provide what hopefully is additional useful information. Like the original poster, things seem OK when booting with the network active. However, network access is extremely slow and timeouts are likely. If I do a service network stop, everything slows down, and keyboard and mouse activity is likely to be dropped. I also get error output which is included below. Booting with irqpoll doesn't seem to have any effect. Of note is that my ethernet driver (r1000) is source built, not a driver included with the build. However, this driver was fine under CentOS 4.4. Let me know what other information may be useful. Thanks Mark ----- irq 177: nobody cared (try booting with the "irqpoll" option) [<c044aacb>] __report_bad_irq+0x2b/0x69 [<c044acb8>] note_interrupt+0x1af/0x1e7 [<c0570092>] usb_hcd_irq+0x23/0x50 [<c044a2ff>] handle_IRQ_event+0x23/0x49 [<c044a3d8>] __do_IRQ+0xb3/0xe8 [<c04063f4>] do_IRQ+0x93/0xae [<c040492e>] common_interrupt+0x1a/0x20 [<c045a83d>] __handle_mm_fault+0x7d/0x87b [<c04b8ea8>] avc_has_perm+0x3a/0x44 [<c05fd4ef>] do_page_fault+0x20a/0x4b8 [<c05fd2e5>] do_page_fault+0x0/0x4b8 [<c0404a71>] error_code+0x39/0x40 [<c04df804>] __copy_to_user_ll+0xd3/0xda [<c0429957>] do_proc_dointvec+0x1ee/0x291 [<c0429a94>] proc_dointvec+0x15/0x19 [<c0428c9c>] do_proc_dointvec_conv+0x0/0x36 [<c0429134>] do_rw_proc+0xaa/0xee [<c042918e>] proc_readsys+0x0/0x13 [<c042919e>] proc_readsys+0x10/0x13 [<c046af3c>] vfs_read+0x9f/0x141 [<c046b38a>] sys_read+0x3c/0x63 [<c0403eff>] syscall_call+0x7/0xb ======================= handlers: [<c057006f>] (usb_hcd_irq+0x0/0x50) Disabling IRQ #177

1 1

← Newer
1
...
14
15
16
17
18
19
20
...
45
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2007