Discuss April 2007

discuss@lists.centos.org

368 participants
444 discussions

any help installing 4.4 for s390 (or s390x) on Z9-BC?
by Kelly F. Hickel 05 Apr '07

05 Apr '07

I should start off by saying that I know a lot more about linux than I do z/series hardware.... I've tried centos 3.3 and 4.4 for s390 and s390x, if it make any difference.... Trying to install 4.4 on an lpar on a z9-BC and having trouble figuring out how to get the OSA adapter working. I've been told that when I ftp-boot from the iso image, I should choose "eth" for adapter type, and enter "0xe38,0xe39,0xe3a" for the addresses. For the additional parameters, I've tried: add_parms,0x10,(0xe38,0xe3a),portname:CHIP00 portname:CHIP00 and just hitting enter (which looks like it's supposed to work with centos 4.4, but not 3.3) After subsequently entering the various IP params (addr, net addr, mask, fqdn, and so on), I typically get messages somewhat like the one below (copied verbatim from the s390x with 4.4 attempt): IPv6 over IPv4 tunneling driver divert: not allocating divert_blk for non-ethernet device sit0 qeth: loading qeth S/390 OSA-Express driver cat: /sys/devices/qeth/0xe38/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device Can anyone shed a little light on what I should be doing? I have a feeling that I'm just not seeing the 800-lb gorilla in the room..... Thanks, -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 kfh(a)mqsoftware.com

2 1

CentOS 4.5 ?
by Pierre Bourgin 05 Apr '07

05 Apr '07

Hello, I've checked the ML, but I don't find anything related to CentOS 4.5 (4U5) (missed it ?) Does the 4.5 will be out these days, or will it be released after the CentOS 5 ? Thanks, Pierre Bourgin

10 15

RE: [CentOS] Problems with SATA DVD+-RW drive [SOLVED]
by Michael St. Laurent 05 Apr '07

05 Apr '07

On the system I'm testing with the CD-Rom drive is IDE but the softlink at /dev/cdrom points to the scsi device and that's not working with the automounter for some reason. Each time I reinstall I have to delete the soft link and recreate it pointing at /dev/hda instead. > -----Original Message----- > From: centos-bounces(a)centos.org > [mailto:centos-bounces@centos.org] On Behalf Of Jay Leafey > Sent: Wednesday, April 04, 2007 4:02 PM > To: CentOS mailing list > Subject: Re: [CentOS] Problems with SATA DVD+-RW drive [SOLVED] > > Jim Perrin wrote: > > > > Nice bit of information here. Have you tested this with the beta for > > centos5 to see if it works out of the box there, or if a similar fix > > is required? > > > > > > Nope, not yet. I was planning on installing the beta this > weekend, I'll > have more information then. > > -- > Jay Leafey - Memphis, TN > jay.leafey(a)mindless.com > _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

CentOS folding@home team
by Scott Silva 05 Apr '07

05 Apr '07

I see the team has passed the 150 ranking. Now at 145 of 58272 total teams! -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

RE: [CentOS] Problems with SATA DVD+-RW drive [SOLVED]
by Michael St. Laurent 05 Apr '07

05 Apr '07

1 0

Problems with SATA DVD+-RW drive
by Jay Leafey 05 Apr '07

05 Apr '07

I just got a Dell Dimension e521 (AMD 64 x2, nVidia MCP51 chipset) and so far it has been fine. Today I tried to burn some CD-R and DVD-R disks and have been able to do nothing but make coasters. The drive is a TSST TS-H653a (Samsung OEM) and does have the current firmware. Playing back data, audio, and video disks work just fine, but recording is a different matter. The drive shows up as /dev/scd0 and all the symlinks for /dev/cdrom, /dev/cdwriter, /dev/dvd, and /dev/dvdwriter point to that device. Both cdrecord and growisofs complete without any errors, but when I try to remount the just-recorded disk I get an error: [jleafey@jaybird Downloads]$ mount /media/cdrecorder/ /dev/scd0: Invalid argument mount: block device /dev/scd0 is write-protected, mounting read-only /dev/scd0: Invalid argument mount: I could not determine the filesystem type, and none was specified I have also tried to explicitly mount it specifying the device and fs type: [jleafey@jaybird Downloads]$ sudo mount -t iso9660 /dev/scd0 \ /media/cdrecorder/ mount: block device /dev/scd0 is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/scd0, or too many mounted file systems The output of dmesg shows the message "cdrom: This disc doesn't have any tracks I recognize!" when this happens. Since I also get an error on the eject command UNLESS RUN AS ROOT (eject: unable to eject, last error: Inappropriate ioctl for device) I thought it might be a permission problem, but the device (/dev/scd0) is showing up as being "owned" by me, courtesy of Gnome no doubt. I get the bad burns whether I run as root or a regular user. At this point I don't know whether to think the problem is with cdrecord or the sata_nv driver. Anybody got any ideas on where to look next? Thanks! -- Jay Leafey - Memphis, TN jay.leafey(a)mindless.com

