Discuss

discuss@lists.centos.org

34753 discussions

keeping a mirror of the updates repo
by Kai Schaetzl 10 Dec '07

10 Dec '07

I have a local mirror of CentOS5 base and updates. Now with 5 having become 5.1 and in case I just want to keep on updating (at the moment) is it enough that I update the mirror of updates or do I also need an update of the base repo? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

3 3

5.1 Upgrade Not Working?
by Scott Moseman 10 Dec '07

10 Dec '07

So both "yum upgrade" and "yum update" now are complete and there's no new packages. However, when I attempt to check my version, I'm still showing 5. # cat /etc/redhat-release CentOS release 5 (Final) I remember seeing 5.1 repositories being access for the upgrades. Is it possible my system did not upgrade? # uname -r 2.6.18-53.1.4.el5.centos.plus Thanks, Scott

5 6

How prevent loading of audio driver at boot?
by Steve Snyder 10 Dec '07

10 Dec '07

CentOS v5.1 insists on loading about a dozen audio-related drivers at boot time. Since this is a server machine, it will never run applications that require sound output. I tried setting "alias snd_cs46xx off" in modprobe.conf. Yet the system still loads that driver and the many, many other audio drivers that go with it. How can I disable the loading of audio drivers at boot time? Thanks.

3 2

Re: [CentOS] remote ssh to machine how display firefox
by Brent L. Bates 10 Dec '07

10 Dec '07

I've looked over the man page for `ssh' and `ssh_config' on several systems and I think people have it backwards. The pages I read indicate that `-X' is more secure than `-Y'. Under the `-X' part on several systems I have access to says: "For this reason, X11 forwarding is subjected to X11 SECURITY extension restrictions by default." The `-Y' says: "Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls." I would think being subjected to security controls would be more secure than not being subjected to them. -- 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/

1 0

CentOS-announce Digest, Vol 34, Issue 7
by centos-announce-request＠centos.org 10 Dec '07

10 Dec '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. CEEA-2007:1132 CentOS 5 i386 tzdata Update (Karanbir Singh) 2. CEEA-2007:1132 CentOS 5 x86_64 tzdata Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Sun, 9 Dec 2007 22:42:18 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEEA-2007:1132 CentOS 5 i386 tzdata Update To: centos-announce(a)centos.org Message-ID: <20071209224218.GA10701(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2007:1132 Upstream details at : http://rhn.redhat.com/errata/RHEA-2007-1132.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: f7ba3d210b6b54f3aace9688721b7857 tzdata-2007j-1.el5.noarch.rpm Source: 450e063e2298fa86366b8b43be382863 tzdata-2007j-1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Sun, 9 Dec 2007 22:42:18 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEEA-2007:1132 CentOS 5 x86_64 tzdata Update To: centos-announce(a)centos.org Message-ID: <20071209224218.GA10714(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2007:1132 Upstream details at : http://rhn.redhat.com/errata/RHEA-2007-1132.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 0852d14cb630164af4bfa8435bfb5fed tzdata-2007j-1.el5.noarch.rpm Source: 450e063e2298fa86366b8b43be382863 tzdata-2007j-1.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 34, Issue 7 **********************************************

1 0

centos 5.1 kernel crash on 2.6.23.9
by Jerry Geis 10 Dec '07

10 Dec '07

