Discuss

discuss@lists.centos.org

34758 discussions

Re: [CentOS] Send in your favorite CentOS slogan today
by Ross S. W. Walker 01 Mar '08

01 Mar '08

CentOS, It's all about the community. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: centos(a)centos.org <centos(a)centos.org> Sent: Fri Feb 29 20:16:22 2008 Subject: [CentOS] Send in your favorite CentOS slogan today Hi everyone, The CentOS project is looking for more slogans that may end up on promotional material (eg media, flyers, posters or stickers). We already collected a few funny, ironic, sarcastic or even distasteful ones. Feel free to visit our Slogans wiki page for a good laugh or rude offenses and add your own slogan by sending them to this thread. See: http://wiki.centos.org/Promo/Slogans And who knows, yours may end up somewhere ? If it gets selected, you win free CentOS updates for a whole month !! So get started ;) Disclaimer: Ideas contributed to this thread are considered free to be reused. Otherwise do NOT submit them to a public mailinglist :) I will be adding them to the wiki. -- -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

3 4

Allocaation resource error (DELL Optiplex 755)...
by John.Giovannis＠csiro.au 01 Mar '08

01 Mar '08

Hi all, (My first time in seeking assistance via the CentOS mailing list ... Not sure if I should be submitting this as a possible kernel bug). I've successfully installed Cent OS 5.1 (kernel: 2.6.18-53.1.13.el5) on an Optiplex 755 (EM64T). However I'm not able to get a NVIDIA Gigabyte 8600GT (PCI-e) card to work with the system despite successfully installing the latest NVIDIA drivers (NVIDIA-Linux-x86_64-169.07-pkg2.run). I've tested the same configuration in Windows with no difficulties. I suspect the kernel is not able to allocate the appropriate hardware resources possibly resulting in the card failing to fire up properly: Some diagnostics: A snippet of the Xorg log file: # more /var/log/Xorg.0.log | grep -E 'WW|EE' (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) ****INVALID MEM ALLOCATION**** b: 0x13a000000 e: 0x13affffff correcting (EE) Cannot find a replacement memory range (WW) ****INVALID MEM ALLOCATION**** b: 0x138000000 e: 0x139ffffff correcting (WW) ****INVALID IO ALLOCATION**** b: 0x13800dc80 e: 0x13800dcff correcting (EE) end of block range 0xffffffff < begin 0x138000000 (EE) Cannot find a replacement memory range (EE) NVIDIA(0): The NVIDIA GPU at PCI:1:0:0 is not supported by the 169.09 (EE) NVIDIA(0): NVIDIA driver. (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! (EE) Screen(s) found, but none have a usable configuration. # dmesg | grep Cannot PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0 PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0 PCI: Cannot allocate resource region 1 of device 0000:00:03.3 PCI: Cannot allocate resource region 0 of device 0000:00:19.0 PCI: Cannot allocate resource region 1 of device 0000:00:19.0 PCI: Cannot allocate resource region 0 of device 0000:00:1a.7 PCI: Cannot allocate resource region 0 of device 0000:00:1b.0 PCI: Cannot allocate resource region 0 of device 0000:00:1f.3 PCI: Cannot allocate resource region 0 of device 0000:01:00.0 PCI: Cannot allocate resource region 3 of device 0000:01:00.0 # lsmod | grep nvidia nvidia 8885796 0 i2c_core 56129 3 i2c_ec,nvidia,i2c_i801 # lspci -v | grep -E '00:01.0|00:1c.0|00:03.3|00:19.0|00:1a.7|00:1b.0|00:1f.3|01:00.0' 00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port (rev 02) (prog-if 00 [Normal decode]) 00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT Controller (rev 02) (prog-if 02 [16550]) 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) (prog-if 20 [EHCI]) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1) (prog-if 00 [VGA]) Is it likely that I need to try an older kernel or attempt to patch the current one ? Any suggestions are appreciated, John

2 2

T43 wireless ipw2200 centos 4.4
by Primorec 01 Mar '08

01 Mar '08

