Discuss

discuss@lists.centos.org

34753 discussions

Wanted: minimal install ks.cfg
by Daniel_Curry＠Dell.com 05 Jul '08

05 Jul '08

Greetings, all. I'm in need of a minimal ks.cfg file for the smallest possible install with yum. I've got the scripting for yum to install the apps I need, I just want to insure all the cruft is not on the system as well. Using the s-c-ks app, the smallest I have gotten is 600MB. This is for a server appliance vm that I need to deploy quickly and dynamically. Thanks Dnaiel

2 1

FW: [CentOS] Problem with nvidia-drv-x11 when upgrading to CentOS 5.2 (Akemi)
by John 05 Jul '08

05 Jul '08

-----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Wednesday, July 02, 2008 10:47 AM To: CentOS mailing list Subject: Re: [CentOS] Problem with nvidia-drv-x11 when upgrading to CentOS 5.2 On Wed, Jul 2, 2008 at 7:29 AM, John <jses27(a)gmail.com> wrote: > Yes, for DKMS users it should auto recompile on Kernel Upgrade. For > users of the Proprietary Nvidia Driver it will not. You will have to > manually recompile it. I have not done this for a while but you can automate the installation of the proprietary Nvidia driver by providing appropriate flags. The following command worked when I tested: sh ./NVIDIAxxxxx.run -a -q -N --ui=none Others posted this: sh ./NVIDIAxxxxx.run --no-network -s -K -n Once you find the way to get the installalation working without human intervention, you can put it in a place like /etc/rc.local : if [ ! -e /lib/modules/`uname -r`/kernel/drivers/video/nvidia.ko ]; then echo "Installing the proprietary NVIDIA driver." /full/path/to/ NVIDIAxxxxx.run --no-network -s -K -n fi This will compile and install the driver each time the kernel is updated. Akemi ---------------------------------------------------------------------------- ------------------- Hi Akemi, this looks like a good option to put into the nvidia how to. Any further ideas? _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

4 4

CentOS-announce Digest, Vol 41, Issue 2
by centos-announce-request＠centos.org 05 Jul '08

05 Jul '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:0547 Critical CentOS 4 ia64 seamonkey - security update (Pasi Pirhonen) 2. CESA-2008:0549 Critical CentOS 4 ia64 firefox - security update (Pasi Pirhonen) 3. CESA-2008:0547 Critical CentOS 4 s390(x) seamonkey - security update (Pasi Pirhonen) 4. CESA-2008:0549 Critical CentOS 4 s390(x) firefox - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Fri, 4 Jul 2008 18:05:25 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0547 Critical CentOS 4 ia64 seamonkey - security update To: centos-announce(a)centos.org Message-ID: <20080704150525.GA8211(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2008:0547 https://rhn.redhat.com/errata/RHSA-2008-0547.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/seamonkey-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-chat-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-devel-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-dom-inspector-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-js-debugger-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-mail-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-nspr-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-nspr-devel-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-nss-1.0.9-16.3.el4.centos.ia64.rpm updates/ia64/RPMS/seamonkey-nss-devel-1.0.9-16.3.el4.centos.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

update Centos 5 with DRBD
by Daniel Bruno 05 Jul '08

05 Jul '08

Hi, I have a server with Centos 5 + DRBD installed and is working fine, but when i run yum for udpate system show this error: Transaction Check Error: file /etc/drbd.conf conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /etc/rc.d/init.d/drbd conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /sbin/drbdadm conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /sbin/drbdmeta conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /sbin/drbdsetup conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /usr/share/man/man5/drbd.conf.5.gz conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /usr/share/man/man8/drbd.8.gz conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /usr/share/man/man8/drbdadm.8.gz conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /usr/share/man/man8/drbddisk.8.gz conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /usr/share/man/man8/drbdmeta.8.gz conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos file /usr/share/man/man8/drbdsetup.8.gz conflicts between attempted installs of drbd-8.0.12-1.el5.centos and drbd82-8.2.6-1.el5.centos Error Summary ------------- Anybody have any idea? Thanks, -- Daniel Bruno http://danielbruno.argo.com.br danielbrunos(a)gmail.com

2 1

cvs command failure on 5.2
by MHR 04 Jul '08

04 Jul '08