4 6

Cluster Services
by Scott McClanahan 04 Apr '07

04 Apr '07

Hello, we are running CentOS 4.3 and the latest cluster suite packages from the csgfs yum repository for this release and need to delete a cluster member. According to the documentation we need to restart all cluster related services on all remaining nodes in the cluster after the node has been removed. This is a four node cluster so removing one node obviously degrades the cluster to three nodes, but we can have the remaining cluster members recalculate the number of votes to remain quorate. It still surprises me that we have to bring down the entire cluster just because we are deleting a node. Any feedback as to why this might be?

3 3

CentOS-announce Digest, Vol 26, Issue 1
by centos-announce-request＠centos.org 04 Apr '07

04 Apr '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:0095 Critical CentOS 3 i386 krb5 - security update (Tru Huynh) 2. CESA-2007:0095 Critical CentOS 3 x86_64 krb5 - security update (Tru Huynh) 3. CESA-2007:0125 Important CentOS 3 i386 XFree86 - security update (Tru Huynh) 4. CESA-2007:0125 Important CentOS 3 x86_64 XFree86 - security update (Tru Huynh) 5. CESA-2007:0095 Critical CentOS 3 ia64 krb5 - security update (Pasi Pirhonen) 6. CESA-2007:0125 Important CentOS 3 ia64 XFree86 - security update (Pasi Pirhonen) 7. CESA-2007:0095 Critical CentOS 3 s390(x) krb5 - security update (Pasi Pirhonen) 8. CESA-2007:0095 Critical CentOS 4 ia64 krb5 - security update (Pasi Pirhonen) 9. CESA-2007:0152 Moderate CentOS 4 ia64 mysql - security update (Pasi Pirhonen) 10. CESA-2007:0126 Important CentOS 4 ia64 xorg - security update (Pasi Pirhonen) 11. CESA-2007:0095 Critical CentOS 4 s390(x) krb5 - security update (Pasi Pirhonen) 12. CESA-2007:0095-01: Critical CentOS 2 i386 krb5 security update (John Newbigin) 13. CESA-2007:0125-01: Important CentOS 2 i386 XFree86 security update (John Newbigin) 14. CESA-2007:0126 Important CentOS 4 s390(x) xorg - security update (Pasi Pirhonen) 15. CESA-2007:0125 Important CentOS 3 s390(x) XFree86 - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Tue, 3 Apr 2007 23:56:56 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2007:0095 Critical CentOS 3 i386 krb5 - security update To: centos-announce(a)centos.org Message-ID: <20070403215656.GA17636(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2007:0095 krb5 security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2007-0095.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/krb5-devel-1.2.7-61.i386.rpm updates/i386/RPMS/krb5-libs-1.2.7-61.i386.rpm updates/i386/RPMS/krb5-server-1.2.7-61.i386.rpm updates/i386/RPMS/krb5-workstation-1.2.7-61.i386.rpm source: updates/SRPMS/krb5-1.2.7-61.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update krb5\* Tru -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Partitioning with LVM
by Cen Tos 04 Apr '07

04 Apr '07

I've been reading up on recommended partitioning scheme and looking at Centos 5 beta's default scheme, it struck me that with LVM, it doesn't matter any more as long as we leave aside enough room for /boot, does it? Or am I still missing something here? Thanks!

6 7

Problem with gettid() on CentOS 5/gcc 4.1.1
by Alfred von Campe 04 Apr '07

04 Apr '07

I can't get the simple program below to compile on CentOS 5 beta. It compiles (and runs) just fine on CentOS 4.4, and I'm using gettid() as described in the man page. I wonder if this is a problem with RHEL 5 as well, but I don't have a system to test on. I also wonder if this is a gcc 4.1.1 issue or something missing in CentOS 5. The issue is that the _syscall0 macro is not defined anywhere. If I copy and paste the following definition for _syscall0 from a CentOS 4.4 system into the test program, it works just fine: #define _syscall0(type,name) \ type name(void) \ {\ return syscall(__NR_##name);\ } Has anyone else run into this problem? Alfred #include <stdio.h> #include <sys/types.h> #include <linux/unistd.h> #include <errno.h> _syscall0(pid_t, gettid) int main(int argc, char *argv[]) { printf("My tid is 0x%08x\n", gettid()); }

6 12

← Newer
1
...
38
39
40
41
42
43
44
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 April 2007