Hi ALL, Short description of my problem: I am not able to make wireless network working on the IBM ThinkPad T43p. System: T43p OS: CentOS 4.4 kernel: 2.6.9-34.EL firmware: ipw2200-firmware-3.0-3.nodist.rf.noarch.rpm What did I do ? - installed firmware from RPM package - removed kernel driver (/sbin/rmmod ipw2200) - installed kernel module (/sbin/modprobe ipw2200) dmesg output: ================= Dec 24 16:45:43 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.0 Dec 24 16:45:43 localhost kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporation Dec 24 16:45:43 localhost kernel: ACPI: PCI interrupt 0000:04:02.0[A] -> GSI 11 (level, low) -> IRQ 11 Dec 24 16:45:43 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Dec 24 16:45:44 localhost hald[3408]: Timed out waiting for hotplug event 577. Rebasing to 578 Dec 24 16:45:44 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Dec 24 16:46:00 localhost hald[3408]: Timed out waiting for hotplug event 580. Rebasing to 581 Dec 24 16:46:02 localhost hald[3408]: Timed out waiting for hotplug event 583. Rebasing to 584 Dec 24 16:46:04 localhost hald[3408]: Timed out waiting for hotplug event 587. Rebasing to 588 Dec 24 16:46:06 localhost hald[3408]: Timed out waiting for hotplug event 590. Rebasing to 591 Dec 24 16:46:08 localhost hald[3408]: Timed out waiting for hotplug event 593. Rebasing to 594 - started 'system-config-network' tool - checked eth1 (wireless) (aka enabled wireless) - edited (via edit buton ) eth1 configuration Mode: auto Network name (SSID): linksys Channel: 1 Transmit rate: auto Key: 0x????? (26 hex numbers) - clicked the Activate button Result: dmesg output: Dec 24 19:25:06 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Dec 24 19:25:07 localhost hald[3408]: Timed out waiting for hotplug event 626. Rebasing to 627 Dec 24 19:25:21 localhost hald[3408]: Timed out waiting for hotplug event 629. Rebasing to 630 Dec 24 19:25:23 localhost hald[3408]: Timed out waiting for hotplug event 632. Rebasing to 633 terminal output: Error for wireless request "Set Bit Rate" (8B20) : SET failed on device eth1 ; Operation not supported. Determining IP information for eth1... failed; no link present. Check cable? Can some merciful soul give me a hint or/and solution or/and RTFM pointer for my problem ? Thanks in advance Igor -- Experience is what you get when you didn't get what you wanted. Randy Pausch

2 2

CentOS Email Wiki and/or mailing list
by John Hinton 29 Feb '08

29 Feb '08

As I hijacked a thread... I thought I'd start this new one. Yes, shame on me. Karanbir Singh wrote: > John Hinton wrote: >> As a side, I could see blossoming a Wiki area specific to email which might >> eventually fill out to an extremely robust set of how to's for installations >> of what amounts to being some of the very hardest things that I've >> accomplished with CentOS. Yes SpamAssassin is a powerful tool, but for >> instance the default setup that comes out of the box is fairly weak. A trip >> to the SpamAssassin site will just leave you mostly confused and reading for >> hours only to find out that what you think is good might not be applicable >> to your system. > Given that, I think it might be a good idea to tackle some of this on > the wiki itself rather than needing a list for it. One thing that we are > working on at the moment is to try and get a commenting system working > on the wiki - so if drive-by users have comments / issues / feedback or > even a contribution of some sort in content - they can drop that in > there with a near zero barrier to entry. The Editorial Team on the wiki > can then evaluate that for inclusion in the main article or leave it as > a comment. This would certainly be a great start. As I see it, a mailsystem Wiki should have some specific divisions itself. One would be 'General' and then it would likely need 'Sendmail', 'Postfix', 'Qmail' areas. I'm just thinking out loud here. I've never done anything on a Wiki. I think a good initial layout however would be important. I'm trying to think about the gotchas I discover when trying to search for things. It seems like it always comes up two out of three and therefore isn't relevant. Sounds like I've just volunteered myself to participate in this Wiki! And yes, I'd be thrilled to! >> I think a fair number of the members of this list and the users of CentOS >> are using it in a server environment and require email. And basically, if >> you require email that is not exclusively internal to a network, spam is a >> huge battle which requires constant time... and I mean hours and hours and >> hours and hours of time. I just spent about 4 days on this again this past >> week. > I am about to take the plunge into this area after about 2 years and > completely rework my own anti-spam system. Hope to take loads of notes > and get them onto the wiki. Pros and Cons would be another great area. Revisiting what I had been doing this past week took me down a few trails to not being satisfied with the end result. Hours spent to a dead end. There are many products out there and each seems to have some gotcha. It would be nice to know how well they get along with CentOS, how well they perform on various levels of load as well as results for accuracy in delivery. > We have plenty of resources within the CentOS setup. I dont see hosting > something of this nature being too hard. However, i think it might be > important to work out what we want to host. IMHO, email is too niche an > area to have a dedicated list for it. Something like NetworkServices > might be a better target. I would be happy with anything! I always feel like I am off topic when posting email system questions to the CentOS list and I do think it is. NetworkServices could be a good place. I'm not sure it's the place for network hardware discussions... but I don't know. I haven't looked lately at how the mailing list are advertised. A good name for the list would certainly help it become more robust or having more users specific to that or those topics. Best, John Hinton