Another little problem I am now having on CentOS 5.2 that I was not seeing on FC8: [mrichter@sushi lane]$ cvs update poll: protocol failure in circuit setup cvs [update aborted]: end of file from server (consult above messages if any) I could understand if there was something that had changed from FC1 to CentOS 5.2, but if it works in FC8, why not here? Here's what's in the CVS directory and files: [mrichter@sushi lane]$ ls CVS Entries Repository Root Tag [mrichter@sushi lane]$ for i in CVS/*; do echo $i; cat $i; echo ""; done CVS/Entries /Makefile.template/1.2/Thu Oct 6 19:06:14 2005//TDEV_608 /makefile.include/2.6/Wed Dec 6 21:58:01 2006//TDEV_608 D/bin//// D/cron_jobs//// D/devices//// D/doc//// D/drivers//// D/include//// D/lanecon//// D/lib_src//// D/main//// D/parser//// D/sim//// D/tcautil//// D/viewcon//// D/webmon//// /Makefile/1.2/Fri Jul 4 23:22:10 2008//TDEV_608 CVS/Repository linuxlane/lane CVS/Root khan:/home/stage/CVS CVS/Tag TDEV_608 (Khan is our main file server, and it's running a Linux that's even older than FC1 - not sure what: [mrichter@khan mrichter]$ uname -a Linux khan 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux Our execution/test server is viper, with FC1: [mrichter@viper lane]$ uname -a Linux viper 2.4.23HZ_opt #12 Fri Apr 1 13:57:09 PST 2005 i686 i686 i386 GNU/Linux What command tells me which distro I'm on? I forget....) I'm a little rusty on my cvs mastery (?) but most of this looks ok to me, and, as I mentioned, it works in FC8, but not CentOS 5.2. Any ideas/suggestions/etc? Thanks. mhr

2 1

OT: General Help in chroot build environment
by Joseph L. Casale 04 Jul '08

04 Jul '08

I am trying to compile a module for a Realtek 8168 for thinstation. I have pulled the developer tarball and executed the script to enter its build environment. I also have the source for the module I want to compile, but when I execute #make clean modules it errors out. Reading the errors, I can see it tried to look for the kernel source of the systems actual running kernel. From within the chroot build environment, I run a #uname -r and see it displays exactly that, and not the build environments expected 2.6.21.1 that it has in the /source/kernel-2.6.21.1/linux-2.6.21.1 dir. I have ran an #export KERNELSRC=/source/kernel-2.6.21.1/linux-2.6.21.1 Any ideas on what's left to convince make it is running with the expected kernel and not my actual one? Thanks! jlc

2 2

Migrating windows to linux proxy server
by lingu 04 Jul '08

04 Jul '08

HI, I am migraing from windows to linux squid proxy server.I configured squid its working fine.But i want to integrate with windows 2003 Active Directory Service for user authentication.Can any one help me in configuring the same. its very urgent for me. Thanks in advance lingu

2 1

How do I check the real size of a filesystem?
by Kevin Thorpe 04 Jul '08

04 Jul '08

I'm having a spot of bother with a large (900GB) partition. fdisk claims it's 900GB. I made an ext3 fs on it and df says it's only 94GB. Which is correct? Or did I do something wrong?

6 10

Status of tracker for 64bit?
by Kwan Lowe 04 Jul '08

04 Jul '08

Good morning to you all: I've been trying for a few hours to connect to the tracker for the 5.2 x64 DVD. It has been giving a "connection refused" error. A few days ago the 5.2 i386 downloaded succesfully. Is the tracker down?? Or is something odd happening on my side?? thanks, Kwan

3 2

Anaconda ignores "cmdline" directive
by Amos Shapira 04 Jul '08

04 Jul '08

Hello, Our environment: CentOS 5.2 (updated over time with "yum update", current "yum update" lists about 7 packages out of date), x86_64. Running Xen, building Xen DomU's with kickstart. We are trying to debug the %post part of the kickstart process for DomU and are hitting difficulties in accessing the output. For a start, the "cmdline" directive in the kickstart seems to be ignored and it stays in "text" (ncurses) mode. Here is the kickstart file we use: install url --url http://a.b.c.d/centos/5.2/os/x86_64 logging --level=debug lang en_US.UTF-8 network --device eth0 --bootproto static --ip=a.b.c.e --netmask=255.255.255.0 --gateway=a.b.c.f --nameserver=a.b.c.g --hostname domu-hostname rootpw --iscrypted $1$password authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Australia/Sydney bootloader --location=mbr --driveorder=xvda --append="console=xvc0" poweroff cmdline # Partitioning zerombr clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup xxx --pesize=32768 pv.2 logvol / --fstype ext3 --name=root --vgname=xxx --size=1024 --grow logvol swap --fstype swap --name=swap --vgname=xxx --size=256 --grow --maxsize=512 %packages --nobase wget %post set -x echo hello world Can anyone point what are we missing? Googl'ing around just keeps coming up with pages saying that this should work (e.g. "Running anaconda in real text-mode" and "Logging %pre and %post" in http://wiki.centos.org/TipsAndTricks/KickStart) but the problem so far still remains that Anaconda uses ncurses, not "cmdline". Thanks, --Amos

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