Hi all - looks like I have a kernel dieing on me. This is an AMD 6400+ with 4 GIG ram. I am using ext3 and software raid on 500G drives. (2) of them. I have an external 1T usb disk connected for backup. This is running 2.6.23.9 as I wanted to use kvm-amd. It has died on me twice. Funny thing is it happens when I am NOT using the machine. Any thoughts? Jerry -------------- Dec 8 22:23:57 devcentos5x64 kernel: Assertion failure in journal_dirty_data() at fs/jbd/transaction.c:983: "jh->b_transaction == journal->j_committing_transaction" Dec 8 22:23:57 devcentos5x64 kernel: ------------[ cut here ]------------ Dec 8 22:23:57 devcentos5x64 kernel: kernel BUG at fs/jbd/transaction.c:983! Dec 8 22:23:57 devcentos5x64 kernel: invalid opcode: 0000 [1] SMP Dec 8 22:23:57 devcentos5x64 kernel: CPU 1 Dec 8 22:23:57 devcentos5x64 kernel: Modules linked in: zttranscode nfsd exportfs lockd nfs_acl auth_rpcgss autofs4 hidp rfcomm l2cap bluetooth sunrpc wcusb wctdm wcfxo wcte11xp wct1xxp wcte12xp wct4xxp tor2 nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables cpufreq_ondemand dm_mirror dm_multipath dm_mod video output sbs battery ac ipv6 lp shpchp snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm nvidia(P) snd_timer wctdm24xxp snd zaptel soundcore sr_mod forcedeth sg parport_pc snd_page_alloc crc_ccitt serio_raw cdrom parport i2c_nforce2 usb_storage i2c_core button sata_nv libata sd_mod scsi_mod raid1 ext3 jbd ehci_hcd ohci_hcd uhci_hcd Dec 8 22:23:57 devcentos5x64 kernel: Pid: 5028, comm: rsync Tainted: P 2.6.23.9 #1 Dec 8 22:23:57 devcentos5x64 kernel: RIP: 0010:[<ffffffff88034a3b>] [<ffffffff88034a3b>] :jbd:journal_dirty_data+0xad/0x1ed Dec 8 22:23:57 devcentos5x64 kernel: RSP: 0018:ffff810095edd7e8 EFLAGS: 00010292 Dec 8 22:23:57 devcentos5x64 kernel: RAX: 0000000000000083 RBX: ffff81008e1f50c8 RCX: ffffffff81344c28 Dec 8 22:23:57 devcentos5x64 kernel: RDX: 0000000100000000 RSI: 0000000000000096 RDI: ffffffff81344c20 Dec 8 22:23:57 devcentos5x64 kernel: RBP: ffff81009b42fdf4 R08: ffffffff81344c28 R09: 00000002ffffffff Dec 8 22:23:57 devcentos5x64 kernel: R10: 0000000000000046 R11: ffffffff813b8000 R12: ffff8100c082b348 Dec 8 22:23:58 devcentos5x64 kernel: R13: ffff81010ce3cc00 R14: 0000000000000000 R15: 0000000000000000 Dec 8 22:23:58 devcentos5x64 kernel: FS: 00002ae6d4b2b560(0000) GS:ffff81011fa9a6c0(0000) knlGS:00000000f7f009a0 Dec 8 22:23:58 devcentos5x64 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Dec 8 22:23:58 devcentos5x64 kernel: CR2: 00002aea6b0d30a8 CR3: 00000000959f0000 CR4: 00000000000006e0 Dec 8 22:23:58 devcentos5x64 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 8 22:23:58 devcentos5x64 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Dec 8 22:23:58 devcentos5x64 kernel: Process rsync (pid: 5028, threadinfo ffff810095edc000, task ffff8100ccc78000) Dec 8 22:23:58 devcentos5x64 kernel: Stack: 0000000000001000 ffff8100c082b348 ffff81008e1f50c8 ffff81008e1f50c8 Dec 8 22:23:58 devcentos5x64 kernel: ffff81008e1f50c8 ffffffff8804ff8f 0000000000001000 0000000000001000 Dec 8 22:23:58 devcentos5x64 kernel: 0000000000001000 ffffffff8804f437 ffffffff8804ffb4 0000000000001000 Dec 8 22:23:58 devcentos5x64 kernel: Call Trace: Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804ff8f>] :ext3:ext3_journal_dirty_data+0xf/0x34 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804f437>] :ext3:walk_page_buffers+0x65/0x8b Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804ffb4>] :ext3:journal_dirty_data_fn+0x0/0xe Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff880521da>] :ext3:ext3_ordered_writepage+0x108/0x18c Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106bf9a>] __writepage+0xa/0x23 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106c4b8>] write_cache_pages+0x17b/0x2aa Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106bf90>] __writepage+0x0/0x23 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106c62a>] do_writepages+0x27/0x2d Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810a8749>] __writeback_single_inode+0x1ba/0x332 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8805b7ea>] :ext3:__ext3_journal_dirty_metadata+0x1e/0x46 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810a8c00>] sync_sb_inodes+0x1a3/0x261 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810a9030>] writeback_inodes+0x82/0xd8 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106c869>] balance_dirty_pages_ratelimited_nr+0x114/0x1f4 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff81068168>] generic_file_buffered_write+0x62d/0x751 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810685c8>] __generic_file_aio_write_nolock+0x33c/0x3a6 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff811ec26b>] sock_aio_read+0x10c/0x124 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff81068693>] generic_file_aio_write+0x61/0xc1 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804e1ae>] :ext3:ext3_file_write+0x16/0x94 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8108d950>] do_sync_write+0xc9/0x10c Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8104912d>] autoremove_wake_function+0x0/0x2e Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8108e118>] vfs_write+0xce/0x157 Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8108e676>] sys_write+0x45/0x6e Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8100bdfc>] tracesys+0xdc/0xe1 Dec 8 22:23:58 devcentos5x64 kernel: Dec 8 22:23:58 devcentos5x64 kernel: Dec 8 22:23:58 devcentos5x64 kernel: Code: 0f 0b eb fe 8b 45 0c 83 f8 01 76 09 83 f8 08 0f 85 eb 00 00 Dec 8 22:23:58 devcentos5x64 kernel: RIP [<ffffffff88034a3b>] :jbd:journal_dirty_data+0xad/0x1ed Dec 8 22:23:58 devcentos5x64 kernel: RSP <ffff810095edd7e8>