2 1

ACPI reboot-issue (CentOS 4)
by Simen Thoresen 29 Feb '08

29 Feb '08

Hi all, I'm trying to troubleshoot my way thru a ACPI-issue on several machines with the Asus P5N32-E SLI motherboard (S775, Nvidia 680i chipset) http://www.asus.com/products.aspx?l1=3&l2=11&l3=397&l4=0&model=1459&modelme… This is CentOS 4 x86_64, and appears on all tested kernels, including kernel-smp-2.6.9-67.0.4.EL My symptoms are that the machine won't reboot on the reboot command. 'poweroff' does turn the power off and halt halts the system (without turning the power off), but reboot effectively does a 'halt'. I can 'fix' this by giving the 'acpi=off' parameter to the kernel in grub, but this causes other problems (some of these machines have quad-core CPUs, and these require ACPI to initialize 3 of the cores. The dual-core CPU-machines work with acpi=off. With acpi=off, reboot works as it is supposed to. I think the root of this issue is the Asus BIOS - we also have several Asus M2N-SLI Deluxe (Athlon64, Nvidia 570 chipset) systems that started exhibiting the same symptom after a BIOS upgrade. On these acpi=off does not cause other problems, so this is no issue for us now. Any suggestions? I think I understand that turning ACPI off basically turns APM on, and that APM reboot works. Is there a way to do reboot with APM instead of ACPI? Yours, -S -- Simen Thoresen - Dolphin ICS Systems Administrator

3 6

Kernel-upgrade breaks forcedeth-driver (CentOS 4)
by Simen Thoresen 29 Feb '08

29 Feb '08

Hi all, Same system as my previous mail - Asus P5N32-E SLI motherboards, CentOS 4 x86_64. The kernel-supplied forcedeth driver works in kernel-smp-2.6.9-55.0.9.EL (both with and without acpi=off), but after upgrading to kernel-smp-2.6.9-67.0.4.EL, networking does not start. After trying dhcp, ifconfig reports 17 dropped TX packets (all other counters are empty). Ethtool reports the same settings for working and non-working kernel, and both report the link arbitrated to 1000Mbps. Setting a manual address does not do anything useful either. When booting with 55.0.9, networking works again. This has also been confirmed on another system - 2.6.9-55.0.12.EL works, and 2.6.9-67.EL fails (but this system is not available for troubleshooting right now). Also, the above system was attempted installed with CentOS 5 (.0 and later with 5.1), but this was aborted due to 'networking problems', so I am thinking that the problem possibly persists at least as late as the CentOS 5.1 install-kernel. Any thoughts or suggestions? Yours, -S -- Simen Thoresen - Dolphin ICS Systems Administrator

2 1

Re: [CentOS] Recommended software for mail greylist?
by Brent L. Bates 29 Feb '08

29 Feb '08

We've been using milter-greylist: http://hcpnet.free.fr/milter-greylist/ ftp://ftp.espci.fr/pub/milter-greylist/ for almost a year now and it works great. I looked over a number of other options and I believe this was the only one that was a compiled executable. I think all the other ones I found were scripts and I wanted something faster. -- Brent L. Bates (UNIX Sys. Admin.) M.S. 912 Phone:(757) 865-1400, x204 NASA Langley Research Center FAX:(757) 865-8177 Hampton, Virginia 23681-0001 Email: B.L.BATES(a)larc.nasa.gov http://www.vigyan.com/~blbates/

2 1

Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1x64
by Ross S. W. Walker 29 Feb '08

29 Feb '08

Well, take it over to CentOS-virt, attach the config of the guest and I'm sure someone will spot the problem. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Fri Feb 29 08:48:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1x64 Ross S. W. Walker wrote: > > Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. > > Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. > > -Ross > > > ----- Original Message ----- > From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> > To: CentOS mailing list <centos(a)centos.org> > Sent: Fri Feb 29 04:46:42 2008 > Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on > CentOS5.1 x64 > > Rudi Ahlers wrote: > > Hi all > > > > This is the first time I try and get Xen working, and want to install > > a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server. > > > > Trying to get the first one to install is rather trivial, and I keep > > on running into errors. At fist I wanted to install it fro the cdrom, > > so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could > > choose my language, but then got an error saying I don't have the > > right driver for the cdrom install. Odd. > > > > So, I copied the whole CD to my intranet server, to try a HTTP > > installation, which got much further, but fails as soon as it starts > > copying the files to the xvda partition. > > > > Here's what I've done: > > virt-install -p > > --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 > > --file=/vm/vm03.img --name=vm03 > > > > Probing for video card: Unable to probe > > No video hardware found, assuming headless > > Graphical installation not available... Starting text mode. > > Welcome to CentOS > > > > +------------------+ Package Installation +------------------+ > > | | > > | Name : libXt-1.0.2-3.1.fc6-i386 | > > | Size : 359k | > > | Summary: X.Org X11 libXt runtime library | > > | | > > | | > > | Status: | > > | | > > | 53% | > > | | > > | Packages Bytes Time | > > | Total : 349 564M 0:02:30 | > > | Completed: 123 200M 0:00:53 | > > | Remaining: 226 364M 0:01:37 | > > | | > > | 35% > > Guest installation complete... restarting guest. > > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > > creating domain: Boot loader didn't return any data!") > > exception was: virDomainCreate() failed POST operation failed: > > (xend.err "Error creating domain: Boot loader didn't return any data!") > > Domain installation may not have been > > successful. If it was, you can restart your domain > > by running 'virsh start vm03'; otherwise, pleasels | <F12> next > > screen > > restart your installation. > > [root@gimbli ~]# virsh start vm03 > > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > > creating domain: Boot loader didn't return any data!") > > error: Failed to start domain vm03 > > > > > > > > /var/log/messages got filled with the following messages: > > > > stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 > > tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > > > > > > > What am I doing wrong? > > > > as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU > on a 64bit dom0 is not supported and known to crash > > > _______________________________________________ > Ok, so what do I do if I want to have a 64bit Host XEN & 32guest's? I'd prefer to use CentOS for this purpose, if possible -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

error creating Centos 5.1 x32 dum_U instance on CentOS 5.1 x64
by Rudi Ahlers 29 Feb '08

29 Feb '08

Hi all This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server. Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd. So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition. Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03 Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS +------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35% Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03 /var/log/messages got filled with the following messages: stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability What am I doing wrong? -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg

3 8

CentOS-announce Digest, Vol 36, Issue 16
by centos-announce-request＠centos.org 29 Feb '08

29 Feb '08

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-2008:0155 Important CentOS 3 ia64 ghostscript - security update (Pasi Pirhonen) 2. CESA-2008:0155 Important CentOS 4 ia64 ghostscript - security update (Pasi Pirhonen) 3. CESA-2008:0131 Moderate CentOS 3 ia64 netpbm - security update (Pasi Pirhonen) 4. CESA-2008:0131 Moderate CentOS 4 ia64 netpbm - security update (Pasi Pirhonen) 5. CESA-2008:0146 Moderate CentOS 4 ia64 gd - security update (Pasi Pirhonen) 6. CESA-2008:0155 Important CentOS 3 s390(x) ghostscript - security update (Pasi Pirhonen) 7. CESA-2008:0155 Important CentOS 4 s390(x) ghostscript - security update (Pasi Pirhonen) 8. CESA-2008:0131 Moderate CentOS 3 s390(x) netpbm - security update (Pasi Pirhonen) 9. CESA-2008:0131 Moderate CentOS 4 s390(x) netpbm - security update (Pasi Pirhonen) 10. CESA-2008:0146 Moderate CentOS 4 s390(x) gd - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Thu, 28 Feb 2008 21:19:56 +0200 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0155 Important CentOS 3 ia64 ghostscript - security update To: centos-announce(a)centos.org Message-ID: <20080228191956.GU3950(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2009:0155 https://rhn.redhat.com/errata/RHSA-2008-0155.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/ghostscript-7.05-32.1.13.ia64.rpm updates/ia64/RPMS/ghostscript-devel-7.05-32.1.13.ia64.rpm updates/ia64/RPMS/hpijs-1.3-32.1.13.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

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