3 2

Trouble getting all my com-ports (ttyS*)
by Christopher Thorjussen 10 Dec '07

10 Dec '07

I just installed CentOS 5.1 on a Dell Vostro 200 (Intel G33) which has a Sunix PCI-Express (x1) 8-port RS-232 card installed. For me it looks like only 4 ports are recognized, but I'm not sure if it's even working with those 4. >From 'dmesg' I see this: ... Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 19 (level, low) -> IRQ 177 0000:04:00.0: ttyS0 at I/O 0xbf00 (irq = 177) is a 16550A 0000:04:00.0: ttyS1 at I/O 0xbf08 (irq = 177) is a 16550A 0000:04:00.0: ttyS2 at I/O 0xbe00 (irq = 177) is a 16550A 0000:04:00.0: ttyS3 at I/O 0xbe08 (irq = 177) is a 16550A Couldn't register serial port 0000:04:00.0: -28 ... [root@smse2e ~]# ls -la /dev/ttyS* crw-rw---- 1 root uucp 4, 64 Dec 6 2007 /dev/ttyS0 crw-rw---- 1 root uucp 4, 65 Dec 6 2007 /dev/ttyS1 crw-rw---- 1 root uucp 4, 66 Dec 6 2007 /dev/ttyS2 crw-rw---- 1 root uucp 4, 67 Dec 6 2007 /dev/ttyS3 Link to the RS_232 card: http://www.sunix.com.tw/it/en/Product_Detail.php?cate=2&class_a_id=35&si d=459 How can I get the other 4 enabled? /Christopher Thorjussen Please don't print this e-mail unless you really need to

2 2

Re: [CentOS] SOLVED - Can't build CentOS 5.1 kernel from source
by MHR 10 Dec '07

10 Dec '07

Problem solved (thanks to Jim and some careful thinking): I was building the 2.6.18-53.el5.src.rpm kernel (the stock RHEL release source) instead of the 2.6.18-53.1.4.el5.src.rpm (the CentOS update source). For the record, the problem was that the RHEL stock kernel source needs the rhel and olpc sections in the spec file that the CentOS kernel does not (if that makes no sense to you, read the wiki). Regards. mhr

1 0

using vnc server and login kills X login
by Jerry Geis 10 Dec '07

10 Dec '07

I changed my X driver from nvidia to xv. Now when I vncviewer into my machine it KILLS my current logged in user. When I try to login it accepts my login looks like its going to do it then kills my X windows screen. When I reconnect I'm back at a login again. This is for my account user geis. If I login as root it all works fine. I was told to change from nvidia to nv as some other interaction was killing my machine with the nvidia drivers. Under the old nvidia driver I did not have an issue. Any ideas? Jerry

2 1

CentOP 5.1 Problem with smbldap-passwd
by Sebastian Marten 10 Dec '07

10 Dec '07

Hi List, Yesterday i have upgraded from 5.0 to 5.1 and now i have a problem with smbldap-tools. I use smbldap-tools-0.9.4-1.el5.rf from rpmforge. Then i use smbldap-passwd <user> i get an error: smbldap-passwd test Changing UNIX and samba passwords for test New password: Retype new password: Use of uninitialized value in string at /usr/sbin/smbldap-passwd line 277, <STDIN> line 2. Failed to modify UNIX password: shadowMax: value #0 invalid per syntax at /usr/sbin/smbldap-passwd line 285, <STDIN> line 2. In 5.0 it works without errors. I hope you can help me Tanks, Sebastian Here is the part of the file ////////////////////////////////////////////////////////////////////// # Update 'userPassword' field if ( $update_unix_passwd ) { my $shadowLastChange=int(time()/86400); my $modify; if ($< != 0) { $modify = $ldap_master->modify ( "$dn", changes => [ replace => [userPassword => "$hash_password"], replace => [shadowLastChange => "$shadowLastChange"] ] ); } else { $modify = $ldap_master->modify ( "$dn", changes => [ replace => [userPassword => "$hash_password"], replace => [shadowLastChange => "$shadowLastChange"], replace => [shadowMax => "$config{defaultMaxPasswordAge}"] ] ); } $modify->code && warn "Failed to modify UNIX password: ", $modify->error ; } //////////////////////////////////////////////////////////////////////////////////